Lock screen sometimes doesn't render (input is locked but desktop visible)

Bug #2037191 reported by Connor Nolan
258
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
New
Undecided
Unassigned

Bug Description

Sometimes when I unlock my laptop by opening the lid, the touchscreen just doesn't render. This renders the system completely frozen until I go into a TTY and run "sudo loginctl unlock-sessions".

But that's not the real problem. The real problem is that while the lock-screen doesn't render, *everything* else does. This means that while I wasn't logged in, Firefox and all other open applications were completely visible. This is obviously a big issue if one has sensitive information open.

There does not seem to be a reliable way to reproduce this, it just happens sometimes. So far, I've experienced this twice, once on 23.04 and once on the 23.10 beta.

There are however, some really suspicious error messages in the logs:

Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1809 (3e69d1677920 @ 73)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1812 (3e69d1677920 @ 124)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1941 (3e69d1677e20 @ 43)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1988 (3e69d1677fb0 @ 112)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:112 (2f81e37d600 @ 43)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:289 (2f81e37dc40 @ 39)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:115 (2f81e37d600 @ 91)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:138 (2f81e37d600 @ 380)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:153 (2f81e37d740 @ 15)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532fe10 b self-hosted:164 (2f81e399ec0 @ 272)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:153 (2f81e37d600 @ 495)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #7 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:153 (2f81e37d740 @ 15)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532fe10 b self-hosted:164 (2f81e399ec0 @ 272)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:153 (2f81e37d600 @ 495)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #7 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:155 (2f81e37d600 @ 511)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 7fff9532fe10 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:687 (2f81e3a0560 @ 25)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:156 (2f81e37d600 @ 562)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 7fff9532fe10 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:687 (2f81e3a0560 @ 25)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:156 (2f81e37d600 @ 562)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:157 (2f81e37d600 @ 583)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:160 (2f81e37d790 @ 15)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532fe10 b self-hosted:180 (2f81e373ce0 @ 294)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:160 (2f81e37d600 @ 603)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #7 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6417e0 i resource:///org/gnome/shell/ui/environment.js:160 (2f81e37d790 @ 15)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532fe10 b self-hosted:180 (2f81e373ce0 @ 294)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e641710 i resource:///org/gnome/shell/ui/environment.js:160 (2f81e37d600 @ 603)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641678 i resource:///org/gnome/shell/ui/environment.js:297 (2f81e37dce0 @ 19)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #4 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1987 (3e69d1677fb0 @ 176)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #5 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #6 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #7 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1997 (3e69d1677fb0 @ 209)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1942 (3e69d1677e20 @ 58)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6415e8 i resource:///org/gnome/shell/ui/keyboard.js:1763 (3e69d1677790 @ 37)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 564e3e641558 i resource:///org/gnome/shell/ui/keyboard.js:1944 (3e69d1677e20 @ 74)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:1931 (3e69d1677dd0 @ 28)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 10)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532f9d0 b resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 16)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532f9d0 b resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 10)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532f9d0 b resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #0 564e3e6414d8 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 16)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #1 7fff9532f9d0 b resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to emit 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_EmojiSelection (0x564e419a5420), has been already disposed — 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e405d4320), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e405d4320), has been already disposed — 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.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: value "inf" of type 'gfloat' is invalid or out of range for property 'translation-y' of type 'gfloat'
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 23 17:31:26 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e41dbc4f0), has been already disposed — 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.
Sep 23 17:31:27 user-83BV gnome-shell[2000]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Sep 23 17:31:28 user-83BV gnome-shell[2000]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Sep 23 17:31:34 user-83BV gnome-shell[2000]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Sep 23 17:31:34 user-83BV gnome-shell[2000]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Sep 23 17:31:34 user-83BV gnome-shell[2000]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Sep 23 17:31:39 user-83BV gnome-shell[2000]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x564e3e64e8c0]': Error on line 1 char 14: “<” is not a valid name
Sep 23 17:31:39 user-83BV gnome-shell[2000]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x564e427db900]': Error on line 1 char 14: “<” is not a valid name
Sep 23 17:31:39 user-83BV gnome-shell[2000]: Object .Gjs_ui_keyboard_Keyboard (0x564e405d4320), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Sep 23 17:31:39 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #0 564e3e641618 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 10)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #1 564e3e6414d8 i resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #0 564e3e641618 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 16)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #1 564e3e6414d8 i resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #0 564e3e641618 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 10)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #1 564e3e6414d8 i resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: == Stack trace for context 0x564e3e5286b0 ==
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #0 564e3e641618 i resource:///org/gnome/shell/ui/keyboard.js:2003 (3e69d1678100 @ 16)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #1 564e3e6414d8 i resource:///org/gnome/shell/ui/layout.js:1061 (2f81e3f6ab0 @ 458)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #2 7fff9532faa0 b self-hosted:1121 (2f81e373f60 @ 407)
Sep 23 17:31:39 user-83BV gnome-shell[2000]: #3 564e3e641448 i resource:///org/gnome/shell/ui/init.js:21 (2f81e37d060 @ 48)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 23 17:27:25 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-02 (53 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 45.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-09-23 (0 days ago)

Revision history for this message
Connor Nolan (thebrokenrail) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The "real problem" you mention is being tracked in bug 1532508.

Please also review the workaround for bug 1876632 in case that's related.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Also please clarify: "the touchscreen just doesn't render" implies that nothing is visible. Hence no information has been exposed until after "sudo loginctl unlock-sessions"? If that's the case then there would be no security issue.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Connor Nolan (thebrokenrail) wrote :

"the touchscreen just doesn't render" was a typo, I meant the lock-screen.

What I meant was that I opened my laptop and just saw my session (including the shell and my current open Firefox window). I assumed that the lock-screen was supposed to render on top of that, but it was failing to.

The system was definitely still locked though as I couldn't interact with any of the UI until I ran "sudo loginctl unlock-sessions".

Revision history for this message
Connor Nolan (thebrokenrail) wrote :

Also, https://bugs.launchpad.net/bugs/1876632 isn't relevant because the Intel iGPU is my primary GPU.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1532508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Connor Nolan (thebrokenrail) wrote :

https://bugs.launchpad.net/bugs/1532508 seems to be about the lockscreen only being invisible for a split second, but in this bug it stays invisible, activity preventing the user from logging in while revealing the desktop.

summary: - Lockscreen sometimes doesn't render
+ Screen is sometimes not locked when opening the laptop lid
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
summary: - Screen is sometimes not locked when opening the laptop lid
+ Lockscreen sometimes doesn't render (input is locked but desktop
+ visible)
information type: Public → Public Security
summary: - Lockscreen sometimes doesn't render (input is locked but desktop
+ Lock screen sometimes doesn't render (input is locked but desktop
visible)
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.