gnome-shell's enabled-extensions gsettings list is difficult for distros

Bug #1692823 reported by Jeremy Bícha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Shell
Won't Fix
Medium
gnome-shell (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

GNOME Shell extensions are enabled if they are listed in gsettings
org.gnome.shell enabled-extensions

1. This makes it difficult to handle upgrades if a distro wants to enable any extension by default.

2. This also causes a problem for certain extensions that should be enabled when installed. For instance, if you install gnome-shell-extension-onboard, it ought to be enabled without having to also explicitly turn it on. At least in Debian, it's expected that something usually starts working once you install it.

Proposal
--------
What about if the enabled key is part of the extension's own gsettings? Then a distro package could easily have the enabled key set or not.

And why not enable extensions by default? This would better match the behavior when you install extensions directly from https://extensions.gnome.org/

See Also
--------
LP: #1692903 issue with GNOME Shell modes

Tags: gnome-17.10
Jeremy Bícha (jbicha)
description: updated
Jeremy Bícha (jbicha)
tags: added: gnome-17.10
Changed in gnome-shell (Ubuntu):
status: New → Triaged
Changed in gnome-shell:
importance: Unknown → Medium
status: Unknown → Confirmed
Changed in gnome-shell:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.