GNOME Bugzilla – Bug 495752
"preferencies" of some media files
Last modified: 2007-11-11 16:51:34 UTC
What were you doing when the application crashed? I press "preferencies" button on *.jpg file also this this error happenf with some of video files an almost picture files Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Xfce-smooth Icon Theme: Mist Memory status: size: 88113152 vsize: 88113152 resident: 36245504 share: 18558976 rss: 36245504 rss_rlim: 4294967295 CPU usage: start_time: 1194739513 rtime: 2402 utime: 2238 stime: 164 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (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 0xb6d946b0 (LWP 11347)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 176912
Thread 1 (Thread 0xb6d946b0 (LWP 11347))
----------- .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: drive = 0 ** Message: volume = 0 Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
i think this is same problem http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/c5d7732f3acd32e5
same: http://bugzilla.gnome.org/show_bug.cgi?id=495413 http://bugzilla.gnome.org/show_bug.cgi?id=495416 http://bugzilla.gnome.org/show_bug.cgi?id=495438
Thanks for the bug report. This particular bug has been fixed already. Please update. *** This bug has been marked as a duplicate of 440988 ***