Member Avatar for happygeek
happygeek 2,411 Most Valuable Poster

There are not many things, it has to be said, that a Linux user would covet of his Windows using neighbor. Skype is quite possibly one of them though, but not for much longer. The first meaningful development for the Linux Skype client in almost a year has arrived in the shape of Beta

I was starting to think that Microsoft rather than eBay had acquired Skype, such has been the time, money and devotion lavished upon the Windows client since: video calls added, stability issues fixed, UI beefed up yada, yada, yada. The bad news is that Linux still does not get any of these. So why the excitement? Well how about because it has been updated at all, suggesting that the eye candy big guns are not too far away. The fact that Advanced Linux Sound Architecture (ALSA) has now been incorporated so that Skype can be switched between this and the default Open Sound System (OSS) is none too shabby either. Nor is the public API for X11 windowing, which might mean some application integration on the Linux front finally.

Oh, and while on the subject of non-Windows Skype versions: do not be tempted by the video enabled Mac version that is doing the P2P rounds. This is actually an internal development version, and one that Skype itself claims to be unstable and extremely buggy. In an attempt, perhaps, to dissuade the curious Skype also warns it will eat your contacts and ‘other data’ as well as your children. Err, actually, I may have added the bit about children, but you get the idea…

  • 1 Contributor
  • 0 Replies
  • 197 Views

Dani AI

Generated

As observed, this refresh is a welcome step. Practical, appliance-ready checks and quick fixes that were commonly needed around this generation of the Linux client are still useful years later — a short checklist follows for verifying sound, permissions and runtime diagnostics so the client actually connects and transmits audio.

Basic diagnostics to run from a shell:

# list ALSA devices and cards
aplay -l
cat /proc/asound/cards

# check kernel sound modules
lsmod | grep snd

# look for OSS device nodes (legacy)
ls -l /dev/dsp /dev/snd 2>/dev/null

# test capture and playback
arecord -f cd -D plughw:0,0 test.wav && aplay test.wav

# run the client from a terminal and capture output
skype &> ~/skype-run.log

Common fixes and notes

  • Confirm mixer levels and capture settings with alsamixer (unmute Capture/Mic, raise levels). Muted channels are the most frequent cause of “no mic” symptoms.
  • Ensure the user has permission to access sound devices (look for an audio or similar group; add the user there and re-login if needed).
  • If the device is reported as “busy”, stop other sound servers or use the appropriate OSS-to-ALSA/PA wrapper your distro provides (wrappers like aoss or padsp are standard options).
  • On 64-bit installs, missing library errors often mean 32-bit compatibility libs are required for a packed binary client.
  • Back up the local profile before experimenting: cp -a ~/.Skype ~/.Skype.bak keeps contacts and settings safe.

When the terminal output shows missing symbols, device errors, or denied permissions, those messages are the diagnostic lead to follow (missing libs, wrong device, or a sound server conflict). The steps above address the majority of integration and sound problems encountered by users running the binary Linux client on varied distributions.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.