LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-20-2018, 08:48 AM   #1
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 205

Rep: Reputation: 14
Spotify client SlackBuild libcurl-gnutls.so.4 error, Slackware64 full install.


I have been trying to sort this out off and on for about a week, without a solution, so I am throwing the problem out to the forum. The Spotify SlackBuild no longer works, as the Spotify client version is no longer available, so I downloaded spotify-client_1.0.77.338.g758ebd78-41_amd64.deb and modified the SlackBuild script to match. The install worked fine without any errors, but Spotify refuses to start, instead kicking up the following error message:
Code:
$ spotify
/opt/spotify/usr/bin/spotify: error while loading shared libraries: libcurl-gnutls.so.4: cannot open shared object file: No such file or directory
Anyone have an idea what is going on? I know that I have the curl-7.59.0-x86_64-1_slack1 package installed and can find the files:
  • libcurl.so
  • libcurl.so.4
  • libcurl.so.4.4.0
  • libcurl.so.4.5.0
but no file that contains libcurl-gnutls.
 
Old 04-20-2018, 09:47 AM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,570

Rep: Reputation: 1092Reputation: 1092Reputation: 1092Reputation: 1092Reputation: 1092Reputation: 1092Reputation: 1092Reputation: 1092
Long story short, that proprietary spotify-client_1.0.77.338.g758ebd78-41_amd64.deb is a Debian package (and build) which is not compatible with your Slackware OS.
 
1 members found this post helpful.
Old 04-20-2018, 01:10 PM   #3
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 -current
Posts: 266
Blog Entries: 1

Rep: Reputation: 70
For a quick fix, maybe try this...
Code:
ln -s /usr/lib64/libcurl.so.4.5.0 /usr/lib64/libcurl-gnutls.so.4
 
1 members found this post helpful.
Old 04-20-2018, 01:15 PM   #4
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,545

Rep: Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690Reputation: 4690
Quote:
Originally Posted by jimX86 View Post
For a quick fix, maybe try this...
Code:
ln -s /usr/lib64/libcurl.so.4.5.0 /usr/lib64/libcurl-gnutls.so.4
I somehow doubt that would work.

A bit of background information on this, old document, but still sums up the state of affairs: https://curl.haxx.se/legal/distro-dilemma.html

Basically, Debian (and Debian-based distros) distribute a version of curl that's linked with GnuTLS rather than OpenSSL. Nobody else does, as far as I'm aware.

I'd see if there's a version of the Spotify client intended for Fedora or some other non-Debian derived distro.
 
1 members found this post helpful.
Old 04-20-2018, 02:12 PM   #5
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 4,330

Rep: Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266Reputation: 2266
Quote:
Originally Posted by globetrotterdk View Post
The Spotify SlackBuild no longer works, as the Spotify client version is no longer available
I hope I have understood this, but the deb version for which the SlackBuild has been tested is actually still available in the sbosrcarch mirror

http://slackware.uk/sbosrcarch/by-na...media/spotify/
 
3 members found this post helpful.
Old 04-20-2018, 04:19 PM   #6
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 -current
Posts: 266
Blog Entries: 1

Rep: Reputation: 70
Quote:
Originally Posted by volkerdi View Post
I somehow doubt that would work.
Well, it's an incredibly ugly kludge... but the program runs and I can play music.

I see no reason to upgrade though. I think that using the archived version is the better option.
 
Old 04-20-2018, 04:26 PM   #7
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 205

Original Poster
Rep: Reputation: 14
Quote:
Originally Posted by volkerdi View Post
I somehow doubt that would work.
Actually, it did

Quote:
Originally Posted by volkerdi View Post
A bit of background information on this, old document, but still sums up the state of affairs: https://curl.haxx.se/legal/distro-dilemma.html
Interesting read.

Quote:
Originally Posted by volkerdi View Post
Basically, Debian (and Debian-based distros) distribute a version of curl that's linked with GnuTLS rather than OpenSSL. Nobody else does, as far as I'm aware.

I'd see if there's a version of the Spotify client intended for Fedora or some other non-Debian derived distro.
That would require a serious rewrite of the SlackBuild script wouldn't it, or would ar still do the heavy lifting?

Ponce is correct, that the old version still can be found here.
 
Old 04-20-2018, 04:28 PM   #8
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 205

Original Poster
Rep: Reputation: 14
Quote:
Originally Posted by jimX86 View Post
Well, it's an incredibly ugly kludge... but the program runs and I can play music.

I see no reason to upgrade though. I think that using the archived version is the better option.
Probably, but as we both discovered, it does work, and I had already installed the newer version of Spotify...

Thanks to all for your replies. Very usefull and informative.

Last edited by globetrotterdk; 04-20-2018 at 04:31 PM.
 
Old 04-20-2018, 06:19 PM   #9
orbea
Senior Member
 
Registered: Feb 2015
Distribution: Slackware64-current
Posts: 1,281

Rep: Reputation: Disabled
Whether it "works" or not, its an incredibly terrible hack that is liable to break something somewhere down the line. Probably when you no longer remember doing it...
 
3 members found this post helpful.
Old 04-20-2018, 10:56 PM   #10
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 -current
Posts: 266
Blog Entries: 1

Rep: Reputation: 70
Which brings us back to using the older version. As far as I can tell, that's what the Fedora repos are doing. (If that's the best path, then the link on Slackbuilds.org would need to point to an archived copy, because Spotify doesn't seem to archive the older versions.)

FWIW, Spotify didn't update the i386 version.
 
1 members found this post helpful.
Old 04-21-2018, 11:32 AM   #11
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 98

Rep: Reputation: 25
If I may suggest, it's possible to use the flatpak package of Spotify client.

Flatpak itself is available in SlackBuilds repository, and after installing that it's possible to install Spotify client from Flathub and keep it updated without depending on Debian/Fedora package.
 
1 members found this post helpful.
Old 04-23-2018, 04:48 AM   #12
globetrotterdk
Member
 
Registered: Nov 2006
Posts: 205

Original Poster
Rep: Reputation: 14
Quote:
Originally Posted by lonestar_italy View Post
If I may suggest, it's possible to use the flatpak package of Spotify client.

Flatpak itself is available in SlackBuilds repository, and after installing that it's possible to install Spotify client from Flathub and keep it updated without depending on Debian/Fedora package.
Personally, I prefer AppImage to Flatpak, as an AppImage is largely self-contained, using the existing system libs, rather than have two copies (system and Flatpak) of QT, GTK, etc. libs, but it is good to know that Flatpak is available, should I need it. BTW, I took the general advice given in this thread, and deleted the symlink, uninstalled the upgraded version of Spotify and downloaded and installed the older version, so that I have a clean system.
 
Old 04-23-2018, 06:18 AM   #13
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,239
Blog Entries: 4

Rep: Reputation: Disabled
Quote:
Originally Posted by globetrotterdk View Post
an AppImage is largely self-contained, using the existing system libs
The first part ("an AppImage is largely self-contained") is not true, because of the second part ("using the existing system libs").

And when AppImage doesn't work, this is the exact reason why it doesn't work: the person creating the AppImage has no idea which "existing system libs" actually exist.
 
1 members found this post helpful.
Old 04-23-2018, 10:30 AM   #14
jimX86
Member
 
Registered: Mar 2006
Distribution: Slackware64 -current
Posts: 266
Blog Entries: 1

Rep: Reputation: 70
FWIW, I regret my initial post. I could try and explain my reasoning in this particular case, but the fact remains that my hack encourages bad practices. I can't really justify that.

The latest version is a proprietary binary that depends on libcurl-gnutls. AFAIK, there's no elegant solution to that.

My bigger concern at this point is whether I'm even willing to accept the security risks of the desktop client. Serious question... wouldn't the browser interface be more secure than keeping a port open all day?
 
Old 04-23-2018, 10:54 AM   #15
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware64-current
Posts: 98

Rep: Reputation: 25
Quote:
Originally Posted by globetrotterdk View Post
Personally, I prefer AppImage to Flatpak, as an AppImage is largely self-contained,
I can agree with this, but the problem is that Spotify is not available as AppImage while it's available as Flatpak
 
  


Reply

Tags
error message, slackbuild, slackware64, spotify


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
OpenSSL and GNUTLS are insecure by default on Slackware64 14.2 Matt Owen Slackware 8 01-18-2018 04:30 AM
Spotify segmentation fault on Slackware64 14.0 stahlkrantz Slackware 8 06-11-2013 02:10 AM
required libcurl-gnutls.so.4 rpm teabagindia Linux - Mobile 8 09-15-2010 04:52 AM
PyQt4 module error in SlackBuild for Slackware 12.2 under Slackware64 13... Alexvader Slackware 3 12-28-2009 04:02 PM
Kmymoney2 Slackware64 Sbo Slackbuild Error AlleyTrotter Slackware 4 07-05-2009 10:10 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:39 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration