After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 325751 - Nautilus crashes when dragging icons to another screen
Nautilus crashes when dragging icons to another screen
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: [obsolete] multihead
2.6.x
Other other
: High critical
: ---
Assigned To: Erwann Chenede
gtk-bugs
: 328505 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-04 10:35 UTC by Hylke van der Schaaf
Modified: 2006-03-31 10:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
a patch (1.66 KB, patch)
2006-03-30 17:38 UTC, Matthias Clasen
none Details | Review

Description Hylke van der Schaaf 2006-01-04 10:35:45 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

Thread 1 (Thread -1225947456 (LWP 3072))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_drag_update_icon
    at gtkdnd.c line 2737
  • #4 gtk_drag_update_idle
    at gtkdnd.c line 3686
  • #5 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 IA__gtk_main
    at gtkmain.c line 991
  • #10 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug created by bug-buddy at 2006-01-04 10:35 -------

Comment 1 Christian Kirbach 2006-01-04 11:49:10 UTC
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.
Comment 2 Hylke van der Schaaf 2006-01-04 13:15:22 UTC
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...
Comment 3 Hylke van der Schaaf 2006-01-13 12:39:46 UTC
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

Thread 1 (Thread -1225398592 (LWP 22532))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_drag_update_icon
    at gtkdnd.c line 2737
  • #4 gtk_drag_update_idle
    at gtkdnd.c line 3686
  • #5 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 IA__gtk_main
    at gtkmain.c line 991
  • #10 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0

Comment 4 Elijah Newren 2006-01-25 20:03:21 UTC
*** Bug 328505 has been marked as a duplicate of this bug. ***
Comment 5 Elijah Newren 2006-01-25 20:04:12 UTC
Bug 328505 has a stack trace using CVS HEAD; stack trace is a little different since this appears to cause a critical warning crasher.
Comment 6 Matthias Clasen 2006-03-29 05:22:05 UTC
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...
Comment 7 Elijah Newren 2006-03-29 05:26:30 UTC
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...
Comment 8 Hylke van der Schaaf 2006-03-29 07:34:15 UTC
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.
Comment 9 Matthias Clasen 2006-03-29 18:41:35 UTC
I would be interested in a test with GTK+ 2.8.16
Comment 10 Hylke van der Schaaf 2006-03-30 07:55:54 UTC
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

Thread 1 (Thread -1226103104 (LWP 32143))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_drag_update_icon
    at gtkdnd.c line 2754
  • #4 gtk_drag_update_idle
    at gtkdnd.c line 3706
  • #5 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 IA__gtk_main
    at gtkmain.c line 1001
  • #10 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0

Comment 11 Tore S Bekkedal 2006-03-30 13:17:44 UTC
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 ()

Thread 1 (Thread -1225410880 (LWP 29364))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_drag_set_icon_default
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_drag_set_icon_default
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 POA_Nautilus_MetafileFactory__fini
  • #12 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #13 ??
  • #0 __kernel_vsyscall

Comment 12 Matthias Clasen 2006-03-30 17:38:16 UTC
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)
Comment 13 Matthias Clasen 2006-03-30 18:29:18 UTC
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)

Comment 14 Hylke van der Schaaf 2006-03-31 10:34:04 UTC
It works!
I can now move icons from one screen to another.