So you removed the connection 7 seconds after, I assume, then waited
20-30 seconds, then killed pulseaudio.
( 7.587| 7.586) D: module-udev-detect.c: /dev/snd/controlC2 is
accessible: no
This probably indicates either a problem in alsa-lib when closing the
connection, or PA struggling with de
Further discovery. Once I have killed PA, as above, and relaunched it, I
cannot make it "rediscover" the USB sound card, even if I completely
remove ~./pulse
For the sound card to function again, I have to reboot.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launch
I also tried rebooting with the card disconnected. Then connected it
after login, then removed it. The same occurred as above.
I observed that memory use does not appear to be increasing while it
loops; I guess it's a loop.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://b
I rebooted with the USB sound card attached. Ubuntu sees this just fine.
I followed the instructions and attach the output. PA goes to 100%
immediately, within 1 second of removing the USB connection.
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio
auxbuss, thanks for reporting this bug. Could you please follow the
instructions on https://wiki.ubuntu.com/PulseAudio/Log when you provide the
log? In particular:
* skip this: sudo /etc/init.d/pulseaudio start - PA is already started
user-wide, so it's not necessary
* make sure the problem is r
I mean ~/.pulse
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
I forgot, I also deleted ~./pulse
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
To get restarted, I have to:
pulseaudio -D
killall gnome-volume
/usr/bin/gnome-volume-control-applet &
Seems to me that the last is a bug too. The applet disappears when
pulseaudio is killed, but remains in memory and doesn't reappear when
another pulseaudio instance is started.
--
pulseaudio
$ pulseaudio --start
N: main.c: User-configured server at
{c10255de8cac4c5c96d4ac784c091d51}unix:/home/marc/.pulse/c10255de8cac4c5c96d4ac784c091d51-runtime/native,
not autospawning.
--
pulseaudio process goes to 100% CPU and cannot be restarted
https://bugs.launchpad.net/bugs/636901
You receive
Attached is the result of:
echo autospawn = no >> ~/.pulse/client.conf
killall pulseaudio
LANG=C pulseaudio - > ~/pulseverbose.log 2>&1
pacmd set-log-time 1
sudo /etc/init.d/pulseaudio start
** Attachment added: "pulseverbose.log"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bu
10 matches
Mail list logo
