This bug was fixed in the package gnome-settings-daemon - 3.8.5-0ubuntu8
---------------
gnome-settings-daemon (3.8.5-0ubuntu8) saucy; urgency=low
* debian/patches/fix_media_keys_on_unity.patch: Don't rely on
org.gnome.ScreenSaver as this might not be available (it's only a
recommends of ubuntu-desktop). Use the names owned by (critical components
of) the DEs themselves instead. (LP: #1237564)
-- Iain Lane <[email protected]> Wed, 16 Oct 2013 09:39:12 +0100
** Changed in: gnome-settings-daemon (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1237564
Title:
Regression: some previous keyboard bindings & all newly created
custom bindings fail if gnome-screensaver isn't installed
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
Bug description:
[ Description ]
gnome-settings-daemon 3.8.5-0ubuntu7 used the presence of
org.gnome.ScreenSaver on the session bus to decide whether to activate
the media keys plugin (used for volume up/down, skipping tracks,
brightness and so on).
This package is only a Recommends of ubuntu-desktop. It's an
undeclared dependency which isn't actually necessary.
[ Proposed fix ]
Check for org.gnome.Panel (for gnome-panel environments) and
com.canonical.Unity (for Unity environments). Unity also provides
org.gnome.Shell so check $DESKTOP_SESSION in that handler to only run
in a real gnome-shell session.
[ Test case ]
Remove the gnome-screensaver package. In a gnome-panel based or a
Unity session, launch gnome-settings-daemon. Make sure your media keys
work with the update.
[ Regression potential ]
This changes activation of a plugin. There's a chance it could be
wrong.
If it doesn't work, make sure the plugin is enabled:
$ gsettings get org.gnome.settings-daemon.plugins.media-keys active
and then run
$ gnome-settings-daemon --debug --replace | tee /tmp/g-s-d.log
wait 5 seconds, try pressing some media keys, then attach
/tmp/g-s-d.log
[ Original report ]
With the latest g-s-d any custom key-bindings fail as do some 'default* ones
(system
Test cases -
remove gnome-screensaver
open keyboard panel > shortcuts> system
change Log out to a new binding
log out/in thru indicator-session
Try the new binding, nothing happens
open keyboard panel > shortcuts> custom
create a new binding for some command
log out/in
use binding, nothing happens
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu7
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct 9 14:03:35 2013
InstallationDate: Installed on 2013-10-03 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002)
MarkForUpload: True
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1237564/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
