Ubuntu Version:
24.04.2 LTS
Desktop Environment (if applicable):
GNOME
Problem Description:
This is a revival of an earlier question that was batted around here some months ago:
https://discourse.ubuntu.com/t/re-my-lenovo-laptop-cannot-be-left-standing-for-any-lengthy-interval-without-requiring-reboot/59614
It’s been closed.
Since then, I did manage to get Ubuntu 24.04.2 LTS installed and working.
I did manage to get a workable hibernation. But I’d rather not have to hibernate every time I walk away from the computer. For one thing, I’d like to have automated backups running and the computer has to be on in order to do this.
So I stopped using the hibernate. Just walking away works most of the time but not all. Crashes occur occasionally.
The logs produced by journalctl have some information but I have no idea what to do with this info. See below. Reading journalctl logs is the ‘standard’ prescribed way to diagnose these sorts of problems, but the clues aren’t of much help to the end user.
Is there anything else worth trying or must I accept that my hardware and chosen peripheral devices are never going to be 100% reliable?
Relevant System Information:
System: Lenovo ThinkPad 16P Gen 2
GPU NVidia RTX 3500 Ada Generation (but I’m not doing anything at the moment that utilizes this card)
Added second Monitor BenQ RD240Q - works fine when running
Added LogiTech MX Mechanical Keyboard and MX Master 3S mouse. These are connected via Bluetooth.
Screenshots or Error Messages:
sudo journalctl -b -1 -ex | pastebinit
https://dpaste.com/9TLZ375PS
At the top we see repeated instances of messages like this:
Jun 28 10:44:11 aigas gnome-shell[4518]: Object .Gjs_ui_slider_Slider (0x5bb1b4c4f300), 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 0x5bb1adec1400 ==
#0 5bb1adf8db20 i resource:///org/gnome/shell/ui/barLevel.js:72 (279e8fb76510 @ 112)
#1 5bb1adf8da90 i resource:///org/gnome/shell/ui/status/brightness.js:44 (39ac7ef2c970 @ 47)
#2 5bb1adf8d9e8 i resource:///org/gnome/shell/ui/status/brightness.js:53 (39ac7ef2c9c0 @ 137)
#3 5bb1adf8d968 i resource:///org/gnome/shell/ui/status/brightness.js:28 (39ac7ef2c8d0 @ 12)
#4 5bb1adf8d8d8 i resource:///org/gnome/shell/ui/init.js:21 (190622d70bf0 @ 48)
This looks like a bug in gnome to me.
Then we see this at line 2220:
Jun 28 10:46:49 aigas gnome-shell[4518]: Exception in callback for signal: updated: TypeError: layout is null
Stack trace:
_rebuildCalendar@resource:///org/gnome/shell/ui/calendar.js:718:13
setEventSource@resource:///org/gnome/shell/ui/calendar.js:463:14
_setEventSource@resource:///org/gnome/shell/ui/dateMenu.js:979:24
_sessionUpdated@resource:///org/gnome/shell/ui/dateMenu.js:999:14
_callHandlers@resource:///org/gnome/gjs/modules/core/_signals.js:130:42
_emit@resource:///org/gnome/gjs/modules/core/_signals.js:119:10
_sync@resource:///org/gnome/shell/ui/sessionMode.js:211:14
pushMode@resource:///org/gnome/shell/ui/sessionMode.js:173:14
activate@resource:///org/gnome/shell/ui/screenShield.js:661:34
_onLongLightbox@resource:///org/gnome/shell/ui/screenShield.js:384:18
onComplete@resource:///org/gnome/shell/ui/lightbox.js:202:18
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:67:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:160:64
@resource:///org/gnome/shell/ui/init.js:21:20
There is this at line 3804:
Jun 28 10:53:28 aigas /usr/libexec/gdm-x-session[4138]: (EE) event20 - Logitech MX Master 3S: client bug: event processing lagging behind by 495ms, your system is too slow
Not sure why the mouse would need to be contacted when the system is idle.
Just walking away works most of the time but not all
Then we come to this (line 4337)
Jun 28 11:00:02 aigas systemd[1]: Started session-c172.scope - Session c172 of User scohen.
░░ Subject: A start job for unit session-c172.scope has finished successfully
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit session-c172.scope has finished successfully.
░░
░░ The job identifier is 54305.
Jun 28 11:00:02 aigas runuser[152019]: pam_unix(runuser-l:session): session opened for user scohen(uid=1001) by (uid=0)
Jun 28 11:00:02 aigas runuser[152019]: pam_unix(runuser-l:session): session closed for user scohen
Jun 28 11:00:02 aigas systemd[1]: session-c172.scope: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit session-c172.scope has successfully entered the 'dead' state.
Uh, what is the “dead state” and why is this considered “success”?
Finally, line 4425, we get this:
Jun 28 11:00:38 aigas kernel: general protection fault, probably for non-canonical address 0x3f15474aded36c: 0000 [#1] PREEMPT SMP NOPTI
Jun 28 11:00:38 aigas kernel: CPU: 0 PID: 150432 Comm: kworker/0:0 Tainted: P O 6.8.0-62-generic #65-Ubuntu
Jun 28 11:00:38 aigas kernel: Hardware name: LENOVO 21FACTO1WW/21FACTO1WW, BIOS N3TET57W (1.57 ) 10/21/2024
What I’ve Tried:
HIbernation is the most reliable way to avoid crashes, but as explained above, I’d rather not have to do it this way.