Scaling issues

[RubenKelevra]

• OS: ArchLinux / KDE
• Version of IPFS Desktop 0.46.0

Describe the bug
I'm using KDE 6.4.5 (Framework versions 6.18.0 and 6.19.0; QT-Version 6.9.2 and 6.10.0) and with a scaling factor of 70%.

Version 0.45.0 of the IPFS Desktop works normally, but IPFS Desktop 0.46.0 has heavy scaling issuing:

• The "full screen" is not full screen but only a section of the screen in the left upper corner.
• The Mouse is offset, so clicking on elements only work if the mouse is not over the element, but below on the right of them (scaling is basicly applied but not properly translated to the application).
• The Logo screen in the beginning is weirdly cutoff.

To Reproduce
Steps to reproduce the behavior:

1. Open app
2. See error

Expected behavior
Same scaling behavior as on 0.45.0

Screenshots
Here's an example of a "full screen" of IPFS Desktop 0.46.0:

[RubenKelevra]

Whatever caused the regression was fixed in one of the system libraries, as it's now working fine. I've updated the package in the AUR.

[RubenKelevra]

Sorry, I was to quick to dismiss it. Just had no scaling turned on for my internal monitor. On the external one it's broken as it was before.

Downgraded the AUR package again. This is a blocker IMHO.

[RubenKelevra]

Can confirm it with KDE Framework versions 6.19.0 as well as QT version 6.10.0 as well - updated initial report to reflect that.

[lidel]

Thank you for reporting! The Electron version changed from 37 to 38, and regression related to Wayland there would be my main suspect, iiuc Waylant support through Ozone is opt-in now.

@RubenKelevra are you able to test with different launch methods to see if anything of the below makes any difference?

• ELECTRON_OZONE_PLATFORM_HINT=wayland
• ELECTRON_FORCE_SCALE_FACTOR=1.0 (tells Electron to "Render everything at 100% internally, don't try to scale", this sounds counterintuitive but could let the OS/display server (KDE) handle ALL the scaling uniformly)
• ELECTRON_FORCE_SCALE_FACTOR=0.7 - just to see if it does anything
• GDK_BACKEND=x11 - just to see if forcing legacy x11 helps

[lidel]

@RubenKelevra is this still happening with the latest version, or can we close this?

[RubenKelevra]

@lidel sorry for the delay: My main computer is currently broken. I'll have a look if I can reproduce it on a secondary one in the older version later and report back.

[RubenKelevra]

I can't reproduce it on a freshly installed ArchLinux with Wayland with scaling on. So my assumption is, that an underlying library has been fixed.