Skip to content

gnome

gio-launch-desktop

TODO: Rethink this profile

  • Access to gio from a profile is handled by child-open-*
  • Direct access should only be needed is some special context and it should not require access to that much resources.

gjs

GNOME JavaScript interpreter. It is used to run some gnome internal app as well as third party extensions.

Therefore, by default, some extension are confined under this profile. To fix this, the various programs using gjs must never run gjs as module, they need to run it as executable with a specific script.

This currently concerns:

  • gnome-extension-ding (used to not be started as a module)
  • org.gnome.ScreenSaver (simple dbus service)
  • org.gnome.Shell.Extensions (full UI app, requires gnome-strict, graphics, ...)
  • org.gnome.Shell.Notifications (simple dbus service)
  • org.gnome.Shell.Screencast (simple dbus service)

gnome-extension

gjs started from gnome-shell should (in theory) only run gnome extensions.

gnome-shell

Warning

Some gnome extensions run from this profile. It would be better to have a way to separate them.