elvetemedve / gnome-shell-extension-system-monitor

Gnome Shell extension for displaying resource usage
GNU General Public License v3.0
87 stars 14 forks source link

Relase 18: TypeError: GObject.registerClass() used with invalid base class (is PopupBaseMenuItem) #65

Open abhijeetviswa opened 4 years ago

abhijeetviswa commented 4 years ago

I'm running Gnome Shell 3.32.2 and release 18 of the extension. However, it fails to load with the following error message:

TypeError: GObject.registerClass() used with invalid base class (is PopupBaseMenuItem)

tyctor commented 4 years ago

same error for me, Gnome Shell 3.32.2 and release 18 of the extension

elvetemedve commented 4 years ago

I'm afraid there are two options at the moment:

tyctor commented 4 years ago

thanks for answer, version from your link is working for me

tyctor commented 4 years ago

after 1day of running, item in system monitor doubled or maybe tripled Screenshot from 2020-03-07 00-32-59

restart of gnome-shell solves this for one day is this related to system monitor extension or gnome-shell itself?

elvetemedve commented 4 years ago

Every extension has the responsibility to remove all the changes it made when it's deactivated. So it's the extension's fault. But there must be an error preventing that happen.

tyctor commented 4 years ago

yes, i can see something in log, sending here, hope it helps systemmonitor.log

elvetemedve commented 4 years ago

Two similar error messages are repeating over the log:

Object St.Label (0x55837356f870), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.

Object St.Button (0x55837428c4a0), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.

Unfortunately it does not tell where the problem is in the extension code. Resolving that would require further debugging.

Since this problem does not exist in latest Gnome Shell with latest extension, either you upgrade to the latest or keep Gnome Shell, but try an older version of the extension. Previous releases are available from the Github releases page.