Bug 494390 - System settings freezes when trying to access energy management and language is set to German
Summary: System settings freezes when trying to access energy management and language ...
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_powerdevil (other bugs)
Version First Reported In: 6.2.2
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-10 05:29 UTC by datatrash
Modified: 2025-03-19 18:28 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.3.3 and/or Frameworks 6.12; unclear
Sentry Crash Report:


Attachments
The empty page in system settings where energy options should be. (120.21 KB, image/png)
2024-10-10 05:29 UTC, datatrash
Details

Note You need to log in before you can comment on or make changes to this bug.
Description datatrash 2024-10-10 05:29:39 UTC
Created attachment 174595 [details]
The empty page in system settings where energy options should be.

SUMMARY

In system settings when system language is set to German and trying to access energy management, the settings page remains empty (see attachment).

At the same time htop shows seemingly random cores going from ~1.5 % utilization (normal load) to ~100%. This effect seems to randomly cycle through the available cores.

The only way to remediate this is to close settings entirely. System settings then becomes unresponsive and has to be killed.

Note that this was not the case when I initially set up the machine maybe two or three months ago.
Initially I could access energy options while system language was set to German.

Also note, that when changing the language to English, energy management can again be accessed. 

STEPS TO REPRODUCE
1.  Set system language to German. (I also changed a few energy options when first setting up the machine)
2. Open system settings, try to access energy management options.
3.  System settings freeze.

OBSERVED RESULT

See above.

EXPECTED RESULT

System language has no influence on ability to access energy management options in system settings.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Manjaro Linux
KDE Plasma Version: 6.1.5
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

Can't think of anything relevant.
Comment 1 Stefan 2024-10-16 16:47:17 UTC
I have had the same problem since updating to Plasma 6.2
The direct call with kcmshell also fails.

KDE Neon 24.04
Plasma 6.2
Frameworks 6.6
Comment 2 postix 2024-10-17 12:14:01 UTC
Cannot reproduce on Fedora 40 with Plasma 6.2.0
Comment 3 Stefan Borggraefe 2024-10-21 21:21:58 UTC
Confirming with Plasma 6.1.5 on Kubuntu 24.10. Energy settings cannot be used because it hangs an an endless loop.

strace systemsettings

shows the two lines

madvise(0x78f020310000, 65536, MADV_WILLNEED) = 0
mprotect(0x78f020320000, 65536, PROT_READ|PROT_WRITE) = 0

endlessly.
Comment 4 Thomas Rother 2024-11-04 08:30:28 UTC
Same behaviour here on openSUSE, confirmed for
Distributor ID: openSUSE
Description:    openSUSE Tumbleweed
Release:        20241102

with current kde plasma 6.2.2, frameworks 6.7, Qt 6.8.0. The kcmshell call shows

thommie@odysseus4:~> kcmshell6 kcm_powerdevilprofilesconfig
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton*
qt.qml.list.incompatible: Cannot append QQuickRepeater(0x55dd6d3d3e60) to a QML list of QQuickAbstractButton*
Comment 5 Nate Graham 2024-11-05 18:01:59 UTC
Cannot reproduce with `LANGUAGE=de_DE kcmshell6 kcm_powerdevilprofilesconfig` on current git master. Is anyone able to reproduce this in a new clean user account?
Comment 6 Thomas Rother 2024-11-06 08:41:58 UTC
(In reply to Nate Graham from comment #5)
> Cannot reproduce with `LANGUAGE=de_DE kcmshell6
> kcm_powerdevilprofilesconfig` on current git master. Is anyone able to
> reproduce this in a new clean user account?

I tested this on the machine where I have this issue (its already de_DE). With a "clean" user there is no problem with the  kcm_powerdevilprofilesconfig UI. So I assume it has to do with some user-side config setting. But a deletion of the .config/powerdevilrc and powermanagementprofilesrc did not change anything.

Any other ideas?
Comment 7 Nate Graham 2024-11-06 18:48:52 UTC
Thanks for the data point. Can you provide a rough list of the kinds of customizations you've made to your user account? Anything significant?
Comment 8 Thomas Rother 2024-11-06 21:02:05 UTC
(In reply to Nate Graham from comment #7)
> Thanks for the data point. Can you provide a rough list of the kinds of
> customizations you've made to your user account? Anything significant?

Hm, nothing relevant, but what kind of customization could be relevant? As I can not edit the power settings through UI, they are default:

thommie@odysseus4:~/.config> powerprofilesctl 
  performance:
    CpuDriver:  intel_pstate
    PlatformDriver:     platform_profile
    Degraded:   no

* balanced:
    CpuDriver:  intel_pstate
    PlatformDriver:     platform_profile

  power-saver:
    CpuDriver:  intel_pstate
    PlatformDriver:     platform_profile

Just a note: I saw that the deleted powermanagementprofilesrc was created automagically. It contains 

[Migration]
MigratedProfilesToPlasma6=powerdevilrc
Comment 9 Nate Graham 2024-11-08 19:54:54 UTC
Hmm, is the `org_kde_powerdevil` process running?
Comment 10 Thomas Rother 2024-11-08 20:31:21 UTC
(In reply to Nate Graham from comment #9)
> Hmm, is the `org_kde_powerdevil` process running?

odysseus4:~ # ps -aux | grep org_kde_powerdevil
thommie     4708  0.2  0.1 1331796 115492 ?      Ssl  21:26   0:00 /usr/libexec/org_kde_powerdevil
root        7459  0.0  0.0   3936  1792 pts/2    S+   21:29   0:00 grep --color=auto org_kde_powerdevil
Comment 11 Nate Graham 2024-11-08 20:44:15 UTC
Then I'm out of ideas, sorry. Hopefully a Powerdevil person can help you further.
Comment 12 Stefan 2025-03-18 14:53:42 UTC
With the update to frameworks 6.12 the error is gone for me.
Comment 13 Thomas Rother 2025-03-18 18:22:27 UTC
confirmed, no issues any more on openSUSE Tumbleweed, Release   20250315 with framework 6.11.0
Comment 14 Nate Graham 2025-03-18 18:24:58 UTC
Sounds like Plasma 6.3.3 fixed it. Thanks folks!
Comment 15 Stefan 2025-03-18 20:46:03 UTC
I still had the problem with Plasma 6.33 and Frameworks 6.11.