After pulseaudio restart, volume keys no longer work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Studio |
Won't Fix
|
Undecided
|
Unassigned | ||
xfce4-volumed (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
# Context
Asus n55sf laptop using Xubuntu 13.10.
Dedicated volume keys on the side of the keyboard work out-of-the-box.
# How to reproduce
(Next sentence is not the problem but the steps to reproduce!)
Sometimes pulseaudio is interrupted (e.g. restarted for some reason, for example with `pulseaudio -k`). Sometimes pulseaudio crashes and is automatically restarted thus sound works again.
To reproduce the problem either kill pulseaudio or issue pulseaudio -k.
# Expected behavior
* pulseaudio works again
* volume keys work just like after login: notification shows volume bar with changing value, audio volume heard actually changes
# Observed behavior (problem)
* pulseaudio works again (ok)
* volume keys don't work: no notification, no volume change (problem).
# Workaround
* One workaround is to logout/login.
* Another, simpler, workaround: killall xfce4-volumed ; xfce4-volumed
# Additional information
When bug happens, xfce4-volumed is still present. When pulseaudio stops, xfce4-volumed outputs:
(xfce4-
) = 151
After that xfce4-volumed still receives volume keys event and reacts, as shown by strace, but produces no notification or actual volume change.
lsb_release -rd
Description: Ubuntu 13.10
Release: 13.10
LC_ALL=C apt-cache policy xfce4-volumed
xfce4-volumed:
Installed: 0.2.0-0ubuntu1
Candidate: 0.2.0-0ubuntu1
Version table:
*** 0.2.0-0ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xfce4-volumed 0.2.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Thu Mar 13 09:31:24 2014
MarkForUpload: True
SourcePackage: xfce4-volumed
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in ubuntustudio: | |
status: | New → Confirmed |
Status changed to 'Confirmed' because the bug affects multiple users.