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 593453 - Crash in Nautilus when drag and drop files from 2nd screen
Crash in Nautilus when drag and drop files from 2nd screen
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-28 22:27 UTC by gutsblack
Modified: 2017-11-21 23:17 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description gutsblack 2009-08-28 22:27:58 UTC
My system is using NVidia's separate X-screen instead of TwinView.
Drag and Drop crash Nautilus from 2nd screen. Tested with different files on different directory. If I cut/copy/paste the file it's ok. The bug is 100% reproductible. The first screen is ok.

System :
Ubuntu 9.10
Gnome 2.27.4
Nautilus 2.27.91
Comment 1 Pierre Wieser 2009-11-21 11:18:03 UTC
Hi

same problem on my Fedora 11, but in TwinView configuration (nVidida 190.42)
Nautilus 2.26.4

My syslog shows
"[Gdk] The program 'nautilus' received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'BadAtom (invalid Atom parameter)'.#012  (Details: serial 35148 error_code 5 request_code 24 minor_code 0)#012  (Note to programmers: normally, X errors are reported asynchronously;#012   that is, you will receive the error a while after causing it.#012   To debug your program, run it with the --sync command line#012   option to change this behavior. You can then get a meaningful#012   backtrace from your debugger if you break on the gdk_x_error() function.)"

All works fine when source and Nautilus dest are on the same screen.
Crash occurs when dnd from one screen to the other.

Almost sure this worked last week-end.
Recent updates on my pc are:

Nov 14 15:34:04 kermit yum: Installed: libXau-1.0.4-5.fc11.i586
Nov 14 15:34:10 kermit yum: Installed: libX11-1.2.2-1.fc11.i586
Nov 14 15:34:10 kermit yum: Installed: libXrender-0.9.4-5.fc11.i586
Nov 14 15:34:11 kermit yum: Installed: libXext-1.0.99.1-3.fc11.i586
Nov 14 15:34:11 kermit yum: Installed: libXv-1.0.4-2.fc11.i586
Nov 14 15:34:31 kermit yum: Installed: libXft-2.1.13-2.fc11.i586
Nov 19 21:35:50 kermit yum: Updated: xorg-x11-drv-evdev-2.2.6-1.fc11.x86_64
Comment 2 Pierre Wieser 2009-11-21 13:41:52 UTC
Additional notes:
- crash occurs even if no extension are loaded (extensions-2.0/ empty)
- crash occurs when drag from file-roller as well as from gedit

Previous syslog message was only displayed because my own extension (Nautilus-Actions) set its own default log handler, which output all it receives. Without any extension, the syslog message is not displayed, but behavior (crash) is the same.
Comment 3 bugzilla.gnome.org 2010-01-06 22:58:42 UTC
Hi,

i have the same problem and found some other bug reports on other sites (no solve yet)
http://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/467862
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558351

The problem exists since my last system update
xorg 1.6 => 1.7
kernel 2.6.28 => 2.6.32
gnome 2.26 => 2.28
nautilus 2.26 => 2.28

but i'm not sure if it's related to nautilus, cause gnome-control center also crashes sometimes when i use hotkeys (volume up/down/mute) on my keyboard.

(i'm using nvidia drivers and seperate xscreen setup, too)
Comment 4 bugzilla.gnome.org 2010-01-28 20:53:07 UTC
The problem still exists.

The hotkey problem is fixed, so the bug seems to be nautilus related!
Comment 5 bugzilla.gnome.org 2011-11-07 21:39:35 UTC
Now Nautilus doesn't crash anymore but it don't react. so you can't drag a file from screen1 to an nautilus window on screen2.

tested with nautilus 2.32.2.1 and gnome 2.32.1
Comment 6 Alexandre Franke 2016-12-05 10:05:47 UTC
Drag and drop across monitors works just fine here with 3.22, but I'm on an Intel graphics card. Does any of you still run into this issue with a recent version of GNOME?
Comment 7 Alexandre Franke 2017-11-21 23:17:57 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!