Red Hat Bugzilla – Bug 474397
pulseaudio using obsolete group id
Last modified: 2008-12-09 12:27:18 EST
Description of problem:
During firstboot I created a user "testuser" that ended up in to group "testuser" with gid 500. This is of course silly and as root I changed the user to group "users" with gid 100. Otherwise everything works perfectly, but for some reason pulseaudio still creates its temp dirs under /tmp for the users with gid 500.
I tried grepping under /etc/pulse etc but didn't find any obvious configuration where does this 500 come from?
FWIW, it also raises complaints from sectool as there's no more group with gid 500.
Version-Release number of selected component (if applicable):
(In reply to comment #0)
> Description of problem:
> During firstboot I created a user "testuser" that ended up in to group
> "testuser" with gid 500. This is of course silly ...
> ... and as root I changed the user
> to group "users" with gid 100. Otherwise everything works perfectly, but for
> some reason pulseaudio still creates its temp dirs under /tmp for the users
> with gid 500.
You need to logout/login again. Check with the "id" command with which uid/gid parameters your shell/session is running. Note that you need to edit both he groups file and the shadow files.
> where does this 500 come from?
From the getgid(2) system call. The same data the "id" outputs.
This is unrelated to PulseAudio. It most likely a configuration error on your side or just a misunderstanding how unix user ids work.
Now come on, now need for that attitude, I have logged out and rebooted the computer dozens of times, I noticed the behavior right after installation and waited for weeks if an update would appear to fix this and as that did not happened, I opened the bug.
"id" does not output 500 but 100.
22:24:23 up 1 min, 1 user, load average: 2.07, 0.88, 0.32
root@localhost:~# rpm -q pulseaudio
root@localhost:~# id testuser
uid=500(testuser) gid=100(users) groups=100(users)
root@localhost:~# ls -ld /tmp/pulse*
drwx------ 2 testuser 500 4.0K 2008-12-08 22:23 /tmp/pulse-PKdhtXMmr18n/
Are you sure that PA is run from exactly the the same environment as you ran "id" as?
Please do this:
pulseaudio -k ; rm -rf /tmp/pulse* ; pulseaudio -vvv
Paste the part about the used state/runtime directories here which will be shown then.
And also try to do a "readlink ~/.pulse/*:runtime" which should show you the actual runtime directory used. Also use do a "stat /proc/`pidof pulseaudio`" to figure out the uid/gid the PA process is running as.
Ok, mea culpa, I did "find / -gid 500" and noticed that ~/.gvfs, ~/.esd_auth, /tmp/.esd-500 were owned by group 500. I removed all those dirs, all tmp files etc, rebooted and now everything seems to be ok.
Closing as luser error.