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 794385 - Keyboard shortcuts stop functioning
Keyboard shortcuts stop functioning
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
3.28.x
Other Linux
: Normal major
: ---
Assigned To: Rui Matos
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2018-03-15 23:00 UTC by Dustin Krysak
Modified: 2019-03-20 11:54 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dustin Krysak 2018-03-15 23:00:22 UTC
Ubuntu Budgie 18.04 Beta 1
gnome-settings-daemon 3.28.0-0ubuntu1 amd64

Good day, I'm having an issue where some keyboard shortcuts will just stop functioning.

* Some of these are custom defined, some are defaults.
* While some will not function, others will (both custom and system).
* I suspect it is after the system had suspended (but not confirmed).
* ps aux | grep settings shows that keyboard, etc are still running

(snip)

```
dustin    4740  0.0  0.0 274868  5840 ?        Sl   08:29   0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard

```

* Post reboot things will operate for a time until I notice that the keyboard shortcuts no longer function.
* Poking around in syslog

```
cat syslog | grep keyboard
Mar 15 15:30:32 bashfulrobot dbus-daemon[1225]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000 pid=11141 comm="gnome-control-center keyboard " label="unconfined")
Mar 15 15:48:50 bashfulrobot dbus-daemon[1225]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.135' (uid=1000 pid=5844 comm="/usr/lib/gnome-settings-daemon/gsd-keyboard " label="unconfined")
```

* Seems to be nothing mind-blowing there.

I'm not super familiar with GSD, so please let me know what additional info you may need.

Dustin
Comment 1 Dustin Krysak 2018-03-15 23:14:41 UTC
I just tried to narrow down the suspected hibernate/suspend issues. So far neither trigger the issue. Post reboot, shortcuts continue to function thus far. Will continue to try and narrow down if there is a pattern when this issue starts.
Comment 2 Dustin Krysak 2018-03-16 03:08:57 UTC
Additional note - I just had it happen with a fresh boot. I literally had opened a browser and then tried to use a shortcut... no, go.
Comment 3 Dustin Krysak 2018-04-14 16:14:48 UTC
I just found out another detail quite by accident.

My system is set up to use the "fn" key to make the F buttons behave as an f button (F1-12). Meaning by default a press will trigger the volume up/down, etc.

So when the audio keys conk out... my other f key functions (brightness, etc) still work. BUT, if I hold "alt", and press my audio keys - they work!

Now knowing this pattern, - I went through my F keys... and tested what worked (brightness, audio, mute, search)

- F1 (mute) - "F1" works with the "fn" key, and the mute only works when also pressing "alt"
- F2 (vol down) - "F2" works with the "fn" key, and the vol down only works when also pressing "alt"
- F3 (vol up) - "F3" works with the "fn" key, and the vol up only works when also pressing "alt"
- F4 (disable mic) - Works as expected.
- F5 (bright down) - Works as expected.
- F6 (bright up) - Works as expected.
- F7 (projector) - Untested.
- F8 (airplane mode) - Works as expected.
- F9 (tools) - Does not work in any capacity
- F10 (Search) - "F10" works with the "fn" key, and the search only works when also pressing "alt"
- F11 (launchA) - Works as expected.
- F12 (open file browser) - Works as expected.
Comment 4 GNOME Infrastructure Team 2019-03-20 11:54:06 UTC
-- 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/389.