Summary: | Widget-pager with visual bug after restart | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Hans-Rudi Denzler <hr.denzler> |
Component: | widget-pager | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | laidig, ua_bugz_kde |
Priority: | NOR | ||
Version: | 4.9.2 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
visual bug
image of incorrect size of virtual desktops and some style corruption |
Description
Hans-Rudi Denzler
2012-09-13 11:34:17 UTC
Created attachment 73886 [details]
visual bug
Same here. This does not happen every start though but >90% of the time. This happens with raster and native (both with OpenGL). Slightly resizing the widget and it is absolutely back to normal. Details: KDE 4.9.2, Qt 4.8.3, gcc 4.7.2, Gentoo x86_64 Created attachment 74358 [details]
image of incorrect size of virtual desktops and some style corruption
(In reply to comment #3) > Created attachment 74358 [details] > image of incorrect size of virtual desktops and some style corruption I should add: Oxyglass style. Confirmed by duplicates. This is still very much a problem w/ KDE 4.9.97 and seems to be even more pronounced: The virtual desktop displays are diagonally offset by approx. 1/3 out of the total widget space until the widget is resized. A clue: If most of the kdelibs and all of Qt is compiled as debug version, this does not happen (at least not in KDE 4.9.x). As soon as you switch to release builds, weirdness ensues again. :( Since Qt does several more sanity checks in its debug build, this is either a race-condition or something that gets fixed by accident (through some debug conditional logic) in the debug build. Forgot to add: With KDE 4.9.97 this most definitely happens with every start. With today's 4.10 branch, the problem is fixed. I was unable to reproduce this anymore. After further investigation: This bug seems to be a duplicate of bug#306414 which was fixed very recently. *** This bug has been marked as a duplicate of bug 306414 *** |