GNOME Bugzilla – Bug 507756
crash in Image Viewer: opening FAQ.bmp of audac...
Last modified: 2008-01-07 00:32:19 UTC
Version: 2.20.3 What were you doing when the application crashed? opening FAQ.bmp of audacious-1.4.4 Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 35794944 vsize: 35794944 resident: 14405632 share: 10727424 rss: 14405632 rss_rlim: 4294967295 CPU usage: start_time: 1199665615 rtime: 35 utime: 28 stime: 7 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6bf56c0 (LWP 4793)] [New Thread 0x95a13b90 (LWP 4795)] [New Thread 0xb6a7cb90 (LWP 4794)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184338
Thread 3 (Thread 0xb6a7cb90 (LWP 4794))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: Failed to write /home/opbuzz/Desktop/Downloads/audiacious/audacious-1.4.4/FAQ.bmp to thumbnail pixbuf loader: Unrecognized image file format ** Message: Failed to write /home/opbuzz/Desktop/Downloads/audiacious/audacious-1.4.4/FAQ.bmp to thumbnail pixbuf loader: Unrecognized image file format EOG-ERROR **: file eog-image.c: line 1148 (eog_image_real_load): assertion failed: (priv->image != NULL) aborting... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 479912 ***