[GH-ISSUE #3101] Firecfg breaks official GNOME Shell extension "Places Status Indicator" #1944

Open
opened 2026-05-05 08:36:37 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @corecontingency on GitHub (Dec 28, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3101

Normally, I wouldn't be too worried about firecfg breaking an extension. However, Places Status Indicator is officially supported by GNOME, as it is used in GNOME Classic, and at least in Arch, comes preinstalled with GNOME (disabled out of the box).

Extension_broken

If I delete ~/.local/share/applications/org.gnome.Nautilus.desktop then the extension works fine again. The only change between the local desktop file firecfg makes and the original in /usr/share/applications/org.gnome.Nautilus.desktop is changing DBusActivatable=true to DBusActivatable=false. Interestingly, this does not seem to be the cause of the problem, as even if I simply make a copy of the /usr/share/applications/ Nautilus desktop file, and put it in ~/.local/share/applications/ without changing anything, the extension will not work. Even a symlink breaks it.

It seems that if there is a file / symlink in ~/.local/share/applications/ named org.gnome.Nautilus.desktop, no matter the contents, the Places Status Indicator extension breaks.

I think that unless there is a pressing security benefit, firecfg should not make a local desktop file for Nautilus, especially since firecfg currently does not add a symlink in /usr/local/bin/ to make Nautilus run by default with firejail.

Originally created by @corecontingency on GitHub (Dec 28, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/3101 Normally, I wouldn't be too worried about `firecfg` breaking an extension. However, Places Status Indicator is [officially supported by GNOME](https://gitlab.gnome.org/GNOME/gnome-shell-extensions), as it is used in [GNOME Classic](https://help.gnome.org/users/gnome-help/stable/gnome-classic.html), and at least in Arch, comes preinstalled with GNOME (disabled out of the box). ![Extension_broken](https://user-images.githubusercontent.com/54042889/71539847-c7ad0d00-28ff-11ea-9ea9-bd813eb011d8.png) If I delete `~/.local/share/applications/org.gnome.Nautilus.desktop` then the extension works fine again. The only change between the local desktop file `firecfg` makes and the original in `/usr/share/applications/org.gnome.Nautilus.desktop` is changing `DBusActivatable=true` to `DBusActivatable=false`. Interestingly, this does not seem to be the cause of the problem, as even if I simply make a copy of the `/usr/share/applications/` Nautilus desktop file, and put it in `~/.local/share/applications/` without changing anything, the extension will not work. Even a symlink breaks it. It seems that if there is a file / symlink in `~/.local/share/applications/` named `org.gnome.Nautilus.desktop`, no matter the contents, the Places Status Indicator extension breaks. I think that unless there is a pressing security benefit, `firecfg` should not make a local desktop file for Nautilus, especially since `firecfg` currently does not add a symlink in /usr/local/bin/ to make Nautilus run by default with firejail.
gitea-mirror added the
bug
firecfg
labels 2026-05-05 08:36:37 -06:00
Author
Owner

@rusty-snake commented on GitHub (Dec 28, 2019):

  1. Looks more like a issue of the extensions, if it is broken with a .desktop file in .local/share/applications.
  2. If a .desktop file contains DBusActivatable=true the applications is usually started over an DBus-interface where firejail is not used. (That the reason why this is changed by firecfg).
  3. I agree with you that if there firecfg does not create a symlink, it should not create fixed .desktop files.
<!-- gh-comment-id:569404046 --> @rusty-snake commented on GitHub (Dec 28, 2019): 1. Looks more like a issue of the extensions, if it is broken with a .desktop file in .local/share/applications. 2. If a .desktop file contains `DBusActivatable=true` the applications is usually started over an DBus-interface where firejail is not used. (That the reason why this is changed by firecfg). 3. I agree with you that if there firecfg does not create a symlink, it should not create fixed .desktop files.
Author
Owner

@ghost commented on GitHub (Jan 20, 2020):

This reminded me of #2624. I did a quick retest of firecfg (which I don't use by default) just now. We really have to improve it IMHO:

  • don't create .desktop files if no symlink is created (which would fix this issue and possibly others);
  • support removing .desktop files when calling sudo firecfg --clean (to fix firecfg for all users using it).

Marking this as a bug to attract attention to the fact firecfg is in a pretty broken state.

<!-- gh-comment-id:576459482 --> @ghost commented on GitHub (Jan 20, 2020): This reminded me of #2624. I did a quick retest of firecfg (which I don't use by default) just now. We really have to improve it IMHO: - don't create .desktop files if no symlink is created (which would fix this issue and possibly others); - support removing .desktop files when calling `sudo firecfg --clean` (to fix firecfg for all users using it). Marking this as a bug to attract attention to the fact firecfg is in a pretty broken state.
Author
Owner

@rusty-snake commented on GitHub (Jan 21, 2020):

Fedora 31, GNOME 3.34.1, places-menu 3.34.1 (installed via dnf), firejail git: No breaktages.

<!-- gh-comment-id:576723387 --> @rusty-snake commented on GitHub (Jan 21, 2020): Fedora 31, GNOME 3.34.1, places-menu 3.34.1 (installed via dnf), firejail git: No breaktages.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1944
No description provided.