Bug 308748 - Page One defunct
Summary: Page One defunct
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Plasma
Component: plasma-netbook (show other bugs)
Version: 4.9.2
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-21 12:03 UTC by Harald Sitter
Modified: 2018-06-08 18:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
broken page one (620.31 KB, image/png)
2012-10-21 12:04 UTC, Harald Sitter
Details
working page 2 (628.38 KB, image/png)
2012-10-21 12:05 UTC, Harald Sitter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Sitter 2012-10-21 12:03:06 UTC
This are actually two bugs, but since I believe the root cause to be the same I'll outline them both in one report.

On Kubuntu 12.10 'Page One' as created by the default layout script is utterly broken. Please note however that the entire Kubuntu team fails to replicate this on notebooks even when forced into exactly the same settings we apply on netbooks (no cd drive, screen resolution < some rather small values). On actual netbooks it is however reproducible even without our settings overlay. That being said for me the issues appear reliably at a 1024x576 display resolution.
https://bugs.launchpad.net/ubuntu/+source/kdeplasma-addons/+bug/1066861

Primarily what happens is that once you try to go to Page One it will lock up and eat memory until bad_alloc. During which time it is stuck in Qt internal polygon splitting invoked by QPaintPath. As the launchpad bug mentions this is at the fault of the opendesktop (community) plasmoid. In particular it most of the time gets stuck in contactimage.cpp::paint when it tries to do drawRoundedRect (border always 1, r usually (0, 0, 38x38) - both in line with what resizeEvent tells contactimage, so that is funny). 

Once one removes that problem another one appears... the layout on Page One is completely kaput. No plasmoid has content, they all are on the far left edge on top of each other (also see screenshot), there is no cashew and trying to move the page will trigger partial apperance of the cashew (though not clickable) along with painting fragments. Visually you mostly get different results per run, but never what it is supposed to look like. Playing with the RC file changes absolutely nothing and it appears there is no particular difference between the autogenerated page one and a manually created page with same content (on a config file level).

The issues are not affected by desktop effects, neither does changing the layout template to only add one widget help.

Reproducible: Always
Comment 1 Harald Sitter 2012-10-21 12:04:34 UTC
Created attachment 74694 [details]
broken page one
Comment 2 Harald Sitter 2012-10-21 12:05:04 UTC
Created attachment 74695 [details]
working page 2
Comment 3 Nick Shaforostoff 2012-10-23 17:00:02 UTC
does anyone have information on when this issue has appeared? (like old development images of kubuntu and so on)? knowing the time the problem was introduced will gratly help to fix the issue ;)
Comment 4 Donatas Glodenis 2013-07-15 07:53:17 UTC
Question: what happens if you delete page one? Is Page 2 still ok?

There might be a related bug here: https://bugs.kde.org/show_bug.cgi?id=320330  My page one got to look the same way as your "broken page one" when I changed the configuration file.

I run kubuntu 13.04 on Asus EEEPC 900.
Comment 5 Nate Graham 2018-06-08 18:53:35 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham