| Summary: | Pulseaudio produces only one sound output with multiple applications running | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dimitris Tsiamasiotis <dtsiamasiotis> |
| Component: | RPM Packages | Assignee: | Colin Guthrie <mageia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | pulseaudio | CVE: | |
| Status comment: | |||
|
Description
Dimitris Tsiamasiotis
2011-03-28 20:19:55 CEST
It's probably related to flash in fact. Could you reproduce when using for example amarok & dragon player ? CC:
(none) =>
balcaen.john Attach to this report, the .txt file resulting from executing: pacmd ls > /tmp/pacmd.txt Keywords:
(none) =>
NEEDINFO I can reproduce it using amarok and vlc at the same time. Pacmd says "No PulseAudio daemon running, or not running as session daemon." . Pulseaudio is enabled in control center and when I start pulseaudio volume control it says "Establishing connection to Pulseaudio.Please wait..." and nothing happens. (In reply to comment #3) > I can reproduce it using amarok and vlc at the same time. Pacmd says "No > PulseAudio daemon running, or not running as session daemon." . Pulseaudio is > enabled in control center and when I start pulseaudio volume control it says > "Establishing connection to Pulseaudio.Please wait..." and nothing happens. How are you: a) running pavucontrol (as your user or as root?) b) checking for PA running (ps aux | grep pulse?) When running applications and such like you should run them as the same user as is running PA. Please provide the output of: 1. ps aux | grep pulse 2. PULSE_LOG=99 pactl stat Thanks. I run pavucontrol as a normal user. ps aux|grep pulse outputs this dimitris 14238 0.0 0.0 4276 728 pts/1 S+ 15:11 0:00 grep --color pulse PULSE_LOG=99 pactl stat outputs this Using shared memory pool with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum usable slot size is 65496 Trying to connect to /home/dimitris/.pulse/40ae0aa22e5ef2ea38eaad09000000b3-runtime/native... connect(): No such file or directory (2) Trying to connect to /home/dimitris/.pulse/native... connect(): No such file or directory (2) Trying to connect to /var/run/pulse/native... connect(): No such file or directory (2) Trying to connect to tcp4:127.0.0.1... connect(): Connection refused Trying to connect to tcp6:[::1]... connect(): Connection refused Trying to autospawn... D: caps.c: Cleaning up privileges. Connection failure: Connection refused This is very strange. It suggests that ~/.pulse/ folder (or perhaps the /tmp or $HOME/tmp) folder is cleaned out after you launch pulseaudio for the first time. I suspect that /home/dimitris/.pulse/40ae0aa22e5ef2ea38eaad09000000b3-runtime exists and is a symbolic link pointing to a folder in ~/tmp (or - less likely - /tmp) that is ultimately cleaned by some other process/system somewhere. I don't think this is a default thing to do, so it would be worth looking to see if this is some kind of housekeeping task that you perform manually or something? But I suspect strongly that this is the issue at hand. Colin you're right, I see a pulse-... folder in /tmp but it's empty and it shouldn't. I ran lsof to that folder but it returned nothing. Maybe those two files that are supposed to be found in that folder are never created? I'm pretty sure that the files in that folder will have been created properly but subseuqently deleted.... the code in PA has to bind to the the socket file for the startup to succeed. You can try: killall pulseaudio and then it should autospawn again automatically (best to start it manually with start-pulseaudio-x11 too to set certain properties on the root X11 window...) You need ot use the killall rather than the more graceful "pulseaudio -k" as the latter needs the socket to work to ask the daemon to exit gracefully! This might recreate a different /tmp/pulse-* folder so make sure you check them all. If this seems to work, then I think something else is to blame... perhaps msec cleaning out /tmp too rigorously or similar? Out of curiosity is your home direction strange in any way? Normally $TMPDIR points to $HOME/tmp rather than /tmp. If NFS homedir then $TMPDIR is usually /tmp, so this could explain it but it would be nice to know why :) Cheers Pulseaudio was broken, so reinstalling it solved the problem. Colin thanks for your help. Yes, just for the record, this was a problem related to (I think) the installer. Draksound was used before PA was installed and thus it did some things which ultimately created the default.pa file (and a few others) when it shouldn't. When pulseaudio was actually installed, these dummy (empty) files prevented the installation of default.pa properly and thus prevented PA starting up. I need to look at draksound code to see if this can be made better/safer. (In reply to comment #10) > > I need to look at draksound code to see if this can be made better/safer. @ Colin Any news? Keywords:
NEEDINFO =>
(none) Oh sorry, I forgot to update this bug. Yes I made several changes to draksound: http://svnweb.mageia.org/soft/drakx/trunk/perl-install/harddrake/sound.pm?view=log (commits 1380, 1381, 1384, 1385, 1386) The actual fix to this problem was in 1384: http://svnweb.mageia.org/soft/drakx/trunk/perl-install/harddrake/sound.pm?r1=1381&r2=1384 I think therefore this bug can be resolved. Thanks for pinging me Marja :D Status:
NEW =>
RESOLVED |