You are not logged in.

#1 2017-04-06 17:12:19

protomolecule
Member
Registered: 2017-04-06
Posts: 6

Spotify is not working anymore due to the openssl rebuild.

Hey,

I am currently using [testing] which also includes the openssl rebuild which I think is the reason why spotify isn't working anymore.

Installed are openssl and openssl-1.0.

When I start spotify I will get the following error message:

/usr/share/spotify/spotify: /usr/lib/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/share/spotify/spotify)
/usr/share/spotify/spotify: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /usr/share/spotify/spotify)
/usr/share/spotify/spotify: /usr/lib/libcurl.so.3: no version information available (required by /usr/share/spotify/spotify)

readelf -V /usr/share/spotify/spotify produces this:

0x01c0: Version: 1  File: libssl.so.1.0.0  Cnt: 1
0x01d0:   Name: OPENSSL_1.0.0  Flags: none  Version: 26
0x01e0: Version: 1  File: libcrypto.so.1.0.0  Cnt: 1
0x01f0:   Name: OPENSSL_1.0.0  Flags: none  Version: 27

I am wondering if it's possible somehow to start spotify without the version checks? Well, since rebuilding spotify is simply not possible.

Offline

#2 2017-04-06 17:54:04

Slithery
Forum Moderator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 4,460

Re: Spotify is not working anymore due to the openssl rebuild.

Does installing testing/openssl-1.0 help?

EDIT - Sorry, missed that you already had this installed. Can you launch spotify with...

LD_PRELOAD=/usr/lib/libssl.so.1.0.0;/usr/lib/libcrypto.so.1.0.0 spotify

Last edited by Slithery (2017-04-06 17:58:25)


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2017-04-06 18:15:28

protomolecule
Member
Registered: 2017-04-06
Posts: 6

Re: Spotify is not working anymore due to the openssl rebuild.

slithery wrote:

Does installing testing/openssl-1.0 help?

EDIT - Sorry, missed that you already had this installed. Can you launch spotify with...

LD_PRELOAD=/usr/lib/libssl.so.1.0.0;/usr/lib/libcrypto.so.1.0.0 spotify

Thank you for the advice but unfortunately I am getting a segmentation fault:

coredumpctl info:

           PID: 2317 (libcrypto.so.1.)
           UID: 1000 (username)
           GID: 10 (wheel)
        Signal: 11 (SEGV)
     Timestamp: Thu 2017-04-06 20:12:06 CEST (36s ago)
  Command Line: /usr/lib/libcrypto.so.1.0.0
    Executable: /usr/lib/libcrypto.so.1.0.0
 Control Group: /user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.serv
          Unit: user@1000.service
     User Unit: gnome-terminal-server.service
         Slice: user-1000.slice
     Owner UID: 1000 (username)
       Boot ID: 3dc6251cf7234941aa27d96fe09473fb
    Machine ID: cbc9d85ef50745368e33e37ca3743452
      Hostname: username
       Storage: /var/lib/systemd/coredump/core.libcrypto\x2eso\x2e1\x2e.
       Message: Process 2317 (libcrypto.so.1.) of user 1000 dumped core.
                
                Stack trace of thread 2317:
                #0  0x0000563c3ff3a623 read_lebn (/usr/lib/libcrypto.so.1.0.0)
                #1  0x0000000000000001 n/a (n/a)

Offline

#4 2017-04-06 18:20:27

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 29,483
Website

Re: Spotify is not working anymore due to the openssl rebuild.

Moving to AUR Issues...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2017-04-06 19:00:05

mis
Member
Registered: 2016-03-16
Posts: 234

Re: Spotify is not working anymore due to the openssl rebuild.

Works for me using this two packages and modified /usr/bin/spotify

https://aur.archlinux.org/packages/libcurl-openssl-1.0/
https://aur.archlinux.org/packages/libo … .0-compat/

#!/bin/sh
export "LD_PRELOAD=libcurl-openssl-1.0.so /usr/lib/openssl-1.0-compat/libssl.so /usr/lib/openssl-1.0-compat/libcrypto.so"
/usr/share/spotify/spotify "$@"

Offline

#6 2017-04-06 21:41:47

letku
Member
Registered: 2017-02-02
Posts: 12

Re: Spotify is not working anymore due to the openssl rebuild.

This also works with Steam, thnx.

Offline

#7 2017-04-07 15:07:41

protomolecule
Member
Registered: 2017-04-06
Posts: 6

Re: Spotify is not working anymore due to the openssl rebuild.

Works fine here. Thank you @mis.

Offline

#8 2017-04-26 05:22:21

felipec
Member
Registered: 2011-12-29
Posts: 11

Re: Spotify is not working anymore due to the openssl rebuild.

This is the wrong approach. The whole point of the openssl-1.0 package is to provide backwards compatibility. However, they fucked up the version script, that's why it doesn't work.

This is the correct patch from debian:
https://gist.github.com/felipec/e3fbebe … 946fab87b9

And with this patch Spotify works with openssl-1.0, no changes needed.

Link to openssl-1.0's bug report:
https://bugs.archlinux.org/task/53836

Last edited by felipec (2017-04-26 05:39:32)

Offline

#9 2017-04-26 08:52:21

thorgal
Member
Registered: 2016-10-30
Posts: 7

Re: Spotify is not working anymore due to the openssl rebuild.

Hello, Im struggeling with the same error. Somebody has the mercy to explain me, how to apply this patch?

Offline

#10 2017-04-26 18:36:40

MightyPork
Member
From: Prague, Czech Republic
Registered: 2014-06-16
Posts: 93
Website

Re: Spotify is not working anymore due to the openssl rebuild.

thorgal wrote:

Hello, Im struggeling with the same error. Somebody has the mercy to explain me, how to apply this patch?

There may be an easier way, but here's how I did it:

1. $ sudo abs extra/openssl-1.0
2. copy the package files from /var/abs/extra/openssl-1.0 to somewhere you want to build it in (eg /tmp)
3. replace contents of the patch file (the big one) with what you find in that gist felipec posted
4. $ updpkgsums  # to update checksum of the patch file
5. $ gpg --recv-keys D9C4D26D0E604491      # this imports a key needed to check the source tarball integrity ???
6. $ makepkg  # build the package, this takes a couple minutes
7. $ sudo pacman -U <the xz file you built>


If it ain't broke, pacman -Syyu and it will be

Offline

#11 2017-04-26 19:09:16

MightyPork
Member
From: Prague, Czech Republic
Registered: 2014-06-16
Posts: 93
Website

Re: Spotify is not working anymore due to the openssl rebuild.

ATTN: The aforementioned fix apparently - for a change - breaks Krusader and a bunch of other stuff.

And while messing with those libs, I then managed to break pacman and had to manually copy the lib files from /var/cache/pkg. So. BE CAREFUL.

I'm not sure how to fix this mess, albeit at least my pacman now works again

----------------------------

It appears the real fix was to simply update spotify from AUR (duh, should've noticed that before)
- and first, install aur/libopenssl-1.0-compat

Last edited by MightyPork (2017-04-26 19:46:50)


If it ain't broke, pacman -Syyu and it will be

Offline

#12 2017-04-26 20:37:30

thorgal
Member
Registered: 2016-10-30
Posts: 7

Re: Spotify is not working anymore due to the openssl rebuild.

Thanks for the try, hope you get your packages running again.
I did update yaourt with -Syyu, nothing got updated.
Then I removed spotify with -Rs, afterwards I tried to install libopenssl-1.0-compat, but it failed due to an unknown PGP-Signature.
Cant reinstall spotify neighter, as libopenssl-1.0-compat is a dependency.

Offline

#13 2017-04-27 08:49:16

hermanr
Member
Registered: 2011-05-25
Posts: 17

Re: Spotify is not working anymore due to the openssl rebuild.

This problem is no longer limited to AUR-packages. Since this morning (after a 'pacman -Syu') Civilization VI won't start in Steam because of this same issue, and all the relevant packages are from the normal repositories.

Offline

#14 2017-04-27 09:07:55

thorgal
Member
Registered: 2016-10-30
Posts: 7

Re: Spotify is not working anymore due to the openssl rebuild.

As mentioned in AUR/spotify, after reinstalling with

$ gpg --recv-key 5CC908FDB71E12C2
$ gpg --recv-key D9C4D26D0E604491
$ yaourt -S spotify

spotify is gonna work again big_smile

Offline

#15 2017-04-27 11:34:38

Archanfel80HUN
Member
Registered: 2017-04-27
Posts: 6

Re: Spotify is not working anymore due to the openssl rebuild.

The problem is with the libcurl-openssl-1.0 package. It depends on openssl-1.0 what is no longer exsist.
Clone the package, edit PKGBUILD change the dependencies row replace 'openssl-1.0' with 'openssl'. Then build and install.
After that spofify install without issues.
In the other hand this will fix the main problem, the openssl library issue which is a problem in the steam and some other packages too, not just spotify.

Last edited by Archanfel80HUN (2017-04-27 11:36:09)

Offline

#16 2017-04-28 19:11:22

SimonT
Member
Registered: 2015-01-26
Posts: 18

Re: Spotify is not working anymore due to the openssl rebuild.

Does anybody know if there will be a solution to this problem which doesn't involve accepting the gpg keys? So that I can just do a system upgrade and it will work again, sooner or later.

I don't know much about how adding software from the AUR works but I can't help but feel that this way of fixing it is insecure. I just know that SSL is used to transfer data securely. Installing the package "openssl-1.0" when the latest version of the package "openssl" is 1.1.0.e-1 feel like it would be a security risk. Especially when I have to do the installation in a different way than I'm used to. I haven't had to add any keys before installing programs with pacaur before.

But then again, I'm not very knowledgeable about these things. Am I just worrying too much about it?

Last edited by SimonT (2017-04-28 22:11:42)

Offline

#17 2017-04-29 15:04:21

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 9,336

Re: Spotify is not working anymore due to the openssl rebuild.

using pgp signatures in aur packages has been possible for a long time, but was rare until sometime last year.
(There was  a lenghty discussion on aur general ML) .


I copied the relevant lines from libcurl-openssl-1.0 PKGBUILD

source=("https://curl.haxx.se/download/curl-${pkgver}.tar.gz"{,.asc})
validpgpkeys=('27EDEAF22F3ABCEB50DB9A125CC908FDB71E12C2') # Daniel Stenberg
sha256sums=('a84b635941c74e26cce69dd817489bec687eb1f230e7d1897fc5b5f108b59adf'
            'SKIP')

The source line tells makepkg to download 2 files :
curl-7.54.0.tar.gz
curl-7.54.0.tar.gz.asc

The asc-file is used by pgp to verify the first file has not been tampered with.
In order to perform that verification , you need to have the public key of the person that created the asc-file .

makepkg uses the keyring of the user it's running as to look for known keys.
The "gpg —recv-key" command is used to add keys to the user keyring .

Keep in mind that knowing a key is not the same as trusting that key.
The validpgpkeys= line tells makepkg that for this one PKGBUILD only it must trust the key(s) in the validpgpkeys array .


TL;DR :
using pgp keys in PKGBUILD vastly reduces the chances sourcefiles have been tampered with.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
Did you use the guided installer ? If yes, I can't help you.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB