You are not logged in.
Pages: 1
I've been trying to set up libetc on my system to clean up my dotfiles. There have been some speed bumps along the way, and this is a bigger one. With libetc enabled as an environment varable (LD_PRELOAD), Chromium does not start, with the error:
[7954:7954:78523094931:ERROR:chrome/browser/zygote_main_linux.cc(522)] Failed to read from chroot pipe: 20
[7954:7954:78523094996:FATAL:chrome/browser/zygote_main_linux.cc(613)] Failed to enter sandbox. Fail safe abort. (errno: 20)
Even if I try to add /usr/bin/chromium or /usr/lib/chromium/chromium to LIBETC_BLACKLIST, or do LD_PRELOAD="" chromium, the same error happens.
I now use libetc through ld.so.preload, to solve some problems when logging in and having bash files in $HOME. I can now launch Chromium by commenting out libetc from ld.so.preload before launching it. However, this also brings some problems, such as the gtk theme being reset and introducing new dotfiles in $HOME like .adobe, .macromedia and .pki.
Is there anyway to get Chromium cooperating with libetc? If not, is there any way to get gtk themes working while using Chromium?
Offline
You could run chromium without the sandbox/chroot but this is really not recommond.
Offline
How do I run Chromium without the sandbox, and why is it not recommended?
Offline
Did you ever solve this? I tried out libetc this morning and have the same issue with chromium (/extra 5.0.307.11-1)
Offline
Nope. I ended up migrating away from libetc in a painful process of moving dotfiles back to ~ (which was very difficult because I couldn't tell which ones were originally in .config or not.) Libetc proved to be too much of a hassle for too small a gain.
Offline
Pages: 1