Help - Search - Members - Calendar
Full Version: Problem with Audio Playback
Skype Community > English > Linux
alexkbs
I'm using built-in intel8x0.

CODE
cat /proc/asound/version; emerge -s alsa-lib skype
Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC)
*  media-libs/alsa-lib
      Latest version installed: 1.0.14_rc3
  *  net-im/skype
      Latest version installed: 1.4.0.74-r1


Everything is set to default.
berkus
Do you happen to have artsd or esd or some other audio daemon running?
alexkbs
No such.

CODE
~ $ ps axuw | grep esd
user   28075  0.0  0.1   2812   816 pts/2    R+   08:30   0:00 grep --colour=auto esd
~ $ ps axuw | grep arts
user   28091  0.0  0.0   2812   764 pts/2    R+   08:30   0:00 grep --colour=auto arts


I looked through whole process list, and haven't found anything which could be a sound daemon.

Also I tried to remove ~/.Skype and start Skype then. It didn't help: problem remains.
rootkowski
Hello!

I have the same problem since I upgraded to the latest beta version of Skype (1.4.0.74). I used to have the sound settings set for OSS and that work just perfect.

I run Linux Mint (based on Ubuntu Feisty).

Some code now:

user@mint:~$ cat /proc/asound/version; emerge -s alsa-lib skype
Advanced Linux Sound Architecture Driver Version 1.0.14rc1 (Tue Jan 09 09:56:17 2007 UTC).
bash: emerge: command not found

user@mint:~$ ps axuw | grep arts
user 17803 0.0 0.0 2884 764 pts/0 R+ 12:10 0:00 grep arts

user@mint:~$ ps axuw | grep esd
user 5577 0.0 0.0 1716 484 ? Ss 11:31 0:00 /bin/sh -c /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 24
user 5578 0.0 0.1 4584 2912 ? S 11:31 0:00 /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 24
user 17907 0.0 0.0 2884 752 pts/0 R+ 12:11 0:00 grep esd

I have been trying different settings in System>Preferences>Sound and nothing worked. The options are:
Audio Conferencing
Sound playback
- Autodetect
- SiS SI7012
- ALSA
- ESD
- OSS
Sound capture
- SiS SI7012 - MIC ADC
- SiS SI7012
- ALSA
- OSS
- Test sound
- Silence.
In Skype itself I have the following choices of devices:
Default device (default)
SIS SI7012 (hw:SI7012,0)
SIS SI7012 (plughw:SI7012,0)
SIS SI7012 (hw:SI7012,1)
SIS SI7012 (plughw:SI7012,1)

It used to be completely different with v. 1.3.0.53 (just OSS or ALSA). I read in some other posts that I should stick to the default settings in Skype. I feel rather lost now. I will be very greatful for any help. Thanx a lot!

PS. I also tried to add my user to the audio group (/dev/dsp has premissions set for the audio group) but it didn't work (or maybe I don't know how to do it). I went to System>Administration>User and Groups and the audio group doesn't even exist there. I added it but it disappeared after a reboot. Any ideas on that one?

I thought that it also might be helpful to know what is in the .asoundrc file. So here it comes:
pcm.!default {
type plug
slave.pcm "surround51"
slave.channels 6
route_policy duplicate
}
That's it.
Thank you a lot!
berkus
QUOTE(rootkowski @ Thu Jun 28 2007, 13:34) [snapback]411987[/snapback]

user@mint:~$ ps axuw | grep esd
user 5577 0.0 0.0 1716 484 ? Ss 11:31 0:00 /bin/sh -c /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 24
user 5578 0.0 0.1 4584 2912 ? S 11:31 0:00 /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 24


Try to kill these.

QUOTE(alexkbs @ Thu Jun 28 2007, 02:38) [snapback]411850[/snapback]

No such.

I looked through whole process list, and haven't found anything which could be a sound daemon.

Also I tried to remove ~/.Skype and start Skype then. It didn't help: problem remains.


Weird, I have intel-hda here and it works charmingly.
rootkowski
How am I to kill it? When I just closed the process in the System Monitor it didn't help. And this is what I get in the terminal now:
user@mint:~$ ps axuw | grep esd
user 19307 0.0 0.0 1712 472 ? Ss 18:00 0:00 /bin/sh -c /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 17
user 19308 0.0 0.0 3200 1400 ? S 18:00 0:00 /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 17
user 19521 0.0 0.0 2884 748 pts/0 R+ 18:00 0:00 grep esd

I have no idea about such things. Frankly, I don't even know what it is I'm to kill (what it does etc).

Thanx for your help :-)
alexkbs
QUOTE(rootkowski @ Thu Jun 28 2007, 17:04) [snapback]412146[/snapback]

How am I to kill it?
user@mint:~$ ps axuw | grep esd
user 19307 0.0 0.0 1712 472 ? Ss 18:00 0:00 /bin/sh -c /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 17
user 19308 0.0 0.0 3200 1400 ? S 18:00 0:00 /usr/bin/esd -terminate -nobeeps -as 1 -spawnfd 17

There is process IDs in second column. For example:
user@mint:~$ kill 19307
berkus
Best way is to use gnome control center to disable this audio system once and for all.
rootkowski
I got finaly that thing about ESD. i turned it off completely. It didn't help unfortunately. I still cannot make or recieve calls. I started Skype from the terminal and this is what I get:

ALSA lib pcm_params.c:2152:(snd_pcm_hw_refine_slave) Slave PCM not usable

And even twice (the very same line) for some reason. Would that be of any help?

______________________________________________________________________

IT'S WOOOOORKING!!!!!!
It was enough to change the default settings in skype from Default device to SiS SI7012 (hw:SI7012,0) in my case.

Thanks for all help and support :-)
berkus
QUOTE(rootkowski @ Sat Jun 30 2007, 04:31) [snapback]412895[/snapback]

It was enough to change the default settings in skype from Default device to SiS SI7012 (hw:SI7012,0) in my case.


Strange. Can you send the logs for the case when you try to make a call with default device and it fails?
rootkowski
QUOTE(berkus @ Sun Jul 1 2007, 17:12) [snapback]413329[/snapback]

Strange. Can you send the logs for the case when you try to make a call with default device and it fails?

Sure, only that I don't know how to get such logs. I'm really new to linux so things that go beyond "click and you're done" are also beyond my skill. But with some help I'll deliver the necessary logs. smile.png
Калин
QUOTE(rootkowski @ Mon Jul 2 2007, 16:10) [snapback]413604[/snapback]

Sure, only that I don't know how to get such logs. I'm really new to linux so things that go beyond "click and you're done" are also beyond my skill. But with some help I'll deliver the necessary logs. smile.png


For information regarding log files please read the following.
berkus
QUOTE(rootkowski @ Mon Jul 2 2007, 16:10) [snapback]413604[/snapback]

Sure, only that I don't know how to get such logs. I'm really new to linux so things that go beyond "click and you're done" are also beyond my skill. But with some help I'll deliver the necessary logs. smile.png


It's easy, just
1) quit skype
2) run in terminal window: "mkdir -p ~/.Skype/Logs"
3) run skype
4) Make the failing call and quit skype
5) run in terminal window: "tar cjf logs.tar.bz2 ~/.Skype/Logs"

You will have a file named logs.tar.bz2 in your current directory, which contains all the logs.
Send them over skype or email to me.

(You can just copy/paste these commands from here to your terminal window and run, to avoid any typos).
rootkowski
I got the logs but I don't see a way to attach files to e-mails on this forum. worried.png
berkus
Just send it to me over skype.
Xeor
I just install Skype on my brother and sister laptops both Acer 1362 with a new installation Kubuntu 7.04 and I have the same problem;"Call Failed:Problem with Audio Playback".
alexkbs
I had send you my logs over email yesterday.
amaurimag
Hi,

I'm using Skype 1.4.0.74 in Mandriva 2006 (with ALSA 1.0.9b - yes, i'm right) and after 2 weeks with a lot of "Problem with Audio Playback" messages, searching in Google I found a simple solution, and Skype is working fine now.

KDE users can do this:

1. Kill artsd

2. disable aRTS in KDE Control Center

3. set a new player for system notifications - in KDE Control Center > Appearance & Themes > System Notifications > Player Settings, check "Use external player" and type: /usr/bin/play

4. configure your sound devices in Skype, choosing the HW ones, not the default

Other KDE sound programs (amaroK, etc.) must be configured to not use aRTS. If you use any of these programs without reconfiguring it, artsd becomes active and must be killed to get Skype working again.

I hope this can help you.

Bye
berkus
QUOTE(amaurimag @ Thu Jul 5 2007, 19:52) [snapback]414838[/snapback]

I'm using Skype 1.4.0.74 in Mandriva 2006 (with ALSA 1.0.9b - yes



It is absolutely extremely highly recommended to upgrade to a post 1.0.11 version of ALSA.
amaurimag
QUOTE(berkus @ Thu Jul 5 2007, 20:31) [snapback]414909[/snapback]

It is absolutely extremely highly recommended to upgrade to a post 1.0.11 version of ALSA.


Wow! Caramba! Vixe! surprised.png

I'm planning an upgrade from Mandriva 2006 to PCLinuxOS 2007, but I have an highly tweaked system used in my daily work, then it must be done carefully.

Why is that "absolutely extremely highly recommended"?
berkus
QUOTE(amaurimag @ Thu Jul 5 2007, 23:37) [snapback]414931[/snapback]

Wow! Caramba! Vixe! surprised.png

I'm planning an upgrade from Mandriva 2006 to PCLinuxOS 2007, but I have an highly tweaked system used in my daily work, then it must be done carefully.

Why is that "absolutely extremely highly recommended"?


Because post-1.0.11 alsa has dmix properly configured and enabled by default, which decreases amount of trouble by itself significantly. There are other major fixes in the codebase, too.
rootkowski
QUOTE(berkus @ Sun Jul 1 2007, 17:12) [snapback]413329[/snapback]

Strange. Can you send the logs for the case when you try to make a call with default device and it fails?

Hello!

Since I didn't find out how to attach files to emails on the forum and couldn't get hold of you on skype I will just attach the logs here. I don't know what information is included in such logs so as soon as you answer that you've got them I'll take them down from this post.

Thanks a lot for your help! I really appreciate it.

So, the logs...


Edit:
I attached the file but I can't see it :-S
I hope though you can. If you can't, please tell me how to send it to you. Is your skype name berkus?
Thomaz R Botelho
Same here...

Slackware 12.0
alsa 1.0.14rc3

artsd stopped here...
with normal user...

CODE
$ skype
ALSA lib pcm_dsnoop.c:558:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:558:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:558:(snd_pcm_dsnoop_open) unable to open slave


and... "Call Failed:Problem with Audio Playback" in a test call

when i try to load it with root... i can hear... but can't speak...

Older versions it works great with oss.

I already fixed the permissions (chmod 666):
CODE
$ ls -l /dev/sound/
total 0
crw-rw-rw- 1 root audio 14, 4 2007-07-11 14:09 audio
crw-rw-rw- 1 root audio 14, 3 2007-07-11 14:09 dsp
crw-rw-rw- 1 root audio 14, 0 2007-07-11 14:09 mixer
crw-rw-rw- 1 root audio 14, 1 2007-07-11 14:09 sequencer
crw-rw-rw- 1 root audio 14, 8 2007-07-11 14:09 sequencer2


Any Help?

Thnks
berkus
QUOTE(rootkowski @ Wed Jul 11 2007, 12:20) [snapback]417097[/snapback]

If you can't, please tell me how to send it to you. Is your skype name berkus?


Yes. When asking for authorization state clearly who you are.
Thomaz R Botelho
QUOTE(Thomaz R Botelho @ Wed Jul 11 2007, 22:04) [snapback]417337[/snapback]

Same here...

Slackware 12.0
alsa 1.0.14rc3

artsd stopped here...
with normal user...

CODE
$ skype
ALSA lib pcm_dsnoop.c:558:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:558:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dsnoop.c:558:(snd_pcm_dsnoop_open) unable to open slave


and... "Call Failed:Problem with Audio Playback" in a test call

when i try to load it with root... i can hear... but can't speak...

Older versions it works great with oss.

I already fixed the permissions (chmod 666):
CODE
$ ls -l /dev/sound/
total 0
crw-rw-rw- 1 root audio 14, 4 2007-07-11 14:09 audio
crw-rw-rw- 1 root audio 14, 3 2007-07-11 14:09 dsp
crw-rw-rw- 1 root audio 14, 0 2007-07-11 14:09 mixer
crw-rw-rw- 1 root audio 14, 1 2007-07-11 14:09 sequencer
crw-rw-rw- 1 root audio 14, 8 2007-07-11 14:09 sequencer2


Any Help?

Thnks


People... solved this one... i put my user in audio group... now i can listen... like root... but can't speak yet... i will check another topic here in forum. Tnks.
Mista_tongz
QUOTE(amaurimag @ Thu Jul 5 2007, 17:52) [snapback]414838[/snapback]

Hi,

I'm using Skype 1.4.0.74 in Mandriva 2006 (with ALSA 1.0.9b - yes, i'm right) and after 2 weeks with a lot of "Problem with Audio Playback" messages, searching in Google I found a simple solution, and Skype is working fine now.

KDE users can do this:

1. Kill artsd

2. disable aRTS in KDE Control Center

3. set a new player for system notifications - in KDE Control Center > Appearance & Themes > System Notifications > Player Settings, check "Use external player" and type: /usr/bin/play

4. configure your sound devices in Skype, choosing the HW ones, not the default

Other KDE sound programs (amaroK, etc.) must be configured to not use aRTS. If you use any of these programs without reconfiguring it, artsd becomes active and must be killed to get Skype working again.

I hope this can help you.

Bye


hey thanks man!! I had the same problem with my Skype as well. Problem was solved after following your steps.
A quick one though, hw do i disable aRTS in kde control centre?


thanks again


tongai


amaurimag
QUOTE(Mista_tongz @ Wed Jul 25 2007, 16:30) [snapback]421793[/snapback]

hey thanks man!! I had the same problem with my Skype as well. Problem was solved after following your steps.
A quick one though, hw do i disable aRTS in kde control centre?
thanks again
tongai


To disable aRTS, choose "Sound & Multimedia" > "Sound System" in KDE Control Center, then uncheck "Enable the sound system".

[]'s
Amauri
AlecLiu
QUOTE(berkus @ Mon Jul 2 2007, 22:49) [snapback]413805[/snapback]

It's easy, just
1) quit skype
2) run in terminal window: "mkdir -p ~/.Skype/Logs"
3) run skype
4) Make the failing call and quit skype
5) run in terminal window: "tar cjf logs.tar.bz2 ~/.Skype/Logs"

You will have a file named logs.tar.bz2 in your current directory, which contains all the logs.
Send them over skype or email to me.

(You can just copy/paste these commands from here to your terminal window and run, to avoid any typos).


I do have the same problem.
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).

please help
ps: the logs[attachmentid=10662][attachmentid=10663]
Andypoo
If you're running a recent version of ALSA (1.0.12 or later), then there shouldn't be a need to disable artsd.

However, if you have an SB Live! card, then there are many reports that you have to set the sound card explicitly by hw: address. And if you set to a hw: address, you must also disable other programs exclusively using the device (ie. artsd).

Andrew.
John Do
QUOTE(Andypoo @ Thu Aug 9 2007, 12:07) [snapback]426491[/snapback]

If you're running a recent version of ALSA (1.0.12 or later), then there shouldn't be a need to disable artsd.

However, if you have an SB Live! card, then there are many reports that you have to set the sound card explicitly by hw: address. And if you set to a hw: address, you must also disable other programs exclusively using the device (ie. artsd).

Andrew.


But that's a little weird. I do have one of those SB Live! cards:

CODE
$ cat /proc/asound/cards
0 [Live           ]: EMU10K1 - SBLive! Value [CT4670]
                      SBLive! Value [CT4670] (rev.5, serial:0x201102) at 0xd000, irq 185


Also ALSA is post 1.0.11:

CODE
cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.13.


The weird thing is, that I can set all options for sound devices (Sound In/Out and Ringing) to default and get a successful test sound. But when I want to make a test call, I immediately get the error message about a problem with the playback device which just worked before when making a test sound?!

So how come, that the same device works fine for just playing back a test sound but fails to playback in (test) calls?

Regards
J.D.
AlecLiu
QUOTE(Andypoo @ Thu Aug 9 2007, 11:07) [snapback]426491[/snapback]

If you're running a recent version of ALSA (1.0.12 or later), then there shouldn't be a need to disable artsd.


i am using the gnome, and i do not running artsd and esd
CODE

ps -aux | grep artsd
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
alec      4503  0.0  0.0   2716   700 pts/0    R+   21:35   0:00 grep --colour=auto artsd
ps -aux | grep esd
Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html
alec      4501  0.0  0.0   2716   692 pts/0    R+   21:35   0:00 grep --colour=auto esd


QUOTE(Andypoo @ Thu Aug 9 2007, 11:07) [snapback]426491[/snapback]

However, if you have an SB Live! card, then there are many reports that you have to set the sound card explicitly by hw: address. And if you set to a hw: address, you must also disable other programs exclusively using the device (ie. artsd).

Andrew.

CODE

cat /proc/asound/cards
0 [I82801DBICH4   ]: ICH4 - Intel 82801DB-ICH4
                      Intel 82801DB-ICH4 with ALC202 at irq 10
1 [Modem          ]: ICH-MODEM - Intel 82801DB-ICH4 Modem
                      Intel 82801DB-ICH4 Modem at irq 10
alexkbs
Same problem here:
CODE
$ cat /proc/asound/cards
0 [I82801DBICH4   ]: ICH4 - Intel 82801DB-ICH4
                      Intel 82801DB-ICH4 with AD1885 at irq 16



CODE
$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC).





AlecLiu
please help~~~~~~
Rodney Crossman
I'm having this issue as well, though sporadically. sometimes if I start skype I can make a call immediately after starting but if I wait a few seconds it won't work. just updated to client 1.4.0.99 and its no better.

Opensuse 10.2 32bit with kernel 2.6.18.8-0.5-default

# cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).

cat /proc/asound/cards
0 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with AD1980 at 0xe000, irq 193
AlecLiu
any skype Staff here for the client ? help us!!!!!!!!!!!
Andypoo
AlecLiu: Do you have the default sound card selected in the client, or some explicit hw: or plughw: device?

Andrew.
AlecLiu
QUOTE(Andypoo @ Thu Aug 23 2007, 12:00) [snapback]432801[/snapback]

AlecLiu: Do you have the default sound card selected in the client, or some explicit hw: or plughw: device?

Andrew.


i selected the default, and i have try some others too, but no work.

i can select default;hw:i82801dbich4,0;plughw:i82801dbich4,0;
hw:i82801dbich4,1;plughw:i82801dbich4,1;
.
.
hw:i82801dbich4,4;plughw:i82801dbich4,4;
hw:modem,0;plughw:modem,0;


thank for reply!!!!!!!!!!!!!
AlecLiu
any help from skype staff?
AlecLiu
geting carzy~~~~~~~~~~~~~~~~~
any help~~~~~????
victori
I am just a casual lurker that stumbled upon this thread from google. I had issues with skype and my mic with an sb live! 5.1 card. Setting each sound in/out/ring to their own individual hardware address seemed to resolve the problem. Thanks for the heads up! Can you please add that tidbit to your faq on the linux section, if it isn't already there?
AlecLiu
QUOTE(victori @ Mon Sep 3 2007, 14:07) [snapback]437000[/snapback]

I am just a casual lurker that stumbled upon this thread from google. I had issues with skype and my mic with an sb live! 5.1 card. Setting each sound in/out/ring to their own individual hardware address seemed to resolve the problem. Thanks for the heads up! Can you please add that tidbit to your faq on the linux section, if it isn't already there?


it is not work for me.
which kind of address r u using?
i have two types, hw and plughw. each 4.(4,1;4,2;4,3;4,4).
i did try, but no use....
AlecLiu
I did find something new!
The skype 1.4.0.99 can call under root only.
CODE

cat /etc/group | grep alec
adm::4:root,adm,daemon,alec
wheel::10:root,alec,test
audio::18:alec,test
users::100:games,alec,test
portage::250:portage,alec
alec:x:1000:

CODE

ls /dev/sound/ -lh
total 0
crw-rw---- 1 root audio 14, 12 2007-09-04 03:20 adsp
crw-rw---- 1 root audio 14,  4 2007-09-04 03:20 audio
crw-rw---- 1 root audio 14, 20 2007-09-04 03:20 audio1
crw-rw---- 1 root audio 14,  3 2007-09-04 03:20 dsp
crw-rw---- 1 root audio 14, 19 2007-09-04 03:20 dsp1
crw-rw---- 1 root audio 14,  0 2007-09-04 11:20 mixer
crw-rw---- 1 root audio 14, 16 2007-09-04 11:20 mixer1
crw-rw---- 1 root audio 14,  1 2007-09-04 11:20 sequencer
crw-rw---- 1 root audio 14,  8 2007-09-04 11:20 sequencer2

CODE

ls /dev/snd/ -lh
total 0
crw-rw---- 1 root audio 116, 10 2007-09-04 11:20 controlC0
crw-rw---- 1 root audio 116, 13 2007-09-04 11:20 controlC1
crw-rw---- 1 root audio 116,  9 2007-09-04 11:20 pcmC0D0c
crw-rw---- 1 root audio 116,  8 2007-09-04 11:20 pcmC0D0p
crw-rw---- 1 root audio 116,  7 2007-09-04 11:20 pcmC0D1c
crw-rw---- 1 root audio 116,  6 2007-09-04 11:20 pcmC0D2c
crw-rw---- 1 root audio 116,  5 2007-09-04 11:20 pcmC0D3c
crw-rw---- 1 root audio 116,  4 2007-09-04 11:20 pcmC0D4p
crw-rw---- 1 root audio 116, 12 2007-09-04 11:20 pcmC1D0c
crw-rw---- 1 root audio 116, 11 2007-09-04 11:20 pcmC1D0p
crw-rw---- 1 root audio 116,  3 2007-09-04 11:20 seq
crw-rw---- 1 root audio 116,  2 2007-09-04 11:20 timer
Andypoo
AlecLiu: In this case, I'd say that possibly your user is not in the audio group on your system.

Using the user management for your distribution, try adding your user to the audio group. You can also cat /etc/group to see what users are currently in the audio group on your system.

Note: You will have to re-login as your user for the group change to take effect.

Andrew.
Ramnath
Ok. I had the same problem with my skype on my Lenovo T140. But I was able to fix the stuff. I manually tried with al the combinations under the sound option. What I did was to set all the three (Sound In, Out and Ringing) to HDA Intel(hw:Intel,0).

But then two days later when I logged in again on my linux machine to call, it showed the same problem even though it was in the same options as I set it last time when it worked. I again manually played with different options and noone of them worked. All of a sudden, when I set back to this option it worked. Though it works (as of now), thats kinda weird. Can anyone explain why this thing happened?
Do you want me to post my h-w config. I am running SuSe 11.1 x64
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.