Red Hat Bugzilla – Bug 855541
[abrt] libreoffice-core-18.104.22.168-2.fc17: multi-threaded XIOError segv
Last modified: 2012-12-20 11:11:32 EST
Version-Release number of selected component:
libreport version: 2.0.13
cmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=6
:Thread no. 1 (6 frames)
: #1 exit at exit.c
: #2 gdk_x_io_error at gdkmain-x11.c
: #3 _XIOError at XlibInt.c
: #5 XGetSelectionOwner at GetSOwner.c
: #6 x11::SelectionManager::run at /usr/src/debug/libreoffice-22.214.171.124/vcl/unx/generic/dtrans/X11_selection.cxx
: #7 osl_thread_start_Impl at thread.c
Created attachment 611045 [details]
Created attachment 611046 [details]
Created attachment 611047 [details]
Created attachment 611048 [details]
Created attachment 611049 [details]
Created attachment 611050 [details]
Created attachment 611051 [details]
Created attachment 611052 [details]
Created attachment 611053 [details]
There was an XIOError which typically is "the X server went away" while the app was running and we can do nothing about that. There appears then to be a segv during the unexpected shutdown
hmm, two threads, both get the XIOError, both call the default gdk xioerror handler which isn't prepared for that. Safest solution might be to install our own xioerror handler which discards xioerrors from the non-main thread.
*** Bug 820074 has been marked as a duplicate of this bug. ***
tweaked the XIOError handler to hopefully avoid this double exit problem. Will be in >= libreoffice-126.96.36.199-5.fc17
libreoffice-188.8.131.52-5.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libreoffice-184.108.40.206-5.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libreoffice-220.127.116.11-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.