GNOME Bugzilla – Bug 512391
crash in Open Folder: Right-click & open with ...
Last modified: 2008-06-22 14:09:52 UTC
Version: 2.20.0 What were you doing when the application crashed? Right-click & open with other application Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Mon Jan 7 01:25:27 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: mac-osx-controls Icon Theme: OSX Memory status: size: 82776064 vsize: 82776064 resident: 31670272 share: 15962112 rss: 31670272 rss_rlim: 4294967295 CPU usage: start_time: 1201439409 rtime: 1565 utime: 1403 stime: 162 cutime:3 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6bc26c0 (LWP 3614)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 186965
Thread 1 (Thread 0xb6bc26c0 (LWP 3614))
The file is actually a broken link to a file that doesn't exist (on a partition that is not mounted) .
Thanks for taking the time to report this bug. Thanks for investigating. Can you please start nautilus from a terminal > gnome-session-remove nautilus && nautilus and paste the output here when it crashes? Thanks.
That's the error message I get : (nautilus:16850): Eel-WARNING **: No extension, not implemented yet
hmmm that is no use here Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! please install libeel, glib and nautilus packages
I think this is a duplicate of bug 355018. Also, no trace has been provided for a long time, so closing as such. *** This bug has been marked as a duplicate of 355018 ***