Dear Maintainer,

The Power Management tab in Plasma 6.3.5 System Settings breaks, showing this error instead of any controls, meaning that power management settings cannot be adjusted. I don't know if powerdevil is working at all, i.e. whether it's only the System Settings that are impacted or powerdevil's power management functionality as a whole.

   Could not load plugin from /usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/kcms/systemsettings/kcm_powerdevilprofilesconfig.so: Cannot load library /usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/kcms/systemsettings/kcm_powerdevilprofilesconfig.so: /lib/x86_64-linux-gnu/libpowerdevilcore.so.2: undefined symbol: ddca_stop_watch_displays

Steps to reproduce:

1. Start Plasma System Settings: /usr/bin/systemsettings
2. In the left-hand pane carrying the various "snap-ins" for system settings, scroll down to the Power Management item in the System group.
3. Click on Power Management.
4. Note the above error appears in the main pane (which generally has system setting controls).

Please see package versions below.

# amitg @ athena in ~ ✦24 [14:41:46]
$ dpkg -S /usr/bin/systemsettings /usr/lib/x86_64-linux-gnu/libpowerdevilcore.so.6.3.5 /usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/kcms/systemsettings/kcm_powerdevilprofilesconfig.so
systemsettings: /usr/bin/systemsettings
libpowerdevilcore2:amd64: /usr/lib/x86_64-linux-gnu/libpowerdevilcore.so.6.3.5
powerdevil: /usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/kcms/systemsettings/kcm_powerdevilprofilesconfig.so

# amitg @ athena in ~ ✦24 [14:41:47]
$ dpkg -l systemsettings libpowerdevilcore2 powerdevil
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                     Version      Architecture Description
+++-========================-============-============-==============================================================
ii  libpowerdevilcore2:amd64 4:6.3.5-1    amd64        shared library for the KDE power management features in Plasma
ii  powerdevil               4:6.3.5-1    amd64        KDE power management service for Plasma
ii  systemsettings           4:6.3.4-2    amd64        System Settings interface

# amitg @ athena in ~ ✦24 [14:42:12]
$ apt policy systemsettings powerdevil libpowerdevilcore2:amd64
systemsettings:
  Installed: 4:6.3.4-2
  Candidate: 4:6.3.4-2
  Version table:
 *** 4:6.3.4-2 900
        500 https://mirror.apps.cam.ac.uk/pub/linux/debian unstable/main amd64 Packages
        900 https://mirror.apps.cam.ac.uk/pub/linux/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status
     4:5.27.5-2 500
        500 https://mirror.apps.cam.ac.uk/pub/linux/debian stable/main amd64 Packages
powerdevil:
  Installed: 4:6.3.5-1
  Candidate: 4:6.3.5-1
  Version table:
 *** 4:6.3.5-1 900
        500 https://mirror.apps.cam.ac.uk/pub/linux/debian unstable/main amd64 Packages
        900 https://mirror.apps.cam.ac.uk/pub/linux/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status
     4:5.27.5-2 500
        500 https://mirror.apps.cam.ac.uk/pub/linux/debian stable/main amd64 Packages
libpowerdevilcore2:
  Installed: 4:6.3.5-1
  Candidate: 4:6.3.5-1
  Version table:
 *** 4:6.3.5-1 900
        500 https://mirror.apps.cam.ac.uk/pub/linux/debian unstable/main amd64 Packages
        900 https://mirror.apps.cam.ac.uk/pub/linux/debian testing/main amd64 Packages
        100 /var/lib/dpkg/status
     4:5.27.5-2 500
        500 https://mirror.apps.cam.ac.uk/pub/linux/debian stable/main amd64 Packages

control: tags -1 + moreinfo unreproducible

Le lundi 30 juin 2025, 15:46:10 heure d’été d’Europe centrale Amit Gurdasani a écrit :

Dear Amit,

I cannot reproduce the issue you describe.

What I hope is that it was transitory and has been fixed by later package updates.
Could you confirm whether the issue is fixed for you ?


Thanks,
--
Aurélien

control: tags -1 + moreinfo unreproducible

Le lundi 30 juin 2025, 15:46:10 heure d’été d’Europe centrale Amit Gurdasani a écrit :

Dear Amit,

I cannot reproduce the issue you describe.

What I hope is that it was transitory and has been fixed by later package updates.
Could you confirm whether the issue is fixed for you ?


Thanks,
--
Aurélien