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 607421 - nautilus crashes when clicking files on second screen (:0.1)
nautilus crashes when clicking files on second screen (:0.1)
Status: RESOLVED INCOMPLETE
Product: gtk+
Classification: Platform
Component: .General
2.18.x
Other Linux
: Normal critical
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-01-19 09:06 UTC by Martin Mai
Modified: 2012-12-28 01:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Martin Mai 2010-01-19 09:06:29 UTC
Originally reported at https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/467862:

Trying to e.g. drag a file on the second display (:0.1) leads to a nautilus crash:

The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 534504 error_code 8 request_code 142 minor_code 2)

Doing the same actions on the primary display is no problem. On :0.1 however it happens on icons on the desktop as well as in a separate nautilus window.

Ubuntu 9.10 (upgraded from Jaunty, which had other issues with the seconds screen but no nautilus crash)


Trace: http://launchpadlibrarian.net/38054205/gdb-nautlius-dndcrash.txt
Comment 1 Matthias Clasen 2010-02-09 03:05:01 UTC
Odd, we push an error trap around the key-grabbing code in gtkdnd.c, and it works reliably in my testing.
Comment 2 bugzilla.gnome.org 2010-02-17 02:23:58 UTC
i'm also tracking the bug cause i've the same trouble, and there exists some bugzilla entrys related to the problem.

i.e.: https://bugzilla.gnome.org/show_bug.cgi?id=593453
Comment 3 chris 2010-09-06 22:40:03 UTC
The problem is gone for me. Dragging icons in Nautilus on the second screen (left of main screen) works now as expected. This may be related to a recent fix of X.orgs handling of negative coordinates (though that bug mentioned Xinerama which i do not use). I guess the bug can be closed.

Ubuntu Lucid, Gnome 2.30.2
Comment 4 André Klapper 2012-08-21 11:37:51 UTC
Does anybody still see this problem in 3.4 or 3.2?
Comment 5 Tobias Mueller 2012-12-28 01:59:38 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!