GNOME Bugzilla – Bug 537652
crash in Open Folder: Listening the music
Last modified: 2008-06-10 19:09:28 UTC
Version: 2.20.0 What were you doing when the application crashed? Listening the music Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 83759104 vsize: 83759104 resident: 27430912 share: 15835136 rss: 27430912 rss_rlim: 4294967295 CPU usage: start_time: 1212338009 rtime: 1174 utime: 1100 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b6c720 (LWP 5809)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200059
Thread 1 (Thread 0xb6b6c720 (LWP 5809))
----------- .xsession-errors (964 sec old) --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:5809): WARNING **: Hit unhandled case 31 (Operation cancelled) in fm_report_error_loading_directory ** Message: Error: Could not read from resource. gstgnomevfssrc.c(683): gst_gnome_vfs_src_create (): /play/source: Failed to read data: Generic error ** (nautilus:5809): WARNING **: Hit unhandled case 2 (Generic error) in fm_report_error_loading_directory (gecko:9209): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
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 522534 ***