[Solved] Libreoffice Calc doesn't open ODS files

jorpheus · 2013-04-02 14:23:07

Since the upgrade to 4, localc doesn't open .ods files. Everything else works fine, including opening .xls files.
It starts, splash screen comes up, loading and then exit. No error messages, including when run from
terminal (tried both "localc" and "libreoffice --localc"). When I start it without trying to open a file, it comes up
without problem. When I try to open a file then, it fails once or twice (I click Open, dialog closes, nothing happens),
but eventually succeeds. I thought it might be corrupt, but I've tried all other .ods files I have, and none of them
open, and I also tried creating a new file and opening that, and the result was the same.

It's a difficult problem to google, but I've found one identical case on the Ubuntu forums, and it remains unsolved.
I did a -Syu just a few minutes ago, so everything is up to date, and I've also tried reinstalling just libreoffice-calc, to no avail.
Reading through a few threads here, I noticed some people recommended running a backtrace, so here's the output of
"localc --backtrace myfile.ods":

warning: Currently logging to gdbtrace.log.  Turn the logging off and on to make the new setting effective.
warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3400.3-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[New Thread 0xb362fb40 (LWP 1122)]
[New Thread 0xb1ee6b40 (LWP 1126)]
[New Thread 0xb14ffb40 (LWP 1127)]
[New Thread 0xafcd8b40 (LWP 1128)]
[Thread 0xb1ee6b40 (LWP 1126) exited]
[New Thread 0xb1ee6b40 (LWP 1131)]
[New Thread 0xad5a4b40 (LWP 1138)]
[Thread 0xad5a4b40 (LWP 1138) exited]
[Thread 0xafcd8b40 (LWP 1128) exited]
[Thread 0xb1ee6b40 (LWP 1131) exited]
[New Thread 0xb1ee6b40 (LWP 1139)]
[Thread 0xb1ee6b40 (LWP 1139) exited]
[New Thread 0xb1ee6b40 (LWP 1140)]
[Thread 0xb1ee6b40 (LWP 1140) exited]
[New Thread 0xb1ee6b40 (LWP 1141)]
[Thread 0xb1ee6b40 (LWP 1141) exited]
[Thread 0xb14ffb40 (LWP 1127) exited]
[Thread 0xb362fb40 (LWP 1122) exited]
[Inferior 1 (process 1118) exited normally]
/usr/lib/libreoffice/program/gdbtrace:9: Error in sourced command file:
No stack.

Ideas?

Last edited by jorpheus (2013-04-03 10:36:19)

6ng4n · 2013-04-02 21:00:17

It looks like a python module is missing. Are the packages up-to-date? If there is an AUR module, did you recompile it? In the past I experienced such errors caused by nonsequential update of python modules.

Last edited by 6ng4n (2013-04-02 21:01:05)

Lone_Wolf · 2013-04-02 21:00:54

looks like you haven't got gdb installed, best install it and then rerun the backtrace.

Lekensteyn · 2013-04-02 21:38:30

The python warning about backtrace is harmless.

jorpheus · 2013-04-02 22:58:12

6ng4n wrote:

It looks like a python module is missing. Are the packages up-to-date? If there is an AUR module, did you recompile it? In the past I experienced such errors caused by nonsequential update of python modules.

Non-AUR packages are all up to date, as stated. I don't really understand which modules do you mean, but I went and checked all the AUR Python modules I had, and one was in need of an update. No improvement. That .py file mentioned in the backtrace belongs to glib2.

Lone_Wolf wrote:

looks like you haven't got gdb installed, best install it and then rerun the backtrace.

I'm not really sure if you're joking or not. GDB is installed and up to date. How do you suppose that pile of text up there was generated? Running that command on a system without GDB produces

Error: Can't find the tool "gdb", --backtrace option will be ignored.

jorpheus · 2013-04-03 10:38:49

I've found the culprit: libreoffice-extension-*. I suppose it was nlpsolver, but I removed the whole thing. Yay. Apologies for wasting space with something as idiotic as this.

Last edited by jorpheus (2013-04-03 10:39:06)

Lone_Wolf · 2013-04-03 20:12:22

jorpheus wrote:

Lone_Wolf wrote:
looks like you haven't got gdb installed, best install it and then rerun the backtrace.
I'm not really sure if you're joking or not. GDB is installed and up to date. How do you suppose that pile of text up there was generated? Running that command on a system without GDB produces
Error: Can't find the tool "gdb", --backtrace option will be ignored.

    import gdb.backtrace
ImportError: No module named backtrace

These lines made me wonder if gdb was installed, as running the same command on my system didn't give any error messages.
Next time i'll try to be more explicit.

Arch Linux

#1 2013-04-02 14:23:07

[Solved] Libreoffice Calc doesn't open ODS files

#2 2013-04-02 21:00:17

Re: [Solved] Libreoffice Calc doesn't open ODS files

#3 2013-04-02 21:00:54

Re: [Solved] Libreoffice Calc doesn't open ODS files

#4 2013-04-02 21:38:30

Re: [Solved] Libreoffice Calc doesn't open ODS files

#5 2013-04-02 22:58:12

Re: [Solved] Libreoffice Calc doesn't open ODS files

#6 2013-04-03 10:38:49

Re: [Solved] Libreoffice Calc doesn't open ODS files

#7 2013-04-03 20:12:22

Re: [Solved] Libreoffice Calc doesn't open ODS files

Board footer