Hardware:
HP ProDesk 400 G2 MINI - i3-6100T - 8GB - HD Graphics 530 - Lexar SSD NQ100 240GB
Fresh install of 9.3, then an upgrade within weeks to 9.4. Started having issues with unresponsive console w/ no wake-ups from mice or keys. Cockpit sessions are touchy sometimes, but generally stay connected once established. All of these problems have been going since the install, and have persisted for the last several weeks.
Seemed like there was an issue with sleep/hibernate/hybrid by not following system or tweak settings, so I disabled all the triggers using sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.target - which seemed to work for a few hours, but later failed.
Rebooted to BIOS setup and removed any/every power saving or OS power controllable setting, assuming hardware would not respond to any commands. Bad assumption.
Noticed that the tuned service had failed to start (previously set to ‘balanced performance’), so restarted it… only to loose console access soon after. Rebooted again and disabled tuned from running, via cockpit services. No effect, after another reboot.
I wish I could post a log, but that will be impossible. Every reboot clears any previous logs, and shows nothing but the current boot log of toughly the last few seconds of events during boot.
I should note that I also have another HP mini - an EliteDesk 705 G3 - AMD PRO A10-8770E R7 w/8GB - running Fedora Workstation. It had similar power issues during a brief period when there were several updates from versions 39 to 40, but it seems to have settled down now after using the same systemctl command above.
More of the same issues, but this time it does not appear to be a time-out issue related to either sleep or suspend. I was actively working on the desktop and the screen blanked. An update done today on 4 packages was initiated by me through Cockpit about 10 minutes before. The notification only detailed that 2 services needed restarting - essentially, Cockpit itself - and that was completed with no issues.
Immediately after finishing the service restarts, I logged into the desktop to use the browser, and within 5 minutes it was gone. It had been running - with me logged in - for at least a full day.
I went back to the Cockpit session on another machine, and before rebooting, checked the logs. There were NO error or above logs for the past 24 hours, so below is what was showing as a 5 minute window into the info and above logs after losing the console…
July 14, 2024
2:42 PM
INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
gnome-shell
3Occurrences
2:42 PM
Started PackageKit Daemon.
systemd
2:42 PM
Started Time & Date Service.
systemd
2:42 PM
Starting Time & Date Service...
systemd
2:42 PM
Starting PackageKit Daemon...
systemd
2:41 PM
systemd-timedated.service: Deactivated successfully.
systemd
2:41 PM
INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
gnome-shell
2:41 PM
Started Time & Date Service.
systemd
2:41 PM
Starting Time & Date Service...
systemd
2:40 PM
systemd-timedated.service: Deactivated successfully.
systemd
2:40 PM
INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
gnome-shell
2:40 PM
Started Time & Date Service.
systemd
2:40 PM
Starting Time & Date Service...
systemd
2:40 PM
Successfully made thread 165297 of process 165145 (/usr/lib64/firefox/firefox) owned by '1000' RT at priority 10.
rtkit-daemon
2:40 PM
(t=1.55271) [GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection.
gnome-shell
2:40 PM
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: vaapitest: ERROR (t=1.55268) |[1][GFX1-]: vaapitest: VA-API test failed: failed to initialise VAAPI connection.
gnome-shell
2:40 PM
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: vaapitest: ERROR (t=1.55268) [GFX1-]: vaapitest: ERROR
gnome-shell
2:40 PM
Started Application launched by gnome-shell.
systemd
2:39 PM
systemd-timedated.service: Deactivated successfully.
systemd
2:39 PM
INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
gnome-shell
2:39 PM
Started Time & Date Service.
systemd
2:39 PM
Starting Time & Date Service...
systemd
2:38 PM
systemd-timedated.service: Deactivated successfully.
systemd
2:38 PM
INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
gnome-shell
2:38 PM
Started Time & Date Service.
systemd
2:38 PM
Starting Time & Date Service...
systemd
2:37 PM
systemd-timedated.service: Deactivated successfully.
systemd
2:37 PM
INFO AppSettingsModel.js::init/this._settingsC(54) Prefrences/Settings value changed
gnome-shell
2:37 PM
Started Time & Date Service.