Red Hat Bugzilla – Bug 611142
When connecting a usb-webcam, pulseaudio resets volumes to defaults
Last modified: 2011-06-27 15:23:45 EDT
Description of problem:
When i connect a webcam, pulseaudio resets all volume to its defaults, even if audio is currently playing.
Version-Release number of selected component (if applicable):
$rpm -qa| grep pulseaudio
Steps to Reproduce:
1. play audio over pulseaudio on low volume
2. connect a supported webcam to one USB-Port
3. Watch the Volume-Slider jumps to default and hear volume changing.
Volume is reset to defaults.
Volume stays on actual value.
==> messages <==
Jul 4 00:23:13 hurricane kernel: usb 2-4: new high speed USB device using ehci_hcd and address 5
Jul 4 00:23:13 hurricane kernel: usb 2-4: New USB device found, idVendor=046d, idProduct=0994
Jul 4 00:23:13 hurricane kernel: usb 2-4: New USB device strings: Mfr=0, Product=0, SerialNumber=2
Jul 4 00:23:13 hurricane kernel: usb 2-4: SerialNumber: 7099C410
Jul 4 00:23:14 hurricane kernel: uvcvideo: Found UVC 1.00 device <unnamed> (046d:0994)
Jul 4 00:23:14 hurricane kernel: input: UVC Camera (046d:0994) as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/input/input6
Jul 4 00:23:14 hurricane kernel: usbcore: registered new interface driver uvcvideo
Jul 4 00:23:14 hurricane kernel: USB Video Class driver (v0.1.0)
Jul 4 00:23:14 hurricane kernel: usbcore: registered new interface driver snd-usb-audio
==> Xorg.0.log <==
[ 1362.321] (II) config/udev: Adding input device UVC Camera (046d:0994) (/dev/input/event6)
[ 1362.323] (**) UVC Camera (046d:0994): Applying InputClass "evdev keyboard catchall"
[ 1362.323] (**) UVC Camera (046d:0994): Applying InputClass "system-setup-keyboard"
[ 1362.323] (**) UVC Camera (046d:0994): always reports core events
[ 1362.323] (**) UVC Camera (046d:0994): Device: "/dev/input/event6"
[ 1362.327] (II) UVC Camera (046d:0994): Found keys
[ 1362.327] (II) UVC Camera (046d:0994): Configuring as keyboard
[ 1362.327] (II) XINPUT: Adding extended input device "UVC Camera (046d:0994)" (type: KEYBOARD)
[ 1362.327] (**) Option "xkb_rules" "evdev"
[ 1362.327] (**) Option "xkb_model" "pc105"
[ 1362.327] (**) Option "xkb_layout" "de"
[ 1362.327] (**) Option "xkb_variant" "nodeadkeys"
[ 1362.327] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
==> messages <==
Jul 4 00:23:14 hurricane rtkit-daemon: Sucessfully made thread 2624 of process 1883 (/usr/bin/pulseaudio) owned by '500' RT at priority 5.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.