Fedora 36 lock screen freeze here's the journalctl

Ask Fedora
1 
May 21 07:33:32 xch dracut[270119]: drwxr-xr-x   1 root     root            0 Mar 30 16:53 var
May 21 07:33:32 xch dracut[270119]: lrwxrwxrwx   1 root     root           11 Mar 30 16:53 var/lock -> ../run/lock
May 21 07:33:32 xch dracut[270119]: lrwxrwxrwx   1 root     root            6 Mar 30 16:53 var/run -> ../run
May 21 07:33:32 xch dracut[270119]: drwxr-xr-x   1 root     root            0 Mar 30 16:53 var/tmp
May 21 07:33:32 xch dracut[270119]: ========================================================================
May 21 07:33:32 xch dracut[270119]: *** Creating initramfs image file '/boot/initramfs-5.17.8-300.fc36.x86_64.img' done ***
May 21 07:33:34 xch systemd[1]: Started run-r1383a3c99ac7414e966897f6152edb52.service - /usr/bin/systemctl start man-db-cache-update.
May 21 07:33:34 xch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-r1383a3c99ac7414e966897f6152edb52 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi>
May 21 07:33:34 xch systemd[1]: Starting man-db-cache-update.service...
May 21 07:33:34 xch systemd[1]: Started run-r584d7cf8fe434d7ea605fc74402c23db.service - /usr/bin/systemctl start man-db-cache-update.
May 21 07:33:34 xch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-r584d7cf8fe434d7ea605fc74402c23db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi>
May 21 07:33:37 xch sudo[247855]: pam_unix(sudo:session): session closed for user root
May 21 07:33:37 xch audit[247855]: USER_END pid=247855 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_u>
May 21 07:33:37 xch audit[247855]: CRED_DISP pid=247855 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? ad>
May 21 07:33:38 xch systemd[1]: man-db-cache-update.service: Deactivated successfully.
May 21 07:33:38 xch systemd[1]: Finished man-db-cache-update.service.
May 21 07:33:38 xch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=man-db-cache-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 21 07:33:38 xch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=man-db-cache-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 21 07:33:38 xch systemd[1]: run-r1383a3c99ac7414e966897f6152edb52.service: Deactivated successfully.
May 21 07:33:38 xch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-r1383a3c99ac7414e966897f6152edb52 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termin>
May 21 07:33:38 xch systemd[1]: run-r584d7cf8fe434d7ea605fc74402c23db.service: Deactivated successfully.
May 21 07:33:38 xch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=run-r584d7cf8fe434d7ea605fc74402c23db comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termin>
May 21 07:33:42 xch systemd[1736]: vte-spawn-1e40aa93-354a-4639-a1e5-9bf805d791bd.scope: Consumed 4min 20.215s CPU time.
May 21 07:35:25 xch google-chrome.desktop[100884]: [100926:100932:0521/073525.511331:ERROR:ssl_client_socket_impl.cc(999)] handshake failed; returned -1, SSL error code 1, net_error -101
May 21 07:35:25 xch google-chrome.desktop[100884]: [100926:100932:0521/073525.511511:ERROR:ssl_client_socket_impl.cc(999)] handshake failed; returned -1, SSL error code 1, net_error -101
May 21 07:36:08 xch google-chrome.desktop[100884]: [100926:100932:0521/073608.795333:ERROR:ssl_client_socket_impl.cc(999)] handshake failed; returned -1, SSL error code 1, net_error -101
May 21 07:36:33 xch systemd[1]: Starting fwupd.service - Firmware update daemon...
May 21 07:36:33 xch systemd[1]: Starting flatpak-system-helper.service - flatpak system helper...
May 21 07:36:33 xch systemd[1]: Started flatpak-system-helper.service - flatpak system helper.
May 21 07:36:33 xch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=flatpak-system-helper comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
May 21 07:36:34 xch fwupd[281067]: 23:36:34:0829 FuPluginUefiCapsule  skipping device that failed coldplug: ESRT GUID '00000000-0000-0000-0000-000000000000' was not valid
May 21 07:36:35 xch systemd[1]: Started fwupd.service - Firmware update daemon.
May 21 07:36:35 xch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fwupd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 21 07:36:35 xch gnome-software[15858]: failed to refresh the cache: Could not activate remote peer.
May 21 07:36:38 xch gnome-software[15858]: not GsPlugin error pk-control-error-quark:0: Could not activate remote peer.
May 21 07:36:40 xch systemd[1]: fwupd.service: Deactivated successfully.
May 21 07:36:40 xch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fwupd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-- Boot 1bd4aefae3344e8abfdc079fc99a7e40 --
May 21 23:49:13 xch kernel: Linux version 5.17.8-300.fc36.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1), GNU ld version 2.37-27.fc36) #1 SMP PREEMPT Mon May 16 01:00:37 UTC 2022
May 21 23:49:13 xch kernel: Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-5.17.8-300.fc36.x86_64 root=UUID=0a0aae80-c25b-4725-90e6-3ec317827ccd ro rootflags=subvol=root rd.luks.uuid=luks-c056eaff-08c7-48ef-b7fc-a662c4a24860 rhgb quiet
May 21 23:49:13 xch kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 21 23:49:13 xch kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 21 23:49:13 xch kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 21 23:49:13 xch kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 21 23:49:13 xch kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.

I don’t know why 07:33:XX then become 23:49:XX

how do I fix this, I don’t even understand the logs

2

That kind of time change in the logs, combined with the content for the very few included entries after the change could easily be indicative of a power loss and restart.

You did not include nearly enough data over a long enough period around the time switch (both before and after) to see what actually may have happened.

This line -- Boot 1bd4aefae3344e8abfdc079fc99a7e40 -- clearly seems to indicate a boot as the cause of the gap in times.

1 Like
3

what can I do to fix this? the timing is actually weird as 06:00:XX switch to 23:00:XX to 15:00:00

logs too long

4

As I suspected the time switch occurs during boot and shutdown.
This is one clue as to why and should be fixed. It is always recommended that the system RTC in bios be set to UTC since the system time depends upon that and the time zone setting to properly maintain local time with ntp.

May 21 15:52:16 xch systemd[1]: RTC configured in localtime, applying delta of 480 minutes to system time.

That accounts for the switch from 23:52 to 15:52 time. It also probably accounts for the initial switch from 0600 to 2200 at boot time since in each case it is setting the clock back by 8 hours without changing the date.

1 Like