Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Frippery extensions installed on RHEL 7.1 do not work when gnome-shell is updated to RHEL 7.2 beta
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Install Frippery panel favorites, Frippery move clock, etc.
2. Upgrade from RHEL 7.1 to RHEL 7.2 beta
Actual results:
Extensions disappear
Tweak tool will not allow them to be turned on
Expected results:
Customer extensions must work when upgrading versions of RHEL. There is no point offering extensions if RHEL minor releases break them.
Additional info:
Tweak tool flags "Extension does not support shell version"
Where is the notification supposed to appear? In tweak tool it implies the wrong version but remove is greyed out and there is no update. Looking glass says the extensions are out of date. FF 38 can't detect version of Gnome and the gnome add-on says it is not compatible with FF 38.
Comment 3Ray Strode [halfline]
2015-09-15 17:02:56 UTC
Brian, do you have gnome-shell-browser-plugin installed? you should be able to update your extensions from extensions.gnome.org
I've filed bug 1264436 with some ideas for improved extension handling in gnome-tweak-tool.
Comment 5Ray Strode [halfline]
2015-09-18 13:23:51 UTC
so I met with Brian yesterday and we discovered that he didn't have gnome-shell-browser-plugin installed, so extensions.gnome.org didn't work for him. This is, in part, because the browser-plugin package is in workstation-optional instead of workstation.
He ended up getting the frippery extension as an rpm from a 3rd party site, which is why the tweak tool was unable to update it.
Proposals:
1) we have knowledgebase article up front before release that discusses extensions and how any third party ones will need to be manually updated
2) we move the browser-plugin from workstation-optional to workstation. We still shouldn't have it installed by default, I think, because that may surprise admins on managed workstations.
3) we make sure the tweak tool gets the updtes mclasen proposes in bug 1264436
4) potentially do the notification mentioned in comment 1
I think 1 and 2 are important before 7.2 release, but the others can potentially wait.
(In reply to Matthias Clasen from comment #1)
> Florian, afaik, the plan was to show a notification that instructs users to
> update extensions. Did that not land ?
I'm afraid it didn't - let's try to use this bug to land it.
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, 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://rhn.redhat.com/errata/RHBA-2015-2216.html