[GH-ISSUE #2113] Custom pulseaudio client.conf issue, firejail being started as non-root #1430

Closed
opened 2026-05-05 08:05:49 -06:00 by gitea-mirror · 5 comments
Owner

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

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 https://github.com/netblue30/firejail/blob/da76c64dcdf7f98e94a33fa74e1e0050e384ce5c/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
gitea-mirror 2026-05-05 08:05:49 -06:00
Author
Owner

@Vincent43 commented on GitHub (Sep 13, 2018):

You mat try --noautopulse option for firejail. It's available in 0.9.54 and newer.

<!-- gh-comment-id:421103933 --> @Vincent43 commented on GitHub (Sep 13, 2018): You mat try [--noautopulse](https://github.com/netblue30/firejail/commit/617ff40c9334929101c39d0a758fbaefad6a0f78) option for firejail. It's available in 0.9.54 and newer.
Author
Owner

@chiraag-nataraj commented on GitHub (Sep 18, 2018):

@tonsimple Did @Vincent43's suggestion work?

<!-- gh-comment-id:422214766 --> @chiraag-nataraj commented on GitHub (Sep 18, 2018): @tonsimple Did @Vincent43's suggestion work?
Author
Owner

@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)

<!-- gh-comment-id:423737520 --> @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)
Author
Owner

@Vincent43 commented on GitHub (Sep 22, 2018):

Firejail 0.9.54 is available in Debian stretch backports.

<!-- gh-comment-id:423741246 --> @Vincent43 commented on GitHub (Sep 22, 2018): Firejail 0.9.54 is available in [Debian stretch backports](https://packages.debian.org/stretch-backports/firejail).
Author
Owner

@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.

<!-- gh-comment-id:425570520 --> @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`.
Sign in to join this conversation.
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#1430
No description provided.