GNOME Bugzilla – Bug 555959
eog locks up from time to time.
Last modified: 2008-10-14 05:23:09 UTC
Starting eog from either nautilus or command line can lead up to a X "lock". Killing eog releases the lock. It affets the whole desktop and one cannot click anymore so you have to ssh from another host to kill it or wait for some timeout (very long for average user). Here is the backtrace I got by running it from the console. It happens with any picture and it is a race condition for sure as it doesn't happen all the time and the trace seems to indicate it's in a thread. $ gdb --args eog file:///home/eva/Images/Photos/Cr%C3%AAperie%20%C3%89tienne/IMG_5855.JPG GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu"... (gdb) run Starting program: /usr/bin/eog file:///home/eva/Images/Photos/Cr%C3%AAperie%20%C3%89tienne/IMG_5855.JPG [Thread debugging using libthread_db enabled] [New Thread 0x2b06d8d30a70 (LWP 9644)] [New Thread 0x40800950 (LWP 9649)] [New Thread 0x40841950 (LWP 9650)] ^C Program received signal SIGINT, Interrupt.
+ Trace 208060
Thread 47308407507568 (LWP 9644)
Created attachment 120412 [details] gedit-2.24-strace.log strace of another run.
Could you possibly attach a full thread backtrace (thread apply all bt)? Currently I fail to see how the lock in eog_list_store_add_thumbnail_job could lock the whole X server so maybe it's something in the other threads.
If the X server locks, it could be something related to accessibility. Do you have accessibility enabled by default? There are several reports about eog locking due to at-spi (see bug #547373 for example).
indeed, I have accessibility features enabled to get the long right == right click feature from mousetweaks. Do you still want a trace from all threads or something else that might be more interesting ?
Stacktrace of all thread is still important. Also, please try whether the locks happen when accessibility is disabled.
Here is a new backtrace. I'm not sure this is exactly the same conditions as yesterday as it's kind of hard to reproduce and this time I wasn't completely locked out of other programs. Starting program: /usr/bin/eog file:///home/eva/Images/Photos/Cr%C3%AAperie%20%C3%89tienne/IMG_5855.JPG [Thread debugging using libthread_db enabled] [New Thread 0x2b909d2d9040 (LWP 9632)] [New Thread 0x40800950 (LWP 9635)] [New Thread 0x40841950 (LWP 9636)] Program received signal SIGINT, Interrupt.
+ Trace 208120
Thread 2 (Thread 0x40800950 (LWP 9635))
Common denominator between this and bug #547373 seems to be at-spi and libcanberra.. Matthias, Li: do you think this could be the same issue?
Yes, comment #6 and bug #547373 are probably the same bug.
Thanks Li. Marking as duplicate. Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 547373 ***