GNOME Bugzilla – Bug 792892
Limit hard-coded keybindings to affected devices
Last modified: 2019-03-20 11:52:57 UTC
From https://bugzilla.gnome.org/show_bug.cgi?id=651571#c29 : " The workaround were only applied on machines that need it. [...] That would need: - a udev rule, shipped by systemd, that would mark the /devices/virtual/dmi/id device as using that key, for affected machines. I'd start with all the Dell and HP machines: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477 - then, a work-around in gnome-settings-daemon to look for that tag, and only catch Win+P on those machines. I'll even go as far as writing the gnome-settings-daemon patch, but somebody else will have to drive those systemd/udev changes. I will still not make this configurable and strand users of Dell and HP laptops, sorry. See also: http://www.advogato.org/person/mjg59/diary.html?start=243 "
*** Bug 789334 has been marked as a duplicate of this bug. ***
*** Bug 651571 has been marked as a duplicate of this bug. ***
What's the reasoning behind not making Super+F1 configurable? It makes sense to launch help by default, after all that's what Windows does, but in my opinion it shouldn't be hardcoded. I use an HP laptop as my main workstation and i consider the help key useless, so i usually rebind it to something else. Sadly, this isn't possible in GNOME now that the shortcut is hardcoded, which annoys me a lot. Sure, the average user should expect the help key to launch a help program, but you shouldn't take away the possibility of rebinding such key, and i'm pretty sure i'm not the only one who considers the help key useless. The same applies for many other media keys, the user should always have the choice, it's stupid to have arbitrary restrictions like these, even Windows allows rebinding of media keys (by third-party programs, at least).
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/382.