mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1391] Okular won't start the second instance - can't open more than one pdf file at the same time #950
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#950
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 @ghost on GitHub (Jul 17, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1391
@curiosity-seeker commented on GitHub (Jul 17, 2017):
This works for me - see also my remarks here. I'm also using the Firejail git version.
@smitsohu commented on GitHub (Jul 18, 2017):
For me, runningfirejail --ignore=protocol okularsolves the issue.What is interesting though, runningfirejail --protocol=unix,inet,inet6,netlink okulardoesn't solve it.@smitsohu commented on GitHub (Jul 18, 2017):
@rekixex Hmmm, I can't reproduce it anymore (the solution, the bug is still there).
Please forget about it :-/
@st31ny commented on GitHub (Jan 24, 2018):
@rekixex I am on Debian stable and observed a similar behaviour:
For me, upgrading
firejail-profilesto version 0.9.52-2 (currently in buster) fixed the issue.@smitsohu commented on GitHub (Jan 26, 2018):
If you launch several instances of okular, firejail keeps each in its own PID namespace.
The problem is the following:
So when you see this error message, two instances of okular have exactly the same PID inside their sandboxes.... you can easily convince yourself by joining the sandboxes and running top e.g.
@smitsohu commented on GitHub (Feb 25, 2018):
#1784 and this issue are closely related.
It should work when
join-or-start okularis added to the profile. But I'm away from my workstation and can't test myself in the moment.