mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3165] Bad quality audio with --noprofile and PCSX2 #1984
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#1984
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 @adrianlshaw on GitHub (Jan 18, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3165
PCSX2 is a video game emulator. When running
firejail --noprofile PCSX2the sound quality is a complete noisy mess. The application console is littered with many entries that sayALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurredThis doesn't happen outside firejail. Any ideas on how to further debug or fix this? Is ALSA running in some fallback or degraded mode?
@ghost commented on GitHub (Jan 19, 2020):
Firejail has several debug options explained in more detail in the man page. But with --noprofile my guess is those won't show very much. AFAIK neither ALSA nor sound in general are crippled in any way, at least not with a default profile. Codebase does however seem to rely on / assumes usage of PulseAudio.
It might be more informative if you'd be able to supply logs/output of the commands you've tried. When using the --noprofile option, Firejail uses /etc/firejail/default.profile (and what gets included by that file. I'd try to test again by making a local copy of it in
${HOME}/.config/firejail/default.localfile in which you start out completely blank (so commenting out everything that is indefault.profile). Keep enabling options one by one and report back if that changes anything, for the better hopefully... Also, can you show us what version of firejail you are seeing this on, and the OS?@adrianlshaw commented on GitHub (Jan 19, 2020):
Thanks for the tip! I actually misunderstood the —noprofile option because I thought it would use no profile at all, rather than default.profile. Will check that.
@Vincent43 commented on GitHub (Jan 19, 2020):
I think there was some misunderstanding here because
--noprofileworks as you thought and doesn't usedefault.profile.@ghost commented on GitHub (Jan 20, 2020):
@adrianlshaw I misinformed you here, my apologies. See @Vincent43's statement above.
@rusty-snake commented on GitHub (Feb 10, 2020):
@adrianlshaw still need help?
@adrianlshaw commented on GitHub (Feb 11, 2020):
Yes, what should I try next? I could try on a different distro that may have different versions of ALSA...
@Vincent43 commented on GitHub (Feb 11, 2020):
Maybe firejail built-in blacklist block some alsa functionality on your system. Could you take a look if there is something alsa-related in
/sys/firmware?Maye try
firejail --noprofile --noblacklist=/sys/module PCSX2@rusty-snake commented on GitHub (May 6, 2020):
I'm closing here due to inactivity, please fell free to reopen if you still have this issue.
@adrianlshaw commented on GitHub (May 6, 2020):
Thanks for reminding me @rusty-snake . I tried @Vincent43's suggestion but that didn't make a difference. I can't re-open the issue due to lack of privileges :-)
@rusty-snake commented on GitHub (May 6, 2020):
You cloud try my noprofile.profile, but I don't think that this works. Likely that there is a general incompatibility.
@adrianlshaw commented on GitHub (May 6, 2020):
I think this issue can be closed. These underruns and crackling only seem to occur before a game starts. The game I just tried seems fine after initial launch. I'll reopen if I see further issues.