If you run into problems, leave your questions anywhere on this site, or on our GitHub bug tracker. Also check our Frequently Asked Questions and Known Problems pages.


Get involved

Firejail is a project developed by volunteers from all around the world. You are welcome to join us on GitHub. All contributions are welcome: ideas, feature requests, patches, documentation, bug reports, complaints.


Bug reports

Bug reports are vital for making Firejail a robust and capable application. Please use the comment section on any page on this site, or the facilities provided by GitHub.

All security bugs in Firejail are taken seriously and should be reported by emailing

108 thoughts on “Support

  1. Jules

    Following the update to Firejail 0.9.46, I can’t use Quiterss with Firejail. I’m on Arch and using Quiterss 0.18.4. Quiterss runs fine when not under Firejail – and before the update, it ran successfully under Firejail.

    Here’s the error message I now get:
    Reading profile /etc/firejail/quiterss.profile
    Reading profile /etc/firejail/
    Reading profile /etc/firejail/
    Reading profile /etc/firejail/
    Reading profile /etc/firejail/
    Warning: noroot option is not available
    Reading profile /etc/firejail/
    Parent pid 8087, child pid 8088
    Warning: /sbin directory link was not blacklisted
    Warning: /usr/sbin directory link was not blacklisted
    Blacklist violations are logged to syslog
    Child process initialized in 250.57 ms
    terminate called after throwing an instance of ‘std::bad_alloc’
    what(): std::bad_alloc

    Parent is shutting down, bye…
    Any thoughts, assistance, advice would be most appreciated.



  2. totalizator

    I have been using firejail just for the sake of –interface=tun0 –defaultgw= –dns= (badvpn/tuntap) and after the last update (0.9.46-1 I believe) my app stopped working, complaining about access permissions. When I launch it with –noprofile it works as expected – I have my app using separate, socks based network interface. Can I know what has changed regarding this “issue”?


    1. netblue30 Post author

      Could be something in the profile for your application. The best way to debug it is to go in /etc/firejail/app.profile (the specific application profile file there) and comment out the lines one by one. I assume one of the m is creating the problem, probably “protocol” line.

      Liked by 1 person

  3. Jens


    I want to supply a solution to a strange problem with sound not working in Firefox. I have been searching for days on this problem which I get in Apparmor when using Firejail and Apparmor at the same time (no problem if I only use Firejail or only use Apparmor):

    apparmor=”DENIED” operation=”connect” info=”Failed name lookup – disconnected path” error=-13 profile=”/usr/lib/firefox/firefox{,*[^s][^h]}” name=”run/user/1000/pulse/native” pid=4636 comm=4D65646961506C7E6261636B202333 requested_mask=”wr” denied_mask=”wr” fsuid=1000 ouid=1000

    I have followed the modifications on this site and tried both older and newer versions of Firejail without any luck. The solution was to change the Firefox Apparmor profile from:

    /usr/lib/firefox/firefox{,*[^s][^h]} {


    /usr/lib/firefox/firefox{,*[^s][^h]} flags=(attach_disconnected) {

    I don’t understand what this is doing but I found it from a similar problem here:

    I hope this can help someone.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s