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 610177 - Can't stop drag 'n' drop
Can't stop drag 'n' drop
Status: RESOLVED DUPLICATE of bug 590606
Product: file-roller
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2010-02-16 17:23 UTC by Axel Lewenhaupt
Modified: 2010-02-16 18:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Axel Lewenhaupt 2010-02-16 17:23:39 UTC 
When navigating fast through an archive by using my mouse and double clicking on folders then when I'm at the destination I want, then I get a "drag 'n' drop" item attached to the mouse. It doesn't matter what I do; if I drop it somewhere I get a new (the same item) "drag 'n' drop" item. The item appears again as soon as I move the mouse over the file list (without clicking or doing anything else). This makes it very hard to use any of the functionality as long as the item is stuck to the mouse. The only way to get rid of it is to restart the archive.

To reproduce: Open an archive which has 3+ folders depth. Then navigate using the mouse by double clicking each folder fast. Then when you get to last folder there is an item stuck to the mouse which will not go away.

Happens every time? Yes.

Using ubuntu 9.10 with file roller 2.28.1
Comment 1 Pablo Castellano (IRC: pablog) 2010-02-16 17:42:01 UTC 
I cannot reproduce it also udner ubuntu 9.10 but I have experienced the "drag and drop" impossible to drop sometimes.
Comment 2 Paolo Bacchilega 2010-02-16 18:26:10 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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