Stop Microsoft

Operating Systems => Linux and UNIX => Topic started by: asdf on 26 January 2002, 02:37

Title: i know this isn't the place to be asking n00b questions, but..
Post by: asdf on 26 January 2002, 02:37

i'm getting desperate. nothing is working. anyway, i'm trying to configure sound on my RH7.2 box. dmesg reports that the sound card was detected properly. lsmod reports that the sound module was loaded. the permissions for /dev/dsp and /dev/audio are 666. but whenever i try to play a sound, i get the following error:

esd: Failed to fix mode of /tmp/.esd to 1777.
Try -trust to force esd to start.
esd: Esound sound daemon unable to create unix domain socket:
/tmp/.esd/socket
The socket is not accessible by esd.
Exiting...

any ideas? thanks a lot

Title: i know this isn't the place to be asking n00b questions, but..
Post by: voidmain on 26 January 2002, 06:41

I'll try and help, but before I do I would like to know a few things.  Does your sound work in KDE (KDE uses artsd)?  If not, have you tried to run "setup" from a shell prompt and select the "Sound Card Configuration" and get the sound test to work ("su -" to root first)?

[ January 25, 2002: Message edited by: VoidMain ]

Title: i know this isn't the place to be asking n00b questions, but..
Post by: Leodak on 26 January 2002, 21:32

first try killall esd under root, if that comes up with nothing run esd -d /dev/dsp, and if that don't work try restarting, that always seems to work

Title: i know this isn't the place to be asking n00b questions, but..
Post by: voidmain on 26 January 2002, 11:00

Actually, it sounds like your permissions are screwed up on your /tmp/.esd directory and the socket file (probably first logged in to gnome as root and it didn't set the perms right, then as a normal user esound would not work). If this is true it will work as root but not as a normal user.  To fix from a shell prompt do this:

su -
chmod 1777 /tmp/.esd
chmod a+rwx /tmp/.esd/socket

[ January 26, 2002: Message edited by: VoidMain ]

Title: i know this isn't the place to be asking n00b questions, but..
Post by: voidmain on 26 January 2002, 11:55

The /tmp/.esd directory should have the permissions set to "1777" and user/group should be root/root (and it has to be a directory not a file. To recreate the directory as it should be do this:

rm -rf /tmp/.esd
mkdir /tmp/.esd
chmod 1777 /tmp/.esd
chown root:root /tmp/.esd

Then when you start esd it should automatically create a socket file called "/tmp/.esd/socket" with these permissions: srwxrwxrwx

[ January 26, 2002: Message edited by: VoidMain ]

Title: i know this isn't the place to be asking n00b questions, but..
Post by: asdf on 27 January 2002, 04:27

the permissions for /tmp/.esd were already 1777 (i had already tried that). deleting the directory did the trick. thanks

Title: i know this isn't the place to be asking n00b questions, but..
Post by: voidmain on 27 January 2002, 06:49

quote:

---

Originally posted by asdf:
the permissions for /tmp/.esd were already 1777 (i had already tried that). deleting the directory did the trick. thanks

---

Great, it sounds like the permissions on the socket weren't correct, or there was some other problem with the socket, or another copy of esd was already running and had a hold on the socket.