mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1015] Firejail prevents printing in AppArmored applications #693
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#693
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 @curiosity-seeker on GitHub (Dec 30, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1015
In Ubuntu 16.04 I'm using the Firefox AppArmor profile and I created own ones for, e.g., Thunderbird, Okular and Gwenview. They work well with one exception: If I start them firejailed I'm unable to print. The printers are simply not visible in the print dialogue, the only offered option is printing to a file. This happens regardless if the respective AppArmor profile is in enforce- or complain-mode.
aa-logprofstrangely enough doesn't show anything, but I'm getting errors from the journal like:This problem can be "fixed" by using
flags=(attach_disconnected)like inHowever, this "solution" does not work anymore if I start those application with the
--apparmorswitch (I compiled Firejail with --enable-apparmor). Besides, using above flag is not recommended:This is an unfortunate situation. The problem seems to be related to the one mentioned here. (Note: I haven't tried delegation - mentioned in above quote - yet. I don't know if it's helpful here.)
@netblue30 : Do you think there is a chance for a work-around in Firejail? Right now it seems that using Firejail and AppArmor side-by-side is questionable at least for applications where printing is required.
@smitsohu commented on GitHub (Mar 2, 2018):
Thanks for the report, the issue should be fixed in
bade3d03e0.