Unity

Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly after logging

Bug #1482181 reported by Will Cooke
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Unity
Triaged
Undecided
Unassigned
unity (Ubuntu)
Triaged
Undecided
Unassigned
unity-settings-daemon (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I've installed 15.10 and I can't open a terminal using ctrl-alt-t or use any other media keys. All system shorcuts as well don't work.

Note that this started at least in 14.10.

Restarting Unity "fixes" it (or logging out/logging back), so it seems a race between Unity and settings daemon at startup.

See original description
Revision history for this message
Will Cooke (willcooke) wrote :

This looks like a race condition. It works now?!

Didier Roche-Tolomelli (didrocks)
summary: - ctrl-alt-t doesn't open the terminal on a fresh 15.10 install
+ Media keys (ctrl-alt-t, brightness, play/pause) don't work randomly
+ after logging
description: updated
no longer affects: unity-settings-daemon
Changed in unity:
status: New → Triaged
Changed in unity (Ubuntu):
status: New → Triaged
Changed in unity-settings-daemon (Ubuntu):
status: New → Triaged
Will Cooke (willcooke)
tags: added: rls-w-incoming
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

I'm getting it for a couple of releases. It was one on 10 login before. It seems recently, it's one every 4 of them, so quite high in term of frequency.

monitoring and pressing a media key gives:
signal time=1443171424.483295 sender=:1.28 -> destination=(null destination) serial=7116 path=/org/gnome/Shell; interface=org.gnome.Shell; member=AcceleratorActivated
   uint32 33
   uint32 0
   uint32 9782134

So, the signal is sent.

I checked, and I have u-s-d running.

Revision history for this message
Lars Karlitski (larsu) wrote :

Problem figured out by Trevinho and didrocks on irc: unity only emits AcceleratorActivated() for the first id returned by GrabAccelerator() and doesn't watch the unique name of the grabbing process. Thus, when something other than unity-settings-daemon grabs the key before it, or u-s-d crashes, those keys it grabbed at the very beginning can never be regrabbed.

After a couple of rounds of testing and some code review, I can't make unity-settings-daemon subscribe to the same accelerator twice and thus getting into that situation itself. Feel free to reassign it to u-s-d once unity is fixed but this problem still persists.

Changed in unity-settings-daemon (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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