Bug 428724

Summary: Freeze when changing the pie chart to a line chart on a new page
Product: [Applications] plasma-systemmonitor Reporter: Noah Davis <noahadvs>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: ahiemstra, justin.zobel, piotr.mierzwinski, plasma-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Noah Davis 2020-11-05 13:14:58 UTC
SUMMARY
After creating a new page, it's possible to freeze plasma-systemmonitor when changing the default pie chart to a line chart. No other changes were made.

STEPS TO REPRODUCE
1. Create a new page
2. edit the pie chart
3. change the pie chart to a line chart

OBSERVED RESULT
plasma-systemmonitor freezes and has to be killed

EXPECTED RESULT
plasma-systemmonitor should change the pie chart to a line chart without freezing

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20201030
KDE Plasma Version: 5.20.80
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1
Kernel Version: 5.8.4-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-6500U CPU @ 2.50GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 520
Comment 1 Justin Zobel 2020-11-06 09:41:55 UTC
I'm unable to reproduce this on plasma-systemmonitor from git master.

If you run it from a terminal does it give you any output that might indicate why it froze?
Comment 2 Arjen Hiemstra 2020-11-06 09:43:33 UTC
Git commit bf8722d56552ed5f558c01f4f6417d7928ce56a3 by Arjen Hiemstra.
Committed on 06/11/2020 at 09:43.
Pushed by ahiemstra into branch 'master'.

Do not use fillWidth on the face control on the face config page

It causes a layout loop that freezes plasma-systemmonitor

M  +2    -1    src/page/FaceConfigurationPage.qml

https://invent.kde.org/plasma/plasma-systemmonitor/commit/bf8722d56552ed5f558c01f4f6417d7928ce56a3
Comment 3 Arjen Hiemstra 2021-02-09 13:49:17 UTC
*** Bug 428908 has been marked as a duplicate of this bug. ***