Red Hat Bugzilla – Bug 1304497
File Roler in Wayland doesn't support drag-n-drop
Last modified: 2017-08-13 12:15:29 EDT
Description of problem:
I can't select a file from an archive file and drag-n-drop to a folder in Nautilus.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a zip, tar.gz, ... any archive file
2. Select one file form the archive
3. Drag the file and drop it on a folder in Nautilus
It should extract the file from the archive
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
This bug is still present in Fedora 25.
When I try do drag-n-drop a file from file-roller into nautilus, both applications become frozen.
I am reproducing this also in F25. Not sure if this is a problem or Wayland or file-roller wayland integration.
I can confirm that this bug is present when using Wayland. Drag-n-drop works as expected when using Xorg though.
The bug is still here in Fedora 25 with Wayland. In Fedora 24 with Xorg there isn't any issue.
*** This bug has been marked as a duplicate of bug 1229018 ***