Package: dbus
Version: 1.14.0-1
Severity: normal
X-Debbugs-Cc: flyingsta...@gmail.com
Dear Maintainer,
My system does not react to Volume Up/Down/Mute events, but still reacts to
Play/Pause/Previous/Next.
Trying to trace the event I checked GNOME keybindings; the UI recognizes the
Audio Raise/Lower/Mute Volume inputs when binding the keys, but nothing happens
when I try to use them; xev does not recognize any XF86Audio* events (volume or
play/pause/etc.).
>From dbus-monitor I noticed that Play/Pause/Previous/Next events are recorded
>as (this is "Pause"):
signal time=1654019599.276609 sender=:1.37 -> destination=:1.63 serial=7245
path=/org/gnome/Shell; interface=org.gnome.Shell; member=AcceleratorActivated
uint32 134
array [
dict entry(
string "timestamp"
variant uint32 179801356
)
dict entry(
string "action-mode"
variant uint32 1
)
dict entry(
string "device-node"
variant string "/dev/input/event4"
)
]
method call time=1654019599.276955 sender=:1.63 -> destination=:1.202
serial=366 path=/org/mpris/MediaPlayer2;
interface=org.mpris.MediaPlayer2.Player; member=PlayPause
method return time=1654019599.277245 sender=:1.202 -> destination=:1.63
serial=396 reply_serial=366
signal time=1654019599.304921 sender=:1.202 -> destination=(null destination)
serial=397 path=/org/mpris/MediaPlayer2;
interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.mpris.MediaPlayer2.Player"
array [
dict entry(
string "PlaybackStatus"
variant string "Paused"
)
]
array [
]
but Volume manipulation inputs do not generate MPRIS events (uint 186 is raise
volume, 183 is lower volume. Neither is followed by the corresponding MPRIS
message):
signal time=1654019648.231914 sender=:1.37 -> destination=:1.63 serial=7251
path=/org/gnome/Shell; interface=org.gnome.Shell; member=AcceleratorActivated
uint32 186
array [
dict entry(
string "timestamp"
variant uint32 179850312
)
dict entry(
string "action-mode"
variant uint32 1
)
dict entry(
string "device-node"
variant string "/dev/input/event4"
)
]
signal time=1654019648.583477 sender=:1.37 -> destination=:1.63 serial=7252
path=/org/gnome/Shell; interface=org.gnome.Shell; member=AcceleratorActivated
uint32 183
array [
dict entry(
string "timestamp"
variant uint32 179850664
)
dict entry(
string "action-mode"
variant uint32 1
)
dict entry(
string "device-node"
variant string "/dev/input/event4"
)
]
Changing volume via `playerctl volume` works; I wrote a script to leverage it
and change volume via GNOME keybindings, but that didn't work either (same
issue: running the script manually works, but trying to get the media keys to
call the script doesn't).
I tried two different keyboards, with the same outcome.
Hope this can be fixed (and that it's actually dbus doing this - sorry if I
misfiled!).
Thanks!
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing'), (499, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-1-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dbus depends on:
ii dbus-bin 1.14.0-1
ii dbus-daemon 1.14.0-1
ii dbus-system-bus-common 1.14.0-1
ii init-system-helpers 1.63
ii libc6 2.33-7
ii libdbus-1-3 1.14.0-1
ii libexpat1 2.4.8-1
ii libsystemd0 250.4-1
dbus recommends no packages.
Versions of packages dbus suggests:
ii dbus-user-session [default-dbus-session-bus] 1.14.0-1
ii dbus-x11 [dbus-session-bus] 1.14.0-1
Versions of packages dbus is related to:
ii dbus-x11 1.14.0-1
ii systemd 250.4-1
ii systemd-sysv 250.4-1
-- no debconf information
