GNOME Bugzilla – Bug 302096
Crash while trying to burn a CD
Last modified: 2006-01-11 23:56:10 UTC
Distribution: Debian 3.1 Package: nautilus Severity: normal Version: GNOME2.10.0 2.10.0 Gnome-Distributor: Ubuntu Synopsis: Crash while trying to burn a CD Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.10.0 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: While copying files in the CD-burner utility it has crashed Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? 1st time Additional Information: Debugging Information: 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) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223891712 (LWP 8443)] [New Thread -1238053968 (LWP 8550)] [New Thread -1237787728 (LWP 8549)] [New Thread -1237521488 (LWP 8548)] [New Thread -1236862032 (LWP 8547)] [New Thread -1226523728 (LWP 8533)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 58768
Thread 6 (Thread -1226523728 (LWP 8533))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-26 21:17 ------- Unknown version 2.10.0 in product nautilus. Setting version to "2.10.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was manolo@austrohungaro.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
*** Bug 302426 has been marked as a duplicate of this bug. ***
*** Bug 303094 has been marked as a duplicate of this bug. ***
Could you get the backtrace with libgnomevfs2-0-dbg nautilus-dbg installed?
No, those are not installed
I know, the bug is not really useful without them (the backtrace has no debug information). Can you install them and get the backtrace again?
*** Bug 304941 has been marked as a duplicate of this bug. ***
*** Bug 305980 has been marked as a duplicate of this bug. ***
*** Bug 305851 has been marked as a duplicate of this bug. ***
*** Bug 306818 has been marked as a duplicate of this bug. ***
*** Bug 307694 has been marked as a duplicate of this bug. ***
*** Bug 308507 has been marked as a duplicate of this bug. ***
*** Bug 308899 has been marked as a duplicate of this bug. ***
Lots of dups; can't sit here in NEEDINFO. Reopening, confirming, setting severity/priority correctly.
Here is a parially decoded backtrace:
+ Trace 62616
I'm not sure what called nautilus_directory_force_reload(). Maybe nautilus-window-manage-views::begin_location_change(), which would be very early in the loading of the window. However, I don't understand why this leads to activation_callback being called. There should not have been an activation in the newly loading window.
Seems to happen when browsing/opening folders, often on FAT/NTFS partitions (summarizing the other bug reports). I wonder if people are using spatial or browser when this happens. I.E. are we opening a new window at this time, or replacing the location in the old window?
Actually, my decoding of frame #12 seems wrong. There are multiple other calls that are more likely.
In fact, I think #12 one of these: deep_count_callback, mime_list_callback, top_left_read_done (via top_left_read_callback), get_info_callback, finish_info_provider since these are callbacks from gnome-vfs that seems to fit with the rest of the stack trace.
I don't quite understand this. It seems we're doing an activation of a file in a window, and when gnome-vfs reports the information we need to do the activation is there (type, mimetype, etc) the window pointer we have in the view is NULL or invalid. However, I added code to close the parent window as soon as possible after an activation, and the code handles that fine. Is the window getting corrupted somewhere?
If anyone sees this, please describe exactly what you did. Browser or spatial, new window or not, did the old one close? Did you get any debug output from nautilus before it happened?
The decoded backtrace looks very much like the one in bug 314615, except it crashes later in nautilus_window_open_location_full. Might be related.
Each and every duplicate of this bug used nautilus 2.10.0 from Ubuntu. A quick query shows that there have not been any more duplicates. Might have been an Ubuntu specific patch, but either way this appears to be fixed now. I'm going to assume fixed for now (nautilus devs can correct me if I'm making an assumption they don't like here); if anyone can duplicate this with a more recent version of nautilus please feel free to reopen.