Bug 491331 - Selecting "process table" as a style for Network Speed widget freezes the Panel
Summary: Selecting "process table" as a style for Network Speed widget freezes the Panel
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Monitor widgets (show other bugs)
Version: 6.1.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-05 22:12 UTC by omano
Modified: 2024-08-13 19:05 UTC (History)
3 users (show)

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

Attachments
settings of Panel (401.10 KB, image/png)
2024-08-08 16:55 UTC, omano 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description omano 2024-08-05 22:12:07 UTC 
SUMMARY
Selecting "process table" as a style for Network Speed widget freezes the Panel

STEPS TO REPRODUCE
1. Add the Network Speed widget
2. Go to its configuration when added to the Panel
3. Select the style "process table" and click Apply

OBSERVED RESULT
Panel freezes, widget configuration window freezes

EXPECTED RESULT
Nothing freezes or crash

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-08-06 19:10:33 UTC 
This was supposed to be fixed with Bug 487815 for Plasma 6.1

Can you describe the settings of your panel? Thickness, alignment, settings, other contents on it, etc.
Comment 2 omano 2024-08-08 16:55:23 UTC 
Attached is a screenshot of my current Panel settings, which are not the defaults.
I also tried a new user without my manually added widgets and I can reproduce the issue.
I updated to 6.1.4. and it solved the issue. It doesn't freeze anymore but shows some kind of triangle/play button instead instead of the widget graph.
Comment 3 omano 2024-08-08 16:55:53 UTC 
Created attachment 172404 [details]
settings of Panel
Comment 4 Nate Graham 2024-08-13 19:05:58 UTC 
Ok, great, sounds like 6.1.4 fixed it. I'd recommend submitting another bug report for the remaining different issue. Thanks!