Arch Linux

radiobla

Member

Registered: 2020-02-19

Posts: 65

Spotify Snap is no longer working on Arch after pacman updates

Hi,

I'm trying to run Spotify installed through snap.

However, since the last updates I did with pacman -Suy, spotify doesn't run anymore and closes with "core dumped" error.

$ spotify --version
Spotify version 1.1.26.501.gbe11e53b, Copyright (c) 2020, Spotify Ltd

$ snap version
snap    2.43.3-1
snapd   2.43.3-1
series  16
arch    -
kernel  5.5.4-arch1-1

$ pacman -Q linux
linux 5.5.4.arch1-1

An "strace spotify" gives me the following:

...
geteuid()                               = 1000
write(2, "need to run as root or suid", 27need to run as root or suid) = 27
write(2, ": Operation not permitted\n", 26: Operation not permitted
) = 26
exit_group(1)                           = ?
+++ exited with 1 +++

I ran spotify as "root" (although I had no hope it would work, and because it's not "safe"), but got "core dumped" too.

I tried it with both AppArmor enabled and disabled, but I get the same error.

I also tried to disable AppArmor (on kernel cmdline), but no success.

Does anyone have any clues on how to figure out this issue?

Am I the only one using Spotify (snap) on Arch Linux (all latest packages by now)?

Thank you!

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

Something I'd like to add is the error message I got from "journalctl -u snapd" with AppArmor enabled.

...
Feb 18 21:24:20  systemd[1]: Starting Snappy daemon...
Feb 18 21:24:20  snapd[1560]: AppArmor status: apparmor is enabled but some kernel features are missing: dbus, network
Feb 18 21:24:20  snapd[1560]: patch.go:64: Patching system state level 6 to sublevel 1...
Feb 18 21:24:20  snapd[1560]: patch.go:64: Patching system state level 6 to sublevel 2...
Feb 18 21:24:20  snapd[1560]: patch.go:64: Patching system state level 6 to sublevel 3...
Feb 18 21:24:20  snapd[1560]: daemon.go:346: started snapd/2.43.3-1 (series 16; classic; devmode) arch/ (amd64) linux/5.5.4-arch1-1.
...

and more...

...
Feb 18 21:24:52  systemd[1]: Started Snappy daemon.
Feb 18 21:25:04  snapd[2000]: udevmon.go:147: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Feb 18 21:25:04  snapd[2000]: udevmon.go:147: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Feb 18 21:25:04  snapd[2000]: udevmon.go:147: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Feb 18 21:25:04  snapd[2000]: udevmon.go:147: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
Feb 18 21:25:04  [2000]: udevmon.go:147: udev event error: Unable to parse uevent, err: cannot parse libudev event: invalid env data
...

Let me know if you need a few more information about the system. Spotify was working (almost) perfectly before the updates.

It worth to mention that it stopped working on my both Arch Linux installs.
Thanks.

Last edited by radiobla (2020-02-19 04:49:54)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,447

Re: Spotify Snap is no longer working on Arch after pacman updates

There's an issue with the electron sandbox in conjunction with glibc 2.31 that tries to use a new syscall, you could try to fix this by downgrading glibc to 2.30 or waiting for a proper update to the snap, see: https://bbs.archlinux.org/viewtopic.php?id=252706

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,488

Website

Re: Spotify Snap is no longer working on Arch after pacman updates

Mod note: moving to AUR Issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

Unfortunately, downgrading glibc to 2.30 (glibc-2.30-3-x86_64.pkg.tar.xz) did not change the Spotify behavior. It's still core dumping. Any other suggestions?

$ pacman -Q glibc
glibc 2.30-3

$ spotify 
Gtk-Message: 12:45:39.667: Failed to load module "canberra-gtk-module"
Trace/breakpoint trap (core dumped)

A full core dump would be helpful?

Also, if I downgrade GLIBC (64-bit) (I'm aware of what is said on Wiki docs about downgrading and its dependencies), it also requires lib32-glibc to be downgraded too, which breaks Steam (from pacman repo - not AUR).

I think we have something else here.

All other snaps are working correctly with both AppArmor enabled or disabled.

Do you guys know how to contact the Spotify snap package maintainer? If it's an official snap by Spotify, I will tear down my hopes to get it working soon, 'cause they don't give a dam* for Linux users

Last edited by radiobla (2020-02-19 15:57:23)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,447

Re: Spotify Snap is no longer working on Arch after pacman updates

In that case update glibc again, and post the contents of the coredump: https://wiki.archlinux.org/index.php/Co … _core_dump

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

Sure, I'll put glibc to the latest version again. In pacman, "glibc" is now marked in "HoldPkg" config. Should I removed it from there? Not sure if pacman included it there by default or because I downgraded glibc manually.

Here goes the coredump with GLIBC 2.30 still installed.

$ coredumpctl info 5964
           PID: 5964 (spotify)
           UID: 1000 (-)
           GID: 1000 (-)
        Signal: 5 (TRAP)
     Timestamp: Wed 2020-02-19 12:58:27 -03 (1min 45s ago)
  Command Line: /snap/spotify/41/usr/share/spotify/spotify
    Executable: /snap/spotify/41/usr/share/spotify/spotify
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (-)
       Boot ID: 6523f01f56e14fbdb6d2b2b9082d3e8c
    Machine ID: -
      Hostname: -
       Storage: /var/lib/systemd/coredump/core.spotify.1000.6523f01f56e14fbdb6d2b2b9082d3e8c.5964.1582127907000000000000.lz4
       Message: Process 5964 (spotify) of user 1000 dumped core.
                
                Stack trace of thread 5964:
                #0  0x00007feb13666742 n/a (libcef.so + 0x46fc742)
                #1  0x00007feb1364fcae n/a (libcef.so + 0x46e5cae)
                #2  0x00007feb13653050 n/a (libcef.so + 0x46e9050)
                #3  0x00007feb13652f3e n/a (libcef.so + 0x46e8f3e)
                #4  0x00007feb1366e332 n/a (libcef.so + 0x4704332)
                #5  0x00007feb1367414e n/a (libcef.so + 0x470a14e)
                #6  0x00007feb13669cff n/a (libcef.so + 0x46ffcff)
                #7  0x00007feb14c949ed n/a (libcef.so + 0x5d2a9ed)
                #8  0x00007feb14c94947 n/a (libcef.so + 0x5d2a947)
                #9  0x00007feb14cac85f n/a (libcef.so + 0x5d4285f)
                #10 0x00007feb14ca10ee n/a (libcef.so + 0x5d370ee)
                #11 0x00007feb14c839ab n/a (libcef.so + 0x5d199ab)
                #12 0x00007feb129f704c n/a (libcef.so + 0x3a8d04c)
                #13 0x00007feb129f2f48 n/a (libcef.so + 0x3a88f48)
                #14 0x00007feb1292185a n/a (libcef.so + 0x39b785a)
                #15 0x00007feb129211e6 n/a (libcef.so + 0x39b71e6)
                #16 0x00007feb12920bb1 n/a (libcef.so + 0x39b6bb1)
                #17 0x00007feb12920586 n/a (libcef.so + 0x39b6586)
                #18 0x00007feb12a5cfa0 n/a (libcef.so + 0x3af2fa0)
                #19 0x00007feb12a6d9fe n/a (libcef.so + 0x3b039fe)
                #20 0x00007feb12a6d7e7 n/a (libcef.so + 0x3b037e7)
                #21 0x00007feb12a2b9b7 n/a (libcef.so + 0x3ac19b7)
                #22 0x00007feb0dcee417 g_main_context_dispatch (libglib-2.0.so.0 + 0x4c417)
                #23 0x00007feb0dcee650 n/a (libglib-2.0.so.0 + 0x4c650)
                #24 0x00007feb0dcee6dc g_main_context_iteration (libglib-2.0.so.0 + 0x4c6dc)
                #25 0x00007feb12a2b822 n/a (libcef.so + 0x3ac1822)
                #26 0x00007feb12a6e2ef n/a (libcef.so + 0x3b042ef)
                #27 0x00007feb12a46527 n/a (libcef.so + 0x3adc527)
                #28 0x00007feb12939ef0 n/a (libcef.so + 0x39cfef0)
                #29 0x0000000001ccdc9b n/a (spotify + 0x1acdc9b)
                #30 0x00007feb0b500b97 n/a (/lib/x86_64-linux-gnu/libc-2.27.so + 0x21b97)

And then the coredump with GLIBC 2.31:

$ pacman -Q glibc
glibc 2.31-1

$ coredumpctl info 8265
           PID: 8265 (spotify)
           UID: 1000 (-)
           GID: 1000 (-)
        Signal: 5 (TRAP)
     Timestamp: Wed 2020-02-19 13:04:20 -03 (14s ago)
  Command Line: /snap/spotify/41/usr/share/spotify/spotify
    Executable: /snap/spotify/41/usr/share/spotify/spotify
 Control Group: /user.slice/user-1000.slice/session-1.scope
          Unit: session-1.scope
         Slice: user-1000.slice
       Session: 1
     Owner UID: 1000 (adon)
       Boot ID: 6523f01f56e14fbdb6d2b2b9082d3e8c
    Machine ID: ---
      Hostname: ---
       Storage: /var/lib/systemd/coredump/core.spotify.1000.6523f01f56e14fbdb6d2b2b9082d3e8c.8265.1582128260000000000000.lz4
       Message: Process 8265 (spotify) of user 1000 dumped core.
                
                Stack trace of thread 8265:
                #0  0x00007f85824c2742 n/a (libcef.so + 0x46fc742)
                #1  0x00007f85824abcae n/a (libcef.so + 0x46e5cae)
                #2  0x00007f85824af050 n/a (libcef.so + 0x46e9050)
                #3  0x00007f85824aef3e n/a (libcef.so + 0x46e8f3e)
                #4  0x00007f85824ca332 n/a (libcef.so + 0x4704332)
                #5  0x00007f85824d014e n/a (libcef.so + 0x470a14e)
                #6  0x00007f85824c5cff n/a (libcef.so + 0x46ffcff)
                #7  0x00007f8583af09ed n/a (libcef.so + 0x5d2a9ed)
                #8  0x00007f8583af0947 n/a (libcef.so + 0x5d2a947)
                #9  0x00007f8583b0885f n/a (libcef.so + 0x5d4285f)
                #10 0x00007f8583afd0ee n/a (libcef.so + 0x5d370ee)
                #11 0x00007f8583adf9ab n/a (libcef.so + 0x5d199ab)
                #12 0x00007f858185304c n/a (libcef.so + 0x3a8d04c)
                #13 0x00007f858184ef48 n/a (libcef.so + 0x3a88f48)
                #14 0x00007f858177d85a n/a (libcef.so + 0x39b785a)
                #15 0x00007f858177d1e6 n/a (libcef.so + 0x39b71e6)
                #16 0x00007f858177cbb1 n/a (libcef.so + 0x39b6bb1)
                #17 0x00007f858177c586 n/a (libcef.so + 0x39b6586)
                #18 0x00007f85818b8fa0 n/a (libcef.so + 0x3af2fa0)
                #19 0x00007f85818c99fe n/a (libcef.so + 0x3b039fe)
                #20 0x00007f85818c97e7 n/a (libcef.so + 0x3b037e7)
                #21 0x00007f85818879b7 n/a (libcef.so + 0x3ac19b7)
                #22 0x00007f857cb4a417 g_main_context_dispatch (libglib-2.0.so.0 + 0x4c417)
                #23 0x00007f857cb4a650 n/a (libglib-2.0.so.0 + 0x4c650)
                #24 0x00007f857cb4a6dc g_main_context_iteration (libglib-2.0.so.0 + 0x4c6dc)
                #25 0x00007f8581887822 n/a (libcef.so + 0x3ac1822)
                #26 0x00007f85818ca2ef n/a (libcef.so + 0x3b042ef)
                #27 0x00007f85818a2527 n/a (libcef.so + 0x3adc527)
                #28 0x00007f8581795ef0 n/a (libcef.so + 0x39cfef0)
                #29 0x0000000001ccdc9b n/a (spotify + 0x1acdc9b)
                #30 0x00007f857a35cb97 n/a (/lib/x86_64-linux-gnu/libc-2.27.so + 0x21b97)

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

I found this in dmesg:

[10117.519458] traps: spotify[59799] trap int3 ip:7f956a814742 sp:7ffd26a65a70 error:0 in [b]libcef.so[/b][7f9567893000+664e000]

As far as I could find this is part of cef-minimal (Chrome Embedded Framework). Indeed, everything is pointing to Electron or some of its dependencies.

But help is still welcome.

Thanks in advance.

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

I found an analog issue which was directly related with the snapd update. Since snapd is a AUR package, the best person to involve would be the maintainer of the SNAPD AUR.

Is here best place to get in touch with the package maintainer? I couldn't find any contact information regarding him, maybe for his own choice.

BTW, a very similar issue was fixed by upgrading snapd from 2.27 to 2.32 in 2018 (with no other documented interventions). See below:

https://bugs.launchpad.net/snapd/+bug/1759173

I'm gonna try to see if there's a way to downgrade the snapd package and test. This might be a workaround until snapd is fixed or updated. I'm gonna see how to contact their people.

Thank you

Last edited by radiobla (2020-02-20 01:33:13)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,447

Re: Spotify Snap is no longer working on Arch after pacman updates

If you set up an AUR account you can click on the maintainer name to find an email address, alternatively they are usually part of the PKGBUILD in this case the second line mentioning the Maintainer is the current maintainer.

bboozzoo

Member

From: Poland

Registered: 2006-08-01

Posts: 125

Re: Spotify Snap is no longer working on Arch after pacman updates

If anyone is interested, or has some ideas, I've opened a forum topic https://forum.snapcraft.io/t/spotify-co … jaro/15615

bboozzoo

Member

From: Poland

Registered: 2006-08-01

Posts: 125

Re: Spotify Snap is no longer working on Arch after pacman updates

To be clear, I think this is unrelated to Arch glibc update. The application running as a snap uses libraries from the runtime/base snap (`core18` in this particular case). To make it more interesting, running the app directly as `/snap/spotiify/current/usr/share/spotify` works just fine, no core dumps whatsoever.

To add some prior context, we had a user notify us about a problem earlier during the week. After some initial investigation, the problem did not appear on Fedora, openSUSE or Ubuntu. It coredumps on Arch and, as I found later on, Manjaro.

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

Indeed, Spotify flatpak is running fine. I see a console warning about libcurl-gnutls.

$ flatpak run com.spotify.Client --version
/app/extra/bin/spotify: /app/lib/libcurl-gnutls.so.4: no version information available (required by /app/extra/bin/spotify)
Spotify version 1.1.26.501.gbe11e53b, Copyright (c) 2020, Spotify Ltd

Observe that the Spotify version is the same in Snap:

$ spotify --version
Spotify version 1.1.26.501.gbe11e53b, Copyright (c) 2020, Spotify Ltd

Something is wrong with Spotify snap package (or snapd itself).

These are the permissions required by Spotify flatpak:

$ flatpak info --show-permissions com.spotify.Client
[Context]
shared=network;ipc;
sockets=x11;pulseaudio;
devices=dri;
filesystems=xdg-pictures:ro;xdg-music:ro;

[Session Bus Policy]
org.gnome.SessionManager=talk
org.freedesktop.Notifications=talk
org.mpris.MediaPlayer2.spotify=own
org.gnome.SettingsDaemon=talk

[Environment]
TMPDIR=/tmp
LD_LIBRARY_PATH=/app/lib

Now with the Spotify snap:

$ snap connections spotify
Interface        Plug                     Slot                   Notes
browser-support  spotify:browser-support  :browser-support       -
desktop          spotify:desktop          :desktop               -
gsettings        spotify:gsettings        :gsettings             -
home             spotify:home             :home                  -
mount-observe    spotify:mount-observe    -                      -
mpris            -                        spotify:spotify-mpris  -
network          spotify:network          :network               -
network-manager  spotify:network-manager  -                      -
opengl           spotify:opengl           :opengl                -
pulseaudio       spotify:pulseaudio       :pulseaudio            -
unity7           spotify:unity7           :unity7                -
wayland          spotify:wayland          :wayland               -
x11              spotify:x11              :x11                   -

Does anyone see something odd in the permissions/connections?

Thanks!

Last edited by radiobla (2020-02-24 15:30:54)

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

I did a deeper investigation on which packages were upgraded by pacman since Spotify was working and after it stopped working.

The list is here: https://pastebin.com/4yUarKF2

Which packages from the list do you guys think might be candidates to have broken Spotify snap?

Spotify also showed to be on revision 36 and was upgraded to revision 41.

$ pwd
/var/lib/snapd/snaps
$ ls -l spotify_*
-rw------- 2 root root 189870080 Feb  7 14:23 spotify_36.snap
-rw------- 1 root root 171618304 Feb 18 15:25 spotify_41.snap

mepqfilho

Member

Registered: 2017-01-02

Posts: 32

Re: Spotify Snap is no longer working on Arch after pacman updates

I have found the same problem recently after I have upgraded Arch and I'd like to know from you guys if you have found a solution?

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

Unfortunately, no. You can use Spotify packaged by flatpak on Arch (it works), but it's not official. It may contain any kind of malware inside of it, since it's packaged by a random guy from the Internet.

I don't think we're gonna have a solution soon. The Spotify Linux team doesn't consider support for Linux distros a priority.

The Spotify snap is working flawlessly on Debian testing as well as other distros that are not Arch-based (Manjaro shows the same behavior). For this reason, I'm only using Debian so far.

Some people are advising that downgrading Spotify (to a version released more than an year ago) works, but it's not a smart solution IMHO.

I'm not totally hopeless anyway. The snapd AUR package maintainer opened a support request for snapd team and we have documented this issue very well here too.

Last edited by radiobla (2020-03-21 21:25:10)

ratcheer

Member

Registered: 2011-10-09

Posts: 912

Re: Spotify Snap is no longer working on Arch after pacman updates

The Spotify Linux team doesn't consider support for Linux distros a priority.

Actually, I was researching an unrelated problem, today, and they flatly state that they do not support Linux. It's apparently provided on a take it or leave it basis.

radiobla

Member

Registered: 2020-02-19

Posts: 65

Re: Spotify Snap is no longer working on Arch after pacman updates

bboozzo,

There's a new version of snapd 2.44 released 4 days ago. Would you update the AUR PKGBUILD?

Sadly, I tried it myself (with 2.44) and also with 2.42.1 (which is the version I'm running in Debian testing/buster). Neither of them worked. Both core dumped.

WTH are we doing wrong?

tonatiuhmira

Member

Registered: 2020-04-28

Posts: 2

Re: Spotify Snap is no longer working on Arch after pacman updates

Hi, I'm facing the same issue, however, if I run spotify from inside it's own snap shell it does work... can anyone else verify if this is the case? for you too?

[$/]
[tonatiuh@totodo ~]$ snap run --shell spotify
[tonatiuh@totodo tonatiuh]$ spotify
...
(spotify:3082): GdkPixbuf-WARNING **: 16:04:44.502: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
[/$]

And despite these warnings, spotify does launch, no more core dumped error...