#903 [chrome-gnome-shell] Project name and source repository changed to gnome-browser-connector | rhbz#2106868
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2106868 **
Information from BlockerBugs App:
2106868

Current vote summary

Commented but haven't voted yet: geraldosimiao, coremodule

The votes have been last counted at 2022-09-13 04:55 UTC and the last processed comment was #comment-816435

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


How that affects basic browser functionality?

I was talking about basic functionality of Shell Extensions, not basic web browser functionality. The chrome-gnome-shell package is preinstalled on Fedora Workstation and allows users to manage GNOME Shell Extensions - it is a backend for the "GNOME Shell integration" Firefox/Chrome Add-on. However, it does not work anymore - it was replaced by gnome-browser-connector in upstream and support for the old api that chrome-gnome-shell uses was removed from the extensions.gnome.org website.

FinalBlocker +1
FinalFE +1

This can be fixed after release as it affects all releases.

FinalBlocker -1
FinalFE -1

Is it really a good idea to ship a core package that is useless (does not work anymore)?

Is it really a good idea to ship a core package that is useless (does not work anymore)?

No really, it's should be removed from comps and retired.
I can't see a review request for the renaming https://bugzilla.redhat.com/show_bug.cgi?id=2106868#c10

Removing the package (that is currently a core part of Fedora Workstation/GNOME) and retiring it means removing the functionality (that is used by many users) instead of fixing it. I have suggested a better possible solution here: https://bugzilla.redhat.com/show_bug.cgi?id=2106868#c11

BetaBlocker +1
FinalBlocker +1

AGREED AcceptedFinalFE

Discussed during the 2022-09-12 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug and accept this as an AcceptedFreezeException (Final) was made as we agreed that current criteria do not cover this, but it's a serious issue and we may want to cover it. adamw will propose a new criterion for discussion, blocker decision is delayed while we do that. We certainly agree it's important enough for a freeze exception.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-12/f37-blocker-review.2022-09-12-16.01.txt

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F37 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata