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.
Have anyone tried skype 4.3 in Slackware?
I tried yesterday, unfortunately does not support ALSA.
It is useless for audio and video calls.
Is there alternative to installing the pulse audio.
Have anyone tried skype 4.3 in Slackware?
I tried yesterday, unfortunately does not support ALSA.
It is useless for audio and video calls.
Is there alternative to installing the pulse audio.
Unfortunately, there is not a viable alternative. See this post for details. I thought Skype for Linux was great too, and used it in the past. However, as PulseAudio is not an option for me (and a lot of other Slackers as well), it looks like this game is over, unfortunately.
However, as PulseAudio is not an option for me (and a lot of other Slackers as well)
I see that build material for PulseAudio is provided @ SlackBuilds.org. What inconveniences or drawbacks are there using it? I ask because I'm a Skype user too.
Last edited by Didier Spaier; 06-20-2014 at 08:46 AM.
I see that build material for PulseAudio is provided @ SlackBuilds.org. What inconveniences or drawbacks are there using it? I ask because I'm a Skype user too.
I've got my audio working just the way I want it, with USB Audio and a Bluetooth stereo system. I know that PulseAudio has ways to get these working under it as well, but I'm of the old school that thinks that if something 'ain't broke, don't fix it!'. I don't use Skype often enough to justify the installation of PA, and judging from subsequent posts, I'll stick with the older version of Skype if and when the (occasional) need arises, because it'll still work.
been looking at this tried to build tox qt gui but no qt 5.0.
hey Pat I can live with out Skype but QT 5.X is it stable yet.
Trust me Pulse is just a layer that uses jack this has nothing to do with
the ability. Skype developers are very lazy. they just grabbed the pulse headers and used them for the build. Pulse really does screw up Slackware I have two systems I test it on.
And none of them work as good as just using qtjack. Alsa modules are in the kernel I guess pulseaudio will be going into it soon. and systemd any other thing Linus must really like sucking up to M$.
I guess the kernel will Get forked again. We all know it not about local community it is about Linus and Linux foundation sucking up to the big bucks.
Not that this directly addresses the OP's PulseAudio question, but since people are suggesting Skype alternatives, a decent open-source VoIP programme I've been using is Jitsi (formerly SIP Communicator). I recently successfully tested 3-way video chat between 2 linux machines and a mac. Performance was a little laggy, probably because of my connection, but it was otherwise excellent.
If anyone wants to try it (tested on slackware64-14.1 with a couple of packages from slackbuilds.org), here is a slackbuild that uses their git repository (you have to clone it first). I built it using fakeroot: $ TMP=/tmp fakeroot ./jitsi.SlackBuild
Code:
#!/bin/sh
# jitsi.SlackBuild written by Tom 2014/05/03
# jitsi (SIP Communicator) available from https://jitsi.org/
# requires:
# from slackbuilds.org: apache-ant and openjdk or similar
# SlackBuild based on:
# https://jitsi.org/Documentation/RetrievingAndBuildingTheSources
# https://jitsi.org/Documentation/HowToBuildAnInstaller
# /usr/bin/jitsi shell script modifications based on the ofiicial rpm package
PRGNAM=jitsi
BUILD=${BUILD:-1}
TAG=${TAG:-_tom}
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) ARCH=i486 ;;
arm*) ARCH=arm ;;
*) ARCH=$( uname -m ) ;;
esac
fi
CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$TMP/package-$PRGNAM
OUTPUT=${OUTPUT:-/tmp}
if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686"
LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC -m64"
LIBDIRSUFFIX="64"
else
SLKCFLAGS="-O2"
LIBDIRSUFFIX=""
fi
set -e
rm -rf $PKG
mkdir -p $TMP $PKG $OUTPUT
# Original source:
# git clone https://github.com/jitsi/jitsi.git
# if bad connection do a combo of git clone --depth=1 copied over an unzipped snapshot downloaded from github
# and/or do $ git fetch --tags
cd $CWD/$PRGNAM
git checkout master
git branch -D tom &2>1
git pull
VERS=`git tag | tail -n1`
VERSION=${VERSION:-${VERS}}
# find latest stable based on https://download.jitsi.org/jitsi/src/
# but we're going to stick with the latest stable release:
VERSION="2.4.4997"
BUILD_VERSION="`echo $VERSION | cut -d'.' -f3`"
echo "Compiling $PRGNAM version $VERSION"
git checkout -b tom $BUILD_VERSION
cd $TMP
rm -rf $PRGNAM-$VERSION
mkdir -p $PRGNAM-$VERSION
cp -a $CWD/$PRGNAM/* $TMP/$PRGNAM-$VERSION
cd $TMP/$PRGNAM-$VERSION
chown -R root:root .
find . \
\( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
-exec chmod 755 {} \; -o \
\( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
-exec chmod 644 {} \;
# this just gives us the version number inside the programme, which is useful
sed -i "s/0.build.by.SVN/$BUILD_VERSION/g" src/net/java/sip/communicator/impl/version/NightlyBuildID.java
# the meat
ant rebuild
mkdir -p $PKG/usr/bin
sed 's/_PACKAGE_NAME_/jitsi/g' resources/install/debian/jitsi.sh.tmpl | sed 's#^CLASSPATH=.*$#CLASSPATH=$LIBPATH/felix.jar:$SCDIR/sc-bundles/sc-launcher.jar:$SCDIR/sc-bundles/util.jar:$LIBPATH#' | sed 's#/usr/lib/jni#$LIBPATH/native#' > $PKG/usr/bin/jitsi
chmod +x $PKG/usr/bin/jitsi
mkdir -p $PKG/usr/share/applications
sed 's/_PACKAGE_NAME_/jitsi/g' resources/install/debian/jitsi.desktop.tmpl | sed 's/_APP_NAME_/Jitsi/g' > $PKG/usr/share/applications/jitsi.desktop
mkdir -p $PKG/usr/share/jitsi/lib/bundle
mkdir -p $PKG/usr/share/jitsi/lib/native
cp lib/{felix.client.run.properties,felix.jar,jitsi-defaults.properties,logging.properties} $PKG/usr/share/jitsi/lib
# what about the jdic files? don't appear to be needed!
if [ "$ARCH" = "x86_64" ]; then
cp -a lib/native/linux-64/*.so $PKG/usr/share/jitsi/lib/native
else
cp -a lib/native/linux/*.so $PKG/usr/share/jitsi/lib/native
fi
cp lib/bundle/{commons-logging.jar,log4j.jar,org.apache.felix.bundlerepository-1.6.4.jar} $PKG/usr/share/jitsi/lib/bundle
mkdir -p $PKG/usr/share/jitsi/sc-bundles
cp sc-bundles/* $PKG/usr/share/jitsi/sc-bundles || echo # note this is so that the 'set -e' d.n. cause it to break here
cp sc-bundles/os-specific/linux/* $PKG/usr/share/jitsi/sc-bundles
# remove unneeded
rm $PKG/usr/share/jitsi/sc-bundles/*-slick.jar
mkdir -p $PKG/usr/share/man/man1
sed 's/_PACKAGE_NAME_/jitsi/g' resources/install/debian/jitsi.1.tmpl | sed 's/_APP_NAME_/Jitsi/g' | gzip -9 > $PKG/usr/share/man/man1/jitsi.1.gz
mkdir -p $PKG/usr/share/pixmaps
cp resources/install/debian/jitsi-*.xpm $PKG/usr/share/pixmaps
cp resources/install/debian/jitsi.svg $PKG/usr/share/pixmaps
mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION
cp \
LICENSE README.md \
$PKG/usr/doc/$PRGNAM-$VERSION
cat $CWD/$0 > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild
mkdir -p $PKG/install
cat $CWD/slack-desc > $PKG/install/slack-desc
#cat $CWD/doinst.sh > $PKG/install/doinst.sh
cd $PKG
/sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz}
mv $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} $CWD
been looking at this tried to build tox qt gui but no qt 5.0.
hey Pat I can live with out Skype but QT 5.X is it stable yet.
Trust me Pulse is just a layer that uses jack this has nothing to do with
the ability. Skype developers are very lazy. they just grabbed the pulse headers and used them for the build. Pulse really does screw up Slackware I have two systems I test it on.
And none of them work as good as just using qtjack. Alsa modules are in the kernel I guess pulseaudio will be going into it soon. and systemd any other thing Linus must really like sucking up to M$.
I guess the kernel will Get forked again. We all know it not about local community it is about Linus and Linux foundation sucking up to the big bucks.
This is a little off topic.
Pulse audio uses alsa to get audio from the sound hardware.
Since pulse audio does not talk with the hardware directly it is highly unlikely that theirs modules will be added to the kernel.
Not that this directly addresses the OP's PulseAudio question, but since people are suggesting Skype alternatives, a decent open-source VoIP programme I've been using is Jitsi (formerly SIP Communicator).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.