LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Skype 4.3 (https://www.linuxquestions.org/questions/slackware-14/skype-4-3-a-4175508618/)

Didier Spaier 07-17-2014 12:31 PM

@Drakeo: The SlackBuild states:
Code:

case "$ARCH" in
  x86_64)
    echo "$ARCH is not supported, you will need 32bit compatibility libs..."
    ARCH=i486
    ;;

But as multilib is not supported by slackbuilds.org, I assume that you are on your own here.

Drakeo 07-17-2014 06:55 PM

look I been using skype and pulse audio for years OMG Didier Spaier come on we had it clear back in the GSB builds. Why would you even bring up multilib. this is about what it takes to control pulseaudio in multilib or 32 bit. So I will make this simple I did my home work on this issue months ago.
but to see a slackbuild that gets OK for something that will not use the sound part come on you need pavucontrol no mater what . and look at all the dependencies.
Slackbuild what are you doing letting this get through. VOIP program will run with no Voice. HELLO.

Ponce what is it with putting another broken half used program out for slackbuilds just like MIXXX a broadcasting program that will not broadcast. just because the maintainer does not want to do their home work. Yet it goes in none tested just because it actually runs does not mean it functions.
Ponce you maintain the git so why all the broken programs in stable. Voice is a optional dependency in a VOIP program.

55020 07-17-2014 09:44 PM

Quote:

Originally Posted by Drakeo (Post 5205582)
Ponce you maintain the git so why all the broken programs in stable.

Perhaps because busy volunteer maintainers rely on timely, efficiently routed (and preferably polite) feedback?

ponce 07-18-2014 12:55 AM

Quote:

Originally Posted by Drakeo (Post 5205582)
Ponce what is it with putting another broken half used program out for slackbuilds just like MIXXX a broadcasting program that will not broadcast. just because the maintainer does not want to do their home work. Yet it goes in none tested just because it actually runs does not mean it functions.

mixxx is a mixing application and it does that. I suggest you get in touch with the maintainer (they're called "maintainers" for a reason ;) ), better providing patches, if there are some additional functions that don't work. If the maintainer doesn't respond in a reasonable amount of time (two weeks? one month? we are all volunteers, you know, and we can have the most disparate problems in RL), write to the slackbuilds-users mailing list.
Quote:

Originally Posted by Drakeo (Post 5205357)
whats with this Ponce.

Quote:

Ponce you maintain the git so why all the broken programs in stable.
please elaborate, as I cannot understand what you're referring to and how this involves me, so I cannot help you providing an answer.

ml4711 07-18-2014 02:35 AM

@Drakeo why so grumpy,
- go out in the garden and get some coffee :-)

Well - I have mixxx broadcasting through icecast!
(compiled on slackware64 14.0)

Install libspeex and libshout

Change in buildscript:

Code:

# it seems libshout isn't detected :(
CFLAGS="$SLKCFLAGS" \
QTDIR=/usr/lib$LIBDIRSUFFIX/qt \
LDFLAGS="-lspeex" \        <--- add this line
scons \
  shoutcast=1 \            <--- change to "1" on this line
  prefix=/usr

QTDIR=/usr/lib$LIBDIRSUFFIX/qt \
LDFLAGS="-lspeex" \        <--- add this line
scons \
  install_root=$PKG/usr \
  prefix=/usr \
  install


Drakeo 07-19-2014 04:02 AM

Quote:

Originally Posted by ponce (Post 5205714)
mixxx is a mixing application and it does that. I suggest you get in touch with the maintainer (they're called "maintainers" for a reason ;) ), better providing patches, if there are some additional functions that don't work. If the maintainer doesn't respond in a reasonable amount of time (two weeks? one month? we are all volunteers, you know, and we can have the most disparate problems in RL), write to the slackbuilds-users mailing list.


please elaborate, as I cannot understand what you're referring to and how this involves me, so I cannot help you providing an answer.

You may note I contact every maintainer first except this skype issue. I do not need to. This is skype slackware thread and the. First off I started complaining to the maintainer of MIXXX with 13.1 then A direct note to you that said hey libshout was updated 2 years ago that solves the problem. As for skype 4.3 if you want to use sound and voice you need a full pulseaudio and pavucontrol with install. Since this is a forum on slackware. It is up to Slackers to tell problems about broken stuff so they do not spend hours working on it. If you remember back 2007 you asked me if I wanted to maintain pulseaudio I said thank but no I would rather just use jackd. It wasn't till slackware 14.1 did the maintainer of mixxx actually update to libshout (2.3.1) which had been out for a couple of years and listed stable. MIXX 1.10.1 is far from what is a good thing since shoutcast has been bought and sold. Just like skpye.
Quote:

LDFLAGS="-lspeex" \ <--- add this line
scons \
shoutcast=1 \ <--- change to "1" on this line
prefix=/usr
This was done because the maintainer did not read what was going on with the issue of 1.10 Libshout headers had changed. And that source code required libshout (2.3.1). and that is why it is set to default on the build. To lazy to go read the developers notes. If you want to be the standard of Slackware just be honest.
Grumpy you damn right we depend on honest people to do there home work before they go public.
You have a CLUE people put their system in root and use your build scripts.
You may trust the maintainer but I can see most of the maintainers are not part of developing.
https://github.com/Drakeo/mixxx

ponce 07-19-2014 04:22 AM

Quote:

Originally Posted by Drakeo (Post 5206315)
First off I started complaining to the maintainer of MIXXX with 13.1 then A direct note to you that said hey libshout was updated 2 years ago that solves the problem.

I'm sorry, but sending private notes (I can't even remember this one) for maintaining issues with specific packages it's not recommended: beside the fact that I receive tons of emails daily and it can happen that some task can slip, these are things that must be brought to public attention, so that they can be tested by other people and kept track of. The correct place is the slackbuilds-users mailing list so that if the maintainers can't keep up for some reason, someone else can step in: we at SBo check and test submitted changes but cannot do also the maintainers' work for all the stuff we host (I think 4000+ scripts).
Quote:

As for skype 4.3 if you want to use sound and voice you need a full pulseaudio with install. Since this is a forum on slackware. It is up to Slackers to tell problems about broken stuff so they do not spend hours working on it.
yes, but I don't maintain pulseaudio or skype (and I don't want to), so you really haven't to complain with me for any problem with it, refer to the respective maintainers.
Quote:

If you remember back 2007 you asked me if I wanted to maintain pulseaudio I said thank but no I would rather just use jackd.
sorry, I don't remember even this, probably because it happened 7 years ago (I hope you can understand).

please write to the slackbuilds-users mailing list (this forum is not a substitute) explaining your issues with mixxx, pulseaudio and skype (please do it in different messages, putting the maintainers in cc, to easily keep track of the requests) eventually attaching patches to the messages.

ponce 07-19-2014 04:40 AM

well, I found the emails you sent me about mixxx/libshout, on 2013/10/18
Quote:

Hi Ponce Drakeo here. I been building that Mixxx for 3 years now. and tried
to contact the maintainer. The Libshout we use in slackbuilds will not
build it. when I pull the 2.3.1 libshout and build and install with out a
script. the build will find the header file. I believe the header file has
been renamed. and that was back in 13.37 or earlier.

I really like to see the latest stable version 1.11.0 go in to 14.1 I am
going to build up a tar ball and submit it.

Quote:

you have to contact libshout and mixxx maintainers for this: I cannot do
much in this sense.

but consider that libshout is needed also by other stuff we have in our
repository, namely ices, ices-cc and vlc, so before suggesting an
upgrade of that be sure that it works fine also with these thingies.
Quote:

Thank You for your reply. the latest stable has more dependencies all in
SBO. the only thing I had to do was build a libshout package with the
latest stable 2.3.1.
1.11.0 has been stable over 6 months. Like to say Alien Bob has been
using the libshout-2.3.1 in his restrictive builds for some time now.
and everything I have compiled from 13.37 to 14.1 rc compiles it and uses
it fine with the sbobuilds script and the the headerfile for libshout is
detected.
Thanks for your hard work
Be well
then, after a few days, I upgraded libshout

http://slackbuilds.org/cgit/slackbui...816c932d6be1a0

Drakeo 07-19-2014 10:23 PM

thank you for your reply Ponce. MIXXX is a very nice program. Skype is broken. If you want to use Voice over internet protocol you will need the pulseaudio
and PulseAudio Volume Control those two programs go hand and hand and the propriety software in order to create the virtual device will only call on pavucontrol. that is the program front end for.
pulseaudio witch uses Optional deps: jack-audio-connection-kit, avahi, lirc, libasyncns, orc In order to create the virtual devices Skype software looks for.

This was well documented https://support.skype.com/en/faq/FA1...kype-for-linux.
When skype 4.3 cam out. All the software you need to get it running is in Slackbuilds. what they did was only use pulseaudio headers and libraries to compile against. And just created a link to pavucontrol it is easier for someone in microbucks to do that I guess.

I started using google talk it works great in Chromium the Phone rates are free for inside the USA. So skype lost another paid account.

schmatzler 08-01-2014 11:42 AM

It looks like Microsoft has started blocking out their old clients.

I can't login anymore with the previous version that still uses ALSA. I can reset my password online and login online, but not in the client.

If Microsoft really tries to force me to the PA-crap, I'm gone. I think I can live without it. It's just sad that I still have some money left on my Skype account :(

metageek 08-01-2014 12:02 PM

Quote:

Originally Posted by schmatzler (Post 5213291)
It looks like Microsoft has started blocking out their old clients.

I'm seeing the same thing here. I have lots of money in my account and even have skype in. Will finish the $ I have there with skype on a Win VM, but after that I will be using Google hangout only.

Goodbye skype.

Paulo2 08-01-2014 12:22 PM

Same problem here, first they asked for a code that they sent me by email,
but even with the code there is a message 'We cannot recognize your connection'

I don't know if this is a version problem (for me, even with PA installed, the
new Skype version doesn't work) or M$ is trying to make Skype only a paid service.

+1 Goodbye Skype

coldbeer 08-01-2014 07:28 PM

Quote:

Originally Posted by schmatzler (Post 5213291)
It looks like Microsoft has started blocking out their old clients.



I'm a skype subscriber and I use an old skype_static-2.2.0.35-x86_64-2sl.tgz on Slackware 14.1 just fine. I've done video calls with my parents on the other side of the country with no issues.

Update August 8th:
Guess not. Its failing now also. I have a desktop skype phone also. Wonder how long its going to work.

Time for Ooma.

gbowden 08-01-2014 08:06 PM

Skype on multilib.
 
On Slackware64 with multilib I finally got Skype 4.3 to work.

You need the 32bit version of pulseaudio for it to work.

To build pulseaudio I had to add --disable-oss-wrapper to the slackbuild.

I had to build the following packages:

Code:

GConf-compat32-3.2.5-x86_64-1compat32.txz
avahi-compat32-0.6.31-x86_64-2slcompat32.txz
fftw-compat32-3.3.3-x86_64-1compat32.txz
jack-audio-connection-kit-compat32-0.121.3-x86_64-4slcompat32.txz
json-c-compat32-0.11-x86_64-1_fscompat32.txz
libcap-compat32-2.22-x86_64-1compat32.txz
pulseaudio-compat32-5.0-x86_64-1_SBocompat32.txz
samba-compat32-4.1.11-x86_64-1_slack14.1compat32.txz
speex-compat32-1.2rc1-x86_64-9slcompat32.txz
udev-compat32-182-x86_64-7compat32.txz

Then Skype would recognise my audio devices instead of saying "Virtual Device".

I also had to build pavucontrol paprefs to configure pulseaudio.

Before I was using a skype-docker-pulseaudio docker container (from here.) to use Skype.

bgeer 08-02-2014 11:31 AM

Ugh - no help here!
 
<rant>Ok, so I fought the pulseaudio battles on Ubuntu when PA broke audio on each release. So, I did a Back to Slack on all my laptops & sound just works without PA.</rant>

So, just how hard would it have been to make Skype compatible with either ALSA or PA?

I know that's not the MicroQuack way of doing things...but hey?

Argh!

<sorry>


All times are GMT -5. The time now is 11:38 AM.