Closed Rosika2 closed 4 years ago
The default.profile
is incompatible with chromium.
@Vincent43 : Hi and thanks a lot for the clarification. I see. I´d say that´s okay but it leaves me with the original issue of the add-on "just read" not working anymore. Do you have any ideas about that as well?
Greetings. Rosika
It seems the problem isn´t related with firejail as I thought in the beginning. On https://github.com/ZachSaucier/Just-Read/issues/297 ("Recently, it appears, the extension has stopped functioning .....") It seems they are currently working on a fix.
Thanks for your help.
Geetings. Rosika
Did you modify the chromium.profile or chromium-common.profile? Neither contains seccomp
but it seems that syscall 161 (=chroot) is blocked for you.
@curiosityseeker the seccomp error comes from default.profile
which OP tried to test.
@Rosika2 still an issue?
@rusty-snake : Sorry, it seems I forgot to close the thread. My apologies. As it turned out the problem with the "Just Read" extension was in the source code itself which has been fixed by the author in the meantime. For further information see https://github.com/ZachSaucier/Just-Read/issues/297 .
Thanks for your help and many greetings. Rosika
Hi altogether,
yesterday I received a chromium-browser update. Now my current version is 80.0.3987.87.
Yet I´ve got problems when running it in firejail (version 0.9.62) which I hadn´t encountered before. I noticed that my extension "Just Read" doesn´t work any more. It should put the displayed page in read-mode. (Description: A feature-packed, customizable reader extension.)
But when clicking on it now it hasn´t any effect at all.
By the way: I start chromium-browser with this command:
firejail --private=/home/rosika/Dokumente/work chromium-browser
.So I decided to give the default.profile-option a try, but the result was even worse:
firejail --profile=/etc/firejail/default.profile --private=/home/rosika/Dokumente/work chromium-browser
So the browser didn´t start at all.
After that I looked up journalctl and encountered the following:
As I said this problem is a new one and seems to be connected to the recent chromium update.
Can anybody help?
Thanks a lot in advance. Greetings. Rosika