Description of problem: When dragging an item, pressing escape should cancel the drag, leaving the dragged item where it was. But in F33, it completes the drag. I'm not sure if this is GTK's fault, but it happens across multiple applications. However, it is also happens in gnome-shell, dragging app icons in the overview, and I'm mot sure if GTK manages those drags. Version-Release number of selected component (if applicable): gtk3-3.24.23-1.fc33.x86_64 How reproducible: Always Steps to Reproduce: 1. In Nautilus, start dragging a file. 2. While holding the dragged file over a valid drop target (e.g. a folder or another window), press the Escape key. Actual results: The dragged file is dropped on the target, so if you held it over a folder the file is moved there; if you held it over a Text Editor window, the file is opened in that window, etc. Expected results: The drag is cancelled. Additional info: This applies specifically to the hardware Escape key. I have Caps Lock set to "Make Caps Lock an additional Esc", and pressing Caps Lock cancels the drag as expected but pressing Esc completes the drag as described under Actual Results. I guess that makes it a workaround. The bug is still present with this key remapping disabled.
Not reproducing this with gtk 3.24.28. Hitting Escape cancels my drags.
I'm no longer reproducing this in Nautilus or other plain-GTK software either. However, it's still the case in Gnome Shell. Steps to reproduce: 1. Start dragging an app icon from the dock to the window area (which would normally launch the app or open a new window). 2. While still holding the icon, press the Escape key. The overview closes and launches the app. Expected: the drag is cancelled, leaving the app un-launched and the overview open. This bug does seem to be entirely fixed in F34Beta, at least when running inside a VM, though.
I'm experiencing the same behavior with Paperwork 2.0.2 (flatpak) in Fedora 34 and opened an issue at https://gitlab.gnome.org/World/OpenPaperwork/paperwork/-/issues/988 GTK version is 3.24.29.
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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.