GNOME Bugzilla – Bug 108205
Crash after attempting to copying a file to trash.
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: major Version: GNOME2.2.0 2.2.2 os_details: Gnome.Org Synopsis: Crash when copying file to desktop trash. Bugzilla-Product: nautilus Bugzilla-Component: File and Folder Operations BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Nautilus crashed when copying file to desktop tra Steps to reproduce the problem: 1. Double click on home folder. 2. Middle click and drag a .jpg from home folder to desktop trash icon. 3. Select 'Copy File' option. Actual Results: Nautilus crashes. Expected Results: Nautilus does not crash. How often does this happen? Only once, but still thought I should report it. Additional Information: Debugging Information: Backtrace was generated from '/gnome/gnome-2-2/INSTALL/bin/nautilus' 0xffffe002 in ?? ()
+ Trace 34808
Works ok here with 2.2.2 nautilus tarball. A dialog box pops up saying "You cannot copy items into the trash".
I said it only happened once. Maybe the debug output would be more helpful rather than simply dismissing the bug because "it works for me"?
Dennis: I don't see how Alex dismissed this bug at all. If you'll notice, the bug is still open, whereas Alex could have closed it. He looks through hundreds of bugs regularly and was likely just leaving a note that he had at least tried this bug once and couldn't reproduce--which can be potentially useful to others. I'm starting to suspect this is a gtk+ problem. This bug and a few others I've recently seen have the following two functions (even with matchine line numbers) at the top of their stack traces: gtk_widget_get_toplevel at gtkwidget.c:5356 gtk_main_get_window_group at gtkmain.c:1569 Half of these bugs were gnome-panel crashes, the other half are nautilus ones. See bug 108656 for the ones tracked against the gnome-panel. I believe either this should be a duplicate of that one, or that one should be a duplicate of this bug (so long as the product is changes)--but I'm not completely sure.
*** Bug 108719 has been marked as a duplicate of this bug. ***
Ooops, forgot to triage. Marking severity->critical (it's a crasher), adding myself to cc list (so I can find out if I was right about this and 108656 being dups), and adding bugsquad keyword.
I agree. I think this is likely a gtk+ bug. Especially after looking at the backtrace in bug 108719.
Owen: I'm adding you to the cc list (as Arvind suggested might be a good idea in bug 108656) so you can take a look at this and perhaps provide some insight as to whether this might be a gtk+ problem or not. Note that this bug is almost identical (if not identical) to the stack traces being tracked in bug 108656 (which is recording gnome-panel crashes instead of nautilus ones).
Well, it's certainly not a GTK+ bug that can be debugged by code inspection ... the code involved is actually really straightforward ... it just takes a widget and walks up the toplevel to the heirarchy. It appears that something has corrupted (or stored invalid data in) the user data field of a GdkWindow.
Oh - another thing. For "Possible GTK+" bugs, please Cc: gtk-bugs@gtk.org rather than me. I don't handle GTK+ maintenance alone, and other people may have more time/interest in trying to track down such intermittent crashers in GNOME apps.
Oh, okay, I'll remember that Owen. Thanks for the pointer. (And sorry for the extra work) I'll drop you from the cc-list so you won't be spammed further from this bug. chrisw@tartarus.uwa.edu.au just added a very interesting comment to bug 108656: GARNOME 0.22.0 uses a patched version of GTK+ to add pretty (albeit buggy) drop shadow eyecandy and the like - installing a clean version of GTK+ fixes the problem. I've informed the list so hopefully an updated version will be released. Dennis: Do you happen to be using garnome or the same GTK+ patch? If so, can you try removing that patch and seeing if the problem still occurs?
Yes. It was that menu shadow patch. I am closing this bug. Sorry for wasting everyone's time on this.
*** Bug 109398 has been marked as a duplicate of this bug. ***
Dennis: You didn't waste anyone's time. Other people are reporting the same or similar bugs, and this bug is helping to track at least one of them down. I'm guessing a few others are dups as well if I look into this further. Thanks for following up and telling us that the gtk+ patch was at fault. :)
*** Bug 126615 has been marked as a duplicate of this bug. ***
*** Bug 140483 has been marked as a duplicate of this bug. ***