RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1474967 - gnome-shell 'enabled-extensions' dconf key doesn't enable extensions for existing users, just for new users
Summary: gnome-shell 'enabled-extensions' dconf key doesn't enable extensions for exis...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Desktop_Migration_and_Administration_Guide
Version: 7.3
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Jana Heves
QA Contact: Tomas Pelka
URL:
Whiteboard:
Depends On:
Blocks: 1470091
TreeView+ depends on / blocked
 
Reported: 2017-07-25 17:26 UTC by Deepu K S
Modified: 2021-06-10 12:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-12 14:37:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Deepu K S 2017-07-25 17:26:40 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Desktop_Migration_and_Administration_Guide/extensions-enable.html

Section Number and Name: 
11.2. Enabling Machine-wide Extensions


Describe the issue:
The documentation states that;
"Note that newly-installed machine-wide extensions are disabled by default. To enable the extensions for all users, you need to set the org.gnome.shell.enabled-extensions key."

However after running `# dconf update`, the added extensions are not reflected to older users even after log out and login as mentioned in point 3.

The older users may have their own-enabled extensions. i.e If the user has their own enabled-extensions key set (e.g. if they've enabled an extension, and possibly even then disabled it), then the default enabled-extensions in dconf 'system' is ignored.


Suggestions for improvement: 
A change is needed in documentation which should say,

"To set the default enabled extensions you need to set the org.gnome.shell.enabled-extensions key. There is currently no way to enable additional extensions for users who have already logged in".

"This doesn't apply for existing users who have installed and enabled their own gnome-extensions."


Additional information: 
[root@vm252-28 ~]# cat /etc/dconf/db/local.d/00-extensions
[org/gnome/shell]
enabled-extensions=['launch-new-instance.github.com','alternate-tab.github.com']
[root@vm252-28 ~]# 

[root@vm252-28 ~]# dconf update

[root@vm252-28 ~]# gsettings get org.gnome.shell enabled-extensions
['launch-new-instance.github.com', 'alternate-tab.github.com']
[root@vm252-28 ~]#

'test' is an older user and 'newuser' is the newly created user.

[newuser@vm252-28 ~]$ gsettings get org.gnome.shell enabled-extensions
['launch-new-instance.github.com', 'alternate-tab.github.com']
[newuser@vm252-28 ~]$ 

[test@vm252-28 ~]$ gsettings get org.gnome.shell enabled-extensions
['launch-new-instance.github.com', 'places-menu.github.com', 'openweather-extension']
[test@vm252-28 ~]$ 



[root@vm252-28 ~]# cat /etc/dconf/db/local.d/00-extensions
[org/gnome/shell]
enabled-extensions=['launch-new-instance.github.com']
[root@vm252-28 ~]#

[root@vm252-28 ~]# dconf update

[root@vm252-28 ~]# gsettings get org.gnome.shell enabled-extensions
['launch-new-instance.github.com']
[root@vm252-28 ~]#

[newuser@vm252-28 ~]$ gsettings get org.gnome.shell enabled-extensions
['launch-new-instance.github.com']
[newuser@vm252-28 ~]$ 

[test@vm252-28 ~]$ gsettings get org.gnome.shell enabled-extensions
['launch-new-instance.github.com', 'places-menu.github.com', 'openweather-extension']
[test@vm252-28 ~]$ 

The changes doesn't affect older users or logged in users. The dconf settings get inherited to newly created users.


Note You need to log in before you can comment on or make changes to this bug.