Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gnome 42.4 Error: Object 0x25caec0a3430 is not a subclass of GObject_Object, it's a Promise #24

Closed
rubberbander opened this issue Sep 27, 2022 · 10 comments

Comments

@rubberbander
Copy link

OS: Fedora Linux 36 (Workstation Edition)
Gnome Version: 42.4
Windowing System: Wayland

The Syncthing Indicator extension is broken. The extension loads successfully and I can see the icon on the top bar, but nothing works. The extension does not connect to the Syncthing service although it does successfully starts the service (I can see it running in the System Monitor). It does not show any of the connected devices or synced folders.

In the Extensions application, the extension is shown as not enabled (even though it is) and the following error message is shown:

Object 0x25caec0a3430 is not a subclass of GObject_Object, it's a Promise

Screenshot from 2022-09-27 13-14-01

@rubberbander rubberbander changed the title Gnome 42.2 Error: Object 0x25caec0a3430 is not a subclass of GObject_Object, it's a Promise Gnome 42.4 Error: Object 0x25caec0a3430 is not a subclass of GObject_Object, it's a Promise Sep 27, 2022
@aguillotc
Copy link

@rubberbander

Are you using https://extensions.gnome.org/extension/615/appindicator-support/ too ?

I had the exact same issue as you for days.
Just today, I just updated this other etxension through my regular update routine, and now just after a reboot of Gnome (Alt+F2, type r, then enter) the syncthing extension works again.

@miadabdi
Copy link

miadabdi commented Oct 1, 2022

@aguillotc
I can confirm it is caused by version 46 of app-indecator extension.
downgrading to 45 fixed the problem.

Edit: does app-indecator auto update itself? it automattically got updated to 46 and there it goes again, facing the same error.

@rubberbander
Copy link
Author

@miadabdi
All Gnome extensions update automatically. I don't think there's a way to disable that.

@aguillotc
Copy link

aguillotc commented Oct 1, 2022

You can install a Gnome extension manually, to avoid the problem of auto-update if you have such thing, I think.

The process is not complicated at all, you just have to do some manual work as depicted in this example article I took randomly on Internet : Manual Installation of GNOME Extension from ZIP File [Easy Steps].

@miadabdi
Copy link

Still no solution? (besides downgrading app-indecator)

@Havard-SL
Copy link

I managed to solve it by removing the "AppIndicator and KStatusNotifierItem Support" extension from extensions, and rather downloading it through the terminal with "sudo dnf install gnome-shell-extension-appindicator".

Turns out I already had gnome-shell-extension-appindicator installed on my system, maybe that caused the issue?

Thanks to AsciiWolf on the gnome extensions website for writing about the dnf package!
https://extensions.gnome.org/extension/615/appindicator-support/

@frost19k
Copy link

@Havard-SL

I managed to solve it by removing the "AppIndicator and KStatusNotifierItem Support" extension from extensions

I don't understand what you mean by this. Gnome Extensions app does not allow you to "add/install" or "remove/uninstall" extensions - just "activate/deactivate" them.

Turns out I already had gnome-shell-extension-appindicator installed on my system

"AppIndicator and KStatusNotifierItem Support" & gnome-shell-extension-appindicator are the same thing.

Could you please paste the output of the following command?
dnf info gnome-shell-extension-appindicator

@miadabdi
Copy link

@Havard-SL
That did not work. I still have the same issue.

@2nv2u
Copy link
Owner

2nv2u commented Oct 29, 2022

I'm not sure what to do about this, any suggestions?

@2nv2u
Copy link
Owner

2nv2u commented May 7, 2023

Since this hasn't been updated for a while and I don't have an idea if this is actually an issue of this extension, I'm closing this for now.

@2nv2u 2nv2u closed this as completed May 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants