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 789334 - <super>F1 binding in control center (unhardcode!)
<super>F1 binding in control center (unhardcode!)
Status: RESOLVED DUPLICATE of bug 792892
Product: gnome-settings-daemon
Classification: Core
Component: media-keys
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
: 789335 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-10-23 04:17 UTC by slyhisky
Modified: 2018-01-25 09:35 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22



Description slyhisky 2017-10-23 04:17:42 UTC
In Debian 9, Ubuntu 17.04, 17.10 Gnome 3.22.2 and 3.26.1 

I can't change keybinding for <super>F1 

It is very common shortcut for me, because I can easily reach in by only left hand while use mouse.

It is probably hardcoded after https://bugzilla.gnome.org/show_bug.cgi?id=764220

Please, delete hardcoded binding and just add default changeable binding in control center.

Thank you!
Comment 1 slyhisky 2017-10-23 05:40:56 UTC
I can bind Super+F1 to some standard actions, that placed at «org.gnome.desktop.wm.keybindings» (thats a guess, just tried maximize-window) and it works correctly, but if i try to set S+F1 for custom user-created shortcuts and some more, like «launch calculator» (placed at org.gnome.settings-daemon.plugins.media-keys), it doesnt work, instead i got Help opened.

That's really confusing. It should be fixed.
Comment 2 André Klapper 2017-10-23 08:48:44 UTC
*** Bug 789335 has been marked as a duplicate of this bug. ***
Comment 3 Bastien Nocera 2018-01-24 13:56:42 UTC
We can't change it as it would break a number of laptops.

See https://bugzilla.gnome.org/show_bug.cgi?id=651571#c29 about a possible way to fix this.

*** This bug has been marked as a duplicate of bug 764220 ***
Comment 4 slyhisky 2018-01-24 14:37:33 UTC
This is not " duplicate of bug 764220 " !
it is opposite of it!

Bug 764220 is solved, but behavior, from this bug
https://bugzilla.gnome.org/show_bug.cgi?id=789334 
is still here!

And again, if it so important for some laptops, please, add switch, so other can disable this behavior.
Why other users should suffer from it?

Thank you!
Comment 5 Bastien Nocera 2018-01-24 15:29:53 UTC
You're right, wrong duplicate bug.

bug 651571 is the closest one to this, with an explanation as to how we'd make those keys configurable on hardware that doesn't use those shortcuts.

*** This bug has been marked as a duplicate of bug 651571 ***
Comment 6 slyhisky 2018-01-24 16:19:20 UTC
It is not looks like duplicate.

If bug 651571 ever will solved, I don't sure you will automatically solve this one.

I really love Gnome for user-friendly interface and simplicity, and understand what different users want different features and it is too complex to add settinds for each wish... But ... 

We already have nice feature what rebind keys and it works good.

I think hardcode bind of some settings in some cases is a bit overhead.
Instead we can just user this as default (changeable) setting, why not?


Thanks!
Comment 7 Bastien Nocera 2018-01-24 16:28:16 UTC
It is a duplicate, the same process to fix bug 651571 would also fix this one.

*** This bug has been marked as a duplicate of bug 651571 ***
Comment 8 Bastien Nocera 2018-01-24 16:31:50 UTC
(In reply to slyhisky from comment #6)
> It is not looks like duplicate.
> 
> If bug 651571 ever will solved, I don't sure you will automatically solve
> this one.
> 
> I really love Gnome for user-friendly interface and simplicity, and
> understand what different users want different features and it is too
> complex to add settinds for each wish... But ... 
> 
> We already have nice feature what rebind keys and it works good.
> 
> I think hardcode bind of some settings in some cases is a bit overhead.
> Instead we can just user this as default (changeable) setting, why not?

And I'm not going to add more configuration when this can be solved without making it configurable. Somebody has to take the lead and start the work on adding metadata about those machines to systemd/hwdb, as mentioned in the duplicate.
Comment 9 slyhisky 2018-01-24 16:55:36 UTC
Sounds great...  but bug 651571 is WONTFIX...

Should I change it status?

How somebody will fix it of bug mark as resolved?
Comment 10 slyhisky 2018-01-24 16:56:32 UTC
* if bug mark as resolved?
Comment 11 slyhisky 2018-01-24 17:04:44 UTC
And in addition.
Ok, then, maybe somebody will implement the vendor-specific solution.
If I own mentioned laptop, why can't I change keybindings?
What if I don't need to user vendor-specific hardware buttons?
Comment 12 Bastien Nocera 2018-01-25 09:28:11 UTC
Here you go.

*** This bug has been marked as a duplicate of bug 792892 ***
Comment 13 slyhisky 2018-01-25 09:35:46 UTC
Thank you!