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 703400 - ALT+F5 invokes dangerous & irreversible program xkill, should not be on a kb shortcut
ALT+F5 invokes dangerous & irreversible program xkill, should not be on a kb ...
Status: RESOLVED FIXED
Product: gparted
Classification: Other
Component: livecd
0.16.1
Other Windows
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2013-07-01 15:51 UTC by olivers-h
Modified: 2016-04-29 05:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description olivers-h 2013-07-01 15:51:03 UTC
This shortcut should be removed or changed to something more obscure.

ALT+F5 is adjacent to many safe commands like FN+F5 (brightness control on some laptops) and ALT+F4. It is easily accidentally pressed.

In the gparted livedisk it runs xkill on the focused window. Xkill is not reversible. Xkill runs without any confirmation and does not give the user any clue as to what it has done. Xkill results in partition corruption & wasted time if it kills gparted while in the middle of an operation.
Comment 1 hegyre 2016-04-24 21:20:50 UTC
Content of file /home/user/.fluxbox/keys :
 
# current window commands
Mod1 F4 :Close
Mod1 F5 :Kill
Mod1 F9 :Minimize
Mod1 F10 :Maximize
Mod1 F11 :Fullscreen

I agree with Olivers-h, this key combination can be dangerous, especially when pressed accidentally when performing gparted jobs...

My thought is to remove the line Mod1 F5 :Kill from the config file by default, or at least, comment it.

If we really have to kill an application, then we can do it via terminal  using command kill or killall.

Regards,
hegyre
Comment 2 Steven Shiau 2016-04-29 05:42:47 UTC
Thanks for the suggestion. This hotkey is disabled in GParted live 0.26.0-1.
If any problem, please reopen this bug.
Thanks.

Steven