GNOME Bugzilla – Bug 497265
crash in Open Folder: Tried to open a .png fil...
Last modified: 2007-11-16 13:44:39 UTC
Version: 2.18.3 What were you doing when the application crashed? Tried to open a .png file on my desktop. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-486 #1 Thu Aug 30 23:45:36 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: NewCarbonit Icon Theme: GnomeElephant-Marine-01 Memory status: size: 103747584 vsize: 103747584 resident: 28123136 share: 15593472 rss: 28123136 rss_rlim: 4294967295 CPU usage: start_time: 1195177481 rtime: 884 utime: 808 stime: 76 cutime:33 cstime: 10 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 0xb6e098c0 (LWP 15186)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178042
Thread 1 (Thread 0xb6e098c0 (LWP 15186))
----------- .xsession-errors (14 sec old) --------------------- ** 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 was trying to view the properties of the file, not open it as I initially said.
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 440988 ***