media keys stopped working: "Could not find accelerator for accel id 123"

Bug #1659517 reported by Marius Gedminas
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Fix Released
Medium
gnome-settings-daemon (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Today after an involuntary reboot (laptop battery ran down) I can no longer use media keys like Mute, Volume Up/Down, PrintScreen.

Every time I hit one of those keys I see messages like this in journalctl:

  Sau 26 11:53:30 platonas gnome-settings-[4972]: Could not find accelerator for accel id 123

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gnome-settings-daemon 3.22.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jan 26 11:56:17 2017
InstallationDate: Installed on 2016-09-10 (138 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (102 days ago)

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Revision history for this message
Marius Gedminas (mgedmin) wrote :

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839958 looks like a similar bug, except my custom shortcuts (e.g. <super>t to launch gnome-terminal) continue to work fine.

Revision history for this message
Marius Gedminas (mgedmin) wrote :

I restarted gnome-shell with Alt-F2 r and media keys started working.

This is probably a duplicate of one of the other "media keys randomly stop working sometimes" bugs. I was searching for the particular error message and found none -- probably because the error message itself was only added relatively recently (in gnome-settings-daemon 3.20), while upstream tries to figure out what causes this bug.

I haven't located the upstream bug report yet.

Revision history for this message
Marius Gedminas (mgedmin) wrote :
Changed in gnome-settings-daemon:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in gnome-settings-daemon:
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue is fixed in the artful version

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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