Apache OpenOffice (AOO) Bugzilla – Issue 50162
soffice crash on startup - Xlib
Last modified: 2008-10-29 13:42:42 UTC
haakon@rincewind:~> soffice Xlib: unexpected async reply (sequence 0x4fe)! Fatal exception: Signal 11 Stack: /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f53d] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f667] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f75b] [0xffffe420] /opt/openoffice.org1.9.104/program/libtl680li.so[0x408013cd] /opt/openoffice.org1.9.104/program/libtl680li.so[0x40804717] /opt/openoffice.org1.9.104/program/libtl680li.so(_ZN6ResMgr10ReadStringEv+0x1c) [ 0x40804766] /opt/openoffice.org1.9.104/program/libvcl680li.so[0x401e0768] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN7MessBoxC2EP6WindowRK5ResId +0x157)[0x401e0a45] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN8QueryBoxC1EP6WindowRK5ResI d+0x30)[0x401e1ee8] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44dfdeb2] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44dfe93d] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44dfe968] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN7Control32ImplCallEventList enersAndHandlerEmRK4LinkPv+0x63)[0x40232055] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN6Button5ClickEv+0x25) [0x402 273f3] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN12CancelButton5ClickEv+0x93 )[0x4022c1fd] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN10PushButton8TrackingERK13T rackingEvent+0x188)[0x4022b058] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN6Window11EndTrackingEt+0x11 7)[0x402200f9] /opt/openoffice.org1.9.104/program/libvcl680li.so[0x40225001] /opt/openoffice.org1.9.104/program/libvcl680li.so[0x40225425] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN11X11SalFrame16Hand leMouseEventEP7_XEvent+0x475)[0x419668fd] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN11X11SalFrame8Dispa tchEP7_XEvent+0x16c)[0x41969d3e] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN13SalX11Display8Dis patchEP7_XEvent+0x209)[0x4198e9a1] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN13SalX11Display5Yie ldEh+0x42)[0x4198eace] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so[0x41989899] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN7SalXLib5YieldEh+0x 353)[0x41988b9b] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN14X11SalInstance5Yi eldEh+0x27)[0x419904bf] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN11Application5YieldEv+0x52) [0x4009936e] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44dff81f] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44dfb477] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44f76adf] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44f76bd6] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop19impl_callRecoveryUIEhhh +0x522)[0x806308c] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop7Desktop11OpenClientsEv+0 x4d4)[0x8064b22] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop7Desktop16OpenClients_Imp lEPv+0x3c)[0x806585e] /opt/openoffice.org1.9.104/program/libvcl680li.so[0x40225cf9] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN10SalDisplay21Dispa tchInternalEventEv+0xaa)[0x4198ea7a] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN13SalX11Display5Yie ldEh+0x1d)[0x4198eaa9] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so[0x41989899] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN7SalXLib5YieldEh+0x 1c7)[0x41988a0f] /opt/openoffice.org1.9.104/program/libvclplug_gen680li.so(_ZN14X11SalInstance5Yi eldEh+0x27)[0x419904bf] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN11Application5YieldEv+0x52) [0x4009936e] /opt/openoffice.org1.9.104/program/libvcl680li.so(_ZN11Application7ExecuteEv+0x2 d)[0x400993b1] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop7Desktop4MainEv+0x2294) [0 x806913c] /opt/openoffice.org1.9.104/program/libvcl680li.so(_Z6SVMainv+0x4d)[0x4009e2e5] /etc/openoffice.org-1.9/program/soffice.bin(sal_main+0x47)[0x805f0fb] /lib/tls/libc.so.6(__libc_start_main+0xe0)[0x41164b10] /etc/openoffice.org-1.9/program/soffice.bin(_ZN6Window11RequestHelpERK9HelpEvent +0x3d)[0x805efe1] /usr/bin/soffice: line 245: 11061 Avbrutt (SIGABRT) "$sd_prog/$sd_binary" "$@" haakon@rincewind:~> soffice terminate called after throwing an instance of 'com::sun::star::uno::RuntimeException' Fatal exception: Signal 6 Stack: /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f53d] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f667] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f75b] [0xffffe420] /lib/tls/libc.so.6(abort+0x129)[0x41178529] /opt/openoffice.org1.9.104/program/libstdc++.so.6 (_ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x101)[0x410f7ad1] /opt/openoffice.org1.9.104/program/libstdc++.so.6[0x410f5505] /opt/openoffice.org1.9.104/program/libstdc++.so.6[0x410f5542] /opt/openoffice.org1.9.104/program/libstdc++.so.6[0x410f56d2] /opt/openoffice.org1.9.104/program/libfwk680li.so[0x443e366f] /opt/openoffice.org1.9.104/program/libfwk680li.so[0x443f2a15] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44df6b6c] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44dfdc4c] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44f65fce] /opt/openoffice.org1.9.104/program/libsvx680li.so[0x44f66ba6] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop19impl_callRecoveryUIEhhh+0x522) [0x806308c] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop7Desktop9SaveTasksEl+0xe) [0x80632b8] /etc/openoffice.org-1.9/program/soffice.bin(_ZN7desktop7Desktop9ExceptionEt+0x9b) [0x8063359] /opt/openoffice.org1.9.104/program/libvcl680li.so[0x4009db7e] /opt/openoffice.org1.9.104/program/libvos3gcc3.so(_ZN3vos28_cpp_OSignalHandler_FunctionEPvP13oslSignalInfo+0xf) [0x409a6aab] /opt/openoffice.org1.9.104/program/libvos3gcc3.so(_Z24_OSignalHandler_FunctionPvP13oslSignalInfo+0x1a) [0x409a6ac8] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f5af] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a4f741] [0xffffe420] /usr/lib/libcups.so.2[0x46177f66] /usr/lib/libcups.so.2(cupsGetDests2+0x5b)[0x46178b2b] /usr/lib/libcups.so.2(cupsGetDests+0x4e)[0x46178e5e] /opt/openoffice.org1.9.104/program/libpsp680li.so(_ZN3psp11CUPSManager8runDestsEv+0x2b) [0x41a0db93] /opt/openoffice.org1.9.104/program/libpsp680li.so(_ZN3psp11CUPSManager13runDestThreadEPv+0x17) [0x41a0dbeb] /opt/openoffice.org1.9.104/program/libuno_sal.so.3[0x40a482a3] /lib/tls/libpthread.so.0[0x40f6d7f3] /lib/tls/libc.so.6(__clone+0x5a)[0x4120762a] /usr/bin/soffice: line 245: 11091 Avbrutt (SIGABRT) "$sd_prog/$sd_binary" "$@"
There's no application on stack. Framework issue.
I'm using SuSE 9.2 with the latest updates. Crashes like these are frequent, and auto-document recovery seem to make things worse. In earlier releases I've been able to cancel auto-document recovery to open a new OOo document, close it, close OOo, then restart. No such luck now. I've tried with different window managers - I usually use KDE 3.4, tried FVWM2, with the same result.
Hi haakonme, thanks for using and supporting OpenOffice.org... I tried this here on FC3 (KDE3.3.x) using m104 and didn't get that problem. I use OOom104 at home on (K)Ubuntu (KDE3.4) and don't get your problem... :(
I've upgraded to OpenOffice.org 1.9.109, but the problem persists. I beginning to think there must be something wrong with Xlib in SuSE. haakon@rincewind:~> soffice Xlib: unexpected async reply (sequence 0xa18)! The OOo windows opens without a document, and is inaccessible. I cannot click anything.
Not reproducible on Suse Linux 9.2 and FedoraCore3 -> closed !
.
Look, this is reproducible on my machine, a Dell Precision M50. Now, what do we do about that? a) close it because it works on your computer? That is not the issue. If it was happening on your computer, you couldn't say WORKSFORME, could you? That's the point, it doesn't work FOR ME. b) or, you could guide me in searching for a possible cause on MY computer, using strace, logs or whatever. I suggest we try again, using method b) this time. :-) Cheers, Haakon
TM->MCI: Please have a look again. Not reproducible with m114 build on several machines. Doesn´t seem to be a OOo problem at all. If it stays unreproducible please feel free to close issue as "worksforme" again.
Another user emailed me directly, having trouble adding a comment here, telling me he had the same problem on Debian using X.org 6.8.2 compiled from source. He wondered if OOo is compiled against XFree86, and if this might be the cause of the Xlib error message. I'm downloading 680m113 now, and will try that. Cheers, Haakon
Hi haakonme, if this was the reason everybody using i.e. XOrg would get this problem... or?...? Since I use Ubuntu (which uses XOrg) and Fedora (which uses XOrg, too) and I don't get that problem .... mci -> pl hi pl, please have a look at this issue, maybe you know something about this problem??
added mci to CC
*** Issue 48465 has been marked as a duplicate of this issue. ***
The stack of the second thread shows a signal handler being called (as would usually done by a SEGV or BUS signal) from within CUPS; this might point to a CUPS related problem. Please try to set the environment variable SAL_DISABLE_CUPS to "true" in a shell and then start soffice from that shell. If that fixes the problem, then either your CUPS system is somehow broken or there is still a bug in OOo's CUPS support which for some reason does only get triggered on your system.
When starting OpenOffice, CUPS sometimes goes wild, issuing the following error messages in /var/log/cups/error_log E [23/Aug/2005:11:26:28 +0200] AddCert: Unable to create certificate file /etc/cups/certs/0 - Too many open files d [23/Aug/2005:11:26:28 +0200] select_timeout: 1 seconds to update root certificate eating CPU time no end. Restarting CUPS fixes this certificate issue.
The latter is certainly a bug in CUPS itself. The difference between OOo and other applications is that OOo queries the system's printers during startup whereas other applications do that when they actually start to print (that is when you open the print dialog). This makes that CUPS problem more visible in OOo, but this really is a problem inside the CUPS server.
Wait a minute - doing this on start up or when opening the print dialog is not the issue. The important thing is how OOo does it, because it is the only application I've got that makes CUPS behave this way. I agree, CUPS shouldn't behave like this, but what is OOo feeding it?
OOo is "feeding" it nothing at all. It's just querying the list of available printers as well as the PPD file for the current default printer, if you switched on "use printer metrics" in Tools->Options->Writer->Compatibility.
I have the same problem with OO2.0 on MandrivaLE2005. It did not appear first after installation. If I remember well, it manifested itself after a crash provoked by trying to open an MS-Works file. Since then the crash happens consistently the first time I start OO after the PC has been restarted. I then kill all soffice processes (usually two of these) and after that I have no problems anymore. While searching for info, I noticed that such behavior has already been reported in issue 3750, but not a real solution??
This Issue requires more information ('needmoreinfo'), but has not been updated within the last year. Please re-test with one of the latest versions of OOo - the problem(s) may have already been addressed. Either use the recent stable version: http://download.openoffice.org/index.html or consider trying the new OOo 3 BETA (still in testing): http://download.openoffice.org/3.0beta/ Please report back the outcome so this Issue may be closed or progressed as necessary - otherwise it may be Resolved as Invalid in the future. You may also wish to search for (and note) any duplicates of this Issue that may have advanced further : http://www.openoffice.org/issues/query.cgi Many thanks, Andrew Cleaning-up and Closing old Issues as part of: ~ The Grand Bug Squash, pre v3 ~
Hello haakonme, *, could you please answer the questions here in this issue, please? Have you tried a newer version of OOo like 2.4.1 or' pre 3.0 builds? Does your problem occur there as well? And - if you still are using your old computer - could you try to install and run memtest to exclude any hardware issues? TIA Thomas.
No reaction for some time. Invalidating
Closing