There were no issues encountered during the system upgrade. Everything went smoothly, even the NVIDIA drivers were installed, and everything works fine.
However, when the system wakes up from sleep, the following message appears:
Oh no! Something has gone wrong.
A problem has occured and the system can’t recover.
Please log out and try again.
After logging out and logging back in, everything works fine again. This is quite annoying, and I’d like to fix it if possible. Does anyone have a suggestion on how to do this?
I’ve asked ChatGPT to help me analyze the journalctl output and identify potential issues and here’s the answer:
The journalctl_10m.txt log file seems to contain system messages primarily related to the GNOME Display Manager (GDM), which manages the user sessions and graphical login screen. Let’s break down the critical sections and identify potential issues:
GDM Starting and Session Management:
The log indicates the start of GDM and the handling of user sessions. There are entries showing “Gdm: GdmDisplay: Session never registered” and “gdm-password]: gkr-pam: unable to locate daemon control file”, which suggests problems with session management or PAM (Pluggable Authentication Modules) configuration.
X11 Session Management:
There are multiple entries for the X11 session starting, but soon after, the system logs messages indicating “gdm-session-worker]: GLib-GObject: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed”. This error points to potential memory management issues within the GNOME components or extensions.
GDM Child Process Exits:
Frequent log entries showing gdm: Child process [PID] was already dead. and GdmDisplay: Session never registered indicate recurring issues with the child processes that GDM spawns. This might be due to crashes or failed initializations of components.
Authentication Issues:
Entries like gkr-pam: unable to locate daemon control file and gkr-pam: stashed password to try later in open session suggest problems with the GNOME Keyring or PAM integration. These messages indicate that the PAM modules cannot correctly interact with the GNOME Keyring daemon, affecting user authentication.
Graphics and X11 Errors:
The log includes several entries related to X11, including “audit: type=1107 audit(…): pid=…” and “gdm-x-session[1381]: (–) Log file renamed from…” These messages might indicate issues with the X11 server configuration or interactions with the graphics hardware/drivers.
Gnome Settings Daemon Errors:
Errors related to GNOME settings daemon, like “gnome-settings-daemon: Failed to get session type: Cannot autolaunch D-Bus without X11 $DISPLAY”, suggest that GNOME settings components cannot correctly initialize or communicate over D-Bus.
Recommendations:
Check PAM and GNOME Keyring Configuration:
Verify that the PAM configuration files for GDM are correctly set up, ensuring that the GNOME Keyring is appropriately integrated. Ensure the daemon control file exists and has the correct permissions.
Review GNOME and X11 Configuration:
Ensure that GNOME and X11 configurations are correct. Check for any missing or misconfigured settings in the X11 configuration files.
Update or Reinstall GNOME and Related Packages:
Ensure that all GNOME and related packages (e.g., gdm, gnome-shell, gnome-keyring) are up-to-date. Reinstalling these packages might resolve some issues if they are due to corrupted files.
Monitor and Debug Child Processes:
Use tools like strace or gdb to monitor the child processes that GDM spawns to identify where they might be failing.
Check System Resources:
Ensure that the system has enough resources (memory, CPU) to handle GNOME’s demands. Resource shortages can sometimes cause erratic behavior in session management.
The problem is caused by the touchpad (device 12).
nantke@E5-573G-ACER:~$ grep gnome-shell journalctl_10m.txt
Jun 24 12:48:52 E5-573G-ACER gnome-shell[2610]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x563fec30b600] is on because it needs an allocation.
Jun 24 12:48:52 E5-573G-ACER gnome-shell[2610]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x563fec319a90] is on because it needs an allocation.
Jun 24 12:48:52 E5-573G-ACER gnome-shell[2610]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x563fec30b600] is on because it needs an allocation.
Jun 24 12:48:52 E5-573G-ACER gnome-shell[2610]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x563fec319a90] is on because it needs an allocation.
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Accel Speed" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Natural Scrolling Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Left Handed Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Left Handed Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Tapping Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Tapping Button Mapping Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Tapping Drag Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Tapping Drag Lock Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Disable While Typing Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Send Events Mode Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Scroll Method Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Scroll Method Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Scroll Method Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Click Method Enabled" with X error 8
Jun 24 12:49:20 E5-573G-ACER gnome-shell[2610]: XIChangeProperty failed on device 12 property "libinput Middle Emulation Enabled" with X error 8
Jun 24 12:50:16 E5-573G-ACER gnome-shell[2610]: Received an X Window System error.
Jun 24 12:50:47 E5-573G-ACER systemd-coredump[4138]: Process 2610 (gnome-shell) of user 1000 dumped core.
If I stay away from the touchpad during the login session after waking up from sleep, X Window doesn’t crash. This means navigating to the login field and entering the password using only the keyboard, without getting anywhere near the touchpad.