Some Media Keys (Not all) and custom keyboard shortcuts irregulary don't work after boot/reboot

Bug #1818978 reported by Bastian Baum
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
budgie-desktop (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Confirmed
Undecided
Unassigned
Cosmic
Confirmed
Undecided
Unassigned
Disco
Fix Released
Undecided
Unassigned

Bug Description

After boot or reboot some media keys (Volume Up/Down) don't work, but others do (e.g. Brightnes Up/Down). Custom Keyboard Shortcuts then don't work at all. When a non working media key oder shortcut is pressed the following message appears in syslog:

gsd-media-keys[2016]: Could not find accelerator for accel id 169

This happens irregulary. Sometimes everything works, sometimes it doesn't work as described above until next reboot.

This bug was first reported here: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/151 (And also here: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1817286 but important information is provided by first link)
Benjamin Berg, Maintainer of gnome-settings-daemon, found out it's related to budgies implementation of gsd-media-keys. Please look at this issue for logs and details. He even pointed out where the root issue might be (It seems like 'UngrabAccelerator' isn't implemented correctly)

I can only reproduce this bug inside budgie desktop enviornment, not inside an ubuntu gnome session installed via 'sudo apt-get install ubuntu-gnome-desktop'

Ubuntu Version: Ubuntu 18.04.2 LTS
gnome-settings-daemon Version: 3.28.1-0ubuntu1.1
Kernel: 4.18.0-15-generic
Architecture: amd64
CurrentDesktop: Budgie:GNOME 10.4

EDIT: Added Budgie Desktop Version
EDIT 2: Link added

Bastian Baum (protree)
description: updated
Bastian Baum (protree)
description: updated
Revision history for this message
fossfreedom (fossfreedom) wrote :

Thanks - I've raised this upstream for you

https://github.com/solus-project/budgie-desktop/issues/1763

no longer affects: ubuntubudgie
Revision history for this message
Bastian Baum (protree) wrote :

Thanks, I suscribed it

Changed in budgie-desktop (Ubuntu):
status: New → Confirmed
Revision history for this message
fossfreedom (fossfreedom) wrote :
Revision history for this message
Bastian Baum (protree) wrote :

Good to know! I only searched the web for the syslog-output which doesn't seem to be mentioned in this thread, so I didn't find it. It was hard to believe I am the only one affected. I will try it out, thanks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in budgie-desktop (Ubuntu Bionic):
status: New → Confirmed
Changed in budgie-desktop (Ubuntu Cosmic):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package budgie-desktop - 10.5~git20190308-0ubuntu1

---------------
budgie-desktop (10.5~git20190308-0ubuntu1) disco; urgency=medium

  * Bug fix release
    - Fix broken custom keyboard shortcuts
      gnome-3.32-compatibility.patch refreshed with fixes
    - Create mkrelease tarball with latest available translations
    - Fix for keyboard shortcuts occasionally stop working
      (LP: #1818978) cleanup-keygrab.patch
    - Add desktop-override.patch to ensure Budgie overrides do not
      impact other GNOME based desktop settings
    - Fix FTBFS due to incorrect Wnck WindowTypes
    - Refresh 0001-Polkit-Correctly-handle-the-user-dismissing-the-auth.patch
      due to changes to the gnome-3.32-compatibility.patch
    - Start GNOME Calendar in normal window on launch - not maximised

 -- David Mohammed <email address hidden> Sat, 09 Mar 2019 23:32:08 +0000

Changed in budgie-desktop (Ubuntu Disco):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.