This bug was fixed in the package gnome-settings-daemon -
3.24.2-0ubuntu0.1
---------------
gnome-settings-daemon (3.24.2-0ubuntu0.1) zesty; urgency=medium
* New upstream release (LP: #1689610)
- Fix gdm starting with no plugins which broke Hi-DPI support
on the login screen (LP: #1685035)
- Fix brightness control in some dual-GPU computers (LP: #1683445)
- Own the D-Bus name that the API documentation tells users of the
multimedia keys API they should use (org.gnome.SettingsDaemon.MediaKeys),
in addition to the D-Bus name that they actually use in practice
(org.gnome.SettingsDaemon). (LP: #1686077)
* Add revert-disable-rfkill-keys-handling.patch:
- Revert commit that disabled GNOME's rfkill handling. Although
this fixes problems for some users, it makes things worse for
other people.
-- Jeremy Bicha <jbi...@ubuntu.com> Tue, 09 May 2017 14:05:29 -0400
** Changed in: gnome-settings-daemon (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1686077
Title:
Own org.gnome.SettingsDaemon.MediaKeys D-Bus name too
Status in GNOME Settings Daemon:
Fix Released
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Status in unity-settings-daemon package in Ubuntu:
Triaged
Status in gnome-settings-daemon source package in Xenial:
Triaged
Status in unity-settings-daemon source package in Xenial:
Triaged
Status in gnome-settings-daemon source package in Yakkety:
Triaged
Status in unity-settings-daemon source package in Yakkety:
Triaged
Status in gnome-settings-daemon source package in Zesty:
Fix Released
Status in unity-settings-daemon source package in Zesty:
Triaged
Status in gnome-settings-daemon package in Debian:
Fix Released
Bug description:
Impact
======
This bugfix enabled gnome-settings-daemon's multimedia key support to work
according to what the API has said for years (in addition to the way it's been
commonly used).
https://git.gnome.org/browse/gnome-settings-
daemon/commit/?h=gnome-3-24&id=42f75ed4cdc86498d6e02e511a1314b8916bd4aa
https://mail.gnome.org/archives/desktop-devel-
list/2017-April/msg00069.html
The SRU justification is that newer versions of apps will be switching
to the D-Bus name in the API documentation. If someone installs the
newer version from a PPA or a Flatpak or Snap, the multimedia key
support should continue working.
Test Case
=========
Install this update on Ubuntu GNOME.
Reboot
Install d-feet then run d-feet
Switch to the session tab.
Type 'settings' into the search box.'
In the list of results there should be both org.gnome.SettingsDaemon and
org.gnome.SettingsDaemon.MediaKeys with cmd:
/usr/lib/gnome-settings-daemon/gsd-media-keys
Regression Potential
====================
This should just make gnome(unity)-settings-daemon own both the commonly used
D-Bus name and the one actually defined in the API docs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686077/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
