GNOME Bugzilla – Bug 408283
crash in nautilus-file.c:308, renaming a link
Last modified: 2007-02-26 14:56:11 UTC
What were you doing when the application crashed? renaming a link Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 104235008 vsize: 0 resident: 104235008 share: 0 rss: 23609344 rss_rlim: 0 CPU usage: start_time: 1171546082 rtime: 0 utime: 2138 stime: 0 cutime:2011 cstime: 0 timeout: 127 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226549584 (LWP 5444)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 111010
Thread 1 (Thread -1226549584 (LWP 5444))
Thanks for taking the time to report this bug. Unfortunately, the 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. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install the following debug packages provided by Ubuntu: nautilus-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg, libpango1.0-0-dbg, libgnomevfs2-0-dbg, libgnome2-0-dbgsym, and libgnomeui-0-dbg. More details can be found here: http://live.gnome.org/GettingTraces
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 76554240 vsize: 0 resident: 76554240 share: 0 rss: 26394624 rss_rlim: 0 CPU usage: start_time: 1172393968 rtime: 0 utime: 351 stime: 0 cutime:324 cstime: 0 timeout: 27 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226471760 (LWP 5435)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 113716
Thread 1 (Thread -1226471760 (LWP 5435))
nice trace, thanks a lot!! is this always reproducible? where and how exactly do you rename that link (clicking on the name by mouse, using a menu entry, using the right-click context menu)? what kind of link is this? can you reproduce this with any link? your ubuntu system has the latest updates installed, i assume? (questions and questions, i know - but we often have a hard time to reproduce crashes. thanks in advance for helping.)
(this bug may be pretty related to bug 358172)
My pleasure! No, it is not always reproducible. The times it has happened are when a folder has been updated and name changed (X-Plane-RC6 to X-Plane-RC7), and then its link (X-Plane) is automatically removed. By right clicking on the new folder and re-creating the link then again right clicking on this link and renaming it to what it was before. Once the bug report is closed the blank nautilus closes and reopens fully functional, showing the change. Ubuntu is up to date.
Yeah, this seems to be a dup of bug 358172. Its the same underlying problem of the symbolic_link hashtable being out-of-date somehow. *** This bug has been marked as a duplicate of 358172 ***