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 1261552 - Extensions from RHEL 7.1 don't work on 7.2 beta
Summary: Extensions from RHEL 7.1 don't work on 7.2 beta
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 7.2
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1133060
TreeView+ depends on / blocked
 
Reported: 2015-09-09 15:46 UTC by Brian Gollaher
Modified: 2015-11-19 07:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:20:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2216 0 normal SHIPPED_LIVE gnome compositor stack bug fix and enhancement update 2015-11-19 08:26:34 UTC

Description Brian Gollaher 2015-09-09 15:46:08 UTC 
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"
Comment 1 Matthias Clasen 2015-09-09 15:50:06 UTC 
Florian, afaik, the plan was to show a notification that instructs users to update extensions. Did that not land ?
Comment 2 Brian Gollaher 2015-09-09 19:29:58 UTC 
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 3 Ray 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
Comment 4 Matthias Clasen 2015-09-18 13:12:11 UTC 
I've filed bug 1264436 with some ideas for improved extension handling in gnome-tweak-tool.
Comment 5 Ray 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.
Comment 6 Matthias Clasen 2015-09-18 14:19:15 UTC 
clearing needinfo
Comment 7 Florian Müllner 2015-09-21 19:26:05 UTC 
(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.
Comment 12 errata-xmlrpc 2015-11-19 07:20:58 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, 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
Note You need to log in before you can comment on or make changes to this bug.