I'm not sure if this is a KDE Frameworks bug QT bug or Wayfire bug but it only happens in Qt applications on Wayland in Wayfire (it may happen in other window managers like Sway). Run `QT_SCALE_FACTOR=2 dolphin` (or `QT_WAYLAND_FORCE_DPI=192 dolphin`) to adjust the scaling. Dolphin works, the keyboard inputs are recognized but the mouse pointer does not register clicks (or registers them in the wrong place on the screen) The console prints: QImage::pixel: coordinate (0,0) out of range which does not come up when running without setting the scale factor. Without the scale factor Dolphin (or other kde apps) works perfectly, it's only when setting QT_SCALE_FACTOR (and number <> 1) that things break. As such, it seems to be a frameworks issue, not a compositor issue. When it's set KDE applications (e.g. Dolpin, ktorrent) do not accept cursor clicks correctly.
Does this happen with any non-KDE app that uses Qt, e.g. qBittorent?
> Does this happen with any non-KDE app that uses Qt, e.g. qBittorent? No, qBittorrent is fine, it scales as expected and the cursor can be used to interact with the buttons when it is directly over them.(In reply to Nicolas Fella from comment #1)
In any case it's most likely not a KDE Frameworks issue, but I can't really tell whether it's Qt or Wayfire. trying with Weston or some other Wayland compositor would tell more
The same thing happens on Sway (the cursor events are ignored). However, Weston is a little different. If I: - Set scale factor to 2 - Maximize the window Click events can be registered, as normal and in the correct location, in the top left quarter of the screen (which would be the size it would be drawn without the scale factor). Outside that quarter (the other 3/4 of the screen) no click events are registered at all. Strangely, this doesn't happen with Wayfire or Sway. No pointer events are registered at all in those. The issue appears to be the way the applications register the area of the screen which accepts pointer events though it's different in Sway/Wayfire and Weston. It's not the cursor position itself though, and the window has not frozen. It's only left/right click events which are ignored. If I use the mouse wheel while hovering over various panels in dolphin, the correct panel gets scrolled down. Except, if I click on the scrollbar, the panel is scrolled down slightly.
For reference, I thought I'd try a few other applications to see if there is a common denominator: VLC: Scales correctly, clicks are registered octopi (package manager): Sales correctly, clicks are not registered Filezilla: Scale is not applied (I'm pretty sure it uses Qt) Elisa: Scales correctly, clicks are registered. Interestingly, this one is a KDE application, though I'm not sure if it uses frameworks as it does look different to the others. kdenlive: Scales correctly, clicks are broken (expected, as it's a kde frameworks application) systemsettings5: Scales correctly, clicks are broken (expected, as it's a kde frameworks application) OBS Studio: Scales correctly, clicks are broken on some elements. Resizing/dragging the video works, the menu does not, buttons do not and the entire panel at the bottom does not respond to clicks. So a mixed bag. Should I report this to Qt? It's not all Qt apps which are affected, and Elisa is definitely Qt5 so it's strange that works. Whereas OBS is not using KDE frameworks at all and that's affected.
Sorry for keeping posting here, but something else strange is going on... QT_WAYLAND_FORCE_DPI works as expected until 143. As soon as I set it to 144, clicks stop registering. However: 1. 144 looks significantly larger than 143 (I should not be able to tell the difference 144 and 143 without comparing them side by side) 2. The default dpi is 96 (verified by comparing launching with it forced to 96 and not set at all). It can't be a coincidence that 144 is a scale factor of exactly 1.5 and it's at exactly 1.5x DPI that things break. There must be something in the code that says if the scale >= 1.5 handle it differently. But, strangely, a scale factor of < 1.5 does not work either (with QT_SCALE_FACTOR=1.1 the click events are still broken, but scaling using QT_WAYLAND_FORCE_DPI works fine until the equivalent of 1.5x.
>Run `QT_SCALE_FACTOR=2 dolphin` (or `QT_WAYLAND_FORCE_DPI=192 dolphin`) to adjust the scaling That isn't something you should be doing. If you're on wayfire scaling comes from the wayland interfaces, setting anything is unsupported.
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!