mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2113] Custom pulseaudio client.conf issue, firejail being started as non-root #1430
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#1430
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 @tonsimple on GitHub (Sep 13, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2113
Hi!
Long story short, I have a non-root user using a custom pulseaudio client.conf defining a path to custom pulseaudio socket (whitelisted in firejail's config, of course!)
When program is started outside firejail, all is fine.
When program is started inside firejail, there is no sound.
Checking by starting bash within firejail (with same profile and all), discovered following:
pulseaudio socket is available, but the client.conf file is replaced with "something else", specifically a default client.conf
After searching around the repository found this
da76c64dcd/src/firejail/pulseaudio.c (L90)which seems to suggest that replacing the client.conf with "something else" is normal and expected behavior.
How do I stop firejail from doing this?
The user in question is non-root (non-sudo) so mount-binding stuff seems problematic
@Vincent43 commented on GitHub (Sep 13, 2018):
You mat try --noautopulse option for firejail. It's available in 0.9.54 and newer.
@chiraag-nataraj commented on GitHub (Sep 18, 2018):
@tonsimple Did @Vincent43's suggestion work?
@tonsimple commented on GitHub (Sep 22, 2018):
@chiraag-nataraj no, I guess my Firejail is a wee too old (I blame Debian :) )
But I'm now running a startup script via bash inside the jail, which restores pulse's config and launches all the stuff.
I guess it's acceptable except I have to allow running bash inside the jail (probably not really a big problem, lol)
@Vincent43 commented on GitHub (Sep 22, 2018):
Firejail 0.9.54 is available in Debian stretch backports.
@chiraag-nataraj commented on GitHub (Sep 28, 2018):
Closing since OP has found a workaround for
firejail<= 0.9.52 and newer versions have--noautopulse.