Problem summary

Skype for Linux version 1.2.0.11 and newer has a bug that makes calling impossible after placing the first one.
Usual signs of this bug are: /dev/dsp: Device or resource busy (on Skype) messages.
Only way to make another call is to restart Skype.

There are a few known workarounds for this problem:

file from Skype's sound directory. Example (tested on Fedora):

CODE
cd /usr/share/skype/sound

mv hangup.wav hangup.wav-disabled


Thanks to Marcello Golfieri who discovered that.


• use skype_dsp_hijacker that workarounds the problem on a lower level.
  Read more on that and other Skype sound problems at http://juljas.net/linux/skype/
  
  
  Jan Slupski
  ----
  Original post
  
  Hi,
  
  I just upgraded Skype to 1.2.0.11 and discovered (probably) new bug.
  
  If you call to some contact (tried with echo123), and immediately disconnect,
  Skype does not handle sound device properly.
  
  Skype tells 'Cancelled', and on the console I get /dev/dsp1: Device or resource busy message. On next connection try Skype tells: Problem with sound device. Only after Skype restart I can call again.
  
  The problem seems to happen olny (but always) when that very short call is first
  call after Skype starts. Maybe some problem with some internal synchronization?
  
  If the first call lasts longer, I can both hear an be heard, and call again.
  
  Reproduce:
  1. Start Skype
  2. Call echo123
  3. Immediately click DISCONNECT
  4, Try to call anything else.
  
  My configuration
  FC3, alsa sound with oss emulation
  
  Can anybody confirm the problem?

Just curious...this may be the same problem I'm having....try dialing +18005551212 for 1-800 directory assistance. Then, hang up and try calling echo123 again. See if you can hear echo123 at all.

I posted about it below. I'd been using skype with no problems until this version came along.

Link to the description of potentially the same problem by tannhaus
http://forum.skype.com/viewtopic.php?t=32193

Update:

It happens after making (successful) longer calls too.
Recent scenario:
1. Run Skype
2. Call SkypeOut
3. Talk...
4. Click disconnect
5. /dev/dsp1: Device or resource busy, cannot call again, Problem with sound device
6. Exit Skype
7. Start Skype again, and all back to normal (can call, etc.)

This happen relatively rarely after "normal" calls, while I'm able to reproduce with the initial sequence (quick disconnect) every time.

Update 2:

It also happens after a few successful calls.

Yeah, I have this sound device problem Too (FC4) ever since I upgraded to 1.2.0.11 ...

The only real differencce that I can see is the "Start" tab is gone ...
So I am downgrading until this issue is resolved, here is a link for those of you affected:
http://download.skype.com/linux/skype-1.1....20-fc3.i586.rpm

I'm using SuSE 9.3 running Skype 1.2.0.11 and there's no problems by using the asound.conf from the other post and I use aoss and it works. I guess it's something Fedora Core has issues w/

xboxrulz

I use aoss and it works. I guess it's something Fedora Core has issues w

I do not use aoss - it crashes once I try to run aoss Skype
I'm using kernel oss emulation.

Will give a try with other aoss/asound.conf configurations, but anyway, these problems with the same sound configuration didn't happen with previous Skype versions.

Thanks for reply.

That's what I'm running into...previous versions of skype worked fine. However, if I try to call echo123 and then attempt skypeout, I get complete silence. If I try to call echo123 again, I get complete silence.

Yeah, I have this sound device problem Too (FC3) ever since I upgraded to 1.2.0.11 ...

I'm using SuSE 9.3 with KDE 3.4.2 (default sound setup) , using the same skype people reported here and I also have the same problem.

It's really annoying...when will this people work with other sound systems!??!...

Hugo

This sound problems with skype are really becoming unbearable. Wasn't suppose for skype to be the internet telephony that just works??! Well it just doesn't work.

If one has to go through a lot of configurations and headaches just to get it working, you can't say that it's an easy install.

And it's very bad every time I loose some money because other people can't ear me or something.

Thanks for confiming that's not only me...
I have submited Support Request.

This is because they used OSS and it is labelled obsolete. If they had native ALSA support, then all of this will not exist.


xboxrulz

They just have to look at amarok's code (or from any other open source program) to see how one can use different sound systems. It's not like you have to do anything new, it's already done somewhere.

They just have to look at amarok's code (or from any other open source program) to see how one can use different sound systems. It's not like you have to do anything new, it's already done somewhere.

Yes and no. They cannot just reuse open source code, until they relase Skype as open source. but anyway rewriting it shouldn't be that difficult.

/dev/dsp1: Device or resource busy

Same problem in Mandrake 10.1

Also have the same problem with Debian testing since upgrading from 1.1.0.20 to 1.2.0.11. I am using ALSA and snd_via82xx with built-in VIA sound. The error I get on the console is "/dev/dsp-1: Device or resource busy"

/proc/asound/version:
Advanced Linux Sound Architecture Driver Version 1.0.9rc2 (Thu Mar 24 10:33:392005 UTC).

/proc/asound/cards:
0 [V8235 ]: VIA8233 - VIA 8235
VIA 8235 with AD1980 at 0xe000, irq 22

I have the same problem on my system (FC4). I am suggesting a petition in getting ALSA into Skype, because for the most of us this is the most wanted feature in the (already almost awesome ;-)) linux-version of Skype.

btw. thanks for the cool "contact groups" feature

where's the contact group feature? I seem to can't find it.

xboxrulz

Hey,

pretty easy: on your buddy list, right-click on a buddy, the last menu item is "Group" where you can "move" the buddy to an existing or new group.