Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
There should be no differences in normal media keys usage between a version with and without this patch.
This patch is only useful for applications that want to be compatible with both the old (incorrect) and the new (as documented) APIs.
gdbus introspect --session --dest org.gnome.SettingsDaemon.MediaKeys --object-path /org/gnome/SettingsDaemon/MediaKeys
and:
gdbus introspect --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/MediaKeys
should return the same output, without errors (note the different "--dest" arguments).
You can also test against RHEL 7.2 version of gnome-settings-daemon, where the first command would fail, and the second would succeed.
In later versions of gnome-settings-daemon (such as the one that will be in Fedora 26), only the second one would succeed.
TEST SETUP 1
On VM running under RHEL 7.3 Workstation x86_64 Released,
with GNOME desktop environment.
TEST PROCEDURE 1
1. Log in to GNOME session.
2. Open a terminal
3. Issue the command:
gdbus introspect --session --dest org.gnome.SettingsDaemon.MediaKeys --object-path /org/gnome/SettingsDaemon/MediaKeys
It returns an error.
4. Issue the command:
gdbus introspect --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/MediaKeys
The command is OK.
TEST SETUP 2
On VM running under RHEL 7.4 Workstation x86_64 Beta,
with GNOME desktop environment.
TEST PROCEDURE 2
1. Log in to GNOME session.
2. Open a terminal
3. Issue the command:
gdbus introspect --session --dest org.gnome.SettingsDaemon.MediaKeys --object-path /org/gnome/SettingsDaemon/MediaKeys
The command is OK.
4. Issue the command:
gdbus introspect --session --dest org.gnome.SettingsDaemon --object-path /org/gnome/SettingsDaemon/MediaKeys
The command is OK.
RESULTS
Upgrading gnome-settings-daemon
from: 3.14.4-12.el7
to: 3.22.2-4.el7
has fixed the issue.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2096