GNOME Bugzilla – Bug 495936
crash in Computer: I was asking a folder's...
Last modified: 2007-11-12 00:12:19 UTC
Version: 2.18.3 What were you doing when the application crashed? I was asking a folder's properties. Nautilus also crashed on asking a mp3 file's properties. I'll try other kinds of files... Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-amd64 #1 SMP Wed Jul 11 05:38:29 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 82817024 vsize: 82817024 resident: 25067520 share: 15515648 rss: 25067520 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194762473 rtime: 886 utime: 812 stime: 74 cutime:0 cstime: 0 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xf6e126b0 (LWP 3516)] (no debugging symbols found) 0xf7662bf1 in waitpid () from /lib/libpthread.so.0
+ Trace 177056
Thread 1 (Thread 0xf6e126b0 (LWP 3516))
----------- .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 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... warning: Lowest section in system-supplied DSO at 0xffffe000 is .hash at ffffe0b4 --------------------------------------------------
- Nautilus crashes for several kinds of files (.wav, .pdf, .odt, .ods, .mp3, .csv) and folders - but not for simple text files, tar files, .ldif and folders containing only this files.
Thanks for the bug report. This particular bug has been fixed already. Please update. *** This bug has been marked as a duplicate of 440988 ***