search

TheAlexDev23 / power-options

Linux GUI application for blazingly fast and simple power-management.
MIT License
222 stars 1 forks source link

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

Closed lbkNhubert closed 2 hours ago

lbkNhubert commented 2 hours ago

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:

[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

TheAlexDev23 commented 2 hours ago

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

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

lbkNhubert commented 2 hours ago

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