GNOME Bugzilla – Bug 325751
Nautilus crashes when dragging icons to another screen
Last modified: 2006-03-31 10:34:04 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.10.2 unspecified Gnome-Distributor: Debian Synopsis: Nautilus crashes when dragging icons to another screen Bugzilla-Product: nautilus Bugzilla-Component: Desktop Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: I have a two monitor, non-xinerama setup. I want to have nautilus' icons on the second head, not on the primary head. Steps to reproduce the crash: 1. Select one or more icons. 2. Drag the icons to the next screen. 3. Nautilus crashes as soon as you mouse moves off the screen Expected Results: The icons apear on the second screen How often does this happen? Every time Additional Information: non-xinerama setup with two monitors. Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225947456 (LWP 3072)] [New Thread -1234154576 (LWP 3075)] [New Thread -1233892432 (LWP 3074)] [New Thread -1228837968 (LWP 3073)] 0xb74b6231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 64951
Thread 1 (Thread -1225947456 (LWP 3072))
------- Bug created by bug-buddy at 2006-01-04 10:35 -------
unique stack trace. icon_window = (GtkWidget *) 0x0 looks suspicious confirming because of debugging symbols. can you upgrade to Gnome 2.12. , please, and try to reproduce? thanks.
I'm running Debian Sid. I don't want to mess around with the experimental repository on this production machine, so 2.12 will have to wait untill it arrives in Sid...
Ok, 2.12 is now in Sid, and this bug is still there. Here's the new info. Distribution: Debian testing/unstable Package: nautilus Severity: Normal Version: GNOME2.12.2 2.12.2 Gnome-Distributor: Debian Synopsis: Nautilus crashes when dragging icons to another screen Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.2 BugBuddy-GnomeVersion: 2.0 (2.12.0) Debugging Information: Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (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 -1225398592 (LWP 22532)] [New Thread -1235326032 (LWP 22538)] [New Thread -1235063888 (LWP 22537)] [New Thread -1234801744 (LWP 22536)] [New Thread -1234539600 (LWP 22535)] [New Thread -1234277456 (LWP 22534)] [New Thread -1227752528 (LWP 22533)] 0xb753e231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 65179
Thread 1 (Thread -1225398592 (LWP 22532))
*** Bug 328505 has been marked as a duplicate of this bug. ***
Bug 328505 has a stack trace using CVS HEAD; stack trace is a little different since this appears to cause a critical warning crasher.
If this is reproducible at all, it would be interesting to step thru gtk_drag_get_icon and see if fallback_icon is computed, and if it remains NULL. I don't see the crash when simulating multi-screen using Xnest, but that could be because Xnest is not supporting RGBA cursors...
From what I recall, I think this was very reproducible, but my machine with the dual monitor setup is dead right now. I don't know when I'll have time to get it fixed either. :( When it's back up, I'll try that out if someone else hasn't done so first. I may need to be pinged in a couple months...
I can still reproduce it on my debian Sid machine, though that is still 2.12. But 2.14 is expected soon, I'll see if that changes anything.
I would be interested in a test with GTK+ 2.8.16
Well, GTK+ 2.8.16 _is_ in sid, so I can do that :) Here's the backtrace. If you want I can install some of the -dev packages, just let me know which ones you need. Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.12.3 2.12.2 Gnome-Distributor: Debian Bugzilla-Product: nautilus Bugzilla-Component: general Bugzilla-Version: 2.12.2 BugBuddy-GnomeVersion: 2.0 (2.12.1) gtk+2.0: 2.8.16-1 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (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 -1226103104 (LWP 32143)] [New Thread -1228305488 (LWP 32145)] 0xb74ec221 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 67336
Thread 1 (Thread -1226103104 (LWP 32143))
I can confirm this on GNOME 2.14 on Ubuntu Dapper Drake. 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) (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) [Thread debugging using libthread_db enabled] [New Thread -1225410880 (LWP 29364)] [New Thread -1226855504 (LWP 29366)] (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) (no debugging symbols found) (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 67341
Thread 1 (Thread -1225410880 (LWP 29364))
Created attachment 62407 [details] [review] a patch It would be great if some of you could test this patch (I don't have a multi-screen setup here)
2006-03-30 Matthias Clasen <mclasen@redhat.com> * gtk/gtkdnd.c (gtk_drag_get_icon): Make sure to get an icon window when constructing the fallback_icon. This fixes a crash when dragging icons between screens in nautilus. (#325751, Hylke van der Schaaf)
It works! I can now move icons from one screen to another.