GNOME Bugzilla – Bug 476718
crash in Image Viewer: Viewing pictures again
Last modified: 2007-09-14 11:06:55 UTC
Version: 2.18.2 What were you doing when the application crashed? Viewing pictures again 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 109748224 vsize: 109748224 resident: 64819200 share: 19005440 rss: 64819200 rss_rlim: 4294967295 CPU usage: start_time: 1189717325 rtime: 668 utime: 634 stime: 34 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 -1208580384 (LWP 6435)] [New Thread -1258017904 (LWP 6440)] [New Thread -1210860656 (LWP 6436)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162738
Thread 1 (Thread -1208580384 (LWP 6435))
----------- .xsession-errors (195 sec old) --------------------- (bug-buddy:5115): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:5115): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:5115): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:5115): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed TagLib: MPEG::Header::parse() -- Invalid sample rate. TagLib: MPEG::Header::parse() -- Invalid sample rate. TagLib: MPEG::Header::parse() -- Invalid sample rate. TagLib: MPEG::Header::parse() -- Invalid sample rate. JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] --------------------------------------------------
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 the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 354154 ***