This bug is closed. If you have any issues, please open a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage
With the caveat that I haven't followed the entire thread, I had a
similar problem today on an older 14.04 release: the owner of
/run/user/$id/pulse would "spontaneously" become root. Comment #34 says
this is easily reproducible when running pkexec/synaptic. I believe I
can explain - broadly -
Launchpad has imported 103 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=753882.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
This bug affects me today on actual elementary 0.3 freya
** Also affects: elementaryos
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
This bug was fixed in the package systemd - 204-0ubuntu19.1
---
systemd (204-0ubuntu19.1) saucy-proposed; urgency=low
* Add pam-check-runtime-dir-user.patch: Don't set an existing
$XDG_RUNTIME_DIR in the PAM module if it isn't owned by the session user.
Otherwise su
Hi, with some difficulty I installed the -proposed packages for saucy having to
do with systemd.
This is a Lenovo E135 running Saucy.
This cleared up several problems for me, some related to sound, some not
obviously related.
One not mentioned here exactly:
FlashPlugin in Firefox made like an
The packages from -proposed fixed the bug for me after rebooting the
computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage
Hello Davide, or anyone else affected,
Accepted systemd into saucy-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/204-0ubuntu19.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a
media player (I use Musique), it freezes, as it finds that it cannot write into
/run/user/$ID/pulse.
If I change the owner of that directory to me, the media player starts as
usual and is
** Branch linked: lp:ubuntu/saucy-proposed/systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage notifications about
** Changed in: pulseaudio (Ubuntu Saucy)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To
Uploaded fix for saucy, now waiting for SRU team to review/accept.
** Changed in: systemd (Ubuntu Saucy)
Status: Confirmed = In Progress
** Description changed:
I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a
media player (I use Musique), it freezes, as it
For end user this is visible as any application (rhythmbox, flash in
browser, etc) freezing totally if trying to play audio. It would be
really good idea to update systemd on Saucy asap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi there,
just tried this evening to read a film with Totem and VLC - and got this bug,
too.
Fyi, if it helps, here is the terminal output I got when trying to read
a film with VLC:
Fontconfig warning: FcPattern object size does not accept value 0
Fontconfig warning: FcPattern object size does
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu Saucy)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Saucy)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Hi Martin,
Just to echo my comment on bugzilla. I reviewed the patch again and
you're entirely right, it deals with the problem pretty well. Sorry
about the confusion. The patch looks good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I wouldn't mind a Saucy SRU for this. It seems to hit quite a few
people.
** Also affects: pulseaudio (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Saucy)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=753882
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Milestone: None = ubuntu-13.11
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
**
Patch sent to RedHat bug, and applied locally in my systemd packaging
git. With that I think we shoudln't work around this in pulse. David's
proposed patch might still be useful for upstream pulse though, if
upstream systemd refuses to apply this.
** Changed in: systemd (Ubuntu)
Status: In
** Branch linked: lp:ubuntu/trusty-proposed/systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage notifications about
This bug was fixed in the package systemd - 204-5ubuntu6
---
systemd (204-5ubuntu6) trusty; urgency=low
* Add pam-check-runtime-dir-user.patch: Don't set an existing
$XDG_RUNTIME_DIR in the PAM module if it isn't owned by the session user.
Otherwise su sessions get a
Hi Martin,
Thanks for stepping up on this.
I think Colin is right over on
https://bugzilla.redhat.com/show_bug.cgi?id=753882, you need to check
the UID. I added a comment there with an example where permissions on
the runtime dir itself are fine.
--
You received this bug notification because
Reencountered the same problem again today (again on my MPr 15). I
_did_ shutdown the computer properly yesterday evening, but I'm pretty
sure that I closed the lid immediatly after clicking on shutdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: pulseaudio (Ubuntu)
Status: Confirmed = Triaged
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
Hi,
It's a regression in the pam module for systemd:
https://bugzilla.redhat.com/show_bug.cgi?id=753882
It affects all distributions afaik and it can make any app/package using
XDG_RUNTIME_DIR crash if it's used with root privileges (including
dconf)...
This is a huge bug. I think the most
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To
** Changed in: systemd (Ubuntu)
Status: New = Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
Aha, thanks for that. I've been trying to find a way to reproduce the
bug and with the help of comment #46 I got one that worked for me:
sudo su -
pacmd list
This will result in an error message and the directory being owned by
root, which screws up further connections.
This does not happen
Please don't use that as a solution... it's just for the purpose of
troubleshooting:
- Add the following to /etc/profile
if [ `id -u` -eq 0 ]; then
mkdir -p /run/user/0
XDG_RUNTIME_DIR='/run/user/0'
fi
- log out and log back in.
This should force the system to behave like it did in raring.
^^ this is mostly for the Ubuntu developers by the way. Please don't
modify your /etc/profile unless you know your way around the tty
consoles and how to repair cache/run permissions. You could find
yourself unable to log back in.
--
You received this bug notification because you are a member of
Ok, here's my take on the problem:
http://lists.freedesktop.org/archives/pulseaudio-
discuss/2013-November/019121.html
Let's give Lennart a day or two to respond, if he does not, let's deploy
the patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the same problem with FLash in all Web Browsers :(
The problem starts after upgrade to ubuntu 13.10 (32bit)
My notebook PacardBell Intel i3-2330M 4x2,2GHz
Intel Sandybridge Mobile
patrycja@patrycja-Satellite-L300:~$ ls -l ./.dmrc
-rw-r--r-- 1 patrycja patrycja 93 lis 9 21:42 ./.dmrc
I've also installed skype recently (before upgrading), and the issue has
affected me since upgrading to ubuntu 13.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse
Problem occurs on a Lenovo Thinkpad X230 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage notifications about
I can reconfirm.
Also, other users have pointed out putting the lid down while docked,
which results in a crash, having to hard-reboot and on restart find this
problem.
This also is exactly how my problem appeared. I think I closed the lid
first, then docked, though.
Clean install 64b, Lenovo
Same here: after failed attempt to suspend my PC, directory
/run/user/1000/pulse was owned by root.
I've just installed system yesterday (fresh one, not upgraded from previous
version).
I've installed only one program that has anything to do with pulseaudio: skype
(from repo, not official deb
Yes - same for me as #37,#38 after failing to enter standby / forced
power off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
Same here, had several standby issues before seeing this. Dell Latitude
E6400, Ubuntu 13.10 (saucy) 64-bit. Temporary workaround: sudo chown -R
1000:1000 /run/user/1000.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had this happen after a failed attempt to put my computer into standby
that required a force poweroff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by
Just had the same problem after a (normal) restart on a Macbook Retina
10,1. Sound wasn't working anymore and most applications using sound
hung up/waited for a ling time and then crashed (most annoyingly
flashplayer, which caused firfox to hang). After deleting the folder
pulse, sound instantily
I think problem is connected with system crash. I also musted do hard
reboot of my computer, because after wake-up my usb WiFi didn't work and
system didn't wanted to reboot (even with root privilages). So after
some minutes of waiting i've pressed power button and after new boot got
this error.
After updated to ubuntu 13.10 I also have this issue. The permission of
the directory (/var/run/user/1000/pulse) was changed to root, every time
I run synaptic, from the gnome-flashback menu in the panel.
From the menu synaptic is invoked by pkexec. I tried gksudo synaptic
then no such problem,
I don't know if it is related, but under XFCE the indicator-sound is
not functional (luckily hotkeys work).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by
I can confirm that. Deleting the directory '/run/user/1000/pulse' is
apparently enough. The problem is solved for good I guess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
The error stays, even in fully updated xubuntu 13.10, on multiseatcomputer.
Log in a first user, the dir /run/user/1001 is created.
Logout this user and login with another user, pulse error shows up in syslog
complaining access to this 1001 dir.
Delete this dir, reboot and do the same logins and
Hit this bug running latest Saucy, with distro pulseaudio after a cold
reboot.
pulseaudio:
Installed: 1:4.0-0ubuntu6
Candidate: 1:4.0-0ubuntu6
Version table:
*** 1:4.0-0ubuntu6 0
500 http://tw.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status
Syslog says:
Oct 22 12:01:51 thinkpad pulseaudio[7500]: [pulseaudio] core-util.c: Failed to
create secure directory (/run/user/1000/pulse): Permission denied
Oct 22 12:01:51 thinkpad pulseaudio[7500]: [pulseaudio] main.c: User-configured
server at
Workaround: I removed the offending directory, and pulse immediately
created one owned by the right user. Even after a reboot, no issues
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
There was something upstream that looked somewhat related:
Ok, got the error: the systemd pam module in /etc/pam.d/common-session does not
create a secure run dir in /run/user for every logged in user.
So pulse is complaining about access .
Deleted the systemd line in /etc/pam.d/common-session
Fixed by deleting the directory '/run/user/1000/pulse'.
Then I had to kill vlc (VLC media player) process that was waiting endlessly
saing Failed to create secure directory (/run/user/1000/pulse).
But I think after reboot it will be the same again.
--
You received this bug notification because
This bug happened to me on upgrade to saucy daily build (10/13/2013)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage
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
I am seeing this right now. I got the updated PA from saucy when it was
uploaded on the 26th and rebooted on the 27th, so my system was booted
with 4.0.
laney@iota ls -la /run/user/1000
total 0
drwx-- 7 laney laney 160 Jul 27 10:40 ./
drwxr-xr-x 3 root root 60 Jul 27 10:41 ../
drwx-- 2
So it's started correctly as my user but the directory has the wrong
permissions. Could this be a bug in lightdm?
At least it can't be a bug in PulseAudio, because PulseAudio shouldn't
have the permission to create that directory with those permissions,
right?
--
You received this bug
When I press the media keys I can hear the 'pip' sound telling me what
the volume will be, so somehow that can use the sound hardware.
Thinking about it, while I can't be sure, it seems quite unlikely that
sound would have been broken for me for a week without me noticing
(implied if it happened
At least it can't be a bug in PulseAudio, because PulseAudio shouldn't
have the permission to create that directory with those permissions,
right?
I agree with you, but what else could make it owned by root? Or PA is started
as root before the DM is started, and maybe it doesn't remove it after
Pulseaudio is run as the logged in user. Pulse itself will refuse to
start as root if system mode is not enabled in the config. I think this
is happening post pulse start, although I have no idea what the problem
could be, and I haven't experienced this problem myself.
--
You received this bug
On Thu, Aug 1, 2013 at 12:29 AM, Luke Yelavich
luke.yelav...@canonical.comwrote:
Pulseaudio is run as the logged in user. Pulse itself will refuse to
start as root if system mode is not enabled in the config. I think this
is happening post pulse start, although I have no idea what the problem
On Thu, Aug 01, 2013 at 08:39:59AM EST, Davide Depau wrote:
It may be a media player started as root! Maybe if a media player is
started as root could change the owner of that directory to root..
If a media player was started as root, libpulse would notice that
pulseaudio is not running for
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
I meet the same problem with the same version of pulseaudio and
permission set uncorrectly as found in my syslog.
pulseaudio:
Installé : 1:3.0-0ubuntu8
Candidat : 1:3.0-0ubuntu8
Table de version :
*** 1:3.0-0ubuntu8 0
500 http://fr.archive.ubuntu.com/ubuntu/ saucy/main amd64
affecting me on a system upgraded from raring around saucy-alpha1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To manage
As above, please try testing with Pulseaudio 4.0 from the mentioned PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197395
Title:
/run/user/$ID/pulse owned by root and not by the user
To
Ok then, could you please try testing Pulseaudio 4.0 from ppa:ubuntu-
audio-dev/pulse-testing? I must say I am not seeing any such problem
similar to this here locally, although I am running Pulse 4.0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, I'm adding it. I didn't have the problem again. I'll try to play music
every time I turn on the PC, and if I won't have problem for almost a week,
I will report it here.
2013/7/9 Luke Yelavich luke.yelav...@canonical.com
Ok then, could you please try testing Pulseaudio 4.0 from ppa:ubuntu-
No, it's not from a PPA:
pulseaudio:
Installed: 1:3.0-0ubuntu8
Candidate: 1:3.0-0ubuntu8
Version table:
*** 1:3.0-0ubuntu8 0
500 http://it.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status
--
You received this bug notification because you are a
68 matches
Mail list logo
