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 122689 - modal dialog on top of multiple file selection drag = ui frozen
modal dialog on top of multiple file selection drag = ui frozen
Status: RESOLVED DUPLICATE of bug 122688
Product: nautilus
Classification: Core
Component: Navigation
2.4.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-09-19 01:16 UTC by Allison Karlitskaya (desrt)
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Allison Karlitskaya (desrt) 2003-09-19 01:47:04 UTC 
I am experiencing a weird problem with nautilus.  It happened once by
accident, but I was able to reproduce my actions and can trigger the
problem every time now.  It's sort of difficult to explain... so here's
what you do to make it happen:

(1) open a navigation window
(2) start a large delete operation that's going to fail with an error
part-way through
(3) start a mouse-drag (like, to select multiple files)
(4) the error message from the delete pops up on top of your drag
(5) the UI is basically frozen now

What I mean by (5) is that you can't stop selecting the files.  If you
release the mouse button, the selection frame is still being dragged
around.  This causes you to not be able to click on the dialog box to clear it.

I'm guessing the mouse-release event doesn't get through to the main window
because of the modal dialog on top of it(?)

Other applications are effected as well.  I wasn't able to clear a dialog
in GIMP (1.3.x) which I was running to attempt to take a screenshot.  The
only way out that I know of is alt+f2 then 'killall nautilus'.

See attached screenshot.
Comment 1 Allison Karlitskaya (desrt) 2003-09-19 01:49:08 UTC 
This bug submitted twice because I thought the first one didn't go
through (bugzilla was totally unresponsive for a bit)

*** This bug has been marked as a duplicate of 122688 ***