Spotify won’t launch, libcurl-gnutls missing?

Issues & Assistance Unsupported Software (AUR & Other)
1

Good day/evening to you,

Since the update (but maybe unrelated) to Plasma 6, I can’t seems to launch the Spotify app. When I try in the command I get the following:

/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify
/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify
/spotify)
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify
/spotify)

Here is the inxi:

System:
Kernel: 6.7.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=21a3c4fd-2895-4651-81e7-b9de4386ced8 rw rootflags=subvol=@
quiet resume=UUID=e6e1c3b7-1697-40f6-840e-325760da7891 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.1 tk: Qt v: N/A info: frameworks v: 6.0.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: PRO B650M-A WIFI (MS-7D77) v: 1.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.F0 date: 02/06/2024
CPU:
Info: model: AMD Ryzen 5 7600 bits: 64 type: MT MCP arch: Zen 4 gen: 5
level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 6 MiB desc: 6x1024 KiB
L3: 32 MiB desc: 1x32 MiB
Speed (MHz): avg: 3737 high: 5150 min/max: 400/5170 scaling:
driver: amd-pstate-epp governor: powersave cores: 1: 5144 2: 4115 3: 400
4: 3624 5: 3930 6: 5147 7: 4791 8: 4116 9: 3923 10: 4111 11: 400 12: 5150
bogomips: 91202
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] vendor: Gigabyte driver: nvidia
v: 550.54.14 alternate: nouveau,nvidia_drm non-free: 545.xx+ status: current
(as of 2024-02; EOL~2026-12-xx) arch: Maxwell code: GMxxx
process: TSMC 28nm built: 2014-2019 pcie: gen: 3 speed: 8 GT/s lanes: 16
ports: active: none off: DP-1,HDMI-A-1 empty: DP-2,DP-3,DVI-I-1
bus-ID: 01:00.0 chip-ID: 10de:17c8 class-ID: 0300
Device-2: AMD Raphael vendor: Micro-Star MSI driver: amdgpu v: kernel
arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: none empty: DP-4, DP-5,
DP-6, HDMI-A-2 bus-ID: 10:00.0 chip-ID: 1002:164e class-ID: 0300
temp: 35.0 C
Device-3: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4
compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia
unloaded: modesetting,nouveau alternate: fbdev,nv,vesa dri: radeonsi
gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
Screen-1: 0 s-res: 4480x1440 s-dpi: 110 s-size: 1034x333mm (40.71x13.11")
s-diag: 1086mm (42.77")
Monitor-1: DP-1 mapped: DP-0 note: disabled pos: primary,left
model: Dell S2721D serial: <filter> built: 2020 res: 2560x1440 hz: 60
dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 676mm (26.6")
ratio: 16:9 modes: max: 2560x1440 min: 640x480
Monitor-2: HDMI-A-1 mapped: HDMI-0 note: disabled pos: right
model: Asus VX239 serial: <filter> built: 2013 res: 1920x1080 hz: 60 dpi: 96
gamma: 1.2 size: 510x290mm (20.08x11.42") diag: 587mm (23.1") ratio: 16:9
modes: max: 1920x1080 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
drv: nvidia device: 2 drv: radeonsi device: 3 drv: swrast gbm: drv: nvidia
surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.54.14
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2
memory: 5.86 GiB
API: Vulkan v: 1.3.279 layers: 14 device: 0 type: discrete-gpu name: NVIDIA
GeForce GTX 980 Ti driver: nvidia v: 550.54.14 device-ID: 10de:17c8
surfaces: xcb,xlib device: 1 type: integrated-gpu name: AMD Radeon
Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv v: 24.0.2-arch1.2
device-ID: 1002:164e surfaces: xcb,xlib device: 2 type: cpu name: llvmpipe
(LLVM 17.0.6 256 bits) driver: mesa llvmpipe v: 24.0.2-arch1.2 (LLVM
17.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: NVIDIA GM200 High Definition Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 01:00.1 chip-ID: 10de:0fb0 class-ID: 0403
Device-2: AMD Rembrandt Radeon High Definition Audio
vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:1640 class-ID: 0403
Device-3: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 10:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-4: Logitech HD Pro Webcam C920 driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 5-2:3
chip-ID: 046d:082d class-ID: 0102 serial: <filter>
API: ALSA v: k6.7.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 0c:00.0
chip-ID: 10ec:8125 class-ID: 0200
IF: enp12s0 state: down mac: <filter>
Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1
bus-ID: 0d:00.0 chip-ID: 14c3:0616 class-ID: 0280
IF: wlp13s0 state: up mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:4 chip-ID: 0e8d:0616
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: <filter> bt-v: 5.2 lmp-v: 11
status: discoverable: no pairing: no
Drives:
Local Storage: total: 1.6 TiB used: 100.81 GiB (6.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Kingston model: SNV2S1000G
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: SBM02103 temp: 36.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 830 Series
size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 3B1Q scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 850 EVO 500GB
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 2B6Q scheme: GPT
Partition:
ID-1: / raw-size: 897.62 GiB size: 897.62 GiB (100.00%)
used: 100.81 GiB (11.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 897.62 GiB size: 897.62 GiB (100.00%)
used: 100.81 GiB (11.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 897.62 GiB size: 897.62 GiB (100.00%)
used: 100.81 GiB (11.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 897.62 GiB size: 897.62 GiB (100.00%)
used: 100.81 GiB (11.2%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 30.54 GiB used: 16.83 GiB (55.1%)
priority: 100 comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12
dev: /dev/zram0
ID-2: swap-2 type: partition size: 33.6 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 48.0 C mobo: 38.0 C
Fan Speeds (rpm): N/A
GPU: device: nvidia screen: :0.0 temp: 59 C fan: 34% device: amdgpu
temp: 35.0 C
Info:
Memory: total: 32 GiB note: est. available: 30.54 GiB used: 23.6 GiB (77.3%)
Processes: 414 Power: uptime: 31m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.18 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1970 libs: 571 tools: octopi,paru Compilers:
clang: 17.0.6 gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.0
running-in: konsole inxi: 3.3.33
Garuda (2.6.23-1):
System install date:     2024-02-23
Last full system update: 2024-03-08 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       No/Undetected
Failed units:

I tried to remove the config file, to reinstall, I get the same result with spotify-launcher instead of Spotify, to launch skipping the last update, always this libcurl-gnults problem, after looking at this type of problem here and on reddit.

2

Not an actual fix but try replacing it with Nuclear. Install it using flatpak.

1 Like
3

Most likely you’ve already tried this further to your internet search, anyway it’s something not mentioned in your checks:

2 Likes
4

Sorry, still the same error. Libcurl is already updated to the newest version and the page of AUR changed nothing unfortunately.

5

maybe GitHub - ivan-hc/Spotify-appimage: Unofficial AppImage for Spotify

3 Likes
6

I never used GitHub before, not sure how this works; do I need to find this AM and then how to add the other app?

7

Make sure to have installed libappimage and (optionally) also appimagelauncher.

In the “releases” page, download the latest .Appimage file (currently Spotify-1.2.31.1205-2-x86_64.AppImage), make it executable and run it.

Appimage launcher takes care of that, also moves it to ~/Applications/ (default, configurable) and makes a .desktop file in ~/.local/share/applications/ so it behaves like an installed application.

2 Likes
8

If you are going to use the Spotify appimage ALWAYS install Appimagelauncher. I also suggest you download the Soptify appimage to a location you keep files you don’t want to lose and then place a copy on your desktop and click on that copy to have Appimagelauncher move it aand create your links.

9

Appimage tries to launch the spotify image, it did moves it to the applications folder, but nothing happends after.

Here is what happens if I launch in a terminal:

appimagelauncherd Spotify-1.2.31.1205-2-x86_64_f0b6673cba2275cca7e147e6221714d9.AppImage
Searching for existing AppImages
Searching directory: /home/haeffound/Applications
Found AppImage: /home/haeffound/Applications/Spotify-1.2.31.1205-2-x86_64_f0b6673cba2275cca7e147e6221714d9.App
Image
AppImage integrated already, skipping
Watching directories: /home/haeffound/Applications

I can’t seems to find the “app” somwhere else.

10

I just tried it, and it fails with

/tmp/.mount_Spotif7sd6aE/opt/spotify/spotify: error while loading shared libraries: libayatana-appindicator3.so.1: cannot open shared object file: No such file or directory

did it not show that error for you?
I think it should have been included in the .appimage (I bet it’s packaged on some distro/DE where it’s installed by default, Ubuntu Gnome perhaps), anyways try

sudo pacman -S libayatana-appindicator

it works here after that.
Beware it may break with updates.

Personally, I’d look for an unofficial open source client, but that’s personal opinion.

1 Like
11

I’m quite surprised by this - I’m also a heavy Spotify user and it was working flawlessly during the last days (always fully updated).

Isn’t this a dependency of spotify anyways? I might be wrong but I could swear I noticed this dep.

12

What do I know… I just downloaded the appimage and gave it a try, got the error, searched packages for what could provide the missing library, tried again.
I’m still on my trusty old Sway and it wasn’t installed, I guess other DE has it.
I did not try the original package with the libcurl-gnutls.so.4 error, that one has it as dependency:

fish❯ pactree -s spotify |rg ayatana
└─libayatana-appindicator
  ├─libayatana-indicator
  │ ├─ayatana-ido

And now I tried the chaotic-aur package (which I should have done before…), it works without problem here too indeed (and starts way faster than the appimage one).
I don’t know why it doesn’t for the OP, I guess something else causes the problem with libcurl.
Some other package pulling in another version maybe?

@Haeffound : try pactree -r libcurl-gnutls, note that pactree is from pacman-contrib in case it’s not installed.

I have an idea: I have curl installed, and

fish❯ pactree spotify |rg libcurl
│ │ │ │ ├─curl provides libcurl.so=4-64
├─libcurl-gnutls
1 Like
13

Do you mean for Spotify? If so I already suggested Nuclear, particularly the Flatpak.

14

Yep that looks like a good one, I guess I’ll try it out.

1 Like
15

Here is the output of both:

pactree -s spotify |rg ayatana
└─libayatana-appindicator
├─libayatana-indicator
│ ├─ayatana-ido

pactree -r libcurl-gnutls
libcurl-gnutls
├─spotify
└─steam-native-runtime
└─proton-ge-custom

pactree spotify |rg libcurl
│ │ │ │ ├─curl provides libcurl.so=4-64
├─libcurl-gnutls

The output is still the same, 4 time
/opt/spotify/spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /opt/spotify/spotify)

And I didn’t got the same error as you weirldy, just what I posted sorry.

1 Like
16

Maybe I found it: Spotify - ArchWiki

/usr/lib/libcurl-gnutls.so.4 error
If you encounter the error:
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)
Delete ~/.cache/spotify

why did I not search the wiki before… I would have never thought of that.

2 Likes
17

Well, there’s my problem! Thanks a lot.
I thought I did deleted it, but I only deleted some stuff in the folder, not all of it.

1 Like
18

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.