mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2591] Seahorse isn't firejailed, but still launches. #1649
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#1649
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 (Mar 13, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2591
General information
firejail --version
firejail version 0.9.58.2
Compile time support:
- AppArmor support is enabled
- AppImage support is enabled
- chroot support is enabled
- file and directory whitelisting support is enabled
- file transfer support is enabled
- networking support is enabled
- overlayfs support is enabled
- private-home support is enabled
- seccomp-bpf support is enabled
- user namespace support is enabled
- X11 sandboxing support is enabled
lsb_release --all
No LSB modules are available.
Distributor ID: Parrot
Description: Parrot GNU/Linux 4.5
Release: 4.5
Codename: stretch
Steps to reproduce
firecfg, this was part of the output:sudo aa-enforce firejail-defaultagain, this time without errors. Theseahorseprocess then launches, but I get the following message:firejail --list. This is the output from syslog after two attempts:How do I proceed?
@SkewedZeppelin commented on GitHub (Mar 13, 2019):
You need to undo all the manual file creation you did and installfirejail-profilespackagenvm, seahorse isn't in 0.9.58.2
@ghost commented on GitHub (Mar 15, 2019):
@hThoreau If you could provide a debug log here (or a link to one on a pastebin service of your choosing) that would help to see what's happening with your seahorse exactly. Something like
firejail --debug seahorse 2>&1 | tee seahorse.logwill capture all output to a file in the path you run it from. Additional output fromfirejail --listand/orfirejail --treeafter running the debug command would be very helpfull too.@ghost commented on GitHub (Mar 16, 2019):
Huh... It's running now. o_O