Changing profile from the webview client does not complete, restarting the webview client or gtk client results in no connection to daemon

This does not happen in v1.2.x - can't delete the issue, will close.

Will reboot to load v 1.2.x, also will clear the display and sleep time values in the webview client and see if that resolves the issue. Update to this ticket pending.

Describe the bug A clear and concise description of what the bug is. Changing profile from the webview client does not complete, restarting the webview client or gtk client results in no connection to daemon

To Reproduce Steps to reproduce the behavior. Changing profile from the webview client does not complete, restarting the webview client or gtk client results in no connection to daemon

System Info:

OS
Kernel Version
power-options version
The output of power-options-mgr print-system-info
The full/recent logs of the power-options.service systemd daemon. Arch Linux hostname 6.11.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Oct 2024 20:11:06 +0000 x86_64 GNU/Linux power-options version 1.1.x - just updated, will reboot and see if I can reprodiuce

[username@hostname ~]$ journalctl -u power-options.service -b Journal file /var/log/journal/59aa3370469c4fc4bb2c16c6f461fd07/system@00061dc6aa62eb33-b4d31ef7389d3cbb.journal~ is truncated, ignoring file. Oct 12 08:31:47 hostname systemd[1]: Started power-options daemon. Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(19) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(21) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(32) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(23) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(26) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(25) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(22) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(24) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(30) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 12 08:31:47 hostname power-daemon-mgr[1758]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 12 08:31:47 hostname power-daemon-mgr[1758]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 12 08:31:47 hostname power-daemon-mgr[1758]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 12 08:31:47 hostname power-daemon-mgr[1758]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(24) Oct 12 08:31:47 hostname power-daemon-mgr[1758]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 12 08:31:47 hostname power-daemon-mgr[1794]: xset: unable to open display ":0" Oct 12 08:31:47 hostname power-daemon-mgr[1758]: ERROR ==> [power_daemon::profile]: Attempted to set suspend time when xautolock is not installed Oct 13 12:17:31 hostname systemd[1]: Stopping power-options daemon... Oct 13 12:17:31 hostname systemd[1]: power-options.service: Deactivated successfully. Oct 13 12:17:31 hostname systemd[1]: Stopped power-options daemon. Oct 13 12:17:31 hostname systemd[1]: Started power-options daemon. Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(20) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(23) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(26) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(21) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(31) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(24) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(28) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(22) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(25) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 13 12:17:31 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 13 12:17:31 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 12:17:31 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 12:17:31 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(20) Oct 13 12:17:31 hostname power-daemon-mgr[157866]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 13 12:17:31 hostname power-daemon-mgr[157903]: Authorization required, but no authorization protocol specified Oct 13 12:17:31 hostname power-daemon-mgr[157903]: xset: unable to open display ":0" Oct 13 12:17:31 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Attempted to set suspend time when xautolock is not installed Oct 13 15:21:06 hostname power-daemon-mgr[157866]: INFO ==> [D-BUS]: get_profiles_info Oct 13 15:21:06 hostname power-daemon-mgr[157866]: INFO ==> [D-BUS]: get_profile_override Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [D-BUS]: set_profile_override: Balanced Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying profile: Balanced Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(24) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(23) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(22) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(31) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(33) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(25) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(28) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(30) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 13 15:21:28 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 13 15:21:28 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 15:21:28 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 15:21:28 hostname power-daemon-mgr[157866]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 13 15:21:28 hostname power-daemon-mgr[157866]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 13 15:21:28 hostname power-daemon-mgr[209409]: Authorization required, but no authorization protocol specified Oct 13 15:21:28 hostname power-daemon-mgr[209409]: xset: unable to open display ":0" Oct 13 15:21:28 hostname power-daemon-mgr[157866]: ERROR ==> [power_daemon::profile]: Attempted to set suspend time when xautolock is not installed Oct 13 15:21:54 hostname power-daemon-mgr[157866]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 13 15:21:54 hostname power-daemon-mgr[157866]: Could not read file: Os { code: 110, kind: TimedOut, message: "Connection timed out" } Oct 13 15:21:54 hostname power-daemon-mgr[157866]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Oct 13 15:23:13 hostname power-daemon-mgr[157866]: INFO ==> [D-BUS]: get_profiles_info Oct 13 15:23:13 hostname power-daemon-mgr[157866]: INFO ==> [D-BUS]: get_config Oct 13 15:23:13 hostname power-daemon-mgr[157866]: INFO ==> [D-BUS]: get_profile_override Oct 13 15:23:14 hostname power-daemon-mgr[157866]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 13 15:23:14 hostname power-daemon-mgr[157866]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 13 15:23:16 hostname power-daemon-mgr[157866]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 13 15:23:16 hostname power-daemon-mgr[157866]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 13 15:24:18 hostname systemd[1]: Stopping power-options daemon... Oct 13 15:24:18 hostname systemd[1]: power-options.service: Deactivated successfully. Oct 13 15:24:18 hostname systemd[1]: Stopped power-options daemon. Oct 13 15:24:18 hostname systemd[1]: power-options.service: Consumed 22.581s CPU time, 10.3M memory peak. Oct 13 15:24:27 hostname systemd[1]: Started power-options daemon. Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(24) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(29) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(28) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(21) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(31) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(23) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(30) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(26) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 13 15:24:27 hostname power-daemon-mgr[210563]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 13 15:24:27 hostname power-daemon-mgr[210563]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(31) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 13 15:24:27 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 13 15:24:27 hostname power-daemon-mgr[210599]: Authorization required, but no authorization protocol specified Oct 13 15:24:27 hostname power-daemon-mgr[210599]: xset: unable to open display ":0" Oct 13 15:24:27 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Attempted to set suspend time when xautolock is not installed lines 31-111/111 (END)

Additional context Add any other context about the problem here.

× power-options.service - power-options daemon Loaded: loaded (/usr/lib/systemd/system/power-options.service; enabled; preset: disabled) Active: failed (Result: exit-code) since Sun 2024-10-13 15:24:27 EDT; 2s ago Duration: 66ms Invocation: fb5678797f6a4d9296b1e98239784adc Process: 210563 ExecStart=/usr/bin/power-daemon-mgr daemon (code=exited, status=101) Main PID: 210563 (code=exited, status=101) Mem peak: 6M CPU: 31ms

Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 13 15:24:27 host power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 13 15:24:27 hostname power-daemon-mgr[210563]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(31) Oct 13 15:24:27 hostname power-daemon-mgr[210563]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 13 15:24:27 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 13 15:24:27 hostname power-daemon-mgr[210599]: Authorization required, but no authorization protocol specified Oct 13 15:24:27 hostname power-daemon-mgr[210599]: xset: unable to open display ":0" Oct 13 15:24:27 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 13 15:24:27 hostname power-daemon-mgr[210563]: ERROR ==> [power_daemon::profile]: Attempted to set suspend time when xautolock is not installed

At first sight, what stands out the most are the unhandled file system timeout panics. Try to add rust backtraces to the daemon:

Edit the /usr/lib/systemd/system/power-options.service file and add a Environment=“RUST_BACKTRACE=1” line.
Run systemctl daemon-reload and systemctl restart power-options

Then send the logs again, so that the root cause of the timeouts could be found.

Does not happen in v.1.2.x. Closing.

Just occurred again. I was on the release just prior to today's, but I have not restarted the machine since upgrading after the daemon hung and I couldn't restart it.

Here's the log:

[username@hostname ]$ journalctl -u power-options.service -b Journal file /var/log/journal/59aa3370469c4fc4bb2c16c6f461fd07/system@00061dc6aa62eb33-b4d31ef7389d3cbb.journal is truncated, ignoring file. Oct 28 17:19:57 hostname systemd[1]: Started power-options daemon. Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(30) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(20) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(29) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(31) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(24) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(27) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(23) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(18) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(26) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 28 17:19:57 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 28 17:19:57 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 28 17:19:57 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 28 17:19:57 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 28 17:19:57 hostname power-daemon-mgr[1746]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 28 17:19:57 hostname power-daemon-mgr[1788]: xset: unable to open display ":0" Oct 28 17:23:07 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profiles_info Oct 28 17:23:07 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profile_override Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: set_profile_override: Performance++ Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying profile: Performance++ Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(19) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(32) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(30) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(24) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(25) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(27) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(22) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(31) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 17:48:07 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 17:48:07 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 17:48:07 hostname power-daemon-mgr[1746]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 17:48:07 hostname power-daemon-mgr[1746]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 29 17:48:07 hostname power-daemon-mgr[1746]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 17:48:07 hostname power-daemon-mgr[424590]: Authorization required, but no authorization protocol specified Oct 29 17:48:07 hostname power-daemon-mgr[424590]: xset: unable to open display ":0" Oct 29 17:48:32 hostname power-daemon-mgr[1746]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 17:48:32 hostname power-daemon-mgr[1746]: Could not read file: Os { code: 110, kind: TimedOut, message: "Connection timed out" } Oct 29 17:48:32 hostname power-daemon-mgr[1746]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Oct 29 17:49:14 hostname power-daemon-mgr[1746]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 17:49:14 hostname power-daemon-mgr[1746]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 17:49:14 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profiles_info Oct 29 17:49:14 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profile_override Oct 29 17:49:34 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profiles_info Oct 29 17:49:34 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profile_override Oct 29 17:49:34 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_config Oct 29 17:49:39 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profiles_info Oct 29 17:49:39 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profile_override Oct 29 17:49:53 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profiles_info Oct 29 17:49:53 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_config Oct 29 17:49:53 hostname power-daemon-mgr[1746]: INFO ==> [D-BUS]: get_profile_override Oct 29 17:49:54 hostname power-daemon-mgr[1746]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 17:49:54 hostname power-daemon-mgr[1746]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 17:49:54 hostname power-daemon-mgr[1746]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 17:49:54 hostname power-daemon-mgr[1746]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 17:50:22 hostname systemd[1]: Stopping power-options daemon... Oct 29 17:50:22 hostname systemd[1]: power-options.service: Deactivated successfully. Oct 29 17:50:22 hostname systemd[1]: Stopped power-options daemon. Oct 29 17:50:22 hostname systemd[1]: power-options.service: Consumed 1min 47.205s CPU time, 11.3M memory peak. Oct 29 17:50:22 hostname systemd[1]: Started power-options daemon. Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(22) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(27) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(28) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(25) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(31) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 17:50:22 hostname power-daemon-mgr[426191]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 17:50:22 hostname power-daemon-mgr[426191]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(32) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(21) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(23) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 17:50:22 hostname power-daemon-mgr[426191]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 17:50:22 hostname power-daemon-mgr[426191]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 17:50:22 hostname power-daemon-mgr[426191]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 17:50:22 hostname power-daemon-mgr[426191]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(23) Oct 29 17:50:22 hostname power-daemon-mgr[426191]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 17:50:22 hostname power-daemon-mgr[426228]: Authorization required, but no authorization protocol specified Oct 29 17:50:22 hostname power-daemon-mgr[426228]: xset: unable to open display ":0" Oct 29 17:50:22 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 17:50:22 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 29 17:55:40 hostname systemd[1]: Started power-options daemon. Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(31) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(18) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(27) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(21) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(20) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(26) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(33) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(32) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(28) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: thread 'INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(29)' panicked at Oct 29 17:55:40 hostname power-daemon-mgr[439494]: crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 17:55:40 hostname power-daemon-mgr[439494]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 17:55:40 hostname power-daemon-mgr[439494]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Oct 29 17:55:40 hostname power-daemon-mgr[439494]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 17:55:40 hostname power-daemon-mgr[439494]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 17:55:40 hostname power-daemon-mgr[439494]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 17:55:40 hostname power-daemon-mgr[439494]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 17:55:40 hostname power-daemon-mgr[439494]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(20) Oct 29 17:55:40 hostname power-daemon-mgr[439494]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 17:55:40 hostname power-daemon-mgr[439531]: Authorization required, but no authorization protocol specified Oct 29 17:55:40 hostname power-daemon-mgr[439531]: xset: unable to open display ":0" Oct 29 17:55:40 hostname rfkill[439533]: block set for type bluetooth Oct 29 17:55:40 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 17:55:40 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 29 18:01:23 hostname systemd[1]: Started power-options daemon. Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(32) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(18) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(26) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(25) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(27) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(28) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(33) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(20) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(30) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 18:01:23 hostname power-daemon-mgr[464527]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 18:01:23 hostname power-daemon-mgr[464527]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace Oct 29 18:01:23 hostname power-daemon-mgr[464527]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 18:01:23 hostname power-daemon-mgr[464527]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 18:01:23 hostname power-daemon-mgr[464527]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:01:23 hostname power-daemon-mgr[464527]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:01:23 hostname power-daemon-mgr[464527]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 29 18:01:23 hostname power-daemon-mgr[464527]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 18:01:23 hostname power-daemon-mgr[464563]: Authorization required, but no authorization protocol specified Oct 29 18:01:23 hostname power-daemon-mgr[464563]: xset: unable to open display ":0" Oct 29 18:01:23 hostname rfkill[464564]: block set for type nfc Oct 29 18:01:23 hostname rfkill[464565]: block set for type bluetooth Oct 29 18:01:23 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 18:01:23 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 29 18:13:26 hostname systemd[1]: Started power-options daemon. Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(32) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(26) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(25) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(30) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(19) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(28) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(29) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(27) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(21):10 Oct 29 18:13:26 hostname power-daemon-mgr[469742]: : Oct 29 18:13:26 hostname power-daemon-mgr[469742]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 18:13:26 hostname power-daemon-mgr[469742]: stack backtrace: Oct 29 18:13:26 hostname power-daemon-mgr[469742]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 18:13:26 hostname power-daemon-mgr[469742]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 18:13:26 hostname power-daemon-mgr[469742]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:13:26 hostname power-daemon-mgr[469742]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:13:26 hostname power-daemon-mgr[469742]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(19) Oct 29 18:13:26 hostname power-daemon-mgr[469742]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 0: rust_begin_unwind Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 1: core::panicking::panic_fmt Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 2: core::result::unwrap_failed Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 5: power_daemon::profile::GpuSettings::apply Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 6: rayon::iter::plumbing::Producer::fold_with Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 7: rayon_core::join::join_context::{{closure}} Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 8: rayon_core::registry::in_worker Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 9: rayon::iter::plumbing::bridge_producer_consumer::helper Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 10: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 11: rayon_core::registry::WorkerThread::wait_until_cold Oct 29 18:13:26 hostname power-daemon-mgr[469742]: 12: rayon_core::registry::ThreadBuilder::run Oct 29 18:13:26 hostname power-daemon-mgr[469742]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 18:13:26 hostname power-daemon-mgr[469778]: Authorization required, but no authorization protocol specified Oct 29 18:13:26 hostname power-daemon-mgr[469778]: xset: unable to open display ":0" Oct 29 18:13:26 hostname rfkill[469780]: block set for type bluetooth Oct 29 18:13:26 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 18:13:26 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 29 18:13:41 hostname systemd[1]: Started power-options daemon. Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(19) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(25) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(23) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(26) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(26) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(24) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(28) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(30) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21)thread ' Oct 29 18:13:41 hostname power-daemon-mgr[470087]: ' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 18:13:41 hostname power-daemon-mgr[470087]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 18:13:41 hostname power-daemon-mgr[470087]: stack backtrace: Oct 29 18:13:41 hostname power-daemon-mgr[470087]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 18:13:41 hostname power-daemon-mgr[470087]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 18:13:41 hostname power-daemon-mgr[470087]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:13:41 hostname power-daemon-mgr[470087]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:13:41 hostname power-daemon-mgr[470087]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 29 18:13:41 hostname power-daemon-mgr[470087]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 0: rust_begin_unwind Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 1: core::panicking::panic_fmt Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 2: core::result::unwrap_failed Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 5: power_daemon::profile::GpuSettings::apply Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 6: rayon::iter::plumbing::Producer::fold_with Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 7: rayon_core::join::join_context::{{closure}} Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 8: rayon_core::registry::in_worker Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 9: rayon::iter::plumbing::bridge_producer_consumer::helper Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 10: < Oct 29 18:13:41 hostname power-daemon-mgr[470123]: Authorization required, but no authorization protocol specified Oct 29 18:13:41 hostname power-daemon-mgr[470087]: rayon_core:: Oct 29 18:13:41 hostname power-daemon-mgr[470087]: job::StackJob<L,F,R> as rayon_core Oct 29 18:13:41 hostname power-daemon-mgr[470123]: xset: unable to open display ":0" Oct 29 18:13:41 hostname power-daemon-mgr[470087]: ::job::Job>::execute Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 11: rayon_core::registry::WorkerThread::wait_until_cold Oct 29 18:13:41 hostname power-daemon-mgr[470087]: 12: rayon_core::registry::ThreadBuilder::run Oct 29 18:13:41 hostname power-daemon-mgr[470087]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 18:13:41 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 18:13:41 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. [username@hostname ~]$

Will reboot now and see if it happens on the latest release.

Update. It does still happen on version 1.2.2. Here is the output of power-daemon-mgr print-system-info:

[user@hostname ~]$ power-daemon-mgr print-system-info SystemInfo { cpu_info: CPUInfo { driver: Amd, mode: Some( "active", ), has_epp: true, has_epb: false, has_perf_pct_scaling: false, hybrid: false, cores: [ CoreInfo { online: None, physical_core_id: 0, logical_cpu_id: 0, current_frequency: 980, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 0, logical_cpu_id: 1, current_frequency: 1454, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 1, logical_cpu_id: 2, current_frequency: 2524, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 1, logical_cpu_id: 3, current_frequency: 400, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 2, logical_cpu_id: 4, current_frequency: 899, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 2, logical_cpu_id: 5, current_frequency: 400, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 3, logical_cpu_id: 6, current_frequency: 1409, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 3, logical_cpu_id: 7, current_frequency: 2066, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 4, logical_cpu_id: 8, current_frequency: 1105, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 4, logical_cpu_id: 9, current_frequency: 400, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 5, logical_cpu_id: 10, current_frequency: 400, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 5, logical_cpu_id: 11, current_frequency: 2523, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 6, logical_cpu_id: 12, current_frequency: 926, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 6, logical_cpu_id: 13, current_frequency: 400, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 7, logical_cpu_id: 14, current_frequency: 1170, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, CoreInfo { online: Some( true, ), physical_core_id: 7, logical_cpu_id: 15, current_frequency: 2063, base_frequency: 0, total_min_frequency: 400, total_max_frequency: 5263, scaling_min_frequency: 400, scaling_max_frequency: 5263, is_performance_core: None, governor: "powersave", epp: Some( "balance_power", ), epb: None, }, ], total_min_frequency: 400, total_max_frequency: 5263, boost: Some( true, ), hwp_dynamic_boost: None, }, pci_info: PCIInfo { pci_devices: [ PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:00.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:00.2", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:01.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:01.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:01.2", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:02.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:02.2", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:02.4", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:03.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:03.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:04.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:04.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:08.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:08.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:08.2", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:08.3", }, PCIDeviceInfo { display_name: "SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller", pci_address: "0000:00:14.0", }, PCIDeviceInfo { display_name: "ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge", pci_address: "0000:00:14.3", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.2", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.3", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.4", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.5", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.6", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:00:18.7", }, PCIDeviceInfo { display_name: "PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch", pci_address: "0000:01:00.0", }, PCIDeviceInfo { display_name: "PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch", pci_address: "0000:02:00.0", }, PCIDeviceInfo { display_name: "VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 33 [Radeon RX 7600/7600 XT/7600M XT/7600S/7700S / PRO W7600]", pci_address: "0000:03:00.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:03:00.1", }, PCIDeviceInfo { display_name: "Non-Volatile memory controller: Sandisk Corp PC SN740 NVMe SSD (DRAM-less)", pci_address: "0000:04:00.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:05:00.0", }, PCIDeviceInfo { display_name: "Non-Volatile memory controller: Shenzhen Longsys Electronics Co., Ltd. Lexar NM790 NVME SSD (DRAM-less)", pci_address: "0000:06:00.0", }, PCIDeviceInfo { display_name: "VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1", pci_address: "0000:c5:00.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c5:00.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c5:00.2", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c5:00.3", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c5:00.4", }, PCIDeviceInfo { display_name: "Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor", pci_address: "0000:c5:00.5", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c5:00.6", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c6:00.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c6:00.1", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c7:00.0", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c7:00.3", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c7:00.4", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c7:00.5", }, PCIDeviceInfo { display_name: "Unknown device", pci_address: "0000:c7:00.6", }, ], aspm_info: ASPMInfo { supported_modes: Some( [ "default", "performance", "powersave", "powersupersave", ], ), }, }, usb_info: USBInfo { usb_devices: [ USBDeviceInfo { display_name: "Linux Foundation 2.0 root hub", id: "1d6b:0002", }, USBDeviceInfo { display_name: "Genesys Logic, Inc. Hub", id: "05e3:0610", }, USBDeviceInfo { display_name: "Genesys Logic, Inc. Hub", id: "05e3:0610", }, USBDeviceInfo { display_name: "Genesys Logic, Inc. Hub", id: "05e3:0610", }, USBDeviceInfo { display_name: "Framework Computer Inc LED Matrix Input Module", id: "32ac:0020", }, USBDeviceInfo { display_name: "MediaTek Inc. Wireless_Device", id: "0e8d:e616", }, USBDeviceInfo { display_name: "Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC", id: "27c6:609c", }, USBDeviceInfo { display_name: "Framework Computer Inc LED Matrix Input Module", id: "32ac:0020", }, USBDeviceInfo { display_name: "Framework Laptop 16 Keyboard Module - ANSI", id: "32ac:0012", }, USBDeviceInfo { display_name: "Linux Foundation 3.0 root hub", id: "1d6b:0003", }, USBDeviceInfo { display_name: "Genesys Logic, Inc. USB3.2 Hub", id: "05e3:0625", }, USBDeviceInfo { display_name: "Linux Foundation 2.0 root hub", id: "1d6b:0002", }, USBDeviceInfo { display_name: "Linux Foundation 3.0 root hub", id: "1d6b:0003", }, USBDeviceInfo { display_name: "Linux Foundation 2.0 root hub", id: "1d6b:0002", }, USBDeviceInfo { display_name: "Linux Foundation 3.0 root hub", id: "1d6b:0003", }, USBDeviceInfo { display_name: "Linux Foundation 2.0 root hub", id: "1d6b:0002", }, USBDeviceInfo { display_name: "Linux Foundation 3.0 root hub", id: "1d6b:0003", }, ], }, sata_info: SATAInfo { hosts: 0, }, firmware_info: FirmwareInfo { platform_profiles: Some( [ "low-power", "balanced", "performance", ], ), }, gpu_info: GpuInfo { intel_info: None, amd_info: Some( AmdGpu { dpm_perf: "low", }, ), }, rapl_info: IntelRaplInfo { rapl_missing: false, package: Some( IntelRaplInterfaceInfo { long_term: None, short_term: None, peak_power: None, }, ), core: Some( IntelRaplInterfaceInfo { long_term: None, short_term: None, peak_power: None, }, ), uncore: None, }, opt_features_info: OptionalFeaturesInfo { supports_xautolock: false, supports_xset: true, supports_xrandr: true, supports_brightnessctl: false, supports_wifi_drivers: false, supports_ifconfig: false, audio_module: SndHdaIntel, }, }

and the log output: [username@hostname ~]$ journalctl -u power-options.service -b Journal file /var/log/journal/59aa3370469c4fc4bb2c16c6f461fd07/system@00061dc6aa62eb33-b4d31ef7389d3cbb.journal~ is truncated, ignoring file. Oct 29 18:41:29 hostname systemd[1]: Started power-options daemon. Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(23) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(24) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(32) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(18) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(27) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(22) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(25) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(30) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(29) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(20) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:41:29 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:41:29 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(20) Oct 29 18:41:29 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 18:41:29 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 18:41:29 hostname power-daemon-mgr[1745]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 18:41:29 hostname rfkill[1790]: block set for type bluetooth Oct 29 18:41:29 hostname power-daemon-mgr[1788]: xset: unable to open display ":0" Oct 29 18:42:12 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profiles_info Oct 29 18:42:12 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profile_override Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: set_profile_override: Performance++ Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying profile: Performance++ Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(20) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(21) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(23) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(31) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(26) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(25) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(30) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(29) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(28) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 18:42:15 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 18:42:15 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:42:15 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:42:15 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(20) Oct 29 18:42:15 hostname power-daemon-mgr[1745]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 18:42:15 hostname power-daemon-mgr[3238]: Authorization required, but no authorization protocol specified Oct 29 18:42:15 hostname power-daemon-mgr[3238]: xset: unable to open display ":0" Oct 29 18:42:18 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profiles_info Oct 29 18:42:18 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profile_override Oct 29 18:42:18 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profiles_info Oct 29 18:42:18 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_config Oct 29 18:42:18 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profile_override Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: set_profile_override: Powersave Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(21) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(27) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(24) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(25) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(28) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(31) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(30) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(22) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(26) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 18:42:26 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 18:42:26 hostname rfkill[3292]: block set for type nfc Oct 29 18:42:26 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:42:26 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 18:42:26 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(22) Oct 29 18:42:26 hostname power-daemon-mgr[1745]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 18:42:26 hostname power-daemon-mgr[3291]: Authorization required, but no authorization protocol specified Oct 29 18:42:26 hostname power-daemon-mgr[3291]: xset: unable to open display ":0" Oct 29 18:42:27 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profiles_info Oct 29 18:42:27 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profile_override Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: set_profile_override: Performance++ Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying profile: Performance++ Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(21) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(22) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(20) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(26) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(27) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(25) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(33) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(24) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(19) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(30) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 19:37:09 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 19:37:09 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:37:09 hostname power-daemon-mgr[1745]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:37:09 hostname power-daemon-mgr[1745]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(19) Oct 29 19:37:09 hostname power-daemon-mgr[1745]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 19:37:09 hostname power-daemon-mgr[29787]: Authorization required, but no authorization protocol specified Oct 29 19:37:09 hostname power-daemon-mgr[29787]: xset: unable to open display ":0" Oct 29 19:37:34 hostname power-daemon-mgr[1745]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:37:34 hostname power-daemon-mgr[1745]: Could not read file: Os { code: 110, kind: TimedOut, message: "Connection timed out" } Oct 29 19:37:34 hostname power-daemon-mgr[1745]: stack backtrace: Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 0: rust_begin_unwind Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 1: core::panicking::panic_fmt Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 2: core::result::unwrap_failed Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 5: power_daemon::profile::GpuSettings::apply Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 6: rayon::iter::plumbing::Producer::fold_with Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 7: rayon_core::join::join_context::{{closure}} Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 8: rayon_core::registry::in_worker Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 9: rayon::iter::plumbing::bridge_producer_consumer::helper Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 10: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 11: rayon_core::registry::WorkerThread::wait_until_cold Oct 29 19:37:34 hostname power-daemon-mgr[1745]: 12: rayon_core::registry::ThreadBuilder::run Oct 29 19:37:34 hostname power-daemon-mgr[1745]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. [username@hostname ~]$

Another log with backtrace set to full. If you know how to get the service to start up without requiring a reboot I am all ears. The reload/restart does not work.

Oct 29 19:49:17 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profiles_info Oct 29 19:49:17 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_config Oct 29 19:49:17 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profile_override Oct 29 19:49:18 hostname power-daemon-mgr[1745]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:49:18 hostname power-daemon-mgr[1745]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:49:18 hostname power-daemon-mgr[1745]: stack backtrace: Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 0: rust_begin_unwind Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 1: core::panicking::panic_fmt Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 2: core::result::unwrap_failed Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 5: power_daemon::systeminfo::GpuInfo::obtain Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 6: power_daemon::systeminfo::SystemInfo::obtain Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 7: ::call::{{closure}} Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 8: zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}} Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 9: <tracing::instrument::Instrumented as core::future::future::Future>::poll Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 10: async_executor::Executor::spawn_inner::{{closure}} Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 11: async_task::raw::RawTask<F,T,S,M>::run Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 12: async_io::driver::block_on Oct 29 19:49:18 hostname power-daemon-mgr[1745]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:49:18 hostname power-daemon-mgr[1745]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:49:18 hostname power-daemon-mgr[1745]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:49:18 hostname power-daemon-mgr[1745]: stack backtrace: Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 0: rust_begin_unwind Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 1: core::panicking::panic_fmt Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 2: core::result::unwrap_failed Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 5: power_daemon::systeminfo::GpuInfo::obtain Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 6: power_daemon::systeminfo::SystemInfo::obtain Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 7: ::call::{{closure}} Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 8: zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}} Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 9: <tracing::instrument::Instrumented as core::future::future::Future>::poll Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 10: async_executor::Executor::spawn_inner::{{closure}} Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 11: async_task::raw::RawTask<F,T,S,M>::run Oct 29 19:49:18 hostname power-daemon-mgr[1745]: 12: async_io::driver::block_on Oct 29 19:49:18 hostname power-daemon-mgr[1745]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:49:59 hostname power-daemon-mgr[1745]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:49:59 hostname power-daemon-mgr[1745]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:49:59 hostname power-daemon-mgr[1745]: stack backtrace: Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 0: rust_begin_unwind Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 1: core::panicking::panic_fmt Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 2: core::result::unwrap_failed Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 5: power_daemon::systeminfo::GpuInfo::obtain Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 6: ::call::{{closure}} Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 7: zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}} Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 8: <tracing::instrument::Instrumented as core::future::future::Future>::poll Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 9: async_executor::Executor::spawn_inner::{{closure}} Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 10: async_task::raw::RawTask<F,T,S,M>::run Oct 29 19:49:59 hostname power-daemon-mgr[1745]: 11: async_io::driver::block_on Oct 29 19:49:59 hostname power-daemon-mgr[1745]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:52:03 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profiles_info Oct 29 19:52:03 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_config Oct 29 19:52:03 hostname power-daemon-mgr[1745]: INFO ==> [D-BUS]: get_profile_override Oct 29 19:52:03 hostname power-daemon-mgr[1745]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:52:03 hostname power-daemon-mgr[1745]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:52:03 hostname power-daemon-mgr[1745]: stack backtrace: Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 0: rust_begin_unwind Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 1: core::panicking::panic_fmt Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 2: core::result::unwrap_failed Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 5: power_daemon::systeminfo::GpuInfo::obtain Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 6: power_daemon::systeminfo::SystemInfo::obtain Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 7: ::call::{{closure}} Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 8: zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}} Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 9: <tracing::instrument::Instrumented as core::future::future::Future>::poll Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 10: async_executor::Executor::spawn_inner::{{closure}} Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 11: async_task::raw::RawTask<F,T,S,M>::run Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 12: async_io::driver::block_on Oct 29 19:52:03 hostname power-daemon-mgr[1745]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:52:03 hostname power-daemon-mgr[1745]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:52:03 hostname power-daemon-mgr[1745]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:52:03 hostname power-daemon-mgr[1745]: stack backtrace: Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 0: rust_begin_unwind Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 1: core::panicking::panic_fmt Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 2: core::result::unwrap_failed Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 5: power_daemon::systeminfo::GpuInfo::obtain Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 6: power_daemon::systeminfo::SystemInfo::obtain Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 7: ::call::{{closure}} Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 8: zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}} Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 9: <tracing::instrument::Instrumented as core::future::future::Future>::poll Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 10: async_executor::Executor::spawn_inner::{{closure}} Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 11: async_task::raw::RawTask<F,T,S,M>::run Oct 29 19:52:03 hostname power-daemon-mgr[1745]: 12: async_io::driver::block_on Oct 29 19:52:03 hostname power-daemon-mgr[1745]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:52:22 hostname systemd[1]: Stopping power-options daemon... Oct 29 19:52:22 hostname systemd[1]: power-options.service: Deactivated successfully. Oct 29 19:52:22 hostname systemd[1]: Stopped power-options daemon. Oct 29 19:52:22 hostname systemd[1]: power-options.service: Consumed 28.083s CPU time, 13.9M memory peak. Oct 29 19:52:33 hostname systemd[1]: Started power-options daemon. Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(31) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(18) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(29) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(28) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(26) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(25) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(24) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(22) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(23) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:52:33 hostname power-daemon-mgr[36641]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:52:33 hostname power-daemon-mgr[36641]: stack backtrace: Oct 29 19:52:33 hostname power-daemon-mgr[36641]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 19:52:33 hostname power-daemon-mgr[36641]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 19:52:33 hostname power-daemon-mgr[36641]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:52:33 hostname power-daemon-mgr[36641]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:52:33 hostname power-daemon-mgr[36641]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 29 19:52:33 hostname power-daemon-mgr[36641]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 0: rust_begin_unwind Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 1: core::panicking::panic_fmt Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 2: core::result::unwrap_failed Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 5: power_daemon::profile::GpuSettings::apply Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 6: rayon::iter::plumbing::Producer::fold_with Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 7: rayon_core::join::join_context::{{closure}} Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 8: rayon_core::registry::in_worker Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 9: rayon::iter::plumbing::bridge_producer_consumer::helper Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 10: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 11: rayon_core::registry::WorkerThread::wait_until_cold Oct 29 19:52:33 hostname power-daemon-mgr[36641]: 12: rayon_core::registry::ThreadBuilder::run Oct 29 19:52:33 hostname power-daemon-mgr[36641]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:52:33 hostname power-daemon-mgr[36677]: Authorization required, but no authorization protocol specified Oct 29 19:52:33 hostname power-daemon-mgr[36677]: xset: unable to open display ":0" Oct 29 19:52:33 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 19:52:33 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 29 19:52:59 hostname systemd[1]: Started power-options daemon. Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(32) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(21) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(30) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(25) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(23) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(28) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(27) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(19) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(22) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(31) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(26):10 Oct 29 19:52:59 hostname power-daemon-mgr[37036]: : Oct 29 19:52:59 hostname power-daemon-mgr[37036]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:52:59 hostname power-daemon-mgr[37036]: stack backtrace: Oct 29 19:52:59 hostname power-daemon-mgr[37036]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 19:52:59 hostname power-daemon-mgr[37036]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 19:52:59 hostname power-daemon-mgr[37036]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:52:59 hostname power-daemon-mgr[37036]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:52:59 hostname power-daemon-mgr[37036]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(19) Oct 29 19:52:59 hostname power-daemon-mgr[37036]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 0: rust_begin_unwind Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 1: core::panicking::panic_fmt Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 2: core::result::unwrap_failed Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 3: power_daemon::sysfs::reading::file_content_to_string Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 4: power_daemon::sysfs::gpu::AmdGpu::from_dir Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 5: power_daemon::profile::GpuSettings::apply Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 6: rayon::iter::plumbing::Producer::fold_with Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 7: rayon_core::join::join_context::{{closure}} Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 8: rayon_core::registry::in_worker Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 9: rayon::iter::plumbing::bridge_producer_consumer::helper Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 10: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 11: rayon_core::registry::WorkerThread::wait_until_cold Oct 29 19:52:59 hostname power-daemon-mgr[37036]: 12: rayon_core::registry::ThreadBuilder::run Oct 29 19:52:59 hostname rfkill[37073]: block set for type nfc Oct 29 19:52:59 hostname power-daemon-mgr[37036]: note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace. Oct 29 19:52:59 hostname power-daemon-mgr[37072]: Authorization required, but no authorization protocol specified Oct 29 19:52:59 hostname power-daemon-mgr[37072]: xset: unable to open display ":0" Oct 29 19:52:59 hostname rfkill[37074]: block set for type bluetooth Oct 29 19:52:59 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 19:52:59 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. Oct 29 19:55:19 hostname systemd[1]: Started power-options daemon. Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(30) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(22) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(26) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(21) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(23) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(22) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(27) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(24) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(18) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: thread '' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 29 19:55:19 hostname power-daemon-mgr[38025]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 29 19:55:19 hostname power-daemon-mgr[38025]: stack backtrace: Oct 29 19:55:19 hostname power-daemon-mgr[38025]: ERROR ==> [power_daemon::profile]: ifconfig is not present in the system, ignoring ethernet settings... Oct 29 19:55:19 hostname power-daemon-mgr[38025]: ERROR ==> [power_daemon::profile]: Could not identify spuported wifi firmware module. Expected either iwlmvm or iwldvm, neither found. Ignoring network kernel module settings... Oct 29 19:55:19 hostname rfkill[38060]: unblock set for type wifi Oct 29 19:55:19 hostname power-daemon-mgr[38025]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:55:19 hostname power-daemon-mgr[38025]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 29 19:55:19 hostname power-daemon-mgr[38025]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(23) Oct 29 19:55:19 hostname power-daemon-mgr[38025]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 0: 0x57594936e562 - ::fmt Oct 29 19:55:19 hostname power-daemon-mgr[38061]: Authorization required, but no authorization protocol specified Oct 29 19:55:19 hostname power-daemon-mgr[38025]: ::h6214d82a5df2595e Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 1: Oct 29 19:55:19 hostname power-daemon-mgr[38061]: xset: unable to open display ":0" Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 0x575949399d5b - core::fmt::write::hf5f42bf308c7c107 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 2: 0x575949369cdf - std::io::Write::write_fmt::h6df9e7e82894c66e Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 3: 0x57594936fa01 - std::panicking::default_hook::{{closure}}::h1126899e8fa68624 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 4: 0x57594936f6dc - std::panicking::default_hook::h8bbbbeff9f5ab593 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 5: 0x575949370061 - std::panicking::rust_panic_with_hook::hb0baad225caa9be4 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 6: 0x57594936fec7 - std::panicking::begin_panic_handler::{{closure}}::ha222a98a0f4c074b Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 7: 0x57594936ea29 - std::sys::backtrace::__rust_end_short_backtrace::haf27a742036be4a5 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 8: 0x57594936fb54 - rust_begin_unwind Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 9: 0x575948e3bbb3 - core::panicking::panic_fmt::h2c68b1b94dbf98c7 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 10: 0x575948e3c086 - core::result::unwrap_failed::h8e93b096c514a928 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 11: 0x575948fd1ed7 - power_daemon::sysfs::reading::file_content_to_string::h6c498736f0e5f478 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 12: 0x575948fbde6f - power_daemon::sysfs::gpu::AmdGpu::from_dir::he0fa490dfc430041 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 13: 0x57594909622f - power_daemon::profile::GpuSettings::apply::hf9c7329ee026cb41 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 14: 0x575948f96364 - rayon::iter::plumbing::Producer::fold_with::hd1000a02a9121931 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 15: 0x575948fbe640 - rayon_core::join::join_context::{{closure}}::hc9d127e68782415a Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 16: 0x575948fbe928 - rayon_core::registry::in_worker::h64fc14d5862301e3 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 17: 0x575948fb7faa - rayon::iter::plumbing::bridge_producer_consumer::helper::hfe4c9fc1cc8c6ec0 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 18: 0x5759490c8ef3 - <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute::h0a93c04e78fec7f3 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 19: 0x575948e2dd56 - rayon_core::registry::WorkerThread::wait_until_cold::h529acc6d7af53ecb Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 20: 0x5759491e9672 - rayon_core::registry::ThreadBuilder::run::heea14a8a98794656 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 21: 0x5759491eeb8a - std::sys::backtrace::__rust_begin_short_backtrace::h03a1cd2ac60a5de7 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 22: 0x5759491ede62 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h1bfbfe28cdf3a7b9 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 23: 0x57594937549b - std::sys::pal::unix::thread::Thread::new::thread_start::haad0edf876459695 Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 24: 0x72f56656339d - Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 25: 0x72f5665e849c - Oct 29 19:55:19 hostname power-daemon-mgr[38025]: 26: 0x0 - Oct 29 19:55:19 hostname systemd[1]: power-options.service: Main process exited, code=exited, status=101/n/a Oct 29 19:55:19 hostname systemd[1]: power-options.service: Failed with result 'exit-code'. [username@hostname ~]$

Clearing out any setting under gpu_settings allows the daemon to start from systemctl or power-daemon-mgr, but the front end still displays "connecting to daemon" and does not load any settings. Snip from a log:

[username@hostname ~]$ sudo power-daemon-mgr daemon INFO ==> [power_daemon::profile]: Applying profile: Powersave INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(30) INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(23) INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(26) INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(29) INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(25) INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(28) INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(31) INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(20) INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(18) INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Authorization required, but no authorization protocol specified

xset: unable to open display ":0"

thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } note: run with RUST_BACKTRACE=1 environment variable to display a backtrace INFO ==> [D-BUS]: get_profiles_info INFO ==> [D-BUS]: get_profile_override ^C [username@hostname ~]$

It seems like the daemon keeps crashing. Judging by your system info and the logs it's timing out when reading a sysfs entry of your amdgpu kernel module. Can you read the content of /sys/class/drm/cardX/device/driver/power_dpm_force_performance_level manually with something like cat? Replace cardX with whatever corresponds to your GPU.

Thank you for the reply. It has run ok since I rebooted. I removed any gpu settings as well as the network settings - non-intel wifi card so they were skipped anyway. I will try changing profiles. then adding in the gpu settings and changing profiles again to see if I can recreate it. Unfortunately I wasn't able to figure out how to get the gui to reconnect to the daemon without rebooting.

I can read the _directories for card1 and card2, but there is no power_dpm_force_performance_level file in them. card1 is the discrete gpu (radeon 7700s) at pci 03 card2 is the integrated gpu at pci c5

In "normal" usage the integrated one is the active one, iirc.

[username@hostname driver]$ pwd /sys/class/drm/card1/device/driver [username@hostname driver]$ ls -larth total 0 lrwxrwxrwx 1 root root 0 Oct 30 14:42 module -> ../../../../module/amdgpu lrwxrwxrwx 1 root root 0 Oct 30 14:42 0000:c5:00.0 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:c5:00.0 lrwxrwxrwx 1 root root 0 Oct 30 14:42 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0 drwxr-xr-x 2 root root 0 Oct 30 14:42 . drwxr-xr-x 38 root root 0 Oct 30 14:42 .. --w------- 1 root root 4.0K Oct 30 14:42 uevent --w------- 1 root root 4.0K Oct 30 14:42 bind --w------- 1 root root 4.0K Oct 30 14:42 new_id --w------- 1 root root 4.0K Oct 30 14:42 remove_id --w------- 1 root root 4.0K Oct 30 14:42 unbind

[username@hostname driver]$ pwd /sys/class/drm/card2/device/driver [username@hostname driver]$ ls -larth total 0 lrwxrwxrwx 1 root root 0 Oct 30 14:42 module -> ../../../../module/amdgpu lrwxrwxrwx 1 root root 0 Oct 30 14:42 0000:c5:00.0 -> ../../../../devices/pci0000:00/0000:00:08.1/0000:c5:00.0 lrwxrwxrwx 1 root root 0 Oct 30 14:42 0000:03:00.0 -> ../../../../devices/pci0000:00/0000:00:01.1/0000:01:00.0/0000:02:00.0/0000:03:00.0 drwxr-xr-x 2 root root 0 Oct 30 14:42 . drwxr-xr-x 38 root root 0 Oct 30 14:42 .. --w------- 1 root root 4.0K Oct 30 14:42 uevent --w------- 1 root root 4.0K Oct 30 14:42 bind --w------- 1 root root 4.0K Oct 30 14:42 new_id --w------- 1 root root 4.0K Oct 30 14:42 remove_id --w------- 1 root root 4.0K Oct 30 14:42 unbind

[username@hostname driver]$ pwd /sys/class/drm/card1/device/driver

[username@hostname driver]$ cat 0000\:c5\:00.0/power_dpm_force_performance_level auto [username@hostname driver]$ cat 0000\:03\:00.0/power_dpm_force_performance_level cat: '0000:03:00.0/power_dp[brad@homer driver]$ sudo vim /etc/power-options/profiles/Performance.toml Place your finger on the fingerprint reader m_force_performance_level': Invalid argument

[username@hostname driver]$ pwd /sys/class/drm/card2/device/driver

Switching the profiles with no gpu options is fine. Enabling the AMD GPU DPM Performance Level, setting it to "auto", and clicking apply causes the daemon to be unhappy:

[username@hostname ~]$ journalctl -u power-options.service -b Journal file /var/log/journal/59aa3370469c4fc4bb2c16c6f461fd07/system@00061dc6aa62eb33-b4d31ef7389d3cbb.journal~ is truncated, ignoring file. Oct 29 23:13:05 hostname systemd[1]: Started power-options daemon. Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(32) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(18) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(22) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(25) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(21) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(27) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(29) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(19) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(30) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(26) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(19) Oct 29 23:13:05 hostname power-daemon-mgr[1748]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 29 23:13:05 hostname power-daemon-mgr[1785]: xset: unable to open display ":0" Oct 29 23:18:14 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profiles_info Oct 29 23:18:14 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profile_override Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: set_profile_override: Performance Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying profile: Performance Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(21) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(20) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(28) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(19) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(29) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(24) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(31) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(23) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(33) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(22) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 30 14:20:25 hostname power-daemon-mgr[1748]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 30 14:20:25 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(21) Oct 30 14:20:25 hostname power-daemon-mgr[1748]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 30 14:20:25 hostname power-daemon-mgr[190898]: Authorization required, but no authorization protocol specified Oct 30 14:20:25 hostname power-daemon-mgr[190898]: xset: unable to open display ":0" Oct 30 14:20:52 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profiles_info Oct 30 14:20:52 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profile_override Oct 30 14:20:52 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profiles_info Oct 30 14:20:52 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_config Oct 30 14:20:52 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profile_override Oct 30 14:21:08 hostname power-daemon-mgr[1748]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 30 14:21:08 hostname power-daemon-mgr[1748]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 30 14:21:08 hostname power-daemon-mgr[1748]: stack backtrace: Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 0: 0x5b60ec938562 - ::fmt::h6214d82a5df2595e Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 1: 0x5b60ec963d5b - core::fmt::write::hf5f42bf308c7c107 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 2: 0x5b60ec933cdf - std::io::Write::write_fmt::h6df9e7e82894c66e Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 3: 0x5b60ec939a01 - std::panicking::default_hook::{{closure}}::h1126899e8fa68624 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 4: 0x5b60ec9396dc - std::panicking::default_hook::h8bbbbeff9f5ab593 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 5: 0x5b60ec93a061 - std::panicking::rust_panic_with_hook::hb0baad225caa9be4 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 6: 0x5b60ec939ec7 - std::panicking::begin_panic_handler::{{closure}}::ha222a98a0f4c074b Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 7: 0x5b60ec938a29 - std::sys::backtrace::__rust_end_short_backtrace::haf27a742036be4a5 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 8: 0x5b60ec939b54 - rust_begin_unwind Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 9: 0x5b60ec405bb3 - core::panicking::panic_fmt::h2c68b1b94dbf98c7 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 10: 0x5b60ec406086 - core::result::unwrap_failed::h8e93b096c514a928 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 11: 0x5b60ec59bed7 - power_daemon::sysfs::reading::file_content_to_string::h6c498736f0e5f478 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 12: 0x5b60ec587e6f - power_daemon::sysfs::gpu::AmdGpu::from_dir::he0fa490dfc430041 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 13: 0x5b60ec591a76 - power_daemon::systeminfo::GpuInfo::obtain::h822b6789b7fa4d20 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 14: 0x5b60ec5bc776 - ::call::{{closure}}::h4a51f9c0196585c6 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 15: 0x5b60ec8a0c5e - zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}}::h3742bfd702021933 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 16: 0x5b60ec895e7f - <tracing::instrument::Instrumented as core::future::future::Future>::poll::h9eee7b011d9a0850 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 17: 0x5b60ec880169 - async_executor::Executor::spawn_inner::{{closure}}::h551d24d9d76d5894 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 18: 0x5b60ec87b7c6 - async_task::raw::RawTask<F,T,S,M>::run::h472f6f04db3e5143 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 19: 0x5b60ec857e4f - async_io::driver::block_on::h01c9c7983b05f6c0 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 20: 0x5b60ec84827e - std::sys::backtrace::rust_begin_short_backtrace::h95b95d3b40909a94 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 21: 0x5b60ec80b0aa - core::ops::function::FnOnce::call_once{{vtable.shim}}::h288f0ed4e177155d Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 22: 0x5b60ec93f49b - std::sys::pal::unix::thread::Thread::new::thread_start::haad0edf876459695 Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 23: 0x783bb0b0e39d - Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 24: 0x783bb0b9349c - Oct 30 14:21:08 hostname power-daemon-mgr[1748]: 25: 0x0 - Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: set_profile_override: Powersave Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying profile: Powersave Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(23) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(28) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(21) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(26) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(30) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(32) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(27) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(25) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(23) Oct 30 14:21:15 hostname power-daemon-mgr[1748]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 30 14:21:15 hostname power-daemon-mgr[191220]: Authorization required, but no authorization protocol specified Oct 30 14:21:15 hostname power-daemon-mgr[191220]: xset: unable to open display ":0" Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profiles_info Oct 30 14:21:15 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profile_override Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: set_profile_override: Performance Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying profile: Performance Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Sleep settings on ThreadId(18) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU settings on ThreadId(22) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Network settings on ThreadId(25) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying SATA settings on ThreadId(30) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying PCI PM settings on ThreadId(23) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Screen settings on ThreadId(27) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Radio settings on ThreadId(19) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying USB settings on ThreadId(20) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying ASPM settings on ThreadId(21) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying Kernel settings on ThreadId(24) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying RAPL settings on ThreadId(26) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 30 14:21:18 hostname power-daemon-mgr[1748]: ERROR ==> [power_daemon::profile]: Min/Max scaling perf percentage is currently only supported for intel CPUs with intel_pstate Oct 30 14:21:18 hostname power-daemon-mgr[1748]: INFO ==> [power_daemon::profile]: Applying CPU core settings on ThreadId(22) Oct 30 14:21:18 hostname power-daemon-mgr[1748]: WARN ==> [power_daemon::sysfs::writing]: Attempted to write 1 to CPU sysfs path /sys/devices/system/cpu/cpu0/online, but that path does not exist! Oct 30 14:21:18 hostname power-daemon-mgr[191245]: Authorization required, but no authorization protocol specified Oct 30 14:21:18 hostname power-daemon-mgr[191245]: xset: unable to open display ":0" Oct 30 14:21:21 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profiles_info Oct 30 14:21:21 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profile_override Oct 30 14:21:21 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profiles_info Oct 30 14:21:21 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_config Oct 30 14:21:21 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: get_profile_override Oct 30 14:22:27 hostname power-daemon-mgr[1748]: INFO ==> [D-BUS]: update_profile_reduced: 3 "Gpu" Oct 30 14:22:27 hostname power-daemon-mgr[1748]: thread 'zbus::Connection executor' panicked at crates/power-daemon/src/sysfs/reading.rs:11:10: Oct 30 14:22:27 hostname power-daemon-mgr[1748]: Could not read file: Os { code: 22, kind: InvalidInput, message: "Invalid argument" } Oct 30 14:22:27 hostname power-daemon-mgr[1748]: stack backtrace: Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 0: 0x5b60ec938562 - ::fmt::h6214d82a5df2595e Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 1: 0x5b60ec963d5b - core::fmt::write::hf5f42bf308c7c107 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 2: 0x5b60ec933cdf - std::io::Write::write_fmt::h6df9e7e82894c66e Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 3: 0x5b60ec939a01 - std::panicking::default_hook::{{closure}}::h1126899e8fa68624 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 4: 0x5b60ec9396dc - std::panicking::default_hook::h8bbbbeff9f5ab593 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 5: 0x5b60ec93a061 - std::panicking::rust_panic_with_hook::hb0baad225caa9be4 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 6: 0x5b60ec939ec7 - std::panicking::begin_panic_handler::{{closure}}::ha222a98a0f4c074b Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 7: 0x5b60ec938a29 - std::sys::backtrace::rust_end_short_backtrace::haf27a742036be4a5 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 8: 0x5b60ec939b54 - rust_begin_unwind Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 9: 0x5b60ec405bb3 - core::panicking::panic_fmt::h2c68b1b94dbf98c7 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 10: 0x5b60ec406086 - core::result::unwrap_failed::h8e93b096c514a928 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 11: 0x5b60ec59bed7 - power_daemon::sysfs::reading::file_content_to_string::h6c498736f0e5f478 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 12: 0x5b60ec587e6f - power_daemon::sysfs::gpu::AmdGpu::from_dir::he0fa490dfc430041 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 13: 0x5b60ec66022f - power_daemon::profile::GpuSettings::apply::hf9c7329ee026cb41 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 14: 0x5b60ec6598b4 - power_daemon::profile::Profile::apply_reduced::hb3c453d3d469a470 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 15: 0x5b60ec59f1f9 - power_daemon::Instance::update_reduced::he925f0c0f882a730 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 16: 0x5b60ec5c62d6 - ::call_mut::{{closure}}::h76d2dc6363dce5e2 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 17: 0x5b60ec8a11ef - zbus::object_server::ObjectServer::dispatch_call_to_iface::{{closure}}::h3742bfd702021933 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 18: 0x5b60ec895e7f - <tracing::instrument::Instrumented as core::future::future::Future>::poll::h9eee7b011d9a0850 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 19: 0x5b60ec880169 - async_executor::Executor::spawn_inner::{{closure}}::h551d24d9d76d5894 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 20: 0x5b60ec87b7c6 - async_task::raw::RawTask<F,T,S,M>::run::h472f6f04db3e5143 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 21: 0x5b60ec857e4f - async_io::driver::block_on::h01c9c7983b05f6c0 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 22: 0x5b60ec84827e - std::sys::backtrace::__rust_begin_short_backtrace::h95b95d3b40909a94 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 23: 0x5b60ec80b0aa - core::ops::function::FnOnce::call_once{{vtable.shim}}::h288f0ed4e177155d Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 24: 0x5b60ec93f49b - std::sys::pal::unix::thread::Thread::new::thread_start::haad0edf876459695 Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 25: 0x783bb0b0e39d - Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 26: 0x783bb0b9349c - Oct 30 14:22:27 hostname power-daemon-mgr[1748]: 27: 0x0 - [username@hostname ~]$

I think I told you the wrong file path. These are all the paths that the daemon reads when parsing for GPUs:

amdgpu module:

/sys/class/drm/cardX/device/power_dpm_force_performance_level

radeon module:

/sys/class/drm/cardX/device/power_dpm_force_performance_level
/sys/class/drm/cardX/device/power_dpm_state

Legacy radeon:

/sys/class/drm/cardX/power_profile

Judging by the system info that you provided you seem to have amdgpu. See if the paths associated exist because InvalidArgument technically does not mean that the file is not present.

Here's that output:

[username@hostname ~]$ cat /sys/class/drm/card1/device/power_dpm_force_performance_level low [username@hostname ~]$ cat /sys/class/drm/card1/device/power_dpm_state performance [username@hostname ~]$ cat /sys/class/drm/card1/power_profile cat: /sys/class/drm/card1/power_profile: No such file or directory

[username@hostname ~]$ cat /sys/class/drm/card2/device/power_dpm_force_performance_level low [username@hostname ~]$ cat /sys/class/drm/card2/device/power_dpm_state performance [username@hostname ~]$ cat /sys/class/drm/card2/power_profile cat: /sys/class/drm/card2/power_profile: No such file or directory [username@hostname ~]$

That's weird, the path that the daemon is failing to read is actually present in your system.

I recently committed a patch that fixed another problem related to amdgpu and while it's unlikely to be the cause of your problems still consider trying it out on the git version of power-options. I've also made errors more verbose so the path that is causing the panic will also be mentioned.

TheAlexDev23 / power-options

Changing profile from the webview client does not complete, restarting the webview client or gtk client results in no connection to daemon #27