Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1940887 - Top Icons Plus can't be enabled in GNOME 40
Summary: Top Icons Plus can't be enabled in GNOME 40
Status: CLOSED DUPLICATE of bug 1936207
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell-extension-topicons-plus
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Audrey Yeena Toskin
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2021-03-19 13:32 UTC by Michal Konecny
Modified: 2021-03-20 06:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-03-20 06:04:06 UTC
Type: Bug

Attachments (Terms of Use)

Description Michal Konecny 2021-03-19 13:32:28 UTC
Description of problem:
I tried to install the TopIcons Plus extension during Fedora Test Days ( After installation and restart of the VM I wasn't able to enable it.

Version-Release number of selected component (if applicable):

How reproducible:
Install TopIcons Plus on GNOME 40

Steps to Reproduce:
1. sudo dnf install gnome-shell-extension-topicons-plus
2. Restart machine
3. Open GNOME Extensions

Actual results:
TopIcons Plus is disabled and can't be enabled

Expected results:
TopIcons Plus extension is enabled

Additional info:
Because of the GNOME decision to remove the tray icons, this extension is now essential for plenty of users.

Comment 1 Audrey Yeena Toskin 2021-03-20 06:04:06 UTC
Thanks for the bug report, I'm glad you find TopIcons Plus useful :)

...I was actually already aware of this issue -- see Bug #1936207. Turns out the extension itself needs to be updated to be compatible with GNOME 40. We may already have a fix upstream, though I haven't tested it yet.

As a Red Hatter, I don't suppose you know how best to handle this sort of situation in the future? At the time, when I first noticed several of the GNOME Shell extensions that I package were incompatible with GNOME 40, I decided to update the dependencies to `gnome-shell < 3.39` to prevent users from installing it at all, which I figured was better UX than letting them install a broken package that can't work on their systems... But now *I'm* getting a million "fails to install" messages, so uh, it hasn't been great UX for me either 😅

Closing this bug now as a duplicate, but I'd still be interested in seeing your comments if you have better ideas of what to do next time there's a major GNOME API change and extensions don't update right away.

*** This bug has been marked as a duplicate of bug 1936207 ***

Note You need to log in before you can comment on or make changes to this bug.