OK, hit this today. Never seen it before. I started to have weird problems with Google Hangout; the plugin failed to start on both
firefox and chromium. Manually starting the plugin from command line I got:
$ /opt/google/talkplugin/GoogleTalkPlugin
Failed to create secure directory (/run/user/1000/pulse): Permission denied
There I figured out there is something wrong with pulse:
$ pulseaudio --check
E: [pulseaudio] core-util.c: Failed to create secure directory (/run/user/1000/pulse): Permission denied
$ ls -lah /run/user/1000/
drwx------ 2 root root 100 elo 13 11:31 pulse
Removing the directory fixed the problem with GoogleTalk. I guess all the programs using pulse were affected.
Everything was working just fine yesterday. This morning I noticed my laptop had apparently run out of battery. Pluggin in the power chord and power up the machine it seemed that unity did not start straight away. I'm not sure what the failsafe error session looks like, but at least I first saw a bunch of undecorated problem report windows. So I would guess that the first session was run as root or something. Anyway after that the normal unity session started and I was greeted with this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1211674
So, could it be that at some error situation the X session is started as root and pulse somehow creates it's /run/user/1000/pulse with root permissions at situation like this?
OK, hit this today. Never seen it before. I started to have weird problems with Google Hangout; the plugin failed to start on both
firefox and chromium. Manually starting the plugin from command line I got:
$ /opt/google/ talkplugin/ GoogleTalkPlugi n 1000/pulse) : Permission denied
Failed to create secure directory (/run/user/
There I figured out there is something wrong with pulse: 1000/pulse) : Permission denied
$ pulseaudio --check
E: [pulseaudio] core-util.c: Failed to create secure directory (/run/user/
$ ls -lah /run/user/1000/
drwx------ 2 root root 100 elo 13 11:31 pulse
Removing the directory fixed the problem with GoogleTalk. I guess all the programs using pulse were affected.
Everything was working just fine yesterday. This morning I noticed my laptop had apparently run out of battery. Pluggin in the power chord and power up the machine it seemed that unity did not start straight away. I'm not sure what the failsafe error session looks like, but at least I first saw a bunch of undecorated problem report windows. So I would guess that the first session was run as root or something. Anyway after that the normal unity session started and I was greeted with this: /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1211674
https:/
So, could it be that at some error situation the X session is started as root and pulse somehow creates it's /run/user/ 1000/pulse with root permissions at situation like this?