Fedora used to have an occasional short lived freeze/lag that ended quickly but in recent months it has gotten extremely bad. My computer is pretty much unusable anymore because of it. At least once an hour and sometimes only a minute or 2 since the prior freeze, Fedora will just start freezing up on me out of no where. The mouse becomes frozen, no buttons on my keyboard do anything, I am forced to either wait a few minuets for it to hopefully stop freezing up on me or more commonly I have to turn off the computer with the physical power button and turn it back on and restart everything I lost to be able to get back to using my computer just to see the process begin all over again.
The few signs I get that aren’t so random is that when I boot up my computer, the first few ~5-20 minuets are sometimes if I get lucky occasionally freeze free but the longer I keep the computer without turning it back off the more often and longer the freezes go on for.
Another clue that makes it slightly less random is my computer LOVES to freeze up on me if I don’t touch the mouse or keyboard for 1+ minute. Most of the time if I just let it sit, i’m just asking for it to freeze up on me and forcing me to power it down to be able to use it again.
Somethings I went ahead and tested:
-I have fedora also installed on my X1 Yoga Thinkpad laptop running fedora 37. It was freezing just as often as on my desktop pc. I was never having these sorts of issues to this extreme during Fedora 36 and before on both laptop and desktop.
-I tried out an Ubuntu live on my desktop pc and opened up as many applications as I could, nothing froze.
-I tried switching to x11 thinking it was a wayland Nvidia thing, still froze just as badly just as often.
-I used to have Fedora installed on an external SSD in an SSD enclosure and I thought maybe it wasn’t communicating fast enough with the pc so I switched the ssd to inside the computer. Zero difference.
-I was using Noevauo drivers all this time so I thought it might have something to do with that, I downloaded the proprietary NVIDA drivers from RPM fusion and no change either.
It’s worth adding that:
-Pretty much all applications freeze up on me. From the Settings to the text editor to Firefox to the Software Center.
-I keep the system monitor open and what I see is some of the cores on the CPU begin to SPIKE our of nowhere when i’m NOT doing anything remotely intensive nor anything I previously wasn’t in the middle of.
-Although I used to have lags on Fedora 36 and the occasional 1 second freeze, it’s only become unbearable this past month ever since upgrading to Fedora 37 and 38.
-I sometimes get a GNOME notification stating “(Some App) Stopped Device memory is nearly full. (App) was using a lot of memory and was forced to stop.” I’ve gotten the message for Firefox, ProtonVPN and a few others as well in recent weeks. It’s a new notification that I haven’t seen before. Don’t get it too often though.
-I wonder how related but in recent months I’ve gotten the “Wait or Force Quit” box SO often on all sorts of apps it’s infuriating to use anything and happens on all sorts of software from Firefox to the Files app to the Software Center and even the settings app.
It froze again while I left the mouse alone for a few minuets to focus on my phone.
Jun 22 10:38:45 fedora avahi-daemon[1222]: Joining mDNS multicast group on inte>
Jun 22 10:38:45 fedora avahi-daemon[1222]: New relevant interface wlp3s0.IPv6 f>
Jun 22 10:38:45 fedora avahi-daemon[1222]: Registering new address record for f>
Jun 22 10:38:45 fedora NetworkManager[1220]: <info> [1687455525.9880] dhcp4 (w>
Jun 22 10:38:45 fedora avahi-daemon[1222]: Joining mDNS multicast group on inte>
Jun 22 10:38:45 fedora avahi-daemon[1222]: New relevant interface wlp3s0.IPv4 f>
Jun 22 10:38:45 fedora avahi-daemon[1222]: Registering new address record for 1>
Jun 22 10:38:45 fedora systemd-resolved[1196]: wlp3s0: Bus client set default r>
Jun 22 10:38:46 fedora NetworkManager[1220]: <warn> [1687455526.0017] dns-sd-r>
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0019] device (>
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0031] device (>
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0031] device (>
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0036] device (>
Jun 22 10:38:46 fedora kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as >
Jun 22 10:38:46 fedora org.gnome.Shell.desktop[1860]: kmsro: driver missing
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE a>
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE a>
Jun 22 10:38:46 fedora gnome-shell[1860]: Added device '/dev/dri/card0' (simple>
Jun 22 10:38:46 fedora gnome-shell[1860]: Created gbm renderer for '/dev/dri/ca>
Jun 22 10:38:46 fedora gnome-shell[1860]: Failed to initialize accelerated iGPU>
Jun 22 10:38:46 fedora gnome-shell[1860]: Created gbm renderer for '/dev/dri/ca>
Jun 22 10:38:46 fedora gnome-shell[1860]: Boot VGA GPU /dev/dri/card1 selected >
Jun 22 10:38:46 fedora gnome-shell[1860]: Obtained a high priority EGL context
lines 1-23...skipping...
Jun 22 10:38:45 fedora avahi-daemon[1222]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::550f:2375:9093:1957.
Jun 22 10:38:45 fedora avahi-daemon[1222]: New relevant interface wlp3s0.IPv6 for mDNS.
Jun 22 10:38:45 fedora avahi-daemon[1222]: Registering new address record for fe80::550f:2375:9093:1957 on wlp3s0.*.
Jun 22 10:38:45 fedora NetworkManager[1220]: <info> [1687455525.9880] dhcp4 (wlp3s0): state changed new lease, address=192.168.68.111
Jun 22 10:38:45 fedora avahi-daemon[1222]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.68.111.
Jun 22 10:38:45 fedora avahi-daemon[1222]: New relevant interface wlp3s0.IPv4 for mDNS.
Jun 22 10:38:45 fedora avahi-daemon[1222]: Registering new address record for 192.168.68.111 on wlp3s0.IPv4.
Jun 22 10:38:45 fedora systemd-resolved[1196]: wlp3s0: Bus client set default route setting: no
Jun 22 10:38:46 fedora NetworkManager[1220]: <warn> [1687455526.0017] dns-sd-resolved[c812ed66cbee911a]: send-updates SetLinkDNS@4 failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid DNS server address
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0019] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0031] device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0031] device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0036] device (wlp3s0): Activation: successful, device activated.
Jun 22 10:38:46 fedora kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 56:a6:e6:99:6a:e8
Jun 22 10:38:46 fedora org.gnome.Shell.desktop[1860]: kmsro: driver missing
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=866700
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-55 noise=9999 txrate=866700
Jun 22 10:38:46 fedora gnome-shell[1860]: Added device '/dev/dri/card0' (simpledrm) using atomic mode setting.
Jun 22 10:38:46 fedora gnome-shell[1860]: Created gbm renderer for '/dev/dri/card1'
Jun 22 10:38:46 fedora gnome-shell[1860]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
Jun 22 10:38:46 fedora gnome-shell[1860]: Created gbm renderer for '/dev/dri/card0'
Jun 22 10:38:46 fedora gnome-shell[1860]: Boot VGA GPU /dev/dri/card1 selected as primary
Jun 22 10:38:46 fedora gnome-shell[1860]: Obtained a high priority EGL context
Jun 22 10:38:46 fedora gnome-shell[1860]: Obtained a high priority EGL context
Jun 22 10:38:46 fedora gnome-shell[1860]: Failed to allocate onscreen framebuffer for /dev/dri/card0: Failed to allocate surface
Jun 22 10:38:46 fedora gnome-shell[1860]: Disabling DMA buffer screen sharing (implicit modifiers not supported)
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" label="system_u:system_r:xdm_t:>
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Successfully activated service 'org.a11y.Bus'
Jun 22 10:38:46 fedora gnome-shell[1860]: Using public X11 display :1024, (using :1025 for managed services)
Jun 22 10:38:46 fedora gnome-shell[1860]: Using Wayland display name 'wayland-0'
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=866700
Jun 22 10:38:46 fedora gnome-shell[1860]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jun 22 10:38:46 fedora gnome-shell[1860]: Will monitor session c1
Jun 22 10:38:46 fedora audit: BPF prog-id=110 op=LOAD
Jun 22 10:38:46 fedora audit: BPF prog-id=111 op=LOAD
Jun 22 10:38:46 fedora audit: BPF prog-id=112 op=LOAD
Jun 22 10:38:46 fedora systemd[1]: Starting systemd-localed.service - Locale Service...
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" label="system_u:s>
Jun 22 10:38:46 fedora systemd[1]: Started systemd-localed.service - Locale Service.
Jun 22 10:38:46 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" >
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Jun 22 10:38:46 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 22 10:38:47 fedora systemd[1822]: Started pipewire.service - PipeWire Multimedia Service.
Jun 22 10:38:47 fedora systemd[1]: Starting geoclue.service - Location Lookup Service...
Jun 22 10:38:47 fedora systemd[1822]: Started wireplumber.service - Multimedia Service Session Manager.
Jun 22 10:38:47 fedora systemd[1822]: Started pipewire-pulse.service - PipeWire PulseAudio.
Jun 22 10:38:47 fedora rtkit-daemon[1256]: Successfully made thread 1960 of process 1960 (/usr/bin/wireplumber) owned by '42' high priority at nice level -11.
Jun 22 10:38:47 fedora polkitd[1249]: Registered Authentication Agent for unix-session:c1 (system bus name :1.35 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jun 22 10:38:47 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" label="system_>
Jun 22 10:38:47 fedora rtkit-daemon[1256]: Successfully made thread 1958 of process 1958 (/usr/bin/pipewire) owned by '42' high priority at nice level -11.
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension apps-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensio>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension background-logo@fedorahosted.org already installed in /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org. /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org wi>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension launch-new-instance@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-instance@gnome-shell-extensions.gcampax.github.com. /usr/share/>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension places-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/exte>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension window-list@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/window-list@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/exte>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension appindicatorsupport@rgcjonas.gmail.com already installed in /usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com. /usr/share/gnome-shell/extensions/appindicatorsupport@rgc>
lines 1-57
Jun 22 10:38:45 fedora avahi-daemon[1222]: Joining mDNS multicast group on interface wlp3s0.IPv6 with address fe80::550f:2375:9093:1957.
Jun 22 10:38:45 fedora avahi-daemon[1222]: New relevant interface wlp3s0.IPv6 for mDNS.
Jun 22 10:38:45 fedora avahi-daemon[1222]: Registering new address record for fe80::550f:2375:9093:1957 on wlp3s0.*.
Jun 22 10:38:45 fedora NetworkManager[1220]: <info> [1687455525.9880] dhcp4 (wlp3s0): state changed new lease, address=192.168.68.111
Jun 22 10:38:45 fedora avahi-daemon[1222]: Joining mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.68.111.
Jun 22 10:38:45 fedora avahi-daemon[1222]: New relevant interface wlp3s0.IPv4 for mDNS.
Jun 22 10:38:45 fedora avahi-daemon[1222]: Registering new address record for 192.168.68.111 on wlp3s0.IPv4.
Jun 22 10:38:45 fedora systemd-resolved[1196]: wlp3s0: Bus client set default route setting: no
Jun 22 10:38:46 fedora NetworkManager[1220]: <warn> [1687455526.0017] dns-sd-resolved[c812ed66cbee911a]: send-updates SetLinkDNS@4 failed: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid DNS server address
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0019] device (wlp3s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0031] device (wlp3s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0031] device (wlp3s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 22 10:38:46 fedora NetworkManager[1220]: <info> [1687455526.0036] device (wlp3s0): Activation: successful, device activated.
Jun 22 10:38:46 fedora kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 56:a6:e6:99:6a:e8
Jun 22 10:38:46 fedora org.gnome.Shell.desktop[1860]: kmsro: driver missing
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=866700
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-55 noise=9999 txrate=866700
Jun 22 10:38:46 fedora gnome-shell[1860]: Added device '/dev/dri/card0' (simpledrm) using atomic mode setting.
Jun 22 10:38:46 fedora gnome-shell[1860]: Created gbm renderer for '/dev/dri/card1'
Jun 22 10:38:46 fedora gnome-shell[1860]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
Jun 22 10:38:46 fedora gnome-shell[1860]: Created gbm renderer for '/dev/dri/card0'
Jun 22 10:38:46 fedora gnome-shell[1860]: Boot VGA GPU /dev/dri/card1 selected as primary
Jun 22 10:38:46 fedora gnome-shell[1860]: Obtained a high priority EGL context
Jun 22 10:38:46 fedora gnome-shell[1860]: Obtained a high priority EGL context
Jun 22 10:38:46 fedora gnome-shell[1860]: Failed to allocate onscreen framebuffer for /dev/dri/card0: Failed to allocate surface
Jun 22 10:38:46 fedora gnome-shell[1860]: Disabling DMA buffer screen sharing (implicit modifiers not supported)
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" label="system_u:system_r:>
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Successfully activated service 'org.a11y.Bus'
Jun 22 10:38:46 fedora gnome-shell[1860]: Using public X11 display :1024, (using :1025 for managed services)
Jun 22 10:38:46 fedora gnome-shell[1860]: Using Wayland display name 'wayland-0'
Jun 22 10:38:46 fedora wpa_supplicant[1737]: wlp3s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-55 noise=9999 txrate=866700
Jun 22 10:38:46 fedora gnome-shell[1860]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jun 22 10:38:46 fedora gnome-shell[1860]: Will monitor session c1
Jun 22 10:38:46 fedora audit: BPF prog-id=110 op=LOAD
Jun 22 10:38:46 fedora audit: BPF prog-id=111 op=LOAD
Jun 22 10:38:46 fedora audit: BPF prog-id=112 op=LOAD
Jun 22 10:38:46 fedora systemd[1]: Starting systemd-localed.service - Locale Service...
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" label="syst>
Jun 22 10:38:46 fedora systemd[1]: Started systemd-localed.service - Locale Service.
Jun 22 10:38:46 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=42 pid=1860 comm="/usr/bin/gnome-s>
Jun 22 10:38:46 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Jun 22 10:38:46 fedora kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 22 10:38:47 fedora systemd[1822]: Started pipewire.service - PipeWire Multimedia Service.
Jun 22 10:38:47 fedora systemd[1]: Starting geoclue.service - Location Lookup Service...
Jun 22 10:38:47 fedora systemd[1822]: Started wireplumber.service - Multimedia Service Session Manager.
Jun 22 10:38:47 fedora systemd[1822]: Started pipewire-pulse.service - PipeWire PulseAudio.
Jun 22 10:38:47 fedora rtkit-daemon[1256]: Successfully made thread 1960 of process 1960 (/usr/bin/wireplumber) owned by '42' high priority at nice level -11.
Jun 22 10:38:47 fedora polkitd[1249]: Registered Authentication Agent for unix-session:c1 (system bus name :1.35 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jun 22 10:38:47 fedora /usr/libexec/gdm-wayland-session[1849]: dbus-daemon[1849]: [session uid=42 pid=1849] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=42 pid=1860 comm="/usr/bin/gnome-shell" label="s>
Jun 22 10:38:47 fedora rtkit-daemon[1256]: Successfully made thread 1958 of process 1958 (/usr/bin/pipewire) owned by '42' high priority at nice level -11.
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension apps-menu@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/apps-menu@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/ex>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension background-logo@fedorahosted.org already installed in /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org. /usr/share/gnome-shell/extensions/background-logo@fedorahosted.>
Jun 22 10:38:47 fedora gnome-shell[1860]: Extension launch-new-instance@gnome-shell-extensions.gcampax.github.com already installed in /usr/share/gnome-shell/extensions/launch-new-instance@gnome-shell-extensions.gcampax.github.com. /usr/>
lines 1-54
The one above is from a ~5 minute long freeze. This one below is for a few seconds 5 minuets after the one pasted above occured: (the slow mode prevented me from adding sooner)
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: start operati>
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with r>
Jun 22 10:54:37 fedora systemd[2425]: Failed to start tracker-miner-fs-3.servic>
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 36.8>
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled res>
Jun 22 10:54:37 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Trac>
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 36.8>
Jun 22 10:54:37 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tra>
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: start operati>
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with r>
Jun 22 10:55:23 fedora systemd[2425]: Failed to start tracker-miner-fs-3.servic>
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 27.9>
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled res>
Jun 22 10:55:23 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Trac>
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 27.9>
Jun 22 10:55:23 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tra>
Jun 22 10:55:56 fedora PackageKit[12894]: daemon quit
Jun 22 10:55:56 fedora systemd[1]: packagekit.service: Deactivated successfully.
Jun 22 10:55:56 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Jun 22 10:55:56 fedora systemd[1]: packagekit.service: Consumed 1.235s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: start operati>
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with r>
Jun 22 10:56:08 fedora systemd[2425]: Failed to start tracker-miner-fs-3.servic>
lines 1-23...skipping...
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:54:37 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 36.838s CPU time.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 5.
Jun 22 10:54:37 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 36.838s CPU time.
Jun 22 10:54:37 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:55:23 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 27.990s CPU time.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 6.
Jun 22 10:55:23 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 27.990s CPU time.
Jun 22 10:55:23 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:55:56 fedora PackageKit[12894]: daemon quit
Jun 22 10:55:56 fedora systemd[1]: packagekit.service: Deactivated successfully.
Jun 22 10:55:56 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 10:55:56 fedora systemd[1]: packagekit.service: Consumed 1.235s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:56:08 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 2.975s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 7.
Jun 22 10:56:08 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 2.975s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:56:54 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 5.987s CPU time.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 8.
Jun 22 10:56:54 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 5.987s CPU time.
Jun 22 10:56:54 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
lines 1-57
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:54:37 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 36.838s CPU time.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 5.
Jun 22 10:54:37 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:54:37 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 36.838s CPU time.
Jun 22 10:54:37 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:55:23 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 27.990s CPU time.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 6.
Jun 22 10:55:23 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:55:23 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 27.990s CPU time.
Jun 22 10:55:23 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:55:56 fedora PackageKit[12894]: daemon quit
Jun 22 10:55:56 fedora systemd[1]: packagekit.service: Deactivated successfully.
Jun 22 10:55:56 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 22 10:55:56 fedora systemd[1]: packagekit.service: Consumed 1.235s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:56:08 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 2.975s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 7.
Jun 22 10:56:08 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:08 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 2.975s CPU time.
Jun 22 10:56:08 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 10:56:54 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 5.987s CPU time.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 8.
Jun 22 10:56:54 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 10:56:54 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 5.987s CPU time.
Jun 22 10:56:54 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 10:57:35 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
When posting journctl lines, please include complete lines – yours are cut off as indicated by the trailing >. If you can’t just cut and paste from a very wide terminal window, you can redirect the output to a file and paste relevant lines inot your post. In particular, it would have been helpful to see the rest of:
tracker-miner-fs-3.service: Failed with r>
Tracker-miner is problematic (see dnf info tracker for description). Some use cases that involve creating and then moving away large volumes of data may overload tracker, causing symptoms similar to yours. You can see tracker processes using a lot of CPU and memory with one of the many process monitoring tools.
I’m not freezing this second but I do see something related to tracker miner still showing if that’s of help. And if i’m understanding correctly, opening the terminal in full window mode before typing in a command makes a difference for copy and pasting?
Jun 22 14:07:04 fedora systemd[2425]: tracker-miner-fs-3.service: start operation timed out. Terminating.
Jun 22 14:07:05 fedora systemd[2425]: tracker-miner-fs-3.service: Failed with result 'timeout'.
Jun 22 14:07:05 fedora systemd[2425]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 14:07:05 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 34.599s CPU time.
Jun 22 14:07:05 fedora systemd[2425]: tracker-miner-fs-3.service: Scheduled restart job, restart counter is at 251.
Jun 22 14:07:05 fedora systemd[2425]: Stopped tracker-miner-fs-3.service - Tracker file system data miner.
Jun 22 14:07:05 fedora systemd[2425]: tracker-miner-fs-3.service: Consumed 34.599s CPU time.
Jun 22 14:07:05 fedora systemd[2425]: Starting tracker-miner-fs-3.service - Tracker file system data miner...
Jun 22 14:07:22 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:25 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:25 fedora org.ksnip.ksnip.desktop[41551]: Critical: Invalid reply from DBus: Screenshot is not allowed
Jun 22 14:07:25 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:26 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:28 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
Jun 22 14:07:29 fedora gnome-shell[2637]: (../clutter/clutter/clutter-frame-clock.c:384):clutter_frame_clock_notify_presented: code should not be reached
See if this can give you some insight of what could be happening:
journalctl -b 0 -p 3
-b 0 is the logs since last boot, and -p 3 is to only show the logs priority 3 or less (error, critical, alert) stuff.
For the computer to freeze like that, it is likely a graphic card issue, or high cpu, memory or disk latencies. The best is to start looking for errors before looking into saturations.
Also, let’s start collecting metrics as well. Let’s setup sar:
# install sysstat
dnf install -y sysstat
# make it collect metrics every min instead of every 10min
mkdir /etc/systemd/system/sysstat-collect.timer.d
cat > /etc/systemd/system/sysstat-collect.timer.d/override.conf <<EOF
[Unit]
Description=Run system activity accounting tool every 1 minute
[Timer]
OnCalendar=
OnCalendar=*:00/1
EOF
# make sar collect all metrics
sed -i -e 's/S DISK/S ALL/' /etc/sysconfig/sysstat
# enable it
systemctl enable --now sysstat.service
systemctl enable --now sysstat-collect.timer
systemctl enable --now sysstat-summary.timer
So when the freezes happens again, we can record saturation numbers.
Searching with clutter_frame_clock_notify_presented: code should not be reached leads to GNOME Mutter Issue 2489 and Ubuntu Mutter Bug 1967707 appears to a Wayland bug that is triggered after something else glitches, so likely a symptom, not cause.
Unlikely its the cause here, but also make sure a Gnome Shell extension is not the culprit: test after disabling all extensions.
To eliminate tracker as the actual cause, see whether the issue reproduces after disabling tracker. The instructions are for Ubuntu, but apply to Gnome Shell in general, and this can be undone.
To eliminate any user configuration of being at stake, temporarily create a new account then test whether it also happens when logged in as that new user (likely yes, but all these tests help narrowing down the issue).
I would strongly expect faulty hardware, or hardware that is starting to fail, to be causing such issue, but you see this on two computers, so that possibility is very unlikely.
I had a very irritating freezes and lags on Latitude 7430 on Fedora 37, and what helped me is blacklisting a module intel_rapl_msr.
You may give it a try with no changes to your system with rmmod intel_rapl_msr
In case it helps just create a file /etc/modprobe.d/intel_rapl_msr-blacklist.conf with following contents:
blacklist intel_rapl_msr
90%+ of the time after it freezes I need to turn it back off and on again so getting these logs took a really long time but here’s what showed up after a 30 second freeze using journalctl -b 0 -p 3
Jun 28 18:08:25 fedora kernel: x86/cpu: SGX disabled by BIOS.
Jun 28 18:09:13 fedora (sd-execu[953]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1.
Jun 28 18:09:14 fedora bluetoothd[1230]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jun 28 18:09:14 fedora bluetoothd[1230]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jun 28 18:09:14 fedora bluetoothd[1230]: src/plugin.c:plugin_init() Failed to init bap plugin
Jun 28 18:09:14 fedora bluetoothd[1230]: Failed to set mode: Failed (0x03)
Jun 28 18:09:15 fedora (sd-execu[1493]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 1.
Jun 28 18:09:15 fedora kernel:
Jun 28 18:09:16 fedora /usr/bin/nvidia-powerd[1253]: Allocate client failed 106
Jun 28 18:09:16 fedora /usr/bin/nvidia-powerd[1253]: Failed to initialize RM Client
Jun 28 18:09:16 fedora systemd[1]: Failed to start nvidia-powerd.service - nvidia-powerd service.
Jun 28 18:09:18 fedora abrt-notification[1826]: [🡕] System encountered a non-fatal error in ??()
Jun 28 18:10:39 fedora dbus-broker-launch[8343]: Ignoring duplicate name 'org.gnome.evince.Daemon' in service file '/usr/share//dbus-1/services/org.gnome.evince.Daemon.service'
Jun 28 18:11:04 fedora gdm-password][8893]: gkr-pam: unable to locate daemon control file
Jun 28 18:11:04 fedora dbus-broker-launch[8976]: Ignoring duplicate name 'org.gnome.evince.Daemon' in service file '/usr/share//dbus-1/services/org.gnome.evince.Daemon.service'
Jun 28 18:11:04 fedora systemd[8913]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-9121.scope - Application launched by gnome-session-binary.
Jun 28 18:11:58 fedora systemd[8913]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 28 18:12:43 fedora systemd[8913]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 28 18:13:29 fedora systemd[8913]: Failed to start tracker-miner-fs-3.service - Tracker file system data miner.
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171991 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171992 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171993 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171994 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171995 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171996 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171997 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171998 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #171999 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172000 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172001 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172002 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172003 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172004 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172005 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172006 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172007 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172008 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172009 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172010 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172011 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172012 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172013 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172014 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172015 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172016 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172017 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172018 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172019 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172020 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172021 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172022 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172023 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172024 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172025 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172026 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172027 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172028 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172029 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172030 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172031 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172032 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172033 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172034 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172035 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:02 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172036 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172037 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172038 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172039 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172040 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172041 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172042 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172043 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172044 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172045 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172046 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172047 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172048 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172049 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172050 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172051 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172052 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172053 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172054 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172055 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172056 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172057 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172058 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172059 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172060 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172061 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172062 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172063 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172064 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172065 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172066 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172067 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172068 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172069 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172070 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172071 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172072 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172073 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172074 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172075 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172076 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172077 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Jun 28 18:14:03 fedora nm-openvpn[10873]: Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #172078 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
Also for installing that sysstat thing in your other comment, what exactly do I type into the terminal as it’s all a little bit too confusing for me. Is this one giant command?
`cat > /etc/systemd/system/sysstat-collect.timer.d/override.conf <<EOF
[Unit]
Description=Run system activity accounting tool every 1 minute
Hmm, there is no error there that indicates nothing that may cause those freezes.
Next time, if you need to reboot, you can run the command like this to give you the errors since the previous boot: journalctl -b -1 -p 3.
The script I posted above setting up sysstat, you can copy and paste it into a file, e.g., setup-syssat.sh, and then run it sudo bash setup-sysstat.sh. It will setup monitoring.
Also, I see you have two hard drive. One SSD and one spinning disk. Your partitions /home and / are greater than what you have in the SSD. How are they mounted? Are they using the WD hard driver? Couldyou please post that information with these two commands:
NAME HCTL TYPE VENDOR MODEL REV SERIAL TRAN
sda 4:0:0:0 disk ATA WDC WD10EZEX-22MFCA0 1A01 WD-WCC6Y5ZVZSDL sata
My linux is running on the SSD one, the WD hard drive is just for extra storage space with 2 partitions with one being for Windows and the other for Linux.
I did both disabling all Gnome Shell extensions and creating a new Fedora user account but no difference to the amount or duration of the freezes. As for disabling the tracker, the link you gave me gives two ways to disable it. Which one is the safe and correct one?
When it freezes, record the exact time period it happens and when it resolves (or not). Let’s assume it happens around 13:11. Then, run the following commands specifying a few minutes before til a few minutes after it started.
# pressure
sar -s '13:08' -e '13:13' -q ALL
# paging utilization
sar -s '13:08' -e '13:13' -B
# memory utilization
sar -s '13:08' -e '13:13' -r
# disk utilization
sar -s '13:08' -e '13:13' -d
# CPU utilization
sar -s '13:08' -e '13:13' -P ALL
# temperature
sar -s '13:08' -e '13:13' -m TEMP
So you are running linux on the SSD device. That’s good.
Also, list your systemd timers and see if any of those timers coincide with your freezes:
Hi guys, I just want to provide an update and state that I was able to stop these specific types of freezes by changing my Firefox Theme from one of the custom ones you could download from the theme store to one of the default black one’s that came preinstalled. I have no idea why the theming I use on Firefox is capable of freezing my entire Linux distribution but every time I disable it, the worst types of freezes completely stop. I do enjoy using those themes though so I do wonder what’s preventing me from using them.