GNOME Bugzilla – Bug 542743
crash in Open Folder: im not sure im drunk, tr...
Last modified: 2008-07-13 21:42:13 UTC
Version: 2.20.0 What were you doing when the application crashed? im not sure im drunk, trying to make it wifi i think Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 66457600 vsize: 66457600 resident: 19902464 share: 13512704 rss: 19902464 rss_rlim: 4294967295 CPU usage: start_time: 1215932106 rtime: 1178 utime: 1073 stime: 105 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 0xb6b15720 (LWP 2974)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 202680
Thread 1 (Thread 0xb6b15720 (LWP 2974))
----------- .xsession-errors (71 sec old) --------------------- ** (nm-applet:2994): CRITICAL **: wso_wep_auth_combo_cleanup: assertion `combo != NULL' failed ** Message: <info> You are now connected to the wired network. closing closing ** (nautilus:2974): WARNING **: file_system_gnome_vfs=0x83518c0 still has handle=0x87d21a0 at finalization which is NOT CANCELLED! (nautilus:2974): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkFileSystemGnomeVFS' (nautilus:2974): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed ** ERROR **: file gtkfilesystemgnomevfs.c: line 3605 (gtk_file_system_handle_gnome_vfs_finalize): assertion failed: (g_hash_table_lookup (system_vfs->handles, handle) != NULL) aborting... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 505002 ***