Bugzilla – Bug 829076
[Pulseaudio startup fail] - running progams (such as Yast) through xdg-su changes owner of /run/user/*/pulse
Last modified: 2014-01-09 15:04:21 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 running programs - especially yast2 - through xdg-su changes the owner of /run/user/$ID/pulse (and possibly other folders under /run/user/$ID/) to root. this causes pulseaudio to fail with the message: E: [autospawn] core-util.c: Failed to create secure directory (/run/user/1001/pulse): Permission denied W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock manually changing the owner back to the user fixes this. depending on the program running through xdg-su this may effect other folders in /run/user/$ID - such as dconf and gvfs - too. this affects all Yast2 desktop files in /usr/share/applications/YaST2/ Reproducible: Always Steps to Reproduce: 1. xdg-su -c "yast2 sw_single" 2. enter correct pw and press enter Actual Results: E: [autospawn] core-util.c: Failed to create secure directory (/run/user/1001/pulse): Permission denied W: [autospawn] lock-autospawn.c: Cannot access autospawn lock. E: [pulseaudio] main.c: Failed to acquire autospawn lock Expected Results: no owner change
This sounds more like a generic issue in xdg-su, not specific to PA. Jiri, could you take a look?
I don't see it with KDE. What DE do you use?
The best would be to attach the output of sh -xx xdg-su -c "yast2 sw_single"
i(In reply to comment #2) > I don't see it with KDE. What DE do you use? at first i thougt with gnome too, but after some deeper looking it's only affecting e17.
if Sebastian is using my modified version of xdg-utils, evil things may happen. But I'll have a look on that after vacation. Thanks for the report.
Tomas i didn't realise there was a patched version of xdg-utils in the e17 repo. but i'll tried standard one and its the same. so the problem is both with gnomesu and when running through xterm.
Thank you for confirmation. If it is not related to my modified version, the same behaviour should appear in any non KDE/GNOME/XFCE DE.
Isn't this same issue as bnc#852015?
Yes, looks so. It was fixed in 13.1 but not for 12.3. The backport isn't too trivial as pam_systemd code has been changed a lot, unfortunately...
. *** This bug has been marked as a duplicate of bug 852015 ***