Disabling the keyring stuff did not change the fact, that freezes occure on login. But there are maybe less? I won’t do a statistical analysis but these frezzes are very infrequent…
I have another theory: https://gitlab.freedesktop.org/drm/amd/-/issues/3092
Maybe on login the power consumption of the graphic card spikes. Does somebody know if this is possible? I use corectrl and i can’t limit the power usage there anymore.
This two bugs go hand in hand and i have freezes in games as well. so maybe this would be the fix for me?
I currently don’t have the time or patience to analyse this anoying bug further. But if someone has further things to test, i am happy to try.
I don’t want to speak too soon, but looks like since the 6.7.2 kernel it didn’t freeze anymore. I just didn’t turn on the system too many times the past week, but I never had to restart since that update.
I’m having this issue as well, anyone figured out why this is happening?
[christopher67@EndeavourOS ~]$ journalctl -f
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:21:36 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:21:37 EndeavourOS systemd[1306]: Started Application launched by gnome-shell.
Mar 05 11:21:37 EndeavourOS systemd[1306]: Started dbus-:1.2-org.xfce.Xfconf@1.service.
Mar 05 11:21:37 EndeavourOS systemd[1306]: Started VTE child process 6159 launched by xfce4-terminal process 6145.
Mar 05 11:22:05 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:05 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:09 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:09 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:16 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:16 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:35 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:22:35 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:23:12 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:23:12 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:23:12 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:23:12 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:23:17 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:23:17 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:23:24 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:23:24 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:23:24 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:23:24 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:23:48 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:23:48 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:23:48 EndeavourOS gnome-shell[1403]: invalid (NULL) pointer instance
Mar 05 11:23:48 EndeavourOS gnome-shell[1403]: g_signal_handler_disconnect: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Mar 05 11:24:12 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:24:12 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:24:18 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:24:18 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:25:20 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
Mar 05 11:25:20 EndeavourOS rtkit-daemon[1187]: Supervising 11 threads of 8 processes of 1 users.
My journal didn’t have these, also post a full journal of a failed login boot. You posted journal -f which is a live journal, not a log of failed boot.
journalctl -b -0 # last boot
journalctl -b -1 # boot before last
journalctl -b -2 # and two boot before last
Freezing stopped for me, after a few updates. I forgot to close the thread. One thing that helped a bit is disabling some autostart items.
Also try to disable extensions, see if it stops happening without extensions.
[christopher67@EndeavourOS ~]$ journalctl -b -0
Mar 05 14:44:49 EndeavourOS kernel: Linux version 6.7.8-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Sun, 03 Mar 2024 00:30:36 +0000
Mar 05 14:44:49 EndeavourOS kernel: Command line: initrd=\c5a4fe9c172342d7a4f39c28b8c9b0f5\6.7.8-arch1-1\initrd nvme_load=YES nowatchdog rw root=UUID=2d24f16b-46d5-41d8-859d-c1ce6690daba resume=UUID=690ec814-cf6a-49b1-ad93-05b20334418e systemd>
Mar 05 14:44:49 EndeavourOS kernel: BIOS-provided physical RAM map:
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000393cbfff] usable
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393cc000-0x00000000393ccfff] ACPI NVS
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393cd000-0x00000000393effff] usable
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393f0000-0x00000000393f0fff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393f1000-0x000000003d1f3fff] usable
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000003d1f4000-0x000000003e1f3fff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e1f4000-0x000000003e323fff] ACPI data
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e324000-0x000000003e423fff] ACPI NVS
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e424000-0x000000003effefff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000003efff000-0x000000003effffff] usable
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x000000003f000000-0x000000003fffffff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fc000000-0x00000000fc00ffff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 05 14:44:49 EndeavourOS kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008bdffffff] usable
Mar 05 14:44:49 EndeavourOS kernel: NX (Execute Disable) protection: active
Mar 05 14:44:49 EndeavourOS kernel: APIC: Static calls initialized
Mar 05 14:44:49 EndeavourOS kernel: e820: update [mem 0x359e9018-0x35a06057] usable ==> usable
Mar 05 14:44:49 EndeavourOS kernel: e820: update [mem 0x359e9018-0x35a06057] usable ==> usable
Mar 05 14:44:49 EndeavourOS kernel: e820: update [mem 0x35baa018-0x35bb9057] usable ==> usable
Mar 05 14:44:49 EndeavourOS kernel: e820: update [mem 0x35baa018-0x35bb9057] usable ==> usable
Mar 05 14:44:49 EndeavourOS kernel: extended physical RAM map:
Mar 05 14:44:49 EndeavourOS kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 05 14:44:49 EndeavourOS kernel: reserve setup_data: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 05 14:44:49 EndeavourOS kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] usable
Mar 05 14:44:49 EndeavourOS kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 14:44:49 EndeavourOS kernel: reserve setup_data: [mem 0x0000000000100000-0x00000000359e9017] usable
Mar 05 14:44:49 EndeavourOS kernel: reserve setup_data: [mem 0x00000000359e9018-0x0000000035a06057] usable
lines 1-38
[christopher67@EndeavourOS ~]$ journalctl -b -1
Mar 05 11:00:22 EndeavourOS kernel: microcode: updated early: 0xe2 -> 0xf8, date = 2023-02-23
Mar 05 11:00:22 EndeavourOS kernel: Linux version 6.6.20-1-lts (linux-lts@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Sun, 03 Mar 2024 07:25:31 +0000
Mar 05 11:00:22 EndeavourOS kernel: Command line: initrd=\c5a4fe9c172342d7a4f39c28b8c9b0f5\6.6.20-1-lts\initrd nvme_load=YES nowatchdog rw root=UUID=2d24f16b-46d5-41d8-859d-c1ce6690daba resume=UUID=690ec814-cf6a-49b1-ad93-05b20334418e systemd.>
Mar 05 11:00:22 EndeavourOS kernel: BIOS-provided physical RAM map:
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000393cbfff] usable
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393cc000-0x00000000393ccfff] ACPI NVS
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393cd000-0x00000000393effff] usable
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393f0000-0x00000000393f0fff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393f1000-0x000000003d1f3fff] usable
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000003d1f4000-0x000000003e1f3fff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e1f4000-0x000000003e323fff] ACPI data
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e324000-0x000000003e423fff] ACPI NVS
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e424000-0x000000003effefff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000003efff000-0x000000003effffff] usable
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x000000003f000000-0x000000003fffffff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fc000000-0x00000000fc00ffff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 05 11:00:22 EndeavourOS kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008bdffffff] usable
Mar 05 11:00:22 EndeavourOS kernel: NX (Execute Disable) protection: active
Mar 05 11:00:22 EndeavourOS kernel: APIC: Static calls initialized
Mar 05 11:00:22 EndeavourOS kernel: e820: update [mem 0x359e9018-0x35a06057] usable ==> usable
Mar 05 11:00:22 EndeavourOS kernel: e820: update [mem 0x359e9018-0x35a06057] usable ==> usable
Mar 05 11:00:22 EndeavourOS kernel: e820: update [mem 0x35baa018-0x35bb9057] usable ==> usable
Mar 05 11:00:22 EndeavourOS kernel: e820: update [mem 0x35baa018-0x35bb9057] usable ==> usable
Mar 05 11:00:22 EndeavourOS kernel: extended physical RAM map:
Mar 05 11:00:22 EndeavourOS kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 05 11:00:22 EndeavourOS kernel: reserve setup_data: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 05 11:00:22 EndeavourOS kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] usable
Mar 05 11:00:22 EndeavourOS kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 11:00:22 EndeavourOS kernel: reserve setup_data: [mem 0x0000000000100000-0x00000000359e9017] usable
[christopher67@EndeavourOS ~]$ journalctl -b -2
Mar 05 10:59:29 EndeavourOS kernel: Linux version 6.7.8-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20230801, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Sun, 03 Mar 2024 00:30:36 +0000
Mar 05 10:59:29 EndeavourOS kernel: Command line: initrd=\c5a4fe9c172342d7a4f39c28b8c9b0f5\6.7.8-arch1-1\initrd nvme_load=YES nowatchdog rw root=UUID=2d24f16b-46d5-41d8-859d-c1ce6690daba resume=UUID=690ec814-cf6a-49b1-ad93-05b20334418e systemd>
Mar 05 10:59:29 EndeavourOS kernel: BIOS-provided physical RAM map:
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000393cbfff] usable
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393cc000-0x00000000393ccfff] ACPI NVS
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393cd000-0x00000000393effff] usable
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393f0000-0x00000000393f0fff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000393f1000-0x000000003d1f3fff] usable
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000003d1f4000-0x000000003e1f3fff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e1f4000-0x000000003e323fff] ACPI data
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e324000-0x000000003e423fff] ACPI NVS
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000003e424000-0x000000003effefff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000003efff000-0x000000003effffff] usable
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x000000003f000000-0x000000003fffffff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fc000000-0x00000000fc00ffff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 05 10:59:29 EndeavourOS kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008bdffffff] usable
Mar 05 10:59:29 EndeavourOS kernel: NX (Execute Disable) protection: active
Mar 05 10:59:29 EndeavourOS kernel: APIC: Static calls initialized
Mar 05 10:59:29 EndeavourOS kernel: e820: update [mem 0x359e9018-0x35a06057] usable ==> usable
Mar 05 10:59:29 EndeavourOS kernel: e820: update [mem 0x359e9018-0x35a06057] usable ==> usable
Mar 05 10:59:29 EndeavourOS kernel: e820: update [mem 0x35baa018-0x35bb9057] usable ==> usable
Mar 05 10:59:29 EndeavourOS kernel: e820: update [mem 0x35baa018-0x35bb9057] usable ==> usable
Mar 05 10:59:29 EndeavourOS kernel: extended physical RAM map:
Mar 05 10:59:29 EndeavourOS kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009dfff] usable
Mar 05 10:59:29 EndeavourOS kernel: reserve setup_data: [mem 0x000000000009e000-0x000000000009efff] reserved
Mar 05 10:59:29 EndeavourOS kernel: reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] usable
Mar 05 10:59:29 EndeavourOS kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
Mar 05 10:59:29 EndeavourOS kernel: reserve setup_data: [mem 0x0000000000100000-0x00000000359e9017] usable
Mar 05 10:59:29 EndeavourOS kernel: reserve setup_data: [mem 0x00000000359e9018-0x0000000035a06057] usable
There was just an update, i updated and booted in with no issues.
Early this morning after the update, i had to reboot like 3 times and on my 3rd time i booted into the LTS Kernel.
It started happening again after it was good for a while. Now it fails almost every time. I just updated. There was a systemd update.
Looks like I need to turn off every autostart item, because it does the same thing without extensions too
May 23 17:40:02 csaba-mini gnome-session[1545]: gnome-session-binary[1545]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
May 23 17:40:02 csaba-mini gnome-session-binary[1545]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
May 23 17:40:26 csaba-mini gnome-session[1545]: gnome-session-binary[1545]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
May 23 17:40:26 csaba-mini gnome-session-binary[1545]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
May 23 17:40:26 csaba-mini gsd-usb-protect[1750]: Failed to get screen saver status: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code24: Timeout was reached
May 23 17:40:26 csaba-mini gsd-usb-protect[1750]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
May 23 17:40:31 csaba-mini systemd[1]: systemd-hostnamed.service: Deactivated successfully.
May 23 17:40:31 csaba-mini tailscaled[763]: open-conn-track: timeout opening (TCP 100.96.101.117:36724 => 95.216.195.133:80); no associated peer node
May 23 17:40:37 csaba-mini tailscaled[763]: open-conn-track: timeout opening (TCP 100.96.101.117:36724 => 95.216.195.133:80); no associated peer node
May 23 17:40:43 csaba-mini tailscaled[763]: open-conn-track: timeout opening (TCP 100.96.101.117:36724 => 95.216.195.133:80); no associated peer node
May 23 17:40:51 csaba-mini tailscaled[763]: open-conn-track: timeout opening (TCP 100.96.101.117:36724 => 95.216.195.133:80); no associated peer node
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Wacom.service: start operation timed out. Terminating.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Keyboard.service: start operation timed out. Terminating.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Power.service: start operation timed out. Terminating.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Color.service: start operation timed out. Terminating.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.MediaKeys.service: start operation timed out. Terminating.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'timeout'.
May 23 17:41:31 csaba-mini systemd[1423]: Failed to start GNOME Wacom tablet support service.
May 23 17:41:31 csaba-mini systemd[1423]: Reached target GNOME Wacom tablet support target.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Color.service: Failed with result 'timeout'.
May 23 17:41:31 csaba-mini systemd[1423]: Failed to start GNOME color management service.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'timeout'.
May 23 17:41:31 csaba-mini systemd[1423]: Failed to start GNOME keyboard configuration service.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'timeout'.
May 23 17:41:31 csaba-mini systemd[1423]: Failed to start GNOME keyboard shortcuts service.
May 23 17:41:31 csaba-mini systemd[1423]: org.gnome.SettingsDaemon.Power.service: Failed with result 'timeout'.
May 23 17:41:31 csaba-mini systemd[1423]: Failed to start GNOME power management service.
literaly nothing relevant just systemd packages and a gnome-remote-desktop update
update: had to roll back with timeshift, now it works again.
I came across the same issue a few days ago and noticed that it would come up if I quickly type a passphrase when prompted. So try waiting at least 10-15 seconds after the GDM has started and log in then. It should help.
I think it must be some stupid systemd optimization, it starts some stuff later than it’s needed. I noticed the waiting thing too, but doesn’t work always…
I think so.
Did you try another distro with GNOME? For example, Fedora. If so, did you encounter the same problem?
No I can’t do that now, I didn’t even have time to go through the startup applications. Does it happen to you if you update?
No, it doesn’t. I’ve had to make a short pause before entering a passphrase so that the problem wouldn’t occur. I guess that it’s a systemd-related thing.
Guys from Arch forum have also no idea what it can be. https://bbs.archlinux.org/viewtopic.php?id=292959&p=3
It remains to be seen what the upstream will bring about.
Well at least you found something, before I made the thread I searched too, didn’t find anything. I’m going to try the suggestions posted and post there too.
I still have this issue on a new endeaverOS gnome install
Noticed that just not using gdm as display managers fixes the problem, but not ideal ofc.
For some reason it stopped for me the last few weeks. I suggest you disable a few start up programs.
Hi
Same video cards (ATI HD5700T)
Same trouble : gnome hang just after login
It happens since Fedora 36 (it a happens with Fedora 37,38 and now, i’m using F39 : same)
BUT
When hanging, if i’m using ssh via network to connect to this PC ;
I do not found any error
And if I do a systemctl restart gdm
in 9 case of 10 ; login to Gnome is working fine
If I do a reboot
in 9 case fo 10 , login gnome hangs again
I do not found why since 3 years.
As I can finally log in : it says that there is no error in my configuration files
So what is it ? A service timeout ?
OK, my PC is an old AMD M3 Athon X4 Phenom with 12Gb of DDR3 and a new SATA SSD 1Tb hard drive.
So, it is not a super speed PC but he works great when Gnome lets me log in.
If you have an answer, this will be great
(Today I try to change my video card by an NVidia GT610 PCI-E : same trouble with “nouveau” driver and with NVidia driver (after black listing nouveau)
I had the same problem but can be fixed. There is a key in my keyboard that makes screen go to blank. Press it, it goes to blank, then press it again, it will be fixed. If you dont have that key, wait untill screen saver makes it blank, then shake the mouse.