Description of problem: Relatively often a situation arises when launched application displays errors as: Failed to create secure directory (/run/user/1000/pulse): Permission denied Failed to create secure directory (/run/user/1000/pulse): Permission denied ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect: Connection refused and audio isn't working. Relevant directory listing is then: $ ls -la /run/user/1000/ total 0 drwx------. 6 hanzlik hanzlik 120 Sep 6 18:09 . drwxr-xr-x. 4 root root 80 Oct 1 03:10 .. drwx------. 2 hanzlik hanzlik 60 Oct 25 15:27 dconf dr-x------. 2 hanzlik hanzlik 0 Jun 29 17:52 gvfs drwx------. 2 hanzlik hanzlik 40 Oct 26 01:05 .orc drwx------. 2 root root 80 Sep 8 13:48 pulse # ls -la /run/user/1000/pulse/ total 0 drwx------. 2 root root 80 Sep 8 13:48 . drwx------. 6 hanzlik hanzlik 120 Sep 6 18:09 .. srwxrwxrwx. 1 hanzlik hanzlik 0 Sep 8 13:48 dbus-socket srwxrwxrwx. 1 hanzlik hanzlik 0 Sep 8 13:48 native The problem may IMO occur when I run some application as root from X terminal (I'm using Xfce and usually MATE terminal) from window where I switch to root using 'su -' - but I'm not sure. Version-Release number of selected component (if applicable): # rpm -q pulseaudio systemd kernel-PAE dbus pulseaudio-3.0-10.fc19.i686 systemd-204-21.fc19.i686 kernel-PAE-3.14.8-100.fc19.i686 dbus-1.6.12-2.fc19.i686 (not sure which process manipulate with '/run/user/$UID/pulse' directory and its content) Expected results: '/run/user/$UID/pulse' UID and GID should be UID:GID of logged user. Additional info: It seems as something apply real/effective UID/GID at this directory, while it had to use login UID (or play at own stuff in '/run/user/0/pulse'?).
My best recommendation is to simply avoid the situation of running graphical apps via su. It can have many bad side-effects, this being one.
Of course, I normally do not do it and consider it as a security aberrance. But mostly I'm doing some things around PC maintenance and management, thus I have some xterm windows open where I'm switched as root and have e.g. Midnight Commander running - and this scamp sometimes starts a graphical application because it is associated with that file type, and so on. Or I'm too lazy to set permission to allow access for my user account or lazy to re-login/switch to new user. What You mean with "many bad side-effect", something other than possible intentional creating/changing files with root permissions? Anyway, I thing this should not be problem when desktop environment works correctly, thus I still consider this as bug.
>What You mean with "many bad side-effect", something other than possible >intentional creating/changing files with root permissions? mostly that ^^, affecting more than just /run/user/$UID/pulse ...
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.