Hello!
I am running slackware Linux 11.0 with kernel 2.4.33. My skype is skype-1.3.0.53. I run it ok as root, but I cannot run it as normal user. I have set chmod 777 /dev/dsp* and still I cannot work with skype as normal user. Could you please tell me what else I need to change? Currently when I start skype as normal user it connects to the network, but cannot make a call-t just freezes saying "Connecting...." when I press the call button.
I thank you very much in advance.

Yours,
Martin

The only thing I can do is to confirm this problem with linux-2.6.16.20. Chat works fine (so loggin in), but no sounds and no so no way to fire a call, even when just closing the program freezes. No problems occur when I start skype as root. This problem is described several times here in this forum, but as far as I can see there is still no solution?!?

Hello!
I installed the 2.6.17.13 kernel and there is no more such problem

Hi!
I am running Dapper Drake Ubuntu (the latest kernel) and Skype version 1.3.0.37_API.
I often had problems sending chat messages (beside bad quality sound): message "..." not yet send (both sender and receiver were online). I tried to restart skype, but it crashed (the tray icon did not disappear).
After rebooting I now get the message:
"skype has experienced a database error. Please make sure your profiles in ~/.Skype are intact and have proper permissons then restart Skype"
ls -l showed:
-rw-r--r-- for all files in ~/.Skype

I tried
chmod -vR u+++rwx *
and
chmod -vR ugoa+++rwx *
so that now all files are read, write and executable:
-rwxrwxrwx
but Skype still shows the error message from above and does not connect anymore

Can someone help and tell me how the permission are set correctly?
Thanks a lot...

Hi,

I found this thread because I was having the same problem, i.e., I could make calls if I was running Skype as root, but not as a normal user. I have a 64-bit AMD system, and the problem in my case was that Skype was running inside a 32-bit chroot, so I needed to have the right permissions inside the chroot. Basically I just went into the chroot as root, added my normal user name to the audio group, and everything was fine. I hope this helps somebody else with a 64-bit system.

# chroot /var/chroot/your_version
# ls -l /dev/dsp
crw-rw---- 1 root audio 14, 3 2005-02-28 23:07 /dev/dsp [ # chmod 660 /dev/dsp if you get something other than crw-rw---- ]
# usermod -Gaudio your_user_name
# exit

Bob