Mailinglist Archive: opensuse-factory (883 mails)

< Previous Next >
Re: [opensuse-factory] Libreoffice not functioning after last zypper up on M4
Op 09-05-12 18:40, phanisvara das schreef:
On Wed, 09 May 2012 21:50:52 +0530, Patrick Shanahan <paka@xxxxxxxxxxxx> wrote:

* Jogchum Reitsma <j.reitsma@xxxxxxxxx> [05-09-12 11:37]:
Hi,

Since the last update through zypper up, libreoffice doesn't start: when
tried from the commandline, a split second the LO-splash screen is shown,
then I'm back on the command line without further messages.

System log says

May 9 17:25:23 linux-0deu kernel: [72040.870485] soffice.bin[15154] general
protection ip:7f844345abba sp:7fff15223450 error:0 in
libX11.so.6.3.0[7f8443429000+13a000]
May 9 17:25:34 linux-0deu kernel: [72052.073054] soffice.bin[15177] general
protection ip:7fa033325bba sp:7fff4806c250 error:0 in
libX11.so.6.3.0[7fa0332f4000+13a000]

Should I file a bug against LO, or against X? Or anything else I should do?

Also running m4 x86_64 and have no problem as you indicate. Further
investigation is probably warrented but I don't know what .... :^(

sorry,

to investigate this further, you'll have to tell what version of openSUSE you're using, which kernel, and where from you installed libreoffice.

apart from that, i don't understand why this is is a discussion for opensuse-factory instead of the opensuse mailing list.

FWIW, i'm running libreoffice from http://download.opensuse.org/repositories/LibreOffice:/Unstable/openSUSE_12.1/ on oS 12.1 (standard kernel, 3.1.10-1.9-desktop) and don't notice any problems with LO.

I already mentioned that the opensuse version is M4 (12.2 of course, otherwise I wouldn't post this on the factory list). Is that what you mean? And, of course, it's from the factory repo's for LO, kernel is the latest from factory, 3.3.0-2-desktop. All this seems pretty obvious to me if I report I've done zypper up on M4, or am I wrong here?
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups