[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 postix changed: What|Removed |Added Version|5.26.3 |5.26.4 Resolution|WAITINGFORINFO

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #13 from Bug Janitor Service --- 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

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #12 from postix --- Now it happened within a session, when I closed PyCharm and reopened it. Could fix it like in comment 9 again. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #11 from postix --- Well, what's described from comment 6 onward doesn't happen always. Maybe there's a racing condition? -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #10 from postix --- (In reply to postix from comment #9) > To comment 6: It helped to set a different scaling factor in kscreen, hit > apply, hit revert and restarting PyCharm: Now it scales with 200% again. Same for GIMP. So for some

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #9 from postix --- To comment 6: It helped to set a different scaling factor in kscreen, hit apply, hit revert and restarting PyCharm: Now it scales with 200% again. -- You are receiving this mail because: You are watching all bug

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 postix changed: What|Removed |Added Attachment #154199|0 |1 is obsolete||

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #7 from postix --- Created attachment 154199 --> https://bugs.kde.org/attachment.cgi?id=154199=edit kWin Support Info: After waking up from suspend -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #6 from postix --- Created attachment 154198 --> https://bugs.kde.org/attachment.cgi?id=154198=edit Screenshot: 5.26.3, PyCharm after waking up from suspend I ran PyCharm w/o setting any env variables and it scaled fine with a factor of

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #5 from Nate Graham --- The system should be setting all necessary environment variables. If it's not, that's another bug. :) The problem with filing bug reports saying, "I applied this workaround and now I have a bug" is that we don't

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #4 from postix --- Nate, you mean it's not supposed to set the scaling now with the "Legacy Applications: Apply scaling themselves" option enabled in the sense of https://wiki.archlinux.org/title/HiDPI#Applications ? -- You are receiving

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #2 from postix --- Created attachment 154133 --> https://bugs.kde.org/attachment.cgi?id=154133=edit kWin Support Info: 2nd screen enabled The application (PyCharm) spontaneously changed 200% scaling while running. The expectation was,

[kwin] [Bug 462389] Legacy Applications: Apply scaling themselves: Scaling changes depending on 2nd screen enabled or not

https://bugs.kde.org/show_bug.cgi?id=462389 --- Comment #1 from postix --- Created attachment 154132 --> https://bugs.kde.org/attachment.cgi?id=154132=edit kWin Support Info: Primary Screen only An application (PyCharm) with GDK_SCALING=1 scaled with 1.0. -- You are receiving this mail