Bug 2222479

Summary: Extension fails to run
Product: [Fedora] Fedora EPEL Reporter: v82a2
Component: gnome-shell-extension-appindicatorAssignee: Carl George 🤠 <carl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: carl, ego.cordatus, epel-packagers-sig, hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-shell-extension-appindicator-49-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-27 01:38:42 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:

Description v82a2 2023-07-12 23:52:07 UTC
Description of problem:
Does not run

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

How reproducible:
Most of the time

Steps to Reproduce:
Install and enable extension

Actual results:
appindicatorsupport.com[9423]: While initalizing proxy for org.kde.StatusNotifierItem-10300-1: Error: Argument two may not be null

Expected results:
No error

Additional info:

Comment 1 Carl George 🤠 2023-07-12 23:57:32 UTC
That error seems similar to this upstream issue [0], which is fixed in version 47.  I don't see any incompatibilities mentioned going from the current 46 to 47, so I can build that as an update to hopefully fix this.

[0] https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/386

Comment 2 Fedora Update System 2023-07-12 23:59:59 UTC
FEDORA-EPEL-2023-8e9203eade has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8e9203eade

Comment 3 Fedora Update System 2023-07-13 01:52:11 UTC
FEDORA-EPEL-2023-8e9203eade has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8e9203eade

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Artem 2023-07-13 07:02:53 UTC
@carl thanks. Maybe we should build v47 for f37 also then.

Comment 5 Carl George 🤠 2023-07-13 07:20:57 UTC
Sure, that makes sense.  But first lets give the reporter a chance to test to confirm this update does resolve the bug.  If it doesn't we may want to try updating it to an even higher version in both epel9 and f37.

Comment 6 v82a2 2023-07-13 11:25:45 UTC
The bug is not present in F37.

New error with testing package.

Name         : gnome-shell-extension-appindicator
Version      : 47
Release      : 1.el9
Architecture : noarch
Size         : 222 k
Source       : gnome-shell-extension-appindicator-47-1.el9.src.rpm
Repository   : @System
From repo    : epel-testing



gnome-shell[2521]: JS ERROR: While initalizing proxy for org.kde.StatusNotifierItem-3496-1: TypeError: method Gio.AsyncInitable.init_async: At least 3 arguments required, but only 2 passed
                                                         initAsync@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:120:20
                                                         _setupProxy@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:273:31
                                                         AppIndicatorsAppIndicator@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:259:14
                                                         _registerItem@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:97:31
                                                         _ensureItemRegistered@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:142:20
                                                         RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:207:24
                                                         async*_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35
                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34
gnome-shell[2521]: JS ERROR: TypeError: this._proxy is undefined
                                                         get status@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:365:9
                                                         get accessibleName@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:373:32
                                                         _init@/usr/share/gnome-shell/extensions/appindicatorsupport.com/indicatorStatusIcon.js:232:9
                                                         _registerItem@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:117:32
                                                         async*_ensureItemRegistered@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:142:20
                                                         RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:207:24
                                                         async*_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35
                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34
gnome-shell[2521]: JS ERROR: TypeError: this._proxy is undefined
                                                         get status@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:365:9
                                                         get accessibleName@/usr/share/gnome-shell/extensions/appindicatorsupport.com/appIndicator.js:373:32
                                                         _init@/usr/share/gnome-shell/extensions/appindicatorsupport.com/indicatorStatusIcon.js:232:9
                                                         _registerItem@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:117:32
                                                         async*_ensureItemRegistered@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:142:20
                                                         RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/appindicatorsupport.com/statusNotifierWatcher.js:207:24
                                                         async*_handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35
                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34

Comment 7 v82a2 2023-07-13 23:26:38 UTC
Manually installed version 48 and the bug is not present in that version.

F37 is on version 46 and is not affected.

Comment 8 Carl George 🤠 2023-07-18 19:07:29 UTC
Thanks for the feedback.  Fedora's commit history went from version 46 to 47 to 49.  I fast forwarded the epel9 branch to 49, built it, and modified the update.

Comment 9 Fedora Update System 2023-07-19 04:12:43 UTC
FEDORA-EPEL-2023-8e9203eade has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8e9203eade

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2023-07-27 01:38:42 UTC
FEDORA-EPEL-2023-8e9203eade has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.