Bug 1802105
| Summary: | rpm based extensions in RHEL8 should not receive updates from extensions.gnome.org | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Martin Krajnak <mkrajnak> |
| Component: | gnome-shell-extensions | Assignee: | Florian Müllner <fmuellner> |
| Status: | CLOSED ERRATA | QA Contact: | Martin Krajnak <mkrajnak> |
| Severity: | high | Docs Contact: | Marek Suchánek <msuchane> |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | fmuellner, jadahl, jkoten, mclasen, tpelka |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 8.0 | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-05-18 14:38:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1739559 | ||
|
Description
Martin Krajnak
2020-02-12 11:25:52 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. Moving back until new build 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 |