GNOME Bugzilla – Bug 515151
crash in Open Folder: I tried to open a folder...
Last modified: 2008-02-08 11:16:40 UTC
Version: 2.20.0 What were you doing when the application crashed? I tried to open a folder pressed double click Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 77172736 vsize: 77172736 resident: 25989120 share: 16039936 rss: 25989120 rss_rlim: 4294967295 CPU usage: start_time: 1202441173 rtime: 530 utime: 500 stime: 30 cutime:6 cstime: 3 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 0xb6b9c6c0 (LWP 4236)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 188508
Thread 1 (Thread 0xb6b9c6c0 (LWP 4236))
----------- .xsession-errors --------------------- ** Message: totemPlugin dtor [0x96ff180] ** Message: totemPlugin dtor [0x9702e48] ** Message: totemPlugin dtor [0x92c08e0] ** Message: NP_Shutdown ====================== libparted : 1.7.1 ====================== warning: could not initiate dbus warning: could not initiate dbus could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security poli current dist not found in meta-release file closing BBDB spinning up... (nautilus:4236): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***