firejail 0.9.64 doesn't start palemoon
 

Hi all,

due to

"include firefox-common.profile" in firejail palemoon.profile

palemoon won't start ending with the error

"libGL error: failed to open drm device: Access denied
libGL error: failed to load driver: i915"

It happens including every firefox profile without regards if nightly esr aso so it seems that firefox and palemoon differs too much to share profiles.

I temporarily solved the issue commenting the include

"#include firefox-common.profile"

but it would be better to fix it definitely.

Does someone have an hint about which line of firefox profiles generate the above libGL error?

Thanks a lot indeed!

Have you tried with a fresh Palemoon profile?

With the standard profile included dropped the redirect to firefox profiles as told above and whitelisting a directory to make it accessible for downloading and uploading files within the browser it works flawlessly

I paste the actual standard in use which works with in bold the two modifications done by me

"# Firejail profile for palemoon
# This file is overwritten after every install/update
# Persistent local customizations
include palemoon.local
# Persistent global definitions
include globals.local

noblacklist ${HOME}/.cache/moonchild productions/pale moon
noblacklist ${HOME}/.moonchild productions/pale moon

mkdir ${HOME}/.cache/moonchild productions/pale moon
mkdir ${HOME}/.moonchild productions
whitelist ${HOME}/.cache/moonchild productions/pale moon
whitelist ${HOME}/.moonchild productions
whitelist ${DOWNLOADS}

# Palemoon can use the full firejail seccomp filter (unlike firefox >= 60)
seccomp
#ignore seccomp

#private-bin palemoon
# private-etc must first be enabled in firefox-common.profile
#private-etc palemoon
#private-opt palemoon

# Redirect
#include firefox-common.profile"

It's an hard work which I would be glad to make easier cause the only way I have to find where the trouble lies is to comment out again the redirect and commenting a line at a time in the included firefox profile until I will find which firefox profile line generates the error.

That's why I asked for an hint.

I will start the tough way and I will report my findings.

Thanks anyway a lot indeed.

I'm sorry about my last post - what I meant is: have you tried starting the browser with a fresh profile, e.g. by renaming the "~/palemoon productions" folder before you start it with firejail.
My reasoning was that some user settings might be causing the failure.