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 1802105 - rpm based extensions in RHEL8 should not receive updates from extensions.gnome.org
Summary: rpm based extensions in RHEL8 should not receive updates from extensions.gnom...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-shell-extensions
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Florian Müllner
QA Contact: Martin Krajnak
Marek Suchánek
URL:
Whiteboard:
Depends On:
Blocks: 1739559
TreeView+ depends on / blocked
 
Reported: 2020-02-12 11:25 UTC by Martin Krajnak
Modified: 2023-04-27 12:07 UTC (History)
5 users (show)

Fixed In Version: chrome-gnome-shell-10.1-7.el8,gnome-shell-3.32.2-29.el8
Doc Type: Bug Fix
Doc Text:
.Supported GNOME Shell extensions now update only from system packages RHEL distributes certain supported GNOME Shell extensions as system RPM packages. Prior to this update, GNOME Shell offered to update the system extensions with upstream versions found on the link:https://extensions.gnome.org/[extensions.gnome.org] website. As a consequence, you could unknowingly replace supported extensions with unsupported, upstream versions. With this update, GNOME Shell no longer allows upstream extensions to replace the system extensions. The system extensions update only from system packages. To update a system extension to an upstream version, use the following procedure: . Uninstall the RPM package that includes the extension. . Make sure that the GNOME Shell browser integration is installed: + ---- # yum install chrome-gnome-shell ---- . Reinstall the extension from the link:https://extensions.gnome.org/[extensions.gnome.org] website.
Clone Of:
Environment:
Last Closed: 2021-05-18 14:38:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab Infrastructure/extensions-web/issues/97 0 None None None 2020-02-17 16:02:19 UTC

Description Martin Krajnak 2020-02-12 11:25:52 UTC 
Description of problem:
We noticed notifications offering updated for gnome-shell-extensions which we ship as rpm and we support them in RHEL. Thing is, we don't want them to be updated from upstream as it's not supported by us. 

The first thing which crossed my mind was that we could change uuids of extensions so they would differ from those that are offered by extensions.gnome.org.

Version-Release number of selected component (if applicable):
gnome-shell-extension-common-3.32.1-10.el8.noarch
chrome-gnome-shell-10.1-6.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1.install rpm based extensions

Actual results:
It's possible to update extensions from extensions.gnome.org.

Expected results:
The only way to update rpm-based extension should be via dnf.

Additional info:
Comment 1 Florian Müllner 2020-02-17 15:58:58 UTC 
(In reply to Martin Krajnak from comment #0)
> Expected results:
> The only way to update rpm-based extension should be via dnf.

The website is indeed expected to only update extensions that are installed in the user's HOME:
https://gitlab.gnome.org/GNOME/chrome-gnome-shell/blob/master/connector/chrome-gnome-shell.py#L593

I haven't done enough testing to confirm whether that is working or not, but I did notice that the extensions website itself adds "update" buttons in the list under "Installed Extensions".

I filed https://gitlab.gnome.org/Infrastructure/extensions-web/issues/97 for tracking that.


> Description of problem:
> The first thing which crossed my mind was that we could change uuids of
> extensions so they would differ from those that are offered by
> extensions.gnome.org.

That's a big-hammer work-around that I'd rather avoid if possible. Those UUIDs may very well show up in scripts or dconf presets, so if we can avoid breaking them by getting fixes for the actual issue (in chrome-gnome-shell(?) and the website), that would be preferable.
Comment 16 Martin Krajnak 2021-02-02 13:29:12 UTC 
Moving back until new build
Comment 23 errata-xmlrpc 2021-05-18 14:38:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: GNOME security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1586
Note You need to log in before you can comment on or make changes to this bug.