Hi,

I am so happy that Skype for Linux is able to deal with Video, I made some tests yesterday with Fedora 7 and it was working like a charm.
Now my laptop is under Fedora 8 which comes with PulseAudio enable by default.
Unfortunaltly I can't get any sound from skype V2 with PulseAudio, I tried this tip External Link without success.

Someone manage to makes Skype works with PulseAudio?

BR,
Yves

I got the version 1.4 with OSS (StaticOSS) to run with PulseAudio.
Just run it as "padsp skype".

Hi,

I wrote the above link you pointed out and I've just tested this with Skype 2 beta. It seems to work mostly for me (e.g. I've been able to make a test call to echo123). Not tested it in a practical situation yet tho'

I have found it to be a little unreliable in general tho'.

I think as desktops convert to PA by default, I think Skype should really seriously consider implementing direct PA support (or at least creating a public API for the creation of sound pluigns, that way someone could write a plugin for direct pulse suport - or a bridge to a suitible audio library like libao (assuming this does not violate GPL).

Agreed. I am only using skype when pulseaudio support arrives otherwse I'd have to give up simultaneous audio playback and video editing capability with JACK.

I see that the Skype absence of Linux 64-bit support has been going on for some time.
I've been fairly happy with Skype until recently, when I had to upgrade a laptop
to Hardy Heron with PulseAudio.

At that time, skype ceased to work. With Hardy Heron Alpha 5(4?), and
the Skype 2.0 Beta, I get the following when I start skype from a terminal session.
[I have Skype configured to use "pulse"; I can watch youtube videos and DVDs
with no problems, so the problem is confined to skype.]

If I try to make a test call, or even go into the "options" page, I get this:

ALSA lib pcm.c:2064:(snd_pcm_open_conf) Cannot open shared library /usr/lib/alsa-lib/libasound_modules_pcm_pulse.so
A test call produces: "Call failed. Problem with audio playback."

An ls -l shows that (a) the shared library member does exist and
(b) a similar member exists under /usr/lib32/...

This is a Toshiba/Intel laptop running 64-bit Hardy Heron, and
a Skype-approved Logitech USB headset.
I would very like to have a workaround for this problem.

I have spent about a week screwing around, trying various methods of
getting Skype to work, and they have all been complete failures.
I am not happy, and I am not happy with Skype's failure to correct
simple problems, while they go off and develop more "fun" features.
Jeez, guys. All I want to do is to make a simple phone call.

I saw one post, presumably from one of the Skype developers, suggesting
that a rewrite of Skype to provide 64-bit support, would be a lot of work.
That may be so, but certainly it can not be an extreme effort for the
Skype development team to provide a way for users to run a 32-bit version of Skype
in a 64-bit Linux environment that happily supports other 32-bit applications.

In any event, I'd like to get Skype back on the air without having to
reverse-engineer it and fix the problem myself. Suggestions welcome.

Robert

----------------------------------------------------------------------------------

OK, now I'm replying to myself...

I finally got this sucker working, no
thanks to skype, except for making the OSS Static version available,
which must have taken them all of 5 minutes work... Ahem.
I digress.

Here's how I got skype working under 64-bit Hardy Heron Alpha 5(4?)
on a Toshiba laptop and a Logitech Clear Chat USB headset.
Mostly, I followed the advice given in this very nice web page:

http://www.pulseaudio.org/wiki/PerfectSetup

1. Download the "Static OSS" version of skype 1.4 from here:
http://www.skype.com/download/skype/linux/

2. If you start this version of skype as recommended in
PerfectSetup:

padsp skype

you get complaints about a missing link library,
libpulsedsp.so. I did an "ls /usr/lib/libpulsedsp.so" and
found that the lib does, in fact, exist, in the 64-bit library,
suggesting that skype is looking for it in /usr/lib32.
This is, apparently, harmless.

3. Going to the options/Sound Devices menu in skype,
I found that I could only choose between /dev/dsp and
/dev/dsp1 for Sound In/Sound Out/Ringing. I picked
/dev/dsp1 and It All Worked.

So, my thanks to the PulseAudioPeople!

Robert

We have tried to redirect people to the appropriate threads here relating to getting 64-bit users running the 32-bit application.

From time to time, there are problems with different combinations of 32-bit libraries on some user's systems. There seem to be no end to these problems, and it's hard to keep track of them all.

Most recently (and as noted above) seems to be some sort of conflict with the 64 and 32-bit ALSA libraries. This appears to be to do with how certain plugin modules for ALSA are linked, and from a technical standpoint, there's not much we can do about this at Skype's side (the problems aren't to do with how Skype is linking to these libraries).

We do look into such issues with active interest, and hope to offer better support to 64-bit users in the future.

For now, we just have to wade through the minefield of issues with 32-bit compatibility variations and see what we can do.

On a positive note, there will be an OSS build of 2.0 released soon.

Andy.

Robert:
The steps bellow work ... but I get "call failed problem with audio playback" in the test call window.
I get the same message with the non OSS static version started with ./skype
....