Description of problem: Drag and drop does work only on Gnome on Xorg session. Version-Release number of selected component (if applicable): file-roller-3.30.1-1.fc29.x86_64 mutter-3.30.1-5.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. Open an archive with file-roller 2. Try drag and drop Actual results: Drag and drop does not work on wayland session. It looks like hover is behaving correctly and apps are reacting to hover when dragging, but dropping does not do anything. Expected results: Drag and drop should work just fine both on Wayland and Xorg sessions. Additional info: Tried this both on Bare metal and VM.
Proposed as a Blocker for 30-final by Fedora user frantisekz using the blocker tracking app because: All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.
Discussed during the 2018-12-17 blocker review meeting: [1] The decision to delay the classification of this as a blocker bug was made as we don't have a clear consensus on this bug, so if it does not get resolved in the mean time, we'll discuss further and try to reach a clearer consensus at a later meeting. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2018-12-17/f30-blocker-review.2018-12-17-17.00.txt
This isn't a new issue, see this upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=776635 The gist is that file-roller uses a different protocol than most applications (https://www.freedesktop.org/wiki/Specifications/XDS/), and that is not available on wayland.
Discussed during the 2019-02-11 blocker review meeting: [1] The decision to punt (delay decision) was made: "there still isn't a clear consensus on this (current vote total at +4 / -4) so we will delay once again, and try to ping desktop team for more info and hopefully a fix" [1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2019-02-11/f30-blocker-review.2019-02-11-17.13.log.txt
https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/thread/CU7KVIXQG3OWE45TOKLAX7S4VE73OKVZ/ Looks like three more not a blocker votes.
(In reply to Chris Murphy from comment #5) > https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject. > org/thread/CU7KVIXQG3OWE45TOKLAX7S4VE73OKVZ/ > > Looks like three more not a blocker votes. Marking as Rejected blocker based on feedback from desktop ml.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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' of '29'. 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 29 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 message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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' of '31'. 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 31 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.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
It's still broken in F33...
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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' of '33'. 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 33 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 message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Still Happening in Fedora 37 Can somebody reopen it? Could it be re-assigned too? It seems it hasn't been looked at for a while.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days