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.
No, I was running everything as root. When I first installed Slackware a couple of months ago I created an user but couldn't login at all, so I removed it and left it that way. But this time it seems to work except for the sound.
No, I was running everything as root. When I first installed Slackware a couple of months ago I created an user but couldn't login at all, so I removed it and left it that way. But this time it seems to work except for the sound.
First check that you made it a member of the "audio" and "video" groups. I don't know how you created it, but the easiest way is to use the "adduser" command. You can generally accept the default answers and when asked, press the UP arrow key to add/select/edit additional groups. It will propose you this list: audio cdrom floppy plugdev video power netdev lp scanner. Just accept that pressing [Enter] and continue to answer other questions.
Thank you, Didier! Added the user to the groups and the sound is working! The only problem remains 'pavucontrol'. Uploaded shot.
The only time I get that for pavucontrol is when I run pulseaudio -k with alsa-plugins set to load.
and my /etc/pulse/client.conf is set to
Quote:
; autospawn = yes
/etc/pulse/default.pa
Quote:
### Make some devices default
#set-default-sink output
#set-default-source input
load-module module-alsa-sink device=dmix
load-module module-alsa-source device=dsnoop
but if I do this.to the
/etc/pulse/default.pa
Quote:
### Make some devices default
set-default-sink output 0
set-default-source input 1
then after a reboot I am able to restart pulseaudio.
; autospawn = yes
with autospawn = yes pulseaudio -k restarts pulseaudio.
so this tells me if you do not have a default ouput and input pulseaudio
crashes till you got to run level 1 or reboot. it has to restart
the xserver in order to update. one pid at a time.
right or wrong I am just learning this thing.
It takes me few days to understand why skype 4.3 always 'aborted'.
It's the CPU. You need sse2 Flag to get skype 4.3 working.
I have an old PC, with an old CPU that only have sse, not sse2.
So i switched to an old Laptop, this one has sse2, installed Slackware 14.1 (32-bit).
Now skype 4.3 works perfect.
Build and installed these packages, in that order:
speex
json-c
libsigc++
glibmm
cairomm
pangomm
atkmm
mm-common
libasyncns
then made the pulse in Terminal:
groupadd -g 216 pulse
useradd -u 216 -g pulse -d /var/lib/pulse pulse
After that build and installed
pulseaudio
gtkmm3
pavucontrol
and finally skype
All without any error.
Then, as my regular user, made a script:
(sorry, don't know how to make these 'Code' box)
#!/bin/bash
pulseaudio --start
skype
pulseaudio --kill
made it +x and copied it to my Desktop.
Then edited /etc/pulse/default.pa on lines 44 and 45,
(as root)
they look now:
load-module module-alsa-sink device=hw:0,0
load module module-alsa-source device=hw:0,0
I started skype with the script,
logged in, gone to options,
in audio devices pulseaudio is present,
opened the pulse volume control.
The only thing i needed to change was the output device.
I pressed the testvoice, sound came up.
Made the test call, all went ok.
Never opened the pavucontrol directly.
Never used the original start button from skype,
only the script.
After closing skype, pulseaudio is killed by the script.
This solution work for me.
I must say, i use skype not often. But this way, it works.
I have no need for pulseaudio except the new skype.
(btw, i was not happy when first the only message from skype was 'aborted'.
I wanted to make it to work. Finally i got it, on the right CPU.)
Maybe this is useful for some people with older hardware.
And sorry for the missing quotes around the Code. I will learn it.
Hi I think Msoft make another realy mess with the new skype 4.3, plz report if any one get the skype locked any other programs when he is running ; I m not able to solve this , every time I used skype he locked the sound , when he finish then other programs make sound like they was waiting.
using Slackware 14.1 x32.with Kde desktop.
Hi, if anyone need to continue using old version of skype (4.2.x), these steps works for me:
* remove skype 4.2.x version
* install skype 4.3.x version
* connect and mark to "auto connect" on next time
* click Exit (don't disconnect)
* remove skype 4.3.x
* install again skype 4.2.x version
* now the skype will connect automatically
* NEVER DISCONNECT when exit
You probably don't need to explicitly start pulseaudio like that before running skype. It should already be started by /etc/xdg/autostart/pulseaudio.desktop (or pulseaudio-kde.desktop) when you log in - you can check whether its running with 'ps -ef |grep pulse'. That means you can just launch skype directly from the Applications Menu/Internet menu and its pavucontrol button will just work.
Of course if you definitely want to kill pulseaudio after using skype, then thats a different matter. However, having had to use it myself for a while now, I've found pulseaudio is not as evil as some people claim.
Of course if you definitely want to kill pulseaudio after using skype, then thats a different matter. However, having had to use it myself for a while now, I've found pulseaudio is not as evil as some people claim.
you need to turn off in your /etc/pulse/client.conf
autospawn=yes to autospawn=no to for kill to work.
* remove skype 4.2.x version
* install skype 4.3.x version
* connect and mark to "auto connect" on next time
* click Exit (don't disconnect)
* remove skype 4.3.x
* install again skype 4.2.x version
* now the skype will connect automatically
* NEVER DISCONNECT when exit
but for my Skype it looks like
Code:
* remove skype 4.2.x version
* install skype 4.3.x version
* connect with mark to "Sign me in when Skype starts"
* click Quit (don't Sign Out)
* remove skype 4.3.x
* install again skype 4.2.x version
* now the skype will connect automatically
* NEVER SIGN OUT, ALWAYS ONLY QUIT
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.