Gnome freezes with drag / drop to 2 different windows

[RonzO]

When moving files from place to another, the computer would freeze up, and in order to fix it, I would have to ctrl alt backspace. I will try to give as much information about the problem as possible. =) I had 2 windows open, with the window I was dragging from in focus. If I moused over the Trash accidentally, the icon in "Places" on the left side of the window, it would freeze up, and I would have to ctrl alt backspace. I will try to recreate the problem on another computer, and post back...=)

[RonzO (ronz0o)]

I was able to recreate the problem on another computer, but it is not a problem with just the trash can. I moused over the home folder while dragging / dropping, and the system also froze up. The mouse does not freeze up, though. Hope this helps!

[Sebastien Bacher (seb128)]

thank you for your bug report, what ubuntu version do you use? could you describe steps to trigger the bug? is the screen still updated when you get the issue?

[RonzO (ronz0o)]

the screen does not update, and there is no progress bar for the files. i'm using a clean install of hardy heron. i opened one folder from the desktop, then another, say, the home folder. the folder from the desktop would be in focus. if you drag and drop an item to the home folder, and go over the places box, it will freeze up. let me recreate it, and post a screenshot to clear it up. =)

the drag path is the blue line, with destination. when it gets to the red X, the "Places" will highlight as if to be copied there, but the system freezes up.

[RonzO (ronz0o)]

A friend of mine also froze his install of Hardy, with the same symptoms. From the looks of it, it's a bigger problem.

[Sebastien Bacher (seb128)]

do you use the desktop effects option? do you get the issue if you don't enable those?

[RonzO (ronz0o)]

I normally run without desktop effects, and thats how it happens. I enabled it, and the same problem occurs. So it exists in both of them. =)

[Sebastien Bacher (seb128)]

still must be something specific to your configurations since nobody else has the issue, could you attach your Xorg.0.log messages and syslog logs after getting the issue?

[nexus (bugie)]

I also had this problem but I think it is gone now. Maybe because of some updates. I tried to reproduce the crash like it is described here - without success.

[RonzO (ronz0o)]

still having the same issue, even with patches, nexus. =( its not that much of a problem, more of a nuisance when moving files. heres the xorg.

[RonzO (ronz0o)]

and syslog

[nexus (bugie)]

Can you exactly describe the procedure to force this crash? I'll have another try then.

[nexus (bugie)]

Ok, I found the way to force it:
- open a nautilus window (change from home to another directory)
- open a second nautilus window (don't change directory)
- resize the second window
- click on a file in the second window and move it -> crash

I don't know if the directory changes are required. I tried it three times now, two times I had to hard shut down (by pressing the power button 4 secs), one time the x-server crashed and restarted automatically ("3. time", see below).

This happend (syslog):
1. time:
May 11 10:55:03 fb-ubuntu kernel: [ 763.728257] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:03 fb-ubuntu kernel: [ 763.728649] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:07 fb-ubuntu kernel: [ 767.756671] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:07 fb-ubuntu kernel: [ 767.757073] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:11 fb-ubuntu kernel: [ 771.779804] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:11 fb-ubuntu kernel: [ 771.780203] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:15 fb-ubuntu kernel: [ 775.802202] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 10:55:15 fb-ubuntu kernel: [ 775.802603] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023

2. time:
May 11 11:10:47 fb-ubuntu kernel: [ 160.081420] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:10:47 fb-ubuntu kernel: [ 160.081848] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:10:51 fb-ubuntu kernel: [ 164.105384] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:10:51 fb-ubuntu kernel: [ 164.105788] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:10:55 fb-ubuntu kernel: [ 168.101674] eth1: No ProbeResp from current AP 00:14:bf:c9:1f:a3 - assume out of range
May 11 11:11:00 fb-ubuntu NetworkManager: <info> Supplicant state changed: 0
May 11 11:11:00 fb-ubuntu kernel: [ 168.122305] NVRM: Xid (0001:00): 13, 0003 00000000 00008297 00001458 00001207 00000040
May 11 11:11:00 fb-ubuntu kernel: [ 168.122785] NVRM: Xid (0001:00): 13, 0003 00000000 00008297 00001458 00001207 00000000

3. time:
May 11 11:19:34 fb-ubuntu kernel: [ 144.032561] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:19:34 fb-ubuntu kernel: [ 144.032969] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:19:38 fb-ubuntu gdm[6021]: WARNING: gdm_slave_xioerror_handler: Schwerwiegender X-Fehler - :0 wird neu gestartet

For "3. time" here's the corresponding part in kern.log:
May 11 11:19:34 fb-ubuntu kernel: [ 144.032561] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
May 11 11:19:34 fb-ubuntu kernel: [ 144.032969] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023

If whole logs are required please do not hesitate...

[RonzO (ronz0o)]

thank you for finding that! i couldn't figure how to get the exact syslog, and when i looked through it...i didn't see anything. you also don't have to resize the window to get it to crash. i'm just glad someone else was able to recreate it =)

[Sebastien Bacher (seb128)]

there is nothing useful there, can you switch to a vt when it hangs? could you attach your Xorg.0.log messages and syslog logs to the bug?

[nexus (bugie)]

What is a "vt"?

[RonzO (ronz0o)]

virtual terminal, if i'm not mistaking. Sebastien, when it crashed for me, i don't think it would let me switch.

[Sebastien Bacher (seb128)]

there is no reason a nautilus crash should block switching or break the desktop, that seems to be a compiz or xorg crash rather

[nexus (bugie)]

As RonzO wrote, the keyboard doesn't respond any more. I tried to change to a terminal with Alt+F1 or F2 yesterday but it did not work.

[RonzO (ronz0o)]

sebastien, i don't think its a compiz problem. i run with it disabled normally. however, it DOES also crash when compiz is enabled.

[Sebastien Bacher (seb128)]

could you attach your messages and syslog logs to the bug? do you have an another computer you could use to ssh to the buggy one when you get the issue to see if something is eating ressources for example?

[davidy (davidyang102)]

I get something like this when dragging videos into vlc. Usually if i notice it hanging - i.e. the dragged icon doesn't follow the mouse, or the mouse is not moving at all, I do not let go of the mouse button, and move the cursor around a bit, and after like 3 seconds the system restores to normal operation - i.e. the dragged file moves with the mouse again.

Before I didn't do that and after i let go of the button it was permanently frozen, the keyboard does not respond. Not even Raising Skinny Elephants Is Utterly Boring works - apparently kernel level keyboard reading....

[flexion (nospam-flexion)]

I also have this behavior here. sometimes when I try to drag a file from the desktop to a folder in the right pane of nautilus, the system freezes when the "dragged" icon passes the places list in the left pane of nautilus.. the icon gets stuck there for a few seconds and the mouse pointer remains in "drag&drop" style and then a OKCANCEL error popup appears.. saying something like "moving file has failed". and today I moved a PDF file with the mouse into another corner of the desktop, and the system freezed exactly when the PDF was hoovering over a nearby "Web page link" on the desktop.. it looked like "querying the information" of the web link caused the freeze, while the PDF was dragged (but not released!) over it..

all this happens every day, but I can not reproduce it every time..

[flexion (nospam-flexion)]

ok I can reproduce it now (8.04 with all updates applied). it happens only once per session. if I log out and in again, the error can be reproduced again.

open two different local folders nautlius. drag a file from the right window to the left, when the cursor passes over the places list and touches the networkserver entry, the drag&drop event is stopped and I get the following error (note: I did not want to place the file on the network!)

Error while copying "test.jpg".
There was an error copying the file into network:///.
(Show more details..)
Operation not supported by backend.

and in another case last week I had a similar error while dragging a file from the desktop to a local folder in nautilus:

There was an error creating the folder "test".
Operation not supported by backend..

[RonzO (ronz0o)]

awesome, it looks like its a bit more widespread than i thought. i'm just glad that its not only me. =)

[mbrennwa (mbrennwa)]

Same problem over here. Dragging files from one nautilus window to another (or to/from the desktop) crashes the system. This occurs with Ubuntu 8.04 and the latest updates as of today (4. June 2008). However, if I turn off Desktop Effects, the problem goes away. Is it linked to Compiz or not?

Also, all this looks VERY similar to Bug #213700 ( https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/213700 ).

[RonzO (ronz0o)]

i don't believe that it is. i have had it happen to me while running compiz, and while not running it.

[p0tw0r (m-staniewski)]

Same here.
This is what I got from syslog:

Jun 15 17:42:23 malamax kernel: [ 295.881791] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
Jun 15 17:42:23 malamax kernel: [ 295.882220] NVRM: Xid (0001:00): 13, 0001 00000000 00005039 00000328 00000000 00000023
Jun 15 17:42:26 malamax gdm[5326]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Jun 15 17:42:26 malamax kernel: [ 300.248707] compiz.real[5758]: segfault at 00000030 eip 08055a6d esp bf9f5ed0 error 4

[mbrennwa (mbrennwa)]

After reporting that this bug also occurs on my machine (2008-06-04) I deactivated the Desktop Effects, which prevented the crashes in my case. Just out of curiosity I re-activated the Desktop Effects again today, and guess what: the problem did not occur any more! I'm not saying the bug is fixed for sure, but some of the recent updates I got through the automatic updater seem to have done something good, at least on my machine.

[Sebastien Bacher (seb128)]

the comments indicate a compiz crash

[psypher (psypher246)]

I'm so happy I'm not the only one experiencing this. This is quite annoying and is wasting a lot of time and I'm losing work when everything crashes. I have been able to Ctrl-alt-f2 and do a killall nautilus and recovered without losing work but it doesn't always work and you have to wait bout 2 mins before the desktop switches to the vt. I haven't tested this with compiz switched off but either way i actually use compiz productively, not just pretty, and this bug was never there before.

[psypher (psypher246)]

Oh and there seems to be a duplicate bug: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/224360

[Pedro Villavicencio (pedro)]

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.