mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2330] Can't get Libreoffice to start on Kbuntu 18.04 #1557
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#1557
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 @BCOH on GitHub (Jan 7, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2330
I have tried all patches and profile modifications but Libreoffice will still not load. Any help would be appreciated. I am by no means a Firejail expert or Linux expert.
Thanks
Brian
ser@user:~/firejail$ firejail --apparmor libreoffice
Reading profile /etc/firejail/libreoffice.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 20071, child pid 20072
Child process initialized in 77.83 ms
Warning: an existing sandbox was detected. /usr/bin/libreoffice will run without any additional sandboxing features
LibreOffice(19)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
Parent is shutting down, bye...
or
user@user:~/firejail$ firejail --ignore=seccomp --ignore=protocol libreoffice %U
Reading profile /etc/firejail/libreoffice.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 20453, child pid 20454
Child process initialized in 75.07 ms
Warning: an existing sandbox was detected. /usr/bin/libreoffice will run without any additional sandboxing features
LibreOffice(19)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
Parent is shutting down, bye..
Or
user@user:~/firejail$ firejail libreoffice
Reading profile /etc/firejail/libreoffice.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-devel.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
Reading profile /etc/firejail/whitelist-var-common.inc
Parent pid 20521, child pid 20522
Child process initialized in 71.17 ms
Warning: an existing sandbox was detected. /usr/bin/libreoffice will run without any additional sandboxing features
LibreOffice(19)/kdeui (kdelibs): Session bus not found
To circumvent this problem try the following command (with Linux and bash)
export $(dbus-launch)
Parent is shutting down, bye...
@Vincent43 commented on GitHub (Jan 7, 2019):
How did you installed
firejail?Please show
which firejail,firejail --versionand/usr/bin/firejail --versionoutput.Maybe you can try if
firejail --ignore=nodbus libreofficeworks.@BCOH commented on GitHub (Jan 7, 2019):
user@user:~$ firejail --ignore=nodbus libreoffice
Reading profile /usr/local/etc/firejail/libreoffice.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-devel.inc
Reading profile /usr/local/etc/firejail/disable-passwdmgr.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Reading profile /usr/local/etc/firejail/whitelist-var-common.inc
Parent pid 15805, child pid 15806
Blacklist violations are logged to syslog
Child process initialized in 97.32 ms
Warning: an existing sandbox was detected. /usr/bin/libreoffice will run without any addit
ional sandboxing features
Warning: failed to launch javaldx - java may not function correctly
ERROR 4 forking process
Parent is shutting down, bye...
user@user:~$ firejail --version
firejail version 0.9.57
Compile time support:
user@user:~$
On Mon, 2019-01-07 at 05:55 -0800, Vincent43 wrote:
@BCOH commented on GitHub (Jan 8, 2019):
I updated after discovering the issue.
firejail version 0.9.57
Compile time support:
- AppArmor support is disabled
- 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
@BCOH commented on GitHub (Jan 8, 2019):
firejail --ignore=nodbus libreoffice
Reading profile /usr/local/etc/firejail/libreoffice.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-devel.inc
Reading profile /usr/local/etc/firejail/disable-passwdmgr.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Reading profile /usr/local/etc/firejail/whitelist-var-common.inc
Parent pid 16220, child pid 16221
Blacklist violations are logged to syslog
Child process initialized in 103.80 ms
Warning: an existing sandbox was detected. /usr/bin/libreoffice will run without any additional sandboxing features
Warning: failed to launch javaldx - java may not function correctly
ERROR 4 forking process
Parent is shutting down, bye..
@SkewedZeppelin commented on GitHub (Jan 9, 2019):
Please try
@BCOH commented on GitHub (Jan 9, 2019):
firejail --ignore=nodbus /usr/bin/libreoffice
Reading profile /usr/local/etc/firejail/libreoffice.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-devel.inc
Reading profile /usr/local/etc/firejail/disable-passwdmgr.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Reading profile /usr/local/etc/firejail/whitelist-var-common.inc
Parent pid 24718, child pid 24719
Blacklist violations are logged to syslog
Child process initialized in 107.06 ms
Warning: failed to launch javaldx - java may not function correctly
ERROR 4 forking process
Parent is shutting down, bye...
@BCOH commented on GitHub (Jan 9, 2019):
Current FIREJAIL Libreoffice profile
@SkewedZeppelin commented on GitHub (Jan 9, 2019):
Eh, are you using the proprietary NVIDIA drivers?
See #1703
@BCOH commented on GitHub (Jan 9, 2019):
I am using the NVIDIA driver that was supplied by the OS.
NVIDIA driver metapackage from nvidia-drive-390 (recommended Driver)
On Tue, 2019-01-08 at 20:27 -0800, SkewedZeppelin wrote:
@ashfaqnisar commented on GitHub (Jan 13, 2019):
I am having the same problem, were you able to solve the problem.
@ashfaqnisar commented on GitHub (Jan 13, 2019):
I am able to run the libreoffice as an root user with firejail
@Vincent43 commented on GitHub (Jan 13, 2019):
This is terrible idea. Please don't do that.
@ashfaqnisar commented on GitHub (Jan 13, 2019):
But why is that a terrible idea
@BCOH commented on GitHub (Jan 13, 2019):
Ashfaq
You should never run Libreoffice as root! This will allow any Malicious content FULL access to your system.
No I still have the issue, it has not been solved.
B
@ashfaqnisar commented on GitHub (Jan 13, 2019):
Thanks for the heads up, I didn't know this and I was running every application in root mode.
@chiraag-nataraj commented on GitHub (Jan 13, 2019):
@ashfaqnisar Please, please, please don't run applications as root unless you have to. It ends up breaking all privilege separation mechanisms. Basically, if you run something as root, it can access anything and do anything on your system. This is not true if you're running as an ordinary user (for example, try doing
cat /etc/shadowversussudo cat /etc/shadow- the first one fails because your regular user doesn't have access to that file while root does).Indeed, Windows used to have a lot more problems precisely because they encouraged everyone to start things as the administrative user (equivalent of root in unix-land), which meant if you made a mistake, your whole computer was at risk.
/endrant@BCOH I noticed in the first couple of things you posted that you got the warning that an existing sandbox was detected. Do you know why that was happening?
@rusty-snake commented on GitHub (Jan 13, 2019):
@BCOH if no you can try
firejail --listbefore and after starting LO.@ashfaqnisar commented on GitHub (Jan 13, 2019):
Thank you very much, From now on, i will keep that in mind.
@BCOH commented on GitHub (Jan 13, 2019):
rusty-snakefirejail --list
2572:user::/usr/bin/firejail /usr/bin/evolution
3002:user::/usr/bin/firejail /usr/bin/keepassx
3067:user::/usr/local/bin/firejail --ignore=seccomp --ignore=protocol
firefox -no-remote
Not sure what you mean by before and after loading LO. I receive the
same results either way.
Vincent43
irejail --version
firejail version 0.9.57
Compile time support:
firejail --ignore=nodbus libreoffice
Reading profile /usr/local/etc/firejail/libreoffice.profile
Reading profile /usr/local/etc/firejail/disable-common.inc
Reading profile /usr/local/etc/firejail/disable-devel.inc
Reading profile /usr/local/etc/firejail/disable-passwdmgr.inc
Reading profile /usr/local/etc/firejail/disable-programs.inc
Reading profile /usr/local/etc/firejail/whitelist-var-common.inc
Parent pid 4539, child pid 4540
Blacklist violations are logged to syslog
Child process initialized in 84.76 ms
Warning: an existing sandbox was detected. /usr/bin/libreoffice will
run without any additional sandboxing fe
atures
Warning: failed to launch javaldx - java may not function correctly
ERROR 4 forking process
Parent is shutting down, bye...
Still fails when running Fails again with "firejail --ignore=nodbus
libreoffice"
@SkewedZeppelin commented on GitHub (Jan 13, 2019):
@BCOH
make ~/.config/firejail/libreoffice.local with the following contents
then try
firejail /usr/bin/libreofficealso try https://github.com/netblue30/firejail/issues/1771#issuecomment-364498909 if you are having trouble with other profiles too
@chiraag-nataraj
firecfg was probably already run
@chiraag-nataraj commented on GitHub (Jan 14, 2019):
@SkewedZeppelin Right, and that might have something to do with the problem. That's why I'm trying to figure out if there's some usage error going on (possibly on top of whatever other errors might be going on with the profile).
@BCOH commented on GitHub (Jan 29, 2019):
OK I've backed myself into a situation and I need to use the application installed on this PC. I uninstalled AppArmor and Firejail here is the log entry in the system log:
blacklist violation - sandbox 15213, name libreoffice, exe soffice.bin, syscall mkdir, path /home/user/.nv
If this can't be resolved is there an uninstall script for firejail?
Thanks
Brian
@BCOH commented on GitHub (Jan 29, 2019):
Discovered all other apps appear to work as intended, e-mail, browsers, etc. With one exception bleach bit root no longer works. Errors with the same code are LibreOffice.
@smitsohu commented on GitHub (Jan 29, 2019):
@BCOH To get it running, one more thing you could try:
firejail --apparmor --ignore=nodbus --ignore=noroot /usr/bin/libreofficeTo selectively disable firejail for libreoffice and bleachbit, open a terminal and run:
cd /usr/local/bin; sudo rm bleachbit libreoffice loffice soffice lodraw loimpress lobase lowriter lomath lofromtemplate loweb localc.To stop all apps from starting in firejail automatically run
sudo firecfg --cleanThere is also
sudo make uninstallto remove everything.@matu3ba commented on GitHub (Mar 3, 2019):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918499
In the latest update they seem to have fixed the issue, however that was not pushed to the package repo from 18.04. That was described as an issue with apparmor.
See for comparison the version number version numbers.
1:6.0.3-0ubuntu1 in repository and
1:6.1.4-4
I would thus suggest to close this.
@BCOH commented on GitHub (Mar 3, 2019):
Agreed, thanks for all the help!
B
Sent from my iPhone