Closed slaufmann closed 4 years ago
I am now running ubuntu 18.04 Linux 4.18.0-20-generic and gnome-shell 3.28.3 This error:
Jun 2 08:40:36 Queeny gnome-shell[XXXXX]: Object objectname(0x55a752a2d6f0), 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
occurs sometimes after login addressing no particular? gnome-extension hanging the computer for about 5min and not executing Gnome start up programs yet mostly during operation unnoticed by me unless I check the system log then it's the same extension during the session.
example without the rest of the error message:
Jun 2 08:40:36 Queeny gnome-shell[11607]: Object .Gjs_BoxLayout_Backup_Tools (0x55a752a2d6f0),
Jun 1 15:50:21 Queeny gnome-shell[5471]: Object .Gjs_BoxLayout_Backup_Tools (0x563e1b82f550)
Jun 1 15:50:22 Queeny gnome-shell[5471]: Object .Gjs_BoxLayout_Backup_Tools (0x563e3216fc50)
Jun 1 15:50:22 Queeny gnome-shell[5471]: Object .Gjs_BoxLayout_Backup_Tools (0x563e32198350)
Jun 1 15:50:24 Queeny gnome-shell[5471]: Object .Gjs_BoxLayout_Backup_Tools (0x563e329f7590)
Jun 1 15:50:24 Queeny gnome-shell[5471]: Object .Gjs_BoxLayout_Backup_Tools (0x563e329f7590)
May 26 17:20:58 Queeny gnome-shell[5029]: Object Gdm.UserVerifierProxy (0x5566fa782bf0), has been May 26 17:21:15 Queeny gnome-shell[5029]: Object Gio.Settings (0x5566f51335c0), has been May 26 17:21:15 Queeny gnome-shell[5029]: Object Gio.Settings (0x5566f51335c0), has been May 26 17:21:15 Queeny gnome-shell[5029]: Object Gio.Settings (0x5566f51335c0), has been May 26 17:21:17 Queeny gnome-shell[5029]: Object Gio.Settings (0x5566f51335c0), has been
If I remember right this has been so since the upgrade to ubuntu 16. LTS about a year ago, tried other gnome versions, other managers, I like this setup yet don't know enough about gnome or the Linux system to fix it myself.
Commenting out the line
this.extension.actor.destroy();
in the file "extension.js" solved the problem for me.
Thanks, I will try this when I find the correct file, this filename in relation to gnome only occurs under gnome-shell/extensions/ . I was trying to build gnome3.33.3 but hit a snag with jhbuild, will try again later.
You do not have to rebuild anything. The .js file can be found in the extension directory under /usr/share/gnome-shell/extensions or ~/.local/share/gnome-shell/extensions respectively. A reload of the gnome-shell should be enough.
Thank you, I did a search on my system and home mount and I'm sure there are only extension.js files in each extension app directory not in /usr/share/gnome-shell/extensions or ~/.local/share/gnome-shell/extensions itself. As I understand, gnome-shell expects an extension.js script in gnome-shell/extensions I wonder why the shell even starts without it.
Thank you, I did a search on my system and home mount and I'm sure there are only extension.js files in each extension app directory not in /usr/share/gnome-shell/extensions or ~/.local/share/gnome-shell/extensions itself. As I understand, gnome-shell expects an extension.js script in gnome-shell/extensions or is your solution specific for the hamster extension.js ?
I meant the "extension.js" inside the plugin directory (hamster@projecthamster...). Sorry for being so unclear.
No,it's my fault, this tread is about the hamster extension I didn't realize the already destroyed Object addressing also occured in stand alone apps at least I learned a little bit more and I thank you for it.
@slaufmann and other affected people, which version of the hamster-shell-extension you've been using? There have been various fixes to problems related to destroying objects but they all went into the 0.10.0 release which has been out for about 2 years. Note that this is not the same code that is currently available from extensions.gnome.org.
As this has been silent for 6 months - have you been able to resolve the issue somehow? Can this be closed?
In the meantime I am running gnome-shell version 3.34.4 on Debian bullseye. Since I wanted to make a small modification I installed the extension from source. I did built on commit 4295319e4a16472f6b8609901c06a753b0437125 and it still runs fine.
So I guess this could be closed then.
Thanks for the heads-up.
I am running gnome-shell 3.30 on Debian buster (10) and hamster-shell-extension crashes after trying to unlock the screen and leads to a crash of gnome-shell. I think that the relevant part from the log is this:
Does anybody also experience this? I am not afraid to attempt a fix but i lack the experience on how to debug this further in order to get an idea where the code relevant for this crash is?
Thanks.