linuxmint / cinnamon

A Linux desktop featuring a traditional layout, built from modern technology and introducing brand new innovative features.
GNU General Public License v2.0
4.47k stars 732 forks source link

Gjs-CRITICAL errors on Linux Mint 21 #11034

Open anatolij-novoselcev opened 1 year ago

anatolij-novoselcev commented 1 year ago
 * Cinnamon version Cinnamon 5.4.9
 * Daily builds PPA: no
 * Distribution: Linux Mint 21 Vanessa
 * 64 bit

Hardware Info

Issue I upgrade to mint 21 and I have much Gjs-CRITICAL errors in .xsession-errors log file. BTW, upgrade history - LM 19.3 -> LM 20.3 -> LM 21 21 successfully updated without any problems. I use the default install options - ext4, swap, etc...

Object St.Button error Object Cinnamon.GenericContainer error Object St.Bin error Object St.BoxLayout error

On fresh install of LM 21 i have the same problems. I found how to reproduce "St.BoxLayout error" and "Object St.Bin error" :

  1. Try to move elements in the main menu
  2. Try to close the application by mouse middle click. Pinned application does not throw an error.

Fresh Linux Mint 21, VirtualBox, how to reproduce errors

I don't know how to reproduce Object Cinnamon.GenericContainer error. This error occurs the most times in the .xsession-errors

mtwebster commented 1 year ago

These things really aren't new for the most part, but before they were never logged. Now they are, which is actually nice - we can identify and eliminate them.

I'll leave this open until we can have a look at the specific cases here.

Thanks

mcarans commented 1 year ago

I have one more (I've upgraded from Mint 20.3 to 21): ` (cinnamon:38765): Gjs-CRITICAL **: 14:19:21.748: Object .MetaWindowActorX11 (0x55ba7921edd0), has been already disposed — impossible to connect to any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. == Stack trace for context 0x55ba777a5380 ==

0 7ffe89ceb320 b /usr/share/cinnamon/js/misc/signalManager.js:137 (3e19b7d0bbf0 @ 218)

1 7ffe89ceb460 b /usr/share/cinnamon/js/misc/signalManager.js:143 (3e19b7d0bba0 @ 123)

2 55ba79ac03e0 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:714 (10a40500ca10 @ 386)

3 55ba79ac02c8 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:804 (10a40500c8d0 @ 1342)

4 55ba79ac0218 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1177 (10a405006dd0 @ 428)

5 55ba79ac0170 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1026 (10a405005150 @ 302)

6 55ba79ac00b8 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:893 (10a405005470 @ 127)

`

timur-g commented 4 months ago

(cinnamon:3370): Gjs-CRITICAL **: 09:37:36.926: Object St.ScrollView (0x55d5c3d25350), has been already disposed — 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. == Stack trace for context 0x55d5c2319260 ==

0 55d5c372b480 i /usr/share/cinnamon/js/ui/popupMenu.js:2886 (38eab87f6380 @ 378)

1 55d5c372b3e0 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:89 (1a09fe0a1150 @ 109)

2 7ffc204ced80 b self-hosted:1121 (38eab87aeb00 @ 463)

3 55d5c372b320 i resource:///org/gnome/gjs/modules/core/_signals.js:130 (38eab879ed80 @ 126)

4 55d5c372b260 i resource:///org/gnome/gjs/modules/core/_signals.js:119 (38eab879ec90 @ 286)

5 7ffc204cfd40 b /usr/share/cinnamon/js/ui/popupMenu.js:2431 (38eab87f5ba0 @ 2348)

6 55d5c372b0e8 i /usr/share/cinnamon/js/ui/popupMenu.js:2138 (38eab87f58d0 @ 63)

7 55d5c372b060 i /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:53 (38eab87e9880 @ 90)

8 55d5c372afc8 i /usr/share/cinnamon/js/ui/applet.js:284 (38eab87cf6a0 @ 192)

9 7ffc204d0800 b self-hosted:1121 (38eab87aeb00 @ 463)

claudiux commented 4 months ago

Check timers and handlers. I'm looking for this type of error on an applet I'm developing.