| Summary: | maximized decoration is not stretched to window width | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | S. Christian Collins <s_chriscollins> |
| Component: | aurorae | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 4.11.6 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot showing the bug | ||
|
Description
S. Christian Collins
2014-02-24 14:42:58 UTC
Created attachment 85308 [details]
screenshot showing the bug
See http://forum.kde.org/viewtopic.php?f=111&t=120953#p309602 There seems an issue with svg parsing in either plasma components, or qt/qml or some svg lib or the combination of all. If you can confirm the "workaround" as well, this is most likely not a bug in KWin/Aurorae but somewhere deeper. I read through the linked thread, and decided to do some testing. All I have to say is: there is something *really weird* going on here. Here are my test results:
1. Every theme I own that contains the "decoration-maximized-center" element exhibits this bug. I decided to do my testing using a theme that I am currently developing called "Frosty". I can provide the files for this theme if necessary, but I would bet that the behavior I discovered can be reproduced with any theme containing the "decoration-maximized-center" element.
2. Aurorae seems to use some caching of the SVG elements, and I found it necessary to disable and then re-enable compositing (shift-alt-F12) to refresh these elements. All-in-all, my steps between each change to the decoration.svgz file included:
a) Changing the window decoration to Oxygen and then back to Frosty. After this step, Aurorae still wouldn't show the changes I had made.
b) Disabling and re-enabling compositing. Now Aurorae would show the changes I had made.
3. I made a backup of the decoration.svgz file to "decoration.svgz.BROKEN", then followed the steps in the forum thread linked in comment #2:
a) Changed the color of the "decoration-maximized-center" element. Result: the color changed, but the bug still remained.
b) Renamed the "decoration-maximized-center" element to "decoration-maximized-top". Result: no change.
c) Renamed it back to "decoration-maximized-center". Result: no change.
4. I was about to post that following the steps had made no difference for me when I decided to play with the SVG element some more. I tried the following things in this order:
a) removed a couple of the group elements
b) removed everything from the group except one object and named that object "decoration-maximized-center" (i.e., no group present, just naming the individual object)
c) adding a couple more elements to the group
d) playing around with the naming some more (named it "poop", then back to "decoration-maximized-center")
5. It was after step "d" above that suddenly Aurorae began stretching the "decoration-maximized-center" element. I remember being puzzled, because this was after one of many attempts at renaming the maximized SVG element. Why did it work *this time* and not the others?
6. I made a backup of this version of the decoration.svgz to "decoration.svgz.WORKS", then I removed the additional elements from the maximized SVG group I had added in 4.c above. Result: the maximized decoration still worked.
7. I decided to see if the problem really was with the svgz file, so I replaced the decoration.svgz with the original backup. Result: decoration is still stretched, even with the old svgz! WTF?!
8. I figured that perhaps the Aurorae cache wasn't being fully updated since the backup decoration.svgz had an older timestamp, so I made a quick change to the file and saved it to update the timestamp: Result: decoration still stretched.
9. I moved my "Frosty" theme to a new folder, which I renamed "Frosty-blah", and I updated the theme name in the "metadata.desktop" and "Frostyrc" files (which I renamed "Frosty-blahrc") as well. I then loaded this new theme. Result: bug returns; maximized element is no longer stretched.
10. I then replaced "decoration.svgz" with the backup of the svgz that had supposedly fixed the bug. Result: bug still remains.
Needless to say, I am thoroughly confused. Perhaps there is something weird with the caching going on?
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! I can no longer reproduce this bug using KDE neon Developer Edition Git-Unstable. Closing as fixed. |