| 1 |
On 04/14/2011 01:21 PM, Carlos Sura wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> On 13 April 2011 01:49, Daniel Pielmeier <billie@g.o <mailto:billie@g.o>> wrote: |
| 5 |
> |
| 6 |
> 2011/4/12 Carlos Sura <carlos.sura1@××××××××××.com <mailto:carlos.sura1@××××××××××.com>>: |
| 7 |
> > |
| 8 |
> > It might be GLIB? (I've reciently updated) |
| 9 |
> |
| 10 |
> Do you also use the ~amd64 version of glib? What about downgradeing it |
| 11 |
> to the version you had before, should be worth a try and quicker than |
| 12 |
> rebuiding libreoffice on and on. |
| 13 |
> |
| 14 |
> -- |
| 15 |
> Daniel Pielmeier |
| 16 |
> |
| 17 |
> |
| 18 |
> Also, I've tried strace, and this is the output: |
| 19 |
> http://tinypaste.com/e025e0 |
| 20 |
|
| 21 |
/usr/bin/libreoffice is just a shell script, not a binary. To capture the |
| 22 |
full output you need to use the -f flag for strace (follow child processes). |
| 23 |
|
| 24 |
I'm on ~amd64 and libreoffice works okay with glib-2.28.6 and dbus-glib-0.92. |
| 25 |
|
| 26 |
You can try re-emerging dbus-glib if you haven't already done it. |
Archives