Bug 500933 - Turning on power management in Settings after modifying the default font causes the Settings app to freeze
Summary: Turning on power management in Settings after modifying the default font caus...
Status: RESOLVED DUPLICATE of bug 499773
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_powerdevil (other bugs)
Version First Reported In: 6.3.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-02 01:14 UTC by 19484
Modified: 2025-03-25 22:14 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Turning on power management in Settings after modifying the default font causes the Settings app to freeze (3.89 MB, application/octet-stream)
2025-03-07 04:10 UTC, 19484
Details

Note You need to log in before you can comment on or make changes to this bug.
Description 19484 2025-03-02 01:14:51 UTC
The default font size is set to 12, and then when opening the power management in the settings, the settings will freeze. If the font size is set to 11 or 13, it won't freeze. Changing the font to another font will also cause the default font size to freeze.
Comment 1 Nate Graham 2025-03-05 20:43:13 UTC
I can't reproduce this as described (though the description is a bit thin; maybe you can attach a screen recording?).

However it does appear that *something* is going wrong with this KCM when opened with non-default fonts; see Bug 499773 and Bug 499991.
Comment 2 19484 2025-03-07 04:10:23 UTC
Created attachment 179195 [details]
Turning on power management in Settings after modifying the default font causes the Settings app to freeze
Comment 3 John Kizer 2025-03-21 18:35:53 UTC
Thanks for the recording! It looks like this is the combination of font size and locale that also comes up in bug 499991 - merging this into that bug report. Thanks!

*** This bug has been marked as a duplicate of bug 499991 ***
Comment 4 Nate Graham 2025-03-25 22:14:00 UTC

*** This bug has been marked as a duplicate of bug 499773 ***