mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2121] man-pages not readable while less firejailed and man app-armored #1439
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#1439
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 @btittelbach on GitHub (Sep 24, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2121
Bug: firejailed less ist not allowed to preprocess / display man-pages. Thus
mandoes not work.Distro: Ubuntu 18.04
Firejail Version: 0.9.52
Possible Workarounds:
export PAGER=most@btittelbach commented on GitHub (Sep 24, 2018):
@chiraag-nataraj commented on GitHub (Sep 25, 2018):
How exactly are you doing this? On Debian,
manuses/usr/bin/pagerby default, which is a link to/etc/alternatives/pager. If I create apagerprofile and symlink it (/usr/local/bin/pager -> /usr/local/bin/firejail),firejailthrows up a warning about an existing sandbox being detected. I can't quite figure out how that's happening though.@Vincent43 commented on GitHub (Sep 25, 2018):
IIRC man is confined by default with AppArmor in Ubuntu. Can you check it with
sudo aa-status |grep man?Also
journalctl |grep DENIED@btittelbach commented on GitHub (Sep 30, 2018):
journalctl |grep DENIED:sudo aa-status | grep man:@Vincent43 commented on GitHub (Sep 30, 2018):
You mat try to disable AppArmor man profile with
sudo aa-disable /usr/bin/manthen reboot and see if this helps. You can undo this withsudo aa-enforce /usr/bin/man.@btittelbach commented on GitHub (Oct 1, 2018):
It works as expected even without rebooting.
So we know the double-sandboxing in Ubuntu of AppArmoring
manand firejailinglessis to blame. Now what's to be done about it so the unassuming firejail Ubuntu user can viewman-pages again?@Vincent43 commented on GitHub (Oct 1, 2018):
It's generally known that AppArmor can break firejail if specific app use both at the same time. We had already reports about libreoffice and thunderbird affected by this on Ubuntu. My advice is to disable one of them for the specific app. I don't know what else we can do.
@chiraag-nataraj commented on GitHub (May 29, 2019):
Since there isn't really much we can do, the culprit/problem has been found, and the issue has been inactive for a while, I'm going to mark this with "workaround" and close it for now. @btittelbach, please feel free to re-open it if you have more questions.