[GH-ISSUE #1942] Firefox 60 no menu with Firejail 0.9.54~rc2

gitea-mirror commented

2026-05-05 07:49:09 -06:00

Owner

Originally created by @ghost on GitHub (May 13, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1942

I had the problem with Firefox 60 not loading any web pages. I uninstalled 0.9.52 including dpkg --purge and installed Firejail 0.9.54~rc2 and ran firecfg. Now Firefox loads webpages but there is no menu at the top of the screen (File, History, etc.) on up to date Ubuntu 16.04. Those options return when I run /usr/bin/firefox to avoid firejail.

Originally created by @ghost on GitHub (May 13, 2018). Original GitHub issue: https://github.com/netblue30/firejail/issues/1942 I had the problem with Firefox 60 not loading any web pages. I uninstalled 0.9.52 including dpkg --purge and installed Firejail 0.9.54~rc2 and ran firecfg. Now Firefox loads webpages but there is no menu at the top of the screen (File, History, etc.) on up to date Ubuntu 16.04. Those options return when I run /usr/bin/firefox to avoid firejail.

gitea-mirror

2026-05-05 07:49:09 -06:00

closed this issue
added the
bug

information_old
labels

gitea-mirror commented

2026-05-05 07:49:14 -06:00

Author

Owner

@smitsohu commented on GitHub (May 14, 2018):

@ianh83 could you add the following to /etc/firejail/firefox.local and try it again?

ignore apparmor
ignore nodbus

In general global menus don't work without D-Bus. Is this actually still an issue with 18.04 on Gnome?

@smitsohu commented on GitHub (May 14, 2018): @ianh83 could you add the following to /etc/firejail/firefox.local and try it again? ``` ignore apparmor ignore nodbus ``` In general global menus don't work without D-Bus. Is this actually still an issue with 18.04 on Gnome?

gitea-mirror commented

2026-05-05 07:49:16 -06:00

Author

Owner

@igor2x commented on GitHub (May 14, 2018):

The same problem in my case using Ubuntu 16.04 32-bit hardware and Firejail version 0.9.54~rc2.

I executed: "firejail --debug firefox &> firefox.txt" see attached firefox.txt file for debug info: firefox.txt

@smitsohu, I added your two commands in newly created file /etc/firejail/firefox.local and menus are displayed fine now.

@igor2x commented on GitHub (May 14, 2018): The same problem in my case using Ubuntu 16.04 32-bit hardware and Firejail version 0.9.54~rc2. ![firefox](https://user-images.githubusercontent.com/10895030/40013690-91252692-57ae-11e8-96b7-8efb44822f3d.png) I executed: "firejail --debug firefox &> firefox.txt" see attached firefox.txt file for debug info: [firefox.txt](https://github.com/netblue30/firejail/files/2001927/firefox.txt) @smitsohu, I added your two commands in newly created file /etc/firejail/firefox.local and menus are displayed fine now.

gitea-mirror commented

2026-05-05 07:49:18 -06:00

Author

Owner

@ghost commented on GitHub (May 14, 2018):

[Edited as I made a mistake]

On my HP Spectre x360 laptop running up to date Ubuntu 16.04 LTS I get the behaviour described by me above - no File, etc., menus with 0.9.54~rc2 but when I run /usr/bin/firefox the menus appear.

When I create /etc/firejail/firefox.local with only the two lines:
ignore apparmor
ignore nodbus

and restart firefox as normal, the menus do appear, so that fixes it.

On my Dell 7280 running up to date 18.04 (brand new install), I installed 0.9.54~rc2 and ran firefox and can't see a File, etc, menu anywhere - so I ran Firefox without firejail, and then additionally removed and purged firejail completely, rebooted. In all cases I can see no File, etc, menu in Firefox at all!

I never actually took note of whether Firefox on 18.04 even has a File, etc, menu to begin with before installing Firejail so I don't know what's going on - I've only just started testing 18.04 so maybe that menu is hidden somewhere I'm unaware of.

@ghost commented on GitHub (May 14, 2018): [Edited as I made a mistake] On my HP Spectre x360 laptop running up to date Ubuntu 16.04 LTS I get the behaviour described by me above - no File, etc., menus with 0.9.54~rc2 but when I run /usr/bin/firefox the menus appear. When I create /etc/firejail/firefox.local with only the two lines: ignore apparmor ignore nodbus and restart firefox as normal, the menus do appear, so that fixes it. On my Dell 7280 running up to date 18.04 (brand new install), I installed 0.9.54~rc2 and ran firefox and can't see a File, etc, menu anywhere - so I ran Firefox without firejail, and then additionally removed and purged firejail completely, rebooted. In all cases I can see **no** File, etc, menu in Firefox at all! I never actually took note of whether Firefox on 18.04 even has a File, etc, menu to begin with before installing Firejail so I don't know what's going on - I've only just started testing 18.04 so maybe that menu is hidden somewhere I'm unaware of.

gitea-mirror commented

2026-05-05 07:49:20 -06:00

Author

Owner

@igor2x commented on GitHub (May 14, 2018):

I have been playing little bit more with /etc/firejail/firefox.local file.

Setting both settings and menus displayed.
ignore apparmor
ignore nodbus
Setting only first setting and menus not displaying.
ignore apparmor
Setting only second setting and menus are displayed.
ignore nodbus
My humble conclusion is only second settings is really required.

@ianh83, what kind of Ubuntu 16.04 do you have 64-bit or 32-bit? Execute: "uname -m" command in my case it displays "i686" which indicates 32-bit. I don't know if this is the issue, just saying...

@ianh83, Firefox on Ubuntu 18.04 using Gnome Shell does not use menus by default, that is pure Gnome Shell experience (that I don't like by the way).

@igor2x commented on GitHub (May 14, 2018): I have been playing little bit more with /etc/firejail/firefox.local file. 1. Setting both settings and menus displayed. ignore apparmor ignore nodbus 2. Setting only first setting and menus **not** displaying. ignore apparmor 3. Setting only second setting and menus are displayed. ignore nodbus My humble conclusion is only second settings is really required. @ianh83, what kind of Ubuntu 16.04 do you have 64-bit or 32-bit? Execute: "uname -m" command in my case it displays "i686" which indicates 32-bit. I don't know if this is the issue, just saying... @ianh83, Firefox on Ubuntu 18.04 using Gnome Shell does not use menus by default, that is pure Gnome Shell experience (that I don't like by the way).

gitea-mirror commented

2026-05-05 07:49:22 -06:00

Author

Owner

@ghost commented on GitHub (May 14, 2018):

@igor2x Sorry I edited my post as I made a typo in the .local file. I see the same behaviour as you now. I'm on x86_64 on both OSs.

That explains 18.04 - I don't like it either but I see most of the options are available through firefox's own menu button - ~~apart from 'restore previous session' under history, which I can't find but use a lot.~~ found 'restore previous session now too.

@ghost commented on GitHub (May 14, 2018): @igor2x Sorry I edited my post as I made a typo in the .local file. I see the same behaviour as you now. I'm on x86_64 on both OSs. That explains 18.04 - I don't like it either but I see most of the options are available through firefox's own menu button - ~~apart from 'restore previous session' under history, which I can't find but use a lot.~~ found 'restore previous session now too.

gitea-mirror commented

2026-05-05 07:49:24 -06:00

Author

Owner

@Vincent43 commented on GitHub (May 14, 2018):

Instead of using ignore aparmor in firefox.local you may try adding:

include <abstractions/dbus-strict>
include <abstractions/dbus-session-strict>
dbus,

to /etc/apparmor.d/local/firejail-local and exec systemctl restart apparmor or do a reboot.

@Vincent43 commented on GitHub (May 14, 2018): Instead of using `ignore aparmor` in `firefox.local` you may try adding: ``` include <abstractions/dbus-strict> include <abstractions/dbus-session-strict> dbus, ``` to `/etc/apparmor.d/local/firejail-local` and exec `systemctl restart apparmor` or do a reboot.

gitea-mirror commented

2026-05-05 07:49:25 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 16, 2018):

@Vincent43 FWIW, the AppArmor wiki suggests that you should not do a systemctl restart apparmor: https://gitlab.com/apparmor/apparmor/wikis/AppArmorInSystemd
Instead, you should do sudo apparmor_parser -r firejail-default, which should have the desired effect.

@chiraag-nataraj commented on GitHub (May 16, 2018): @Vincent43 FWIW, the AppArmor wiki suggests that you should _not_ do a `systemctl restart apparmor`: https://gitlab.com/apparmor/apparmor/wikis/AppArmorInSystemd Instead, you should do `sudo apparmor_parser -r firejail-default`, which should have the desired effect.

gitea-mirror commented

2026-05-05 07:49:26 -06:00

Author

Owner

@Vincent43 commented on GitHub (May 16, 2018):

On latest upstream apparmor release and ubuntu 18.04 systemctl restart apparmor is a safe thing to do. I don't know about 16.04. Perhaps reboot will be better.

@Vincent43 commented on GitHub (May 16, 2018): On latest upstream apparmor release and ubuntu 18.04 `systemctl restart apparmor` is a safe thing to do. I don't know about 16.04. Perhaps reboot will be better.

gitea-mirror commented

2026-05-05 07:49:27 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (May 16, 2018):

Hmmm, okay. Yeah, I'm not sure - I saw that wiki a while back when I first started experimenting with apparmor and figured it was safer to either use apparmor_parser -r or reboot. I suppose it depends on how the service file is shipped (quite possible the issue has been solved and the wiki hasn't been updated!).

@chiraag-nataraj commented on GitHub (May 16, 2018): Hmmm, okay. Yeah, I'm not sure - I saw that wiki a while back when I first started experimenting with apparmor and figured it was safer to either use `apparmor_parser -r` or reboot. I suppose it depends on how the service file is shipped (quite possible the issue has been solved and the wiki hasn't been updated!).

gitea-mirror commented

2026-05-05 07:49:29 -06:00

Author

Owner

@igor2x commented on GitHub (May 20, 2018):

Today I have installed firejail 0.9.54 final on Ubuntu 16.04 32-bit hardware and the problem is the same as in 0.9.54~rc2.

@Vincent43, I tried setting your suggestions from https://github.com/netblue30/firejail/issues/1942#issuecomment-388912279 and I get error:

Reading profile /etc/firejail/firefox.profile
Reading profile /etc/firejail/firefox.local
Error: "<abstractions/dbus-strict>" is an invalid filename

Third solution from my reply https://github.com/netblue30/firejail/issues/1942#issuecomment-388907285 solves the problem, so writing: ignore nodbus in /etc/firejail/firefox.local solves the problem.

@igor2x commented on GitHub (May 20, 2018): Today I have installed firejail 0.9.54 final on Ubuntu 16.04 32-bit hardware and the problem is the same as in 0.9.54~rc2. @Vincent43, I tried setting your suggestions from https://github.com/netblue30/firejail/issues/1942#issuecomment-388912279 and I get error: ``` Reading profile /etc/firejail/firefox.profile Reading profile /etc/firejail/firefox.local Error: "<abstractions/dbus-strict>" is an invalid filename ``` Third solution from my reply https://github.com/netblue30/firejail/issues/1942#issuecomment-388907285 solves the problem, so writing: ` ignore nodbus` in /etc/firejail/firefox.local solves the problem.

gitea-mirror commented

2026-05-05 07:49:30 -06:00

Author

Owner

@chiraag-nataraj commented on GitHub (Jul 25, 2018):

This seems to be solved. If this affects too many people, we can enable dbus as the default, but for right now, we can just document this.

@chiraag-nataraj commented on GitHub (Jul 25, 2018): This seems to be solved. If this affects too many people, we can enable dbus as the default, but for right now, we can just document this.

gitea-mirror referenced this issue

2026-05-05 08:32:07 -06:00

[GH-ISSUE #2983] SSH creates core dumps while using seccomp #1865

Rows
Columns

[GH-ISSUE #1942] Firefox 60 no menu with Firejail 0.9.54~rc2 #1299