GNOME Bugzilla – Bug 477089
crash in Image Viewer:
Last modified: 2007-09-15 19:15:36 UTC
Version: 2.18.2 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve-BerriesAndCream Icon Theme: Clearlooks Memory status: size: 34521088 vsize: 34521088 resident: 7376896 share: 6107136 rss: 7376896 rss_rlim: 4294967295 CPU usage: start_time: 1189818682 rtime: 8 utime: 6 stime: 2 cutime:0 cstime: 0 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 -1208776992 (LWP 7279)] [New Thread -1210877040 (LWP 7280)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 163013
Thread 2 (Thread -1210877040 (LWP 7280))
----------- .xsession-errors --------------------- fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub fixme:shell:SHGetFileInfoW set icon to shell size, stub Eog-ERROR **: file eog-image.c: line 777 (eog_image_real_load): assertion failed: (priv->image != NULL) aborting... --------------------------------------------------
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 ***