SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In my experience using explicit dmix via asoundrc makes sound system choke at peak system loads. It's much better to use implicit mixing which alsa already supports. This is my .asoundrc, which makes my analog sound output the default one:
Code:
defaults.ctl.card 1;
defaults.pcm.card 1;
All sounds from different apps are mixed properly, performance is much better than using `type dmix`. I'd suggest looking at /usr/share/alsa/alsa.conf, it has a lot of interesting things.
I originally downloaded Drako's skype bundle with pulseaudio and installed with his install script. It worked.
But later I installed studioware (www.studioware.org) and skype stopped working (no mic). I couldn't figure out how to fix it so I uninstalled all of studioware and uninstalled all the pulse audio packages.
I decided to try the apulse solution:
Compiling apulse after extraction:
bash-4.2$ mkdir build && cd build
bash-4.2$ CFLAGS=-m32 cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release ..
bash-4.2$ make
bash-4.2$ sudo make install
Both my playback and capture are on hw:0,0
$ arecord -f cd -D hw:0,0 >test.wav
$ aplay -D hw:0,0 test.wav
Works!
I have slackbuild for apulse (including the instruction how to install it; warning, it is link to russian slackware forum). This slackbuild was written when apulse does not ships the pulseaudio headers, for so, you don't need pulseaudio to build apulse).
Also, IMO, you don't need to have a asound.conf or ~/.asoundrc modification, if you have a single soundcard.
Last edited by yars; 12-02-2014 at 11:34 AM.
Reason: Removed unneeded "/url" tag, and addition.
yars, apulse is already at SBo. Also, my SlackBuild of Skype has an option to use apulse, which IMHO is more appropriate given the apulse project's main goal.
Last edited by fsLeg; 12-03-2014 at 11:06 AM.
Reason: typo
Some news at the Skype front. Microsoft has released "Skype for Web", a browser frontend that allows us to log in to the Skype network without the actual client.
Eion Robb is working on that end to create a standalone plugin for Pidgin. I made a SlackBuild for that. It's not yet ready - if you write to a contact it may get deleted from your contact list and all other kinds of weird things can occur.
I've had the same problem with skype. Then I did a quick search, and found "apulse" on slackbuilds. apulse is a compatibility layer between Pulse Audio and ALSA. Compiled it, installed it and I had sound again. Hope this helps.
The "Skype Web" plugin from Eion finally works stable for me. It was segfaulting very often - we traced it down to some of my contacts having weird characters (<,",') in their status messages.
Pidgin can escape these characters with a different parser. A quick and dirty fix. I updated my SlackBuild and I am officially ditching the damn client now. I don't make calls with Skype anyway :-)
It maybe useful or at least a little bit time saver to anyone wanting to use apulse which works pretty well by the way that if you have slackware64 you have to compile it for 32bit since skype doesn't bother building native 64bit binaries.
slackbuilds have a little bit of documentation on how to compile it for 32bit arch, if you are using sbopkg program it's as simple as:
COMPAT32=yes sudo -i /usr/sbin/sbopkg -i apulse
I would like to thank all the contributors to this thread. With your help I now appear to have a working Skype on my Slackware64-current setup.
First, I cheated and installed the package skype_static-4.3.0.37-x86_64-3sl.txz that includes apulse from zerouno at post#251. I have to change the symlink '/lib/ld-linux.so.2 -> /lib/ld-2.20.so' to '/lib/ld-linux.so.2 -> /usr/share/skype/lib32/ld-2.17.so' for this package to work for me. (Maybe I should do a rebuild?)
I then followed the instructions under the heading "Skype with a grain of salt" in the README.SLACKWARE linked by Didier Spaier in post#268. I needed to add a line '#includedir /etc/sudoers.d/' using visudo to /etc/sudoers to complete this and also remember to logout and login for the new settings to take effect.
I am using a webcam with an inbuilt microphone, which appears as a second sound card in alsamixer. To get the microphone to work I added a ~/.asoundrc file slightly modified from the one posted by coldbeer at post#287 for the dedicated skype user with the contents
Code:
pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm "hw:0,0"
}
capture.pcm {
type plug
slave.pcm "hw:1,0"
}
}
Skype is by far the most annoying thing I have ever had to install and deal with. While skype 4.2 was doable, skype 4.3 seems to be close to impossible. I've tried most things in this thread (slackbuilds, static, etc), but never managed to install it with working audio. I ended up dual-booting Mint just for Skype. This is NOT something I would normally do, but pressure from people at my job has forced me to Eventually, I'll be able to afford a smartphone and maybe then I won't ever have to deal with it again on my computers.
Hello Firefox is a great alternative tho and maybe more people will adopt it. I'll certainly try to get people to try it out.
Last edited by metaschima; 04-19-2015 at 07:18 PM.
Skype is by far the most annoying thing I have ever had to install and deal with. While skype 4.2 was doable, skype 4.3 seems to be close to impossible. I've tried most things in this thread (slackbuilds, static, etc), but never managed to install it with working audio. I ended up dual-booting Mint just for Skype. This is NOT something I would normally do, but pressure from people at my job has forced me to Eventually, I'll be able to afford a smartphone and maybe then I won't ever have to deal with it again on my computers.
Hello Firefox is a great alternative tho and maybe more people will adopt it. I'll certainly try to get people to try it out.
Getting Skype 4.3 did cost me a lot of time, but since then it has been working OK. If you could tell me more about your system (distribution, version, 32-bit or 64-bit, etc.), I might be able to help you.
I was trying to install it on Slackware 14.0, but it's gone now, I'll try again with the next slackware version when it comes out (which may be soon). Part of it was me being lazy and not upgrading to Slackware 14.1, where the chances of it working are higher.
I was trying to install it on Slackware 14.0, but it's gone now, I'll try again with the next slackware version when it comes out (which may be soon). Part of it was me being lazy and not upgrading to Slackware 14.1, where the chances of it working are higher.
I managed to get it working on Slackware64 13.37, so I do not think that the version should really be an issue.
Are you working with the 32-bit or the 64-bit version of Slackware?
It was 64-bit, but I can't diagnose it anymore, I already installed Mint over it and will install next version Slackware when it comes out.
I mean I installed Alien Bob's multilib, I tried the various skype slackbuilds (in this thread and slackbuilds.org) and the static package and various asoundrc, but nothing made the audio work. Probably, more time spent on it may have finally fixed it, but I draw the line at around 5 hours spent trying to make it work. Installing Mint took less time, so I took the easy way out, but I don't like pulseaudio or skype, so I expect that buying a smartphone will no longer require me to keep Mint around.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.