Bug 421887 - After scaling the screen all windows get bold black frames when using Aurorae window decorations
Summary: After scaling the screen all windows get bold black frames when using Aurorae...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: aurorae (show other bugs)
Version: 5.18.5
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-21 23:25 UTC by thomsonmx
Modified: 2023-09-06 10:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description thomsonmx 2020-05-21 23:25:41 UTC
SUMMARY
In Kubuntu 20.04 or Neon 18.04: when you scale the screen for example to 125%, all windows get a bold black border (window decoration / aurorae) even if no window border was set.

STEPS TO REPRODUCE
1. Go to the settings and set the display scaling to 125 %
2. All windows get a bold black frame - even if you set "nor borders".
3. You can test it with the window decoration (aurorare) "Qogir".

OBSERVED RESULT
s. above.

EXPECTED RESULT
Windowd do not change by scaling the screen. No border frame. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: neon 18.04 and Kubuntu 20.04 
(available in About System)
KDE Plasma Version: 5.18.x
KDE Frameworks Version: ?
Qt Version: ?

ADDITIONAL INFORMATION
Comment 1 thomsonmx 2020-05-31 11:38:04 UTC
Meanwhile after some minor updates I confirm the problem:

a) Boot without power supply => black screen even before login dialog
b) Boot with power supply and then after login working normally, then after a standby => black screen.

I am using Kubutu 20.04. on Thinkpad T495 (AMD Ryzen 3500U CPU with Vega mobile Graphics).
Comment 2 thomsonmx 2020-05-31 11:53:47 UTC
Sorry: my last comment concerning the "black screen" problem was wrong here. It belongs to another bug. You can delete it here. 

But the scaling problem still exist.
Comment 3 thomsonmx 2020-09-09 18:58:51 UTC
You changed the summary so that the problem hapens only when "quogir" aurorare windows decoration is used. This is NOT correct. The scaling problem happens to many other decorations too like: "McMojave-light",  "WhiteSur", "Artim-Dark", "Arc Dark", "Arc" and many more. Only "Breeze" works as expected.
Comment 4 Nate Graham 2020-09-09 19:09:41 UTC
It was just meant to be an example, not an implication that it happens with only that theme.
Comment 5 thomsonmx 2020-09-09 19:14:45 UTC
ok, i understand, but then it was a bit misleading. Any chance to fix it soon? It is quite important on typial 14 inch screens with smaller screens with high (Full HD) resolutions.
Comment 6 David Edmundson 2020-09-19 21:19:30 UTC
>1. Go to the settings and set the display scaling to 125 %

X or wayland?
Comment 7 thomsonmx 2020-09-20 15:14:15 UTC
kubutu standard = X.
Comment 8 Bug Janitor Service 2020-10-05 04:33:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Christoph Feck 2020-10-06 03:58:04 UTC
Requested information was added with comment 7; changing status for inspection.
Comment 10 thomsonmx 2020-10-06 07:25:04 UTC
I wrote in Cmment #7 that I use standrad Kubuntu. So it is xorg.
Comment 11 David Edmundson 2023-09-06 10:38:48 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.