Description of problem: xfce PulseAudio. Unable to connect: Timeout 2 minutes 20+ second timeout is too long. desktop performance very poor to non-existent until audio connection completes. Snippet from .xsession-errors Connection failure: Timeout ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Timeout ------------------------ pulseaudio is setup as a system daemon/service. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. setup system to have pulseaudio running as a system wide daemon/service. 2. put user in pulse-access and audio group 3. Reboot system 4. login and verify audio works with something like aplay /usr/lib64/libreoffice/share/gallery/sounds/applause.wav
Assignee: bugsquad => mageia
@Colin Getting performance delay when running KDE(Plasma) so not necessarily a Xfce problem. The pulseaudio connection timeout needs to be cut way down, say ~5 seconds. As soon as the pulseaudio 02:20+ connect timeout completes, mouse and window management activity performance go back to normal and next aplay audio test works. While I am waiting for Xfce desktop to complete startup/audio connection, I can click my browser desktop shortcut to run "sudo su - browser" where ~browser/.bash_profile launches Firefox. Click a youtube video and sound works immediately. Going to guess the keyboard/desktop performance will be traced back to systemd. I found lack of keyboard/desktop performance will also happen when systemd can not bring up the network. I have my system configured to use systemd.networking static ip with netmanager disabled. When I mistype the ip address during insall, typing/mouse response was terrible after reboot. I could ssh into the system, edit network files and reboot quicker than doing anything at the system desktop login. My guess is a problem in systemd dbus connection logic. No idea if other messages are being blocked or if dbus connection error logic goes into a tight loop with a long timeout or just preventing all other messages to get through in a timely manner.
Summary: 6_rc0: xfce PulseAudio. Unable to connect: Timeout 2 minutes 20+ second timeout is too long. => 6_rc0: PulseAudio. Unable to connect: Timeout 2 minutes 20+ second timeout is too long.
Is this a different bug than Bug 19228?
(In reply to David Walser from comment #2) > Is this a different bug than Bug 19228? Absolutely a different bug. That bug causes desktop launch time delay. This is a connect delay. I have also patched that bug with a klude which eliminates that delay. Xfce autostart apps now show up in ~5 seconds after hitting enter on password. This bug will only show up if you can not connect to a pulseaudio service. Not a lot of people running pulseaudio as a system service. Guessing the only time other users will hit this bug is after running 'su' and do something that causes ~/.config/pulse files to become owned by root. For what it's worth, mga5 has no problem connecting to pulseaudio as a system daemon. Now I wonder if I aught to open another bug report "Unable to connect to pulseaudio running as a daemon upon login. Second audio access connects to server. This bug is a show stopper for me.
Unable to connect to pulseaudio running as a system service/daemon after pulseaudio-9.0-1 update. What was working is now broke.
Source RPM: pulseaudio-8.0-5.mga6.src.rpm => pulseaudio-9.0-1.mga6.src.rpm
Timeout 2 minutes+ no longer occurs. Still not getting connection to pulseaudio when it is setup to run as a system wide service/daemeon.
Status: NEW => RESOLVEDResolution: (none) => FIXED