Bug 449145 - Desktop widgets created out of charts have a too small background
Summary: Desktop widgets created out of charts have a too small background
Status: RESOLVED DUPLICATE of bug 442703
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.90
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: wayland-only
Depends on:
Blocks:
 
Reported: 2022-01-25 14:04 UTC by postix
Modified: 2022-10-31 18:08 UTC (History)
5 users (show)

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

Attachments
Screenshot (96.00 KB, image/png)
2022-01-25 14:04 UTC, postix 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description postix 2022-01-25 14:04:22 UTC 
Created attachment 145912 [details]
Screenshot

STEPS TO REPRODUCE
1.  Open Systemmonitor 
2.  Right click on the Networks chart and choose "Add chart as desktop widget"

OBSERVED RESULT
The very first chart is placed in the center of the screen, where the content overflows the quadratic background.

EXPECTED RESULT
There's space on the screen, so use it for the background! :-)

SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.3
Kernel Version: 5.13.0-27-generic (64-bit)
Graphics Platform: Wayland
Graphics Processor: Radeon RX 580 Series
Scaling: 200%
Comment 1 Arjen Hiemstra 2022-01-27 15:05:44 UTC 
I suspect this is a symptom of 440592. Marking it as such, if it doesn't turn out the be the same feel free to reopen this.

*** This bug has been marked as a duplicate of bug 440592 ***
Comment 2 postix 2022-01-27 15:38:06 UTC 
Yes, the symptoms are the same in case of a too small widget and window but this bug report was more intended to propose to give the widgets a more suitable size in the first place.

 I guess this is the task of the Plasmashell then? Does the widget communicate its optimal size / ratio?
Comment 3 Patrick Silva 2022-10-29 15:06:03 UTC 
Possibly duplicate of bug 442703
Comment 4 Nate Graham 2022-10-31 18:08:37 UTC 
*** This bug has been marked as a duplicate of bug 442703 ***