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 773005 - Super & Fn shortcuts not working, "Could not find accelerator for accel id X"
Super & Fn shortcuts not working, "Could not find accelerator for accel id X"
Status: RESOLVED DUPLICATE of bug 758302
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
: 773020 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2016-10-15 23:53 UTC by soren121
Modified: 2016-10-25 08:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description soren121 2016-10-15 23:53:21 UTC 
My Super-key shortcuts and Fn volume control shortcuts no longer work after upgrading to 3.22.

For example, when I press Super+W (which I've mapped to "Launch web browser" in Keyboard settings), my web browser does not start, but the message "gnome-settings-[3225]: Could not find accelerator for accel id 100" appears in journalctl. 

If I set the shortcut to Ctrl+W however, it works fine, so it seems that it's only Super + any key that's broken.

The same message appears if I press Fn+F2 (volume down on my keyboard) with the ID 129. Fn+F3 (volume up) results in ID 130.

Using Gnome 3.22.1 on Arch Linux.
Comment 1 Bastien Nocera 2016-10-16 00:48:15 UTC 
This isn't related to the Super key, unfortunately.

See bug 758302 where we've been trying to track this down for a while. Pressing "Alt+F2" and entering "r" as the command should "fix it".

*** This bug has been marked as a duplicate of bug 758302 ***
Comment 2 Bastien Nocera 2016-10-16 12:37:45 UTC 
*** Bug 773020 has been marked as a duplicate of this bug. ***
Comment 3 Christian Stadelmann 2016-10-24 18:26:42 UTC 
I'm running into this bug too. It is not limited to the super key. Anyway, I don't have a monitor to hotplug, this even happens on a simple cold boot so I doubt this really is a duplicate of bug #758302. Or the "cause"/condition of bug #758302 has been misidentified.

I haven't seen this bug in months, it is just happening after the 3.22 release but didn't happen on 3.21.9x.

Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1388208
Comment 4 Bastien Nocera 2016-10-25 08:32:34 UTC 
(In reply to Christian Stadelmann from comment #3)
> I'm running into this bug too. It is not limited to the super key. Anyway, I
> don't have a monitor to hotplug, this even happens on a simple cold boot so
> I doubt this really is a duplicate of bug #758302.

It is.

> Or the "cause"/condition
> of bug #758302 has been misidentified.

That's what happened for the original reporter.

> I haven't seen this bug in months, it is just happening after the 3.22
> release but didn't happen on 3.21.9x.

I also doubt it.

> Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=1388208