GNOME Bugzilla – Bug 103235
Nautilus crashes, when folders/progams/icons should be moved
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: When trying to sort Icons on the Desktop, I can drag and drop one. It does not move. Klicking another icon after it, nautilus crashes. Though, the icon is moved afterwards. Steps to reproduce the problem: 1. drag and drop any icon somewhere 2. try to drag and drop another icon 3. Actual Results: Nautilus restarts; has moved icon to desired place Expected Results: should move immediately; without crashing. ;) How often does this happen? Allways Additional Information: none
Please include a backtrace of the crash using bug-buddy or gdb. See http://bugzilla.gnome.org/getting-traces.cgi for more information. Thanks.
Created attachment 13515 [details] debug output from crash; from bug-buddy
Don't know if it is the same bug, but each try to move an icon on the desktop or inside a nautilus window causes nautilus to crash. This happens on two different systems running Debian testing/unstable. In the past there was no such error, only since the update of some packages. I don' t know which package exatcly caused this bug, perhaps (gtk+2.2.0???).
The stack trace looks familar. I'm pasting it inline so that it can be searched easier... 0x40b23a39 in wait4 () from /lib/libc.so.6
+ Trace 33859
Thread 4 (Thread 32771 (LWP 23887))
Thread 3 (Thread 16386 (LWP 23886))
Thread 1 (Thread 16384 (LWP 23884))
Looks like a duplicate of bug 102907, which is marked as a duplicate of 102811. thomas.kulessa@epost.de: I don't know if this is the same bug as you are experiencing or not, though I suspect it is. I've seen several crashes with similar stack traces to the one shown in this bug, all coming from debian testing/unstable. It seems that the Debian packages were temporarily broken (or just included a version that not many other people used). Bug 102811 may contain more information. If you'd really like to know if this is the same bug, please file another bug report with a stack trace. I'm going to reopen this so I can mark it as a duplicate.
*** This bug has been marked as a duplicate of 102811 ***