github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #3765] Spotify 1.1.42.622 Hangs on Arch Linux #2371

New issue

Closed

opened 2026-05-05 09:03:14 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 09:03:14 -06:00

Owner

Originally created by @njfox on GitHub (Nov 21, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3765

Launching spotify via firejail on archlinux causes it to hang after the spotify window opens. I see the following warnings/errors related to libcurl-gnutls.so.4, although I'm not sure if it's related to the issue:

Child process initialized in 570.30 ms
spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify)

(spotify:32): Gtk-WARNING **: 19:05:48.088: Unable to locate theme engine in module_path: "adwaita",
/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)
/proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe)

Any ideas on how to troubleshoot?

update: Looks like the same warnings happen when launching without firejail, so they appear to be irrelevant. I tried commenting out private opt spotify but that didn't change anything.

Originally created by @njfox on GitHub (Nov 21, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3765 Launching spotify via firejail on archlinux causes it to hang after the spotify window opens. I see the following warnings/errors related to libcurl-gnutls.so.4, although I'm not sure if it's related to the issue: ``` Child process initialized in 570.30 ms spotify: /usr/lib/libcurl-gnutls.so.4: no version information available (required by spotify) (spotify:32): Gtk-WARNING **: 19:05:48.088: Unable to locate theme engine in module_path: "adwaita", /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) /proc/self/exe: /usr/lib/libcurl-gnutls.so.4: no version information available (required by /proc/self/exe) ``` Any ideas on how to troubleshoot? **update**: Looks like the same warnings happen when launching without firejail, so they appear to be irrelevant. I tried commenting out `private opt spotify` but that didn't change anything.

gitea-mirror closed this issue

2026-05-05 09:03:15 -06:00

gitea-mirror commented

2026-05-05 09:03:17 -06:00

Author

Owner

@rusty-snake commented on GitHub (Nov 21, 2020):

First try firejail --noprofile /opt/spotify/spotify, if that fails it will be hard to fix (if it is possible to fix).

Try firejal --private-etc=ld.so.cache,ld.so.conf,ld.so.conf.d,ld.so.preload /opt/spotify/spotify. If this did not help, try firejail --ignore=private-etc /opt/spotify/spotify. If it's still broken, copy /etc/firejail/spoify.profile to your home, open it in a text editor and comment everything. Then uncomment it line for line and try firejail --profile=~/spotify.profile /opt/spotify/spotify to find the line(s) which cause this.

@rusty-snake commented on GitHub (Nov 21, 2020): First try `firejail --noprofile /opt/spotify/spotify`, if that fails it will be hard to fix (if it is possible to fix). Try `firejal --private-etc=ld.so.cache,ld.so.conf,ld.so.conf.d,ld.so.preload /opt/spotify/spotify`. If this did not help, try `firejail --ignore=private-etc /opt/spotify/spotify`. If it's still broken, copy /etc/firejail/spoify.profile to your home, open it in a text editor and comment everything. Then uncomment it line for line and try `firejail --profile=~/spotify.profile /opt/spotify/spotify` to find the line(s) which cause this.

gitea-mirror commented

2026-05-05 09:03:18 -06:00

Author

Owner

@njfox commented on GitHub (Nov 21, 2020):

Thanks, --noprofile works fine, but firejail --private-etc=ld.so.cache,ld.so.conf,ld.so.conf.d,ld.so.preload /opt/spotify/spotify does not. It seems to be an issue with the GUI not updating, as I can click on the play button and music will play, but nothing in the window will animate when mousing over/clicking.

@njfox commented on GitHub (Nov 21, 2020): Thanks, `--noprofile` works fine, but `firejail --private-etc=ld.so.cache,ld.so.conf,ld.so.conf.d,ld.so.preload /opt/spotify/spotify` does not. It seems to be an issue with the GUI not updating, as I can click on the play button and music will play, but nothing in the window will animate when mousing over/clicking.

gitea-mirror commented

2026-05-05 09:03:19 -06:00

Author

Owner

@rusty-snake commented on GitHub (Nov 21, 2020):

I see no lines in spotify.profile who smile at me and say it's me, so the good old trial-and-error solution is probably the best. Is something related in the syslog? I think the most hangs are caused by seccomp, so you could try firejail --ignore=seccomp /opt/spotify/spotify.

@rusty-snake commented on GitHub (Nov 21, 2020): I see no lines in spotify.profile who smile at me and say it's me, so the good old trial-and-error solution is probably the best. Is something related in the syslog? I think the most hangs are caused by seccomp, so you could try `firejail --ignore=seccomp /opt/spotify/spotify`.

gitea-mirror commented

2026-05-05 09:03:20 -06:00

Author

Owner

@njfox commented on GitHub (Nov 22, 2020):

firejail --ignore=seccomp fixes the issue. What does that mean for tuning the profile? Is there a way to adjust the seccomp configuration without disabling it completely?

@njfox commented on GitHub (Nov 22, 2020): `firejail --ignore=seccomp` fixes the issue. What does that mean for tuning the profile? Is there a way to adjust the seccomp configuration without disabling it completely?

gitea-mirror commented

2026-05-05 09:03:21 -06:00

Author

Owner

@rusty-snake commented on GitHub (Nov 22, 2020):

If you have a AMD-GPU it's #3219, add seccomp !kcmp to your spotify.local if that's the case.

If not, run journalctl --grep=SECCOMP --reverse and look for spotify (comm="spotify" or exec="/opt/spotify/spotify") then scroll to syscall=NUMBER in that line and run firejail --debug-syscalls | grep NUMBER. Now you can run firejail '--seccomp=!SYSCALL /opt/spotify/spotify to test.

@rusty-snake commented on GitHub (Nov 22, 2020): If you have a AMD-GPU it's #3219, add `seccomp !kcmp` to your spotify.local if that's the case. If not, run `journalctl --grep=SECCOMP --reverse` and look for spotify (`comm="spotify"` or `exec="/opt/spotify/spotify"`) then scroll to `syscall=NUMBER` in that line and run `firejail --debug-syscalls | grep NUMBER`. Now you can run `firejail '--seccomp=!SYSCALL /opt/spotify/spotify` to test.

gitea-mirror commented

2026-05-05 09:03:21 -06:00

Author

Owner

@njfox commented on GitHub (Nov 22, 2020):

Thanks! I do have an AMD GPU and seccomp !kcmp fixed it.

@njfox commented on GitHub (Nov 22, 2020): Thanks! I do have an AMD GPU and `seccomp !kcmp` fixed it.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2371

No description provided.

Rows
Columns