GNOME Bugzilla – Bug 507173
crash in Open Folder:
Last modified: 2008-01-05 18:47:18 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (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: Clearlooks Icon Theme: gnome Memory status: size: 86192128 vsize: 86192128 resident: 24977408 share: 16355328 rss: 24977408 rss_rlim: 4294967295 CPU usage: start_time: 1199415053 rtime: 378 utime: 351 stime: 27 cutime:64 cstime: 7 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 0xb6d676b0 (LWP 3995)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184001
Thread 1 (Thread 0xb6d676b0 (LWP 3995))
----------- .xsession-errors --------------------- CPU: Genuine Intel(R) CPU T2050 @ 1.60GHz (Family: 6, Model: 14, Stepping: 8) CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Window manager warning: Window 0x2e00019 (MPlayer) sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 440 x 120; this doesn't make much sense. Playing /media/disk/Piratas De Silicon Valley.avi. Exiting... (Quit) 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... --------------------------------------------------
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 ***