[GH-ISSUE #356] Firejail cannot launch if ~/.asoundrc is a symlink #254

New issue

Closed

opened 2026-05-05 05:25:57 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:25:57 -06:00

Owner

Originally created by @boltronics on GitHub (Mar 7, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/356

I use GNU Stow to have many of the configuration dotfiles in my home directory basically managed via symlinks, which point to another location (also under my home directory). This makes version control simple and allows me to load different configuration files on a per-machine basis. One of those managed files is ~/.asoundrc.

I see /etc/firejail/whitelist-common.inc has whitelist ~/.asoundrc, but even with that line commented, the problem persists. I also tried adding ignore whitelist ~/.asoundrc without success. Lastly, I tried adding whitelist ~/.dotfiles/alsa/.asoundrc (which is where ~/.asoundrc is a symlink to), and that still didn't work.

Browsing through the source, it appears there are references to the file location hard-coded, so I'm assuming this is a bug in firejail and not my configuration. There could well be the same problem for some of the other locations that are hard-coded as well.

Originally created by @boltronics on GitHub (Mar 7, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/356 I use GNU Stow to have many of the configuration dotfiles in my home directory basically managed via symlinks, which point to another location (also under my home directory). This makes version control simple and allows me to load different configuration files on a per-machine basis. One of those managed files is ~/.asoundrc. I see /etc/firejail/whitelist-common.inc has `whitelist ~/.asoundrc`, but even with that line commented, the problem persists. I also tried adding `ignore whitelist ~/.asoundrc` without success. Lastly, I tried adding `whitelist ~/.dotfiles/alsa/.asoundrc` (which is where ~/.asoundrc is a symlink to), and that still didn't work. Browsing through the source, it appears there are references to the file location hard-coded, so I'm assuming this is a bug in firejail and not my configuration. There could well be the same problem for some of the other locations that are hard-coded as well.

gitea-mirror

2026-05-05 05:25:57 -06:00

closed this issue
added the
bug
label

gitea-mirror commented

2026-05-05 05:26:03 -06:00

Author

Owner

@netblue30 commented on GitHub (Mar 7, 2016):

BUG! Will fix soon!

@netblue30 commented on GitHub (Mar 7, 2016): BUG! Will fix soon!

gitea-mirror commented

2026-05-05 05:26:06 -06:00

Author

Owner

@netblue30 commented on GitHub (Mar 20, 2016):

Fixed!

@netblue30 commented on GitHub (Mar 20, 2016): Fixed!

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#254

No description provided.

Rows
Columns