Ubuntu
gnome-settings-daemon package

Inconsistent behavior for some keyboard shortcuts: user is able to bind them, but pressing them does nothing

Bug #1064345 reported by Andrei Dziahel
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Repro:

1. Set 'Launch media player' shortcut to <Super>XF86Play (media key with "Play" icon on it) (either with GUI, either with `gsettings set org.gnome.settings-daemon.plugins.media-keys media '<Super>XF86AudioPlay'`)
2. Press just assigned shortcut key.

What happens: nothing.
What is expected: default media player is launched.

This affects shortcuts like'<Super>XF86Back' and '<Super>XF86Forward' as well.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.4.2-0ubuntu0.4
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Tue Oct 9 14:50:23 2012
EcryptfsInUse: Yes
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=gnome-256color
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Andrei Dziahel (develop7) wrote :
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
Andrei Dziahel (develop7)
tags: added: quantal
Revision history for this message
Andrei Dziahel (develop7) wrote :

is there any additional info I can provide to get this bug fixed?

Revision history for this message
Andrei Dziahel (develop7) wrote :

UPD: Remapping "Lock screen" action to "<Super>L" does nothing too (just prints "l" in current input).

Revision history for this message
Andrei Dziahel (develop7) wrote :

Is there any way I can improve this bugreport? Or any clues where I should start investigating?

Revision history for this message
Andrei Dziahel (develop7) wrote :

Replacing <Super> with <Mod4> got this fixed.

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.