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 740233 - Drag-drop extraction breaks when not over Nautilus
Drag-drop extraction breaks when not over Nautilus
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2014-11-17 03:23 UTC by Damon Poole
Modified: 2015-02-15 17:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Error generated when dragging a file outside of the file-roller window (9.79 KB, image/png)
2014-11-17 03:23 UTC, Damon Poole
Details

Description Damon Poole 2014-11-17 03:23:04 UTC
Created attachment 290830 [details]
Error generated when dragging a file outside of the file-roller window

Dragging files out of an archive to a Nautilus window throws an error and stops the drag if the dragged object passes over a non-nautilus window. If the file-roller window and the Nautilus window overlap/intersect, then it behaves as expected and allows you to drag-extract files to a folder in Nautilus.

It seems that as soon as a dragged object is dragged out of file-roller and isn't targeting a Nautilus window, the drag gets released resulting in file-roller trying to extract the file to where it was released (null since it happens immediately after leaving the file-roller window, not giving you time to get to a Nautilus one).

Running OpenSUSE 13.2, gnome-session 3.14, file-roller 3.14.1
Comment 1 Andrea Antolini 2015-01-04 16:15:15 UTC
confirmed also on Archlinux gnome 3.14.2, file roller 3.14.2

Regards
Andrea
Comment 2 Paolo Bacchilega 2015-02-15 10:27:07 UTC
I cannot reproduce this problem, maybe it is related to bug #479351, can someone try the current master version and see if it works correctly?
Comment 3 Evangelos Foutras 2015-02-15 11:04:23 UTC
The problem still exists in current master.

Maybe you'll be able to reproduce the issue by following the steps from this report:

https://bugzilla.gnome.org/show_bug.cgi?id=735857

The first comment there is by an Xfce developer who came across bug 735857 after I reported a similar behavior with the then newly released xfdesktop 4.10.3:

https://bugzilla.xfce.org/show_bug.cgi?id=11314
Comment 4 Paolo Bacchilega 2015-02-15 12:34:07 UTC
(In reply to Evangelos Foutras from comment #3)
> The problem still exists in current master.
> 
> Maybe you'll be able to reproduce the issue by following the steps from this
> report:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=735857
> 
> The first comment there is by an Xfce developer who came across bug 735857
> after I reported a similar behavior with the then newly released xfdesktop
> 4.10.3:
> 
> https://bugzilla.xfce.org/show_bug.cgi?id=11314

Thanks for pointing this out, I think I've fixed the chromium bug now, can you test master again?
Comment 5 Evangelos Foutras 2015-02-15 16:03:49 UTC
(In reply to Paolo Bacchilega from comment #4)
> Thanks for pointing this out, I think I've fixed the chromium bug now, can
> you test master again?

Both master and commit af95f7d applied on top of File Roller 3.14.2 behave correctly now.

Dragging an item from File Roller over Chromium doesn't abort like before, and I can now also extract files by dragging them onto my desktop (xfdesktop 4.10.3). Prior to your fix, both cases would produce the error mentioned in bug 735857.

Many thanks for fixing this! :)
Comment 6 Paolo Bacchilega 2015-02-15 17:12:37 UTC
good, closing as fixed...