Power Management Issues

danSman · 2025-06-20 08:50:18

Hey

I have a problem with my power management under KDE (version 6.3.5, will test 6.4 soon). This has actually already started at the beginning of this year.

Suspend Session before:
suspend_session-before

After a while, it is no longer possible to select the sleep option. I can only use it via “Application Launcher > sleep”. The power profile also seems to have disappeared.

Suspend Session after:
suspend_session-after

I guess it happens after the first "Turn off screen" or something.
After that it takes forever to open “Power Management - System Settings” and even opened videos end up in a huge lag 30sec - 1min.

I haven't checked any logs after the problem yet, but what I have found during boot so far is:

Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000001e109435 (20240827/exresop-557)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240827/dswexec-433)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000006a10d133 (20240827/exresop-557)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240827/dswexec-433)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000009326a3d9 (20240827/exresop-557)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240827/dswexec-433)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000c2aa0483 (20240827/exresop-557)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20240827/dswexec-433)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WVPO due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)
Jun 20 20:06:47 dansdesktop kernel: ACPI Error: Aborting method \_SB.WMIV.WMPV due to previous error (AE_AML_OPERAND_TYPE) (20240827/psparse-529)

Could it be related to the ACPI issues?
I will post some logs as soon as the problem occurs again.

Thanks!

twelveeighty · 2025-06-20 14:27:54

To isolate if it's ACPI or KDE, use systemctl to suspend the system and see if that works fine (including waking up). Preferably without having KDE started, either by starting a different WM or booting with systemd.unit=multi-user.target.

Why would you not check your logs after the problem?

danSman · 2025-06-21 01:01:45

My priority list was different. I don't watch really videos etc, so it didn't bother me much. But now I wanted to solve the problem and just haven't checked the logs after the issue. Maybe I'll install Arch again (it's just time to get rid of old things, which I do every now and then), but actually I'm curious and would like to know what's causing the problem before I possibly reinstall it, which isn't quite decided yet either

Anyway, everything seems to be working normally today. It is now also running on v6.4. systemctl suspend works fine. I had put the computer to “sleep” overnight, which usually causes the problem after such a long time (next morning). I also set “Performance” under “Switch to power profile”, which was previously set to Balance. I have now changed this back to “Balance” (but manually on performance via the icon) and will see if this causes the problem again.

Last edited by danSman (2025-06-21 01:03:33)

seth · 2025-06-21 11:29:06

1280 wrote:

Why would you not check your logs after the problem?

You can btw. access older journals "sudo journalctl -b -3" for three boots ago and there're also time based filters, https://wiki.archlinux.org/title/System … ing_output

From the images the change also seems to have introduced backlight control - did you maybe undock the notebook, thus lose access to A power button?

danSman · 2025-06-22 00:18:37

It goes back 4 days max. Cant find anything there anymore.
It's a elitedesk computer so no laptop. Backlight has the logitech mx mechanical.

What I realised having "Dim automatically" and "Turn off screens" enabled doesn't work for one monitor though (the middle one). I have three (2 displayports and 1 VGA) . Left is VGA middle and right is DP.
screens
Usually, I push the power button to set the computer in sleep mode. ~~I'm going to have a look now what happens when I use "When inactive: Sleep" after 30 minutes.~~ <- Can't do that. I have to run things which needs the computer running.

Back to logitech:

Jun 20 21:07:00 dansdesktop (udev-worker)[688]: 1-13:1.0: /etc/udev/rules.d/logitech-unifying.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.0/power/wakeup}="disabled", ignoring: No such file or directory
Jun 20 21:07:00 dansdesktop (udev-worker)[696]: 1-13:1.3: /etc/udev/rules.d/logitech-unifying.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.3/power/wakeup}="disabled", ignoring: No such file or directory
Jun 20 21:07:00 dansdesktop (udev-worker)[689]: 1-13:1.1: /etc/udev/rules.d/logitech-unifying.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.1/power/wakeup}="disabled", ignoring: No such file or directory
Jun 20 21:07:01 dansdesktop (udev-worker)[692]: 1-13:1.2: /etc/udev/rules.d/logitech-unifying.rules:1 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb1/1-13/1-13:1.2/power/wakeup}="disabled", ignoring: No such file or directory

I might to have a look into that again - https://wiki.archlinux.org/title/Power_ … _with_udev

cat /etc/udev/rules.d/logitech-unifying.rules
ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c548", ATTR{power/wakeup}="disabled"

But the goal was to ensure that it is no longer possible to wake the device with the unified devices when it is in sleep mode which works.

Last edited by danSman (2025-06-22 00:21:15)

seth · 2025-06-22 05:45:43

After that it takes forever to open “Power Management - System Settings” and even opened videos end up in a huge lag 30sec - 1min.

Please post your complete system journal for a boot covering such condition

sudo journalctl -b -δ | curl -F 'file=@-' 0x0.st # replace δ with an appropriate number

danSman · 2025-06-24 07:26:13

Hi seth

Got the following issue:

curl: (6) Could not resolve host: 0x0.st

seth · 2025-06-24 07:36:41

You've no network connection?
You can redirect the output

sudo journalctl -b -δ > /tmp/journal.txt

into a file and upload that from a system w/ internet connection.

danSman · 2025-06-24 08:47:27

Yeah, I've network connection.

I can't push the whole file. Too much information.

So I looked and pulled out what might be helpful. If you have something specific you'd like to look for, it would be great if you let me know.

Jun 24 08:53:03 dansdesktop dbus-broker-launch[1639]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Jun 24 08:53:03 dansdesktop dbus-broker-launch[1639]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Jun 24 08:53:03 dansdesktop dbus-broker-launch[1639]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jun 24 08:53:03 dansdesktop dbus-broker-launch[1639]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jun 24 08:53:03 dansdesktop dbus-broker-launch[1639]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'

Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: > Warning:          Unsupported maximum keycode 708, clipping.
Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: >                   X11 cannot support keycodes above 255.
Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: > Warning:          Could not resolve keysym XF86RefreshRateToggle
Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: > Warning:          Could not resolve keysym XF86Accessibility
Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: > Warning:          Could not resolve keysym XF86DoNotDisturb
Jun 24 08:53:05 dansdesktop kwin_wayland_wrapper[1800]: Errors from xkbcomp are not fatal to the X server

Jun 24 08:53:06 dansdesktop systemd[1]: Started Daemon for power management.
Jun 24 08:53:06 dansdesktop org_kde_powerdevil[1975]: Initializing libddcutil.  ddcutil version: 2.2.0, shared library: /usr/lib/libddcutil.so.5.2.0
Jun 24 08:53:06 dansdesktop org_kde_powerdevil[1975]: [  1975] Options passed from client:
Jun 24 08:53:06 dansdesktop org_kde_powerdevil[1975]: [  1975] Applying combined libddcutil options:
Jun 24 08:53:06 dansdesktop plasmashell[1905]: kf.plasma.quick: Applet preload policy set to 1
Jun 24 08:53:06 dansdesktop kaccess[1971]: X server XKB extension major= 1  minor= 0
Jun 24 08:53:07 dansdesktop kded6[1841]: org.kde.libkbolt: Failed to connect to Bolt manager DBus interface:
Jun 24 08:53:07 dansdesktop kded6[1841]: org.kde.bolt.kded: Couldn't connect to Bolt DBus daemon
Jun 24 08:53:07 dansdesktop kded6[1841]: org.kde.colorcorrectlocationupdater: Geolocator stopped
Jun 24 08:53:07 dansdesktop NetworkManager[1228]: <info>  [1750711987.0316] agent-manager: agent[a5e0a29935697967,:1.53/org.kde.plasma.networkmanagement/1000]: agent registered
Jun 24 08:53:07 dansdesktop kded6[1841]: QDBusObjectPath: invalid path "/modules/wpad-detector"
Jun 24 08:53:07 dansdesktop kded6[1841]: kf.dbusaddons: The kded module name "wpad-detector" is invalid!
Jun 24 08:53:07 dansdesktop kded6[1841]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Jun 24 08:53:07 dansdesktop kded6[1841]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
Jun 24 08:53:07 dansdesktop kconf_update[2089]: kf.config.kconf_update: /usr/share/kconf_update/ark.upd defined Version=5 but Version=6 was expected
Jun 24 08:53:07 dansdesktop kconf_update[2089]: kf.config.kconf_update: /usr/share/kconf_update/dolphin_directorysizemode.upd defined Version=5 but Version=6 was expected
Jun 24 08:53:07 dansdesktop kconf_update[2089]: kf.config.kconf_update: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected
Jun 24 08:53:07 dansdesktop kded6[1841]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.54'
Jun 24 08:53:07 dansdesktop kded6[1841]: qt.dbus.integration: QDBusConnection: name 'org.freedesktop.UPower' had owner '' but we thought it was ':1.59'
Jun 24 08:53:07 dansdesktop dbus-broker-launch[977]: Activation request for 'org.freedesktop.ModemManager1' failed: The systemd unit 'dbus-org.freedesktop.ModemManager1.service' could not be found.
Jun 24 08:53:07 dansdesktop kded6[1841]: kf.modemmanagerqt: Failed enumerating MM objects: "org.freedesktop.DBus.Error.NameHasNoOwner"
                                         "Could not activate remote peer 'org.freedesktop.ModemManager1': activation request failed: unknown unit"
Jun 24 08:53:07 dansdesktop kded6[2095]: xsettingsd: Loaded 16 settings from /home/dan/.config/xsettingsd/xsettingsd.conf
Jun 24 08:53:07 dansdesktop kded6[2095]: xsettingsd: Created window 0xe00001 on screen 0 with timestamp 25241
Jun 24 08:53:07 dansdesktop kded6[2095]: xsettingsd: Selection _XSETTINGS_S0 is owned by 0x0
Jun 24 08:53:07 dansdesktop kded6[2095]: xsettingsd: Took ownership of selection _XSETTINGS_S0
Jun 24 08:53:07 dansdesktop systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.kded.smart.
Jun 24 08:53:07 dansdesktop systemd[1]: Started dbus-:1.2-org.kde.kded.smart@0.service.
Jun 24 08:53:07 dansdesktop kded6[1841]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor"

Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: Library initialization complete.
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: [  1975] Watching for display connection changes, resolved watch mode = Watch_Mode_Xevent, poll loop interval = 100 millisec
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: [  1975]                                          extra_stabilization_millisec: 0,  stabilization_poll_millisec: 100
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: [  1975] libddcutil recheck thread (nil) started
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: [  1975] libddcutil watch thread 0x562ae89bea80 started
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: [  2129] (dw_recheck_displays_func) Recheck interval: Slept for 200 millisec
Jun 24 08:53:08 dansdesktop systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.discretegpuhelper.
Jun 24 08:53:08 dansdesktop systemd[1]: Started dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service.
Jun 24 08:53:08 dansdesktop systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.chargethresholdhelper.
Jun 24 08:53:08 dansdesktop systemd[1]: Started dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service.
Jun 24 08:53:08 dansdesktop systemd[1]: Created slice Slice /system/dbus-:1.2-org.kde.powerdevil.backlighthelper.
Jun 24 08:53:08 dansdesktop systemd[1]: Started dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service.
Jun 24 08:53:08 dansdesktop backlighthelper[2182]: org.kde.powerdevil: no kernel backlight interface found
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Jun 24 08:53:08 dansdesktop org_kde_powerdevil[1975]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed

Jun 24 08:53:09 dansdesktop org_kde_powerdevil[1975]: org.kde.powerdevil: Handle button events action could not check for screen configuration
Jun 24 08:53:09 dansdesktop org_kde_powerdevil[1975]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"

Jun 24 08:53:10 dansdesktop env[2214]: Error: Failed to open Wayland display, fallback to X11. WAYLAND_DISPLAY='wayland-0' DISPLAY=':1'gGgfg
Jun 24 08:53:10 dansdesktop DiscoverNotifier[2233]: couldn't load "/usr/lib/qt6/plugins/discover-notifier/DiscoverPackageKitNotifier.so" because "Cannot load library /usr/lib/qt6/plugins/discover-notifier/DiscoverPackageKitNoti     fier.so: libpackagekitqt6.so.1: cannot open shared object file: No such file or directory"
Jun 24 08:53:10 dansdesktop dbus-broker-launch[977]: Activation request for 'org.bluez' failed: The systemd unit 'dbus-org.bluez.service' could not be found

Jun 24 08:53:18 dansdesktop kded6[1841]: Registering ":1.83/StatusNotifierItem" to system tray
Jun 24 08:53:18 dansdesktop kwin_wayland[1652]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Jun 24 08:53:19 dansdesktop systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully.
Jun 24 08:53:19 dansdesktop systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully.
Jun 24 08:53:19 dansdesktop systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully.

Jun 24 08:55:14 dansdesktop systemd-logind[985]: The system will suspend now!
Jun 24 08:55:14 dansdesktop NetworkManager[1228]: <info>  [1750712114.3832] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 24 08:55:14 dansdesktop NetworkManager[1228]: <info>  [1750712114.3833] device (wlp1s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 24 08:55:14 dansdesktop NetworkManager[1228]: <info>  [1750712114.3844] device (wlp1s0): set-hw-addr: reset MAC address to 34:F3:9A:8C:1A:C2 (unmanage)
Jun 24 08:55:14 dansdesktop NetworkManager[1228]: <info>  [1750712114.3853] manager: NetworkManager state is now ASLEEP
Jun 24 08:55:14 dansdesktop dbus-broker[982]: A security policy denied :1.40 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
Jun 24 08:55:14 dansdesktop kwin_wayland[1652]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
Jun 24 08:55:14 dansdesktop dbus-broker[982]: A security policy denied :1.40 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
Jun 24 08:55:14 dansdesktop kwin_wayland[1652]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
Jun 24 08:55:14 dansdesktop dbus-broker[982]: A security policy denied :1.40 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
Jun 24 08:55:14 dansdesktop kwin_wayland[1652]: kwin_core: Failed to delay sleep: Sender is not authorized to send message

Edit:
BTW 0x0.st got blocked by adguard

Last edited by danSman (2025-06-24 09:17:02)

seth · 2025-06-24 15:08:46

BTW 0x0.st got blocked by adguard

Unblock it and post the journal - random lines out of context won't help much here

Arch Linux

#1 2025-06-20 08:50:18

Power Management Issues

#2 2025-06-20 14:27:54

Re: Power Management Issues

#3 2025-06-21 01:01:45

Re: Power Management Issues

#4 2025-06-21 11:29:06

Re: Power Management Issues

#5 2025-06-22 00:18:37

Re: Power Management Issues

#6 2025-06-22 05:45:43

Re: Power Management Issues

#7 2025-06-24 07:26:13

Re: Power Management Issues

#8 2025-06-24 07:36:41

Re: Power Management Issues

#9 2025-06-24 08:47:27

Re: Power Management Issues

#10 2025-06-24 15:08:46

Re: Power Management Issues

Board footer