Summary: | Krunner has broken shadow / corners | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | soee <kontakt> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bshah, jr, plasma-bugs-null, vmorenomarin |
Priority: | NOR | ||
Version First Reported In: | 5.6.95 | ||
Target Milestone: | 1.0 | ||
Platform: | Neon | ||
OS: | Linux | ||
URL: | http://i.imgur.com/8qUPVhm.png | ||
Latest Commit: | http://commits.kde.org/kwin/62d09fad123d9aab5afcff0f27d109ef7c6c18ba | Version Fixed In: | |
Sentry Crash Report: | |||
Attachments: | Other dropdowns have the same problem |
Description
soee
2016-07-05 09:09:49 UTC
The reporter is using KDE neon User Edition with Plasma 5.7 I also get this on KDE neon Developer Edition unstable branches (git master, 5.7.90) doesn't happen on a fresh install. may be due to upgrading from Plasma 5.6 More stupid cache problems. Let us know if you see it again. Indeed it was cache issue. I have removed ~/.cache and /var/tmp/kdecache-$USER and the problem is gone. I don't know why but this problem is back. It was working fin for some time but all of sudden is roken again and i'm not sure why :/ Created attachment 99875 [details]
Other dropdowns have the same problem
The dropdown in panel settings has the same issue.
Update in case I get hit by a bus over lunch. After a morning in gammaray - the framesvg behind krunner is absolutely fine right pixmaps, right geometry. Problem seems to be within dialogshadows/kwin. Debug in dialog shadow looks fine (plus it's not changed) So I built kwin5.6, and that renders fine. Git commit 62d09fad123d9aab5afcff0f27d109ef7c6c18ba by David Edmundson. Committed on 06/07/2016 at 12:16. Pushed by davidedmundson into branch 'Plasma/5.7'. Fix shadow rendering calculations Reviewers: #plasma Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2100 M +3 -2 scene_opengl.cpp http://commits.kde.org/kwin/62d09fad123d9aab5afcff0f27d109ef7c6c18ba *** Bug 365168 has been marked as a duplicate of this bug. *** |