mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1140] Strange error when I use firejail with $HOME/.local for prefix #787
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#787
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 @kadogo on GitHub (Mar 13, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1140
Hello, I most all build and install my application in $HOME/.local so I did the same for firejail
./configure --prefix=$HOME.localmakeI need to use sudo withtout it I have an error about elevation privilege
sudo make installI need to comment .local profile because they not exist
sed -e '/.local$/ s/^#*/#/' -i ~/.local/etc/firejail/*It looked ok for me before I saw the next error.
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
I don't have this error if I use default prefix.
If I did something false in the build process let me know.
Thanks for you help.
@netblue30 commented on GitHub (Mar 13, 2017):
I think you need a / in --prefix: ./configure --prefix=$HOME/.local
Without it, it will use /home/user.local as a prefix:
@kadogo commented on GitHub (Mar 13, 2017):
Oups my bad
I did it good, I just missed copy paste here.
I did this
./configure --prefix=$HOME/.local@netblue30 commented on GitHub (Mar 14, 2017):
I got it:
Thanks for the bug!
@kadogo commented on GitHub (Mar 14, 2017):
A workaround is to comment it with this line.
sed -e '/.local$/ s/^#*/#/' -i ~/.local/etc/firejail/*But it's more about the next error that I don't know if it's related or not.
I forgot to say, I had the error when I run
firejail --private firefox@netblue30 commented on GitHub (Mar 14, 2017):
Fixed!
@kadogo commented on GitHub (Mar 14, 2017):
I confirm it's ok for the error about the profile.
But it look that these is not fix:
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
I don't have this error if I build it with the default prefix.
@netblue30 commented on GitHub (Mar 15, 2017):
It seems to be working fine:
@kadogo commented on GitHub (Mar 15, 2017):
If I do the same command as you it's ok.
But with chromium it make the next errors.
I use a Debian Jessie x64 in case it can help.
~/.local/bin/firejail --tracelog chromium
Reading profile /home/user/.local/etc/firejail/chromium.profile
Reading profile /home/user/.local/etc/firejail/disable-common.inc
Reading profile /home/user/.local/etc/firejail/disable-programs.inc
Reading profile /home/user/.local/etc/firejail/whitelist-common.inc
Parent pid 10886, child pid 10887
Blacklist violations are logged to syslog
Child process initialized
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
...
[7:7:0315/132757.401633:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
...
[106:106:0315/132804.418462:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process.
@netblue30 commented on GitHub (Mar 16, 2017):
The problem is specific to Chromium, I am getting it on Debian stable installed using the regular prefix. Probably Chrome sandbox disables most files in the filesystem, and when they start the process in the sandbox, the process cannot load the library.
@kadogo commented on GitHub (Mar 16, 2017):
I just tried it with firefox-esr of Debian because I use normaly firefox nightly and I have the same error.
firejail --private /usr/bin/firefox-esr
Reading profile /home/user/.local/etc/firejail/firefox-esr.profile
Reading profile /home/user/.local/etc/firejail/firefox.profile
Reading profile /home/user/.local/etc/firejail/disable-common.inc
Reading profile /home/user/.local/etc/firejail/disable-programs.inc
Reading profile /home/user/.local/etc/firejail/disable-devel.inc
Reading profile /home/user/.local/etc/firejail/whitelist-common.inc
Parent pid 29407, child pid 29408
*** Warning: cannot whitelist Downloads directory
*** Any file saved will be lost when the sandbox is closed.
*** Please create a proper Downloads directory for your application.
Blacklist violations are logged to syslog
Child process initialized
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Sorry to bother you with this error, now if you say it's nothing really bad it's ok to let it so.
I prefer to ask to be sure.
@netblue30 commented on GitHub (Mar 18, 2017):
Actually I like your examples. This particular one with Firefox explains what's going on: by the time Firefox starts and tries to load in libracelog.so, the sandbox already removed all the directories from user home with the exception of ~/Downloads and ~/.mozilla.
You would need to whitelist ~/.local:
I'll try to put some fix in.
@kadogo commented on GitHub (Mar 19, 2017):
I tried to whitelist ~/.local like you said but it seem that the problem is still there.
firejail --private firefox-esr
Reading profile /home/user/.config/firejail/firefox-esr.profile
Reading profile /home/user/.local/etc/firejail/firefox.profile
Reading profile /home/user/.local/etc/firejail/disable-common.inc
Reading profile /home/user/.local/etc/firejail/disable-programs.inc
Reading profile /home/user/.local/etc/firejail/disable-devel.inc
Reading profile /home/user/.local/etc/firejail/whitelist-common.inc
Parent pid 15669, child pid 15670
*** Warning: cannot whitelist Downloads directory
*** Any file saved will be lost when the sandbox is closed.
*** Please create a proper Downloads directory for your application.
Blacklist violations are logged to syslog
Child process initialized
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/home/user/.local/lib/firejail/libtracelog.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
@chiraag-nataraj commented on GitHub (Aug 19, 2018):
Is this still an issue?
@chiraag-nataraj commented on GitHub (Aug 22, 2018):
Closing for inactivity. @kadogo, please feel free to re-open if you still have this issue.
@kadogo commented on GitHub (Aug 23, 2018):
It's not completely the same.
I just tried to compile it and I have the following error
I just clone the git, did a ./configure --prefix $HOME/.local and sudo make install before testing with firefox-esr.
Cheers.
@chiraag-nataraj commented on GitHub (Aug 23, 2018):
Reopening!
@chiraag-nataraj commented on GitHub (Aug 23, 2018):
.local/bin/firejail --whitelist=~/.local firefox-esrworked for me with the stock firefox-esr profile from git.@kadogo commented on GitHub (Aug 23, 2018):
It's true I forgot .local must be whitelist
I only have a warning but I think it's normal
So I think It may be closed again (sorry)
@chiraag-nataraj commented on GitHub (Aug 23, 2018):
Yeah, that warning is normal.
No worries! 🙂