GNOME Bugzilla – Bug 489665
crash in Image Viewer: I just changed to an oth...
Last modified: 2007-10-27 12:08:45 UTC
Version: 2.18.2 What were you doing when the application crashed? I just changed to an other picture and I stop the fullscreen preview (back from F11). Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 396587008 vsize: 396587008 resident: 141299712 share: 12918784 rss: 141299712 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193200256 rtime: 4926 utime: 4761 stime: 165 cutime:3 cstime: 15 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2af3ad692f00 (LWP 6289)] [New Thread 0x41001950 (LWP 6293)] [New Thread 0x40800950 (LWP 6290)] (no debugging symbols found) 0x00002af3a7c84c7f in waitpid () from /lib/libpthread.so.0
+ Trace 172427
Thread 1 (Thread 0x2af3ad692f00 (LWP 6289))
----------- .xsession-errors (500 sec old) --------------------- (pidgin:3994): GStreamer-CRITICAL **: Trying to dispose element play, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. (pidgin:3994): GStreamer-CRITICAL **: Trying to dispose element play, but it is not in the NULL state. You need to explicitly set elements to the NULL state before dropping the final reference, to allow them to clean up. ** (update-notifier:3993): WARNING **: no cdrom: disk --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in version 2.20. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 320206 ***