Bug 391359 - System Monitor Plasma Widgets break rendering in Plasma Shell
Summary: System Monitor Plasma Widgets break rendering in Plasma Shell
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.12.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-03 22:19 UTC by Dan
Modified: 2018-03-06 23:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Broken rendering in plasmashell (61.56 KB, image/png)
2018-03-03 22:19 UTC, Dan
Details
qdbus org.kde.KWin /KWin supportInformation > Kwin-info.txt (4.75 KB, text/plain)
2018-03-06 21:32 UTC, Dan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan 2018-03-03 22:19:54 UTC
Created attachment 111168 [details]
Broken rendering in plasmashell

Widgets part of org.kde.plasma.systemmonitor seem to break rendering when added to plasmashell after my latest update.

Version of Plasma installed:
extra/plasma-desktop 5.12.2-1 (plasma) [installed]
    KDE Plasma Desktop
extra/plasma-framework 5.43.0-1 (kf5) [installed]
    Plasma library and runtime components based upon KF5 and Qt5


The only widget that appears to not break rendering is Disk Usage. Everything else will cause the widget appearance to turn completely black. This rendering bug persists after removing the widget, but if the widget is removed and you stop and start a new session, rendering is restored. It occurs irrelevant of the Desktop theme used for me. 

Attached is a screenshot.
Comment 1 Dan 2018-03-06 21:32:02 UTC
Created attachment 111233 [details]
qdbus org.kde.KWin /KWin supportInformation > Kwin-info.txt

Should this be relevant
Comment 2 Dan 2018-03-06 22:20:36 UTC
OK, so I've located the source of this issue:

An upgraded library libepoxy 1.5.0-1 was the source of the rendering issues.

I downgraded to libepoxy-1.4.3-1 and the widgets now render properly.

I don't think this is a KDE bug.
Comment 3 David Edmundson 2018-03-06 23:20:52 UTC
thanks for reporting back