cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

Pre-upgrade
From 19.x to each release until 20.3.

On 20.3, I had created a swapfile on btrfs. Whatever the reason, I was then prevented from creating snapshots, which blocked mintupgrade. Turning off swap let me create a snapshot and proceed with mintupgrade.

Upgrading
During the upgrade, after disabling some sources, removing some packages, and setting adding some orphans, 21 "successfully" installed.

I also had this held package but proceeded anyway:
viewtopic.php?p=2213216#p2213216

Post-upgrade
It first booted to the error console. Commenting out external drives in fstab allowed loading to the login screen, logging in, and so forth.

Code: Select all

* "Failed to start Load AppArmor profiles."
apparmor.systemd[100592]: AppArmor parser error for /etc/apparmor.d in profile /etc/apparmor.>
apparmor.systemd[100597]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
apparmor.systemd[100653]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
apparmor.systemd[100698]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confin>
apparmor.systemd[100716]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
apparmor.systemd[100567]: Error: At least one profile failed to load
systemd[1]: apparmor.service: Main process exited, code=exited, status=1/FAILURE
* .xsession-errors, which seems to grow 50-100MB or so per hour, is continually spammed with entries like the following:

1.

Code: Select all

(cinnamon:3151): Gjs-CRITICAL **: 06:43:25.229: Object St.Bin (0x55a8bed9fd80), 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 0x55a8be3f1380 ==
#0   7fff50f3eec0 b   /usr/share/cinnamon/js/ui/layout.js:647 (2c902ca892e0 @ 174)
#1   7fff50f3ef90 b   /usr/share/cinnamon/js/ui/layout.js:656 (2c902ca89290 @ 30)
#2   7fff50f3f070 b   /usr/share/cinnamon/js/ui/layout.js:589 (2c902ca894c0 @ 476)
#3   55a8be73fce8 i   /usr/share/cinnamon/js/ui/layout.js:695 (2c902ca89100 @ 130)
#4   7fff50f3fd80 b   self-hosted:850 (2e5da6caf9c0 @ 423)
2.

Code: Select all

(cinnamon:3151): Gjs-CRITICAL **: 07:03:02.589: Object St.Bin (0x55a8bf204b60), 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 0x55a8be3f1380 ==
#0   7fff50f40420 b   /usr/share/cinnamon/js/ui/layout.js:715 (2c902ca890b0 @ 310)
#1   7fff50f404e0 b   self-hosted:850 (2e5da6caf9c0 @ 398)

(cinnamon:3151): Gjs-CRITICAL **: 07:03:02.589: Object St.Bin (0x55a8bf204b60), 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 0x55a8be3f1380 ==
#0   7fff50f40420 b   /usr/share/cinnamon/js/ui/layout.js:716 (2c902ca890b0 @ 575)
#1   7fff50f404e0 b   self-hosted:850 (2e5da6caf9c0 @ 398)

(cinnamon:3151): Gjs-CRITICAL **: 07:03:02.590: Object St.Bin (0x55a8bf204b60), 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 0x55a8be3f1380 ==
#0   7fff50f40420 b   /usr/share/cinnamon/js/ui/layout.js:732 (2c902ca890b0 @ 1098)
#1   7fff50f404e0 b   self-hosted:850 (2e5da6caf9c0 @ 398)
3.

Code: Select all

(cinnamon:3151): Gjs-CRITICAL **: 07:03:55.657: Object St.Bin (0x55a8bed548b0), 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 0x55a8be3f1380 ==
#0   7fff50f3d910 b   /usr/share/cinnamon/js/ui/layout.js:593 (2c902ca894c0 @ 557)
#1   7fff50f3e650 b   /usr/share/cinnamon/js/ui/layout.js:277 (2c902ca89b50 @ 37)
#2   55a8bed4b058 i   /usr/share/cinnamon/js/ui/main.js:1233 (2e5da6cf7b00 @ 454)
#3   55a8bed4af50 i   /usr/share/cinnamon/js/ui/appSwitcher/appSwitcher.js:126 (275d859425b0 @ 31)
#4   55a8bed4ae80 i   /usr/share/cinnamon/js/ui/appSwitcher/classicSwitcher.js:58 (275d8594ba10 @ 190)
#5   55a8bed4add8 i   /usr/share/cinnamon/js/ui/appSwitcher/classicSwitcher.js:39 (275d8594ba60 @ 36)
#6   55a8bed4ad40 i   /usr/share/cinnamon/js/ui/windowManager.js:1272 (275d8593a420 @ 178)
#7   55a8bed4aca8 i   /usr/share/cinnamon/js/ui/windowManager.js:1277 (275d8593a3d0 @ 20)
#8   55a8bed4ac08 i   /usr/share/cinnamon/js/ui/windowManager.js:294 (275d8593e8d0 @ 21)
Compared to 20.3 and prior, input and UI responsiveness is sluggish.

Some apps no longer work or exhibit a problem, such as:
* One that plays audio while using the GPU and OpenGL has short, periodic audio blips.
* One that also uses the GPU and can play audio doesn't load but throws this: "error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory" although it exists in its own folder.
* One opens but features don't work.

Otherwise, the system is at least generally usable.

Code: Select all

$ inxi -Fxz
System:
  Kernel: 5.15.0-43-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: Cinnamon 5.4.9 Distro: Linux Mint 21 Vanessa
    base: Ubuntu 22.04 jammy
Machine:
  Type: Convertible System: LENOVO product: 20LHCTO1WW
    v: ThinkPad X380 Yoga S1 serial: <superuser required>
  Mobo: LENOVO model: 20LHCTO1WW v: 0B98423 WIN
    serial: <superuser required> UEFI: LENOVO v: R0SET46W (1.30 )
    date: 08/21/2019
Battery:
  ...
CPU:
  Info: quad core model: Intel Core i5-8350U bits: 64 type: MT MCP
    arch: Coffee Lake rev: A cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB
  Speed (MHz): avg: 799 high: 800 min/max: 400/3600 cores: 1: 800 2: 800
    3: 800 4: 792 5: 800 6: 800 7: 800 8: 800 bogomips: 30399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel
    bus-ID: 00:02.0
  Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
    bus-ID: 1-8:5
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2)
    v: 4.6 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
  Device-2: C-Media Schiit Modi 3 type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-3.3:8
  Sound Server-1: ALSA v: k5.15.0-43-generic running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.99.1 running: yes
  Sound Server-4: PipeWire v: 0.3.48 running: yes
Network:
  ...
Drives:
  ...
  ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKF256G8L size: 238.47 GiB
    temp: 34.9 C
Partition:
  ID-1: / ...         fs: btrfs
    dev: /dev/nvme0n1p2
  ID-2: /boot/efi ... fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home ...     fs: btrfs
    dev: /dev/nvme0n1p2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 45.0 C pch: 40.5 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  ...
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.0 Packages: 4185 Shell: Bash
  v: 5.1.16 inxi: 3.3.13
Last edited by LockBot on Thu Feb 09, 2023 11:00 pm, edited 3 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

I have the same problem with "Gjs-CRITICAL" error :(

Code: Select all

(cinnamon:4870): Gjs-CRITICAL **: 16:39:43.089: Object St.Button (0x55ce1630e410), 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 0x55ce139e2380 ==
#0   55ce14edc188 i   /usr/share/cinnamon/js/ui/environment.js:280 (2055014afec0 @ 42)
#1   7ffd341deba0 b   /usr/share/cinnamon/js/ui/messageTray.js:610 (3a30244626f0 @ 35)
#2   55ce14edc0f0 i   /usr/share/cinnamon/js/ui/messageTray.js:595 (3a3024462790 @ 77)
#3   55ce14edc068 i   /usr/share/cinnamon/js/ui/messageTray.js:268 (3a3024462d30 @ 12)


(cinnamon:4870): Gjs-CRITICAL **: 16:46:07.584: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   55ce1594fe18 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:320 (31ebc608c9c0 @ 174)
#1   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:329 (31ebc608c920 @ 24)
#2   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)

(cinnamon:4870): Gjs-CRITICAL **: 16:46:07.584: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   55ce1594fe18 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:321 (31ebc608c9c0 @ 200)
#1   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:329 (31ebc608c920 @ 24)
#2   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)

(cinnamon:4870): Gjs-CRITICAL **: 16:46:08.086: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:324 (31ebc608c970 @ 43)
#1   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)

(cinnamon:4870): Gjs-CRITICAL **: 16:46:08.086: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:325 (31ebc608c970 @ 83)
#1   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)

(cinnamon:4870): Gjs-CRITICAL **: 16:46:08.086: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:326 (31ebc608c970 @ 109)
#1   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)

(cinnamon:4870): Gjs-CRITICAL **: 16:46:08.588: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   55ce1594fe18 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:320 (31ebc608c9c0 @ 174)
#1   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:329 (31ebc608c920 @ 24)
#2   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)

(cinnamon:4870): Gjs-CRITICAL **: 16:46:08.588: Object Cinnamon.GenericContainer (0x55ce16b47770), 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 0x55ce139e2380 ==
#0   55ce1594fe18 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:321 (31ebc608c9c0 @ 200)
#1   7ffd341df500 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:329 (31ebc608c920 @ 24)
#2   7ffd341dfa90 b   /usr/share/cinnamon/js/misc/util.js:597 (2055014eeb00 @ 114)
BTW, Upgrade history - LM 19.3 -> LM 20.3 -> LM 21
21 "successfully" installed without any problems.
I did not use btrfs. I use the default install options - ext4, swap, etc...

On fresh install of LM 21 i see the same problem. I test it in VirtualBox. https://mega.nz/file/zxkRRCKD#xbvgZZyY- ... wriWZkPq7Q
Last edited by SMG on Wed Aug 10, 2022 11:07 am, edited 1 time in total.
Reason: Changed quote tags to code tags.
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

Code: Select all

$ inxi -Fxz
System:
  Kernel: 5.15.0-46-generic x86_64 bits: 64 compiler: gcc v: 11.2.0
    Desktop: Cinnamon 5.4.9 Distro: Linux Mint 21 Vanessa
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: ASRock model: B75 Pro3 serial: <superuser required>
    BIOS: American Megatrends v: P1.90 date: 12/20/2013
CPU:
  Info: quad core model: Intel Xeon E3-1275 V2 bits: 64 type: MT MCP
    arch: Ivy Bridge rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1962 high: 2237 min/max: 1600/3900 cores: 1: 2237
    2: 1910 3: 1980 4: 2073 5: 1795 6: 1596 7: 1979 8: 2126 bogomips: 55870
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics
    vendor: ASRock driver: i915 v: kernel bus-ID: 00:02.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting
    unloaded: fbdev,vesa gpu: i915 resolution: 1: 1920x1080~60Hz
    2: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics P4000 (IVB GT2)
    v: 4.2 Mesa 22.0.5 direct render: Yes
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASRock
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
  Sound Server-1: ALSA v: k5.15.0-46-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wireless 8260 driver: iwlwifi v: kernel bus-ID: 01:00.0
  IF: wlp1s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel port: d000 bus-ID: 03:00.0
  IF: enp3s0 state: down mac: <filter>
  IF-ID-1: br-43fffa4dc5d2 state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
    bus-ID: 1-1.1:3
  Report: hciconfig ID: hci0 rfk-id: 2 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>
Drives:
  Local Storage: total: 5.13 TiB used: 4.37 TiB (85.2%)
  ID-1: /dev/nvme0n1 model: SSD 256GB size: 238.47 GiB temp: 28.9 C
  ID-2: /dev/sda vendor: Intel model: SSDSC2KW256G8 size: 238.47 GiB
  ID-3: /dev/sdb vendor: Western Digital model: WD30EFRX-68AX9N0
    size: 2.73 TiB
  ID-4: /dev/sdc vendor: Western Digital model: WD10EFRX-68PJCN0
    size: 931.51 GiB
  ID-5: /dev/sdd vendor: Western Digital model: WD10EFRX-68JCSN0
    size: 931.51 GiB
  ID-6: /dev/sde vendor: OCZ model: VERTEX4 size: 119.24 GiB
Partition:
  ID-1: / size: 233.67 GiB used: 56.41 GiB (24.1%) fs: ext4 dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 768 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 340 Uptime: 9h 9m Memory: 31.05 GiB used: 7.5 GiB (24.2%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.2.0 Packages: 2586 Shell: Bash
  v: 5.1.16 inxi: 3.3.13
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

Mouse middle click on the panel app icon.
If do the same with pinned app, there is no error.

Code: Select all

(cinnamon:4870): Gjs-CRITICAL **: 21:50:26.173: Object St.Bin (0x55ce145690e0), 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 0x55ce139e2380 ==
#0   55ce1425b130 i   /usr/share/cinnamon/js/ui/popupMenu.js:2512 (3a3024439f60 @ 1188)
#1   7ffd341dc330 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1064 (31ebc608d920 @ 436)
#2   7ffd341dca70 b   /usr/share/cinnamon/js/ui/popupMenu.js:3729 (3a302442d420 @ 44)
#3   55ce1425b088 i   /usr/share/cinnamon/js/ui/popupMenu.js:3512 (3a302442d8d0 @ 46)
#4   55ce1425aff0 i   /usr/share/cinnamon/js/ui/popupMenu.js:3663 (3a302442d600 @ 20)
#5   7ffd341dd780 b   self-hosted:850 (2055014af9c0 @ 423)
#6   7ffd341dd870 b   resource:///org/gnome/gjs/modules/core/_signals.js:114 (2055014d69c0 @ 439)
#7   55ce1425af58 i   /usr/share/cinnamon/js/ui/popupMenu.js:2171 (3a302443a2e0 @ 77)
#8   55ce1425aea8 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1251 (31ebc608d510 @ 356)
#9   55ce1425ae08 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1154 (31ebc60876f0 @ 225)
#10   55ce1425ad58 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:410 (31ebc6094c40 @ 676)
#11   55ce1425aca8 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:959 (31ebc6087b50 @ 602)
#12   7ffd341de520 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:376 (31ebc6094d30 @ 446)
#13   7ffd341de5e0 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:242 (31ebc60866a0 @ 23)
#14   7ffd341de6c0 b   /usr/share/cinnamon/js/misc/util.js:505 (2055014eec90 @ 98)
#15   7ffd341de780 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:241 (31ebc60866f0 @ 27)
#16   7ffd341de860 b   /usr/share/cinnamon/js/misc/state.js:241 (31ebc6087330 @ 692)
#17   7ffd341de920 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:355 (31ebc6094d30 @ 326)
#18   7ffd341df260 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:58 (31ebc6099740 @ 127)
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

The same error on fresh LM 21 in VirtualBox

Code: Select all

(cinnamon:1801): Gjs-CRITICAL **: 19:00:51.749: Object St.Bin (0x55e75e61ba20), 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 0x55e75d9ce380 ==
#0   55e75ec01e38 i   /usr/share/cinnamon/js/ui/popupMenu.js:2512 (35bbb5639f60 @ 1188)
#1   7ffe95c97ec0 b   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1058 (3e7e8d20d150 @ 436)
#2   7ffe95c98600 b   /usr/share/cinnamon/js/ui/popupMenu.js:3729 (35bbb562d420 @ 44)
#3   55e75ec01d90 i   /usr/share/cinnamon/js/ui/popupMenu.js:3512 (35bbb562d8d0 @ 46)
#4   55e75ec01cf8 i   /usr/share/cinnamon/js/ui/popupMenu.js:3663 (35bbb562d600 @ 20)
#5   7ffe95c99310 b   self-hosted:850 (8f1eeaaf9c0 @ 423)
#6   7ffe95c99400 b   resource:///org/gnome/gjs/modules/core/_signals.js:114 (8f1eead69c0 @ 439)
#7   55e75ec01c60 i   /usr/share/cinnamon/js/ui/popupMenu.js:2171 (35bbb563a2e0 @ 77)
#8   55e75ec01bb0 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1245 (3e7e8d206ce0 @ 356)
#9   55e75ec01b10 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:1154 (3e7e8d200ec0 @ 225)
#10   55e75ec01a60 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:410 (3e7e8d20f3d0 @ 676)
#11   55e75ec019b0 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:959 (3e7e8d205380 @ 602)
#12   55e75ec01908 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:376 (3e7e8d20f4c0 @ 446)
#13   55e75ec01870 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:242 (b20883fbe70 @ 23)
#14   7ffe95c9a0b0 b   /usr/share/cinnamon/js/misc/util.js:505 (8f1eeaeec90 @ 98)
#15   55e75ec017d8 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:241 (b20883fbec0 @ 27)
#16   7ffe95c9ad30 b   /usr/share/cinnamon/js/misc/state.js:241 (3e7e8d200b00 @ 692)
#17   55e75ec01730 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:355 (3e7e8d20f4c0 @ 326)
#18   55e75ec01678 i   /usr/share/cinnamon/js/misc/fileUtils.js line 211 > Function:58 (3e7e8d20fe70 @ 127)
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

anatolij_novoselcev wrote: Wed Aug 10, 2022 2:56 pm Mouse middle click on the panel app icon.
If do the same with pinned app, there is no error.

Code: Select all

(cinnamon:4870): Gjs-CRITICAL **: 21:50:26.173: Object St.Bin (0x55ce145690e0), 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.
...
Restarting cinnamon does not remove the error for me.
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

On slugglishness introduced in 21, I noticed this in the boot log:

Code: Select all

ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Which seems to be confirmed:

Code: Select all

$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
powersave
This may at least partially, if not fully, explain the slugglishness, as setting this to `performance` makes the system about as responsive as before the upgrade.
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

Particle_Man wrote: Wed Aug 10, 2022 6:41 pm
anatolij_novoselcev wrote: Wed Aug 10, 2022 2:56 pm Mouse middle click on the panel app icon.
If do the same with pinned app, there is no error.

Code: Select all

(cinnamon:4870): Gjs-CRITICAL **: 21:50:26.173: Object St.Bin (0x55ce145690e0), 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.
...
Restarting cinnamon does not remove the error for me.
+1

btw, https://github.com/linuxmint/cinnamon/issues/11034
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

Particle_Man wrote: Wed Aug 10, 2022 6:44 pm On slugglishness introduced in 21, I noticed this in the boot log:

Code: Select all

ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Which seems to be confirmed:

Code: Select all

$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
powersave
This may at least partially, if not fully, explain the slugglishness, as setting this to `performance` makes the system about as responsive as before the upgrade.

Code: Select all

$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
schedutil

$ uname -r
5.15.0-46-generic
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

The recent libgtk-4 updates (from 4.6.5+ds-0ubuntu1) may not have reduced the .xsession-errors entries but they seem to have improved responsiveness.
anatolij_novoselcev
Level 1
Level 1
Posts: 7
Joined: Tue May 31, 2022 2:48 pm

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by anatolij_novoselcev »

Particle_Man wrote: Fri Aug 12, 2022 4:50 pm The recent libgtk-4 updates (from 4.6.5+ds-0ubuntu1) may not have reduced the .xsession-errors entries but they seem to have improved responsiveness.
There is no libgtk-4 in default install :(

Code: Select all

$ sudo apt list --installed | grep libgtk

libgtk-3-0/jammy,now 3.24.33-1ubuntu1 amd64 [installed,upgradable to: 3.24.33-1ubuntu2]
libgtk-3-bin/jammy,now 3.24.33-1ubuntu1 amd64 [installed,upgradable to: 3.24.33-1ubuntu2]
libgtk-3-common/jammy,jammy,now 3.24.33-1ubuntu1 all [installed,upgradable to: 3.24.33-1ubuntu2]
libgtk-layer-shell0/jammy,now 0.7.0-1 amd64 [installed]
libgtk2.0-0/jammy,now 2.24.33-2ubuntu2 amd64 [installed]
libgtk2.0-bin/jammy,now 2.24.33-2ubuntu2 amd64 [installed]
libgtk2.0-common/jammy,jammy,now 2.24.33-2ubuntu2 all [installed]
libgtk3-perl/jammy,jammy,now 0.038-1 all [installed]
libgtkmm-3.0-1v5/jammy,now 3.24.5-1build1 amd64 [installed]
libgtksourceview-3.0-1/jammy,now 3.24.11-2build1 amd64 [installed]
libgtksourceview-3.0-common/jammy,jammy,now 3.24.11-2build1 all [installed]
libgtksourceview-4-0/jammy,now 4.8.3-1 amd64 [installed]
libgtksourceview-4-common/jammy,jammy,now 4.8.3-1 all [installed]
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

For this:
error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

Fix by installing this:
http://nz2.archive.ubuntu.com/ubuntu/po ... _amd64.deb

If the link is dead, download the latest build from here:
http://nz2.archive.ubuntu.com/ubuntu/po ... l/?C=M;O=D

Thanks go here:
https://stackoverflow.com/questions/721 ... file-or-di
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

This error prevented apparmor.service from starting:

Code: Select all

apparmor.systemd[###]: AppArmor parser error for /etc/apparmor.d/usr.lib.snapd.snap-confine.>
apparmor.systemd[###]: Error: At least one profile failed to load
Fix with this:

Code: Select all

sudo apt install snapd; sudo apt remove snapd
Now, on the two disabled AppArmor profiles that remain:

Code: Select all

Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
usr.bin.firefox can be disabled becuase it's not installed (as I prefer LibreWolf).

But should usr.sbin.rsyslogd be enabled?
I don't know whether it was enabled in 20.3. I never changed default behavior since the initial install of 19.x, and I never saw an error. rsyslogd seems to be running without issue. So, since /etc/apparmor.d/usr.sbin.rsyslogd exists and is identical to /etc/apparmor.d/disable/usr.sbin.rsyslogd, I deleted the one in the disable dir (and then ran systemctl status apparmor). Unless it's advised otherwise for some reason or some issue arises, I will keep the rsyslogd profile enabled.
Particle_Man
Level 1
Level 1
Posts: 19
Joined: Thu Feb 06, 2020 9:27 am

Re: cinnamon Gjs-CRITICAL errors and other errors after upgrade to 21

Post by Particle_Man »

To mitigate the increasing size of .xsession-errors (until these issues are resolved), I added a cron job to check its size and periodically truncate, based on this:

https://www.daniloaz.com/en/how-to-prev ... huge-size/
Locked

Return to “Installation & Boot”