GNOME Bugzilla – Bug 445266
crash in Image Viewer: viewing image
Last modified: 2007-10-05 14:03:30 UTC
Version: 2.18.0.1 What were you doing when the application crashed? viewing image Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 141029376 vsize: 141029376 resident: 85655552 share: 10293248 rss: 85655552 rss_rlim: 4294967295 CPU usage: start_time: 1181247605 rtime: 3946 utime: 2336 stime: 1610 cutime:1 cstime: 9 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 -1208875296 (LWP 4899)] [New Thread -1257825392 (LWP 4901)] [New Thread -1210975344 (LWP 4900)] (no debugging symbols found) 0x00ebb402 in __kernel_vsyscall ()
+ Trace 139183
Thread 3 (Thread -1210975344 (LWP 4900))
----------- .xsession-errors (26 sec old) --------------------- (eog:4899): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed (eog:4899): Eog-CRITICAL **: eog_image_cache_add: assertion `EOG_IS_IMAGE_CACHE (cache)' failed (eog:4899): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed (eog:4899): Eog-CRITICAL **: eog_image_list_iter_valid: assertion `EOG_IS_IMAGE_LIST (list)' failed (eog:4899): Eog-WARNING **: Image 100_2504.jpg has requested data already loaded. Eog-ERROR **: file eog-image.c: line 662 (eog_image_real_load): assertion failed: (priv->image == NULL) aborting... Xlib: unexpected async reply (sequence 0x6f73)! --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 454169 has been marked as a duplicate of this bug. ***
*** Bug 449020 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 468264 has been marked as a duplicate of this bug. ***
*** Bug 471844 has been marked as a duplicate of this bug. ***
*** Bug 473151 has been marked as a duplicate of this bug. ***
*** Bug 474077 has been marked as a duplicate of this bug. ***
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 357405 ***
*** Bug 483727 has been marked as a duplicate of this bug. ***