mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1872] Spotify with ALSA cannot play songs under firejail #1263
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1263
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Tritonio on GitHub (Apr 8, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1872
I had issues with PulseAudio and today I uninstalled it. Everything is running fine with ALSA now: Chromium (in firejail), VLC, system sounds etc. But Spotify, when run under firejail, will not play any songs. If I start it from a console like "firejail spotify I get the following:
There are no messages in /var/log/syslog related to ALSA or Spotify (only one message about spotify not using the notifications correctly)
When I had PulseAudio, Spotify was working fine under firejail.
I am using firejail version 0.9.52 on Mint with the MATE desktop.
@Fred-Barclay commented on GitHub (Apr 9, 2018):
G'day @Tritonio
Can you edit /etc/firejail/spotify.profile and replace the line beginning with
private-etcwith the following line:Thanks!
Fred
@Tritonio commented on GitHub (Apr 9, 2018):
Hello Fred! You're the best. And actually it doesn't need all of these. Just adding "group" was enough:
Should I assume that "The field ipc_gid must be a valid group (create group audio)" is what gave it away for you? I'll check the documentation for "private-etc" to see what it does.
Thanks again!
@Fred-Barclay commented on GitHub (Apr 10, 2018):
G'day @Tritonio I actually had a similar experience a few weeks ago when installing Arch (see
a2aaf6fb38). Spotify wouldn't work withoutgroupsinprivate-etc, so I added a commit, only to never be able to replicate the issue (that is, Spotify started working withoutgroups). I ended up reverting that change.Your post here tipped me off that alsa must require
groupsin the private-etc filter, at least for Spotify.Cheers! I'll (re)fix this right now. 😄
Fred