[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #14 from Andrey --- OK, can see it now on Virtual Box. No Guest additions are needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #13 from guimarcalsi...@gmail.com --- (In reply to guimarcalsilva from comment #12) > (In reply to Andrey from comment #10) > > (In reply to guimarcalsilva from comment #0) > > > ADDITIONAL INFORMATION > > > > > > VMWare open-tools package installed for drivers. > > Are VMWare open-tools essential for the problem? I couldn't reproduce on > > VirtualBox with Guest Additions installed. > > Sorry, I don't have access to the virtual machine right now, but I was > indeed using open-tools instead of guest additions. I don't know if it's > reproducible with guest additions. > > I gotta add I was using Windows 10 as the guest. I mean, Windows 10 as the host. Also, I couldn't get guest additions to work, that's why I was using open-tools. I'll try to get it to work and see if I can reproduce the issue. If there's any kind of logs or other useful information I can provide please let me know. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #12 from guimarcalsi...@gmail.com --- (In reply to Andrey from comment #10) > (In reply to guimarcalsilva from comment #0) > > ADDITIONAL INFORMATION > > > > VMWare open-tools package installed for drivers. > Are VMWare open-tools essential for the problem? I couldn't reproduce on > VirtualBox with Guest Additions installed. Sorry, I don't have access to the virtual machine right now, but I was indeed using open-tools instead of guest additions. I don't know if it's reproducible with guest additions. I gotta add I was using Windows 10 as the guest. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 nttkde changed: What|Removed |Added CC||watisthis...@outlook.com --- Comment #11 from nttkde --- I can reproduce in VirtualBox 6.1.16_Ubuntu r140961. Guest Additions of same version installed in the KDE Neon User Edition VM. Guest using Wayland; KDE Neon host using X11. VMSVGA graphics with 3D acceleration enabled. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 Andrey changed: What|Removed |Added CC||butir...@gmail.com --- Comment #10 from Andrey --- (In reply to guimarcalsilva from comment #0) > ADDITIONAL INFORMATION > > VMWare open-tools package installed for drivers. Are VMWare open-tools essential for the problem? I couldn't reproduce on VirtualBox with Guest Additions installed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 hujq changed: What|Removed |Added CC||h...@live.com --- Comment #9 from hujq --- *** Bug 423849 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 Méven Car changed: What|Removed |Added Version Fixed In||5.20.2 Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/1fd9ae618aaf ||8b9fcd5b644fa3039ec782d6355 ||f --- Comment #8 from Méven Car --- (In reply to guimarcalsilva from comment #7) > (In reply to Vlad Zahorodnii from comment #6) > > Git commit 1fd9ae618aaf8b9fcd5b644fa3039ec782d6355f by Vlad Zahorodnii. > > Committed on 16/10/2020 at 17:06. > > Pushed by vladz into branch 'Plasma/5.20'. > > > > platforms/drm: Compute correct cursor transform matrix > > > > Currently, when the DRM platform uses cursor planes, the cursor on > > a rotated output may be cropped because the math behind the current > > cursor transform matrix is off. > > > > In order to fix the cropping issue, this change replaces the current > > cursor transform matrix with the core part of the surface-to-buffer > > matrix, which was written against the wl_output spec. > > Related: bug 427605 > > > > M +39 -11 plugins/platforms/drm/drm_output.cpp > > M +0-1plugins/platforms/drm/drm_output.h > > > > https://invent.kde.org/plasma/kwin/commit/ > > 1fd9ae618aaf8b9fcd5b644fa3039ec782d6355f > > Hi, how can I test these patches? Is it only available on the latest stable > Plasma 5.20? Because I'm testing the latest fully updated Neon >Unstable > Edition< and the bug still persists. Thanks. This fix was part of plasma 5.20.1, but it did not fix this bug. The commit just CC-ed the bug "CCBUG: 427060" which means it might related or of interest for this bug fix. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #7 from guimarcalsi...@gmail.com --- (In reply to Vlad Zahorodnii from comment #6) > Git commit 1fd9ae618aaf8b9fcd5b644fa3039ec782d6355f by Vlad Zahorodnii. > Committed on 16/10/2020 at 17:06. > Pushed by vladz into branch 'Plasma/5.20'. > > platforms/drm: Compute correct cursor transform matrix > > Currently, when the DRM platform uses cursor planes, the cursor on > a rotated output may be cropped because the math behind the current > cursor transform matrix is off. > > In order to fix the cropping issue, this change replaces the current > cursor transform matrix with the core part of the surface-to-buffer > matrix, which was written against the wl_output spec. > Related: bug 427605 > > M +39 -11 plugins/platforms/drm/drm_output.cpp > M +0-1plugins/platforms/drm/drm_output.h > > https://invent.kde.org/plasma/kwin/commit/ > 1fd9ae618aaf8b9fcd5b644fa3039ec782d6355f Hi, how can I test these patches? Is it only available on the latest stable Plasma 5.20? Because I'm testing the latest fully updated Neon >Unstable Edition< and the bug still persists. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #6 from Vlad Zahorodnii --- Git commit 1fd9ae618aaf8b9fcd5b644fa3039ec782d6355f by Vlad Zahorodnii. Committed on 16/10/2020 at 17:06. Pushed by vladz into branch 'Plasma/5.20'. platforms/drm: Compute correct cursor transform matrix Currently, when the DRM platform uses cursor planes, the cursor on a rotated output may be cropped because the math behind the current cursor transform matrix is off. In order to fix the cropping issue, this change replaces the current cursor transform matrix with the core part of the surface-to-buffer matrix, which was written against the wl_output spec. Related: bug 427605 M +39 -11 plugins/platforms/drm/drm_output.cpp M +0-1plugins/platforms/drm/drm_output.h https://invent.kde.org/plasma/kwin/commit/1fd9ae618aaf8b9fcd5b644fa3039ec782d6355f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #5 from Vlad Zahorodnii --- Git commit 3b8e489b6f384239cbe30a2dccc064a4ecc2c9bd by Vlad Zahorodnii. Committed on 16/10/2020 at 17:03. Pushed by vladz into branch 'master'. platforms/drm: Compute correct cursor transform matrix Currently, when the DRM platform uses cursor planes, the cursor on a rotated output may be cropped because the math behind the current cursor transform matrix is off. In order to fix the cropping issue, this change replaces the current cursor transform matrix with the core part of the surface-to-buffer matrix, which was written against the wl_output spec. Related: bug 427605 M +39 -11 plugins/platforms/drm/drm_output.cpp M +0-1plugins/platforms/drm/drm_output.h https://invent.kde.org/plasma/kwin/commit/3b8e489b6f384239cbe30a2dccc064a4ecc2c9bd -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #4 from Vlad Zahorodnii --- Aren't VM cursors just regular cursor planes? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 Méven Car changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||meven@enioka.com --- Comment #3 from Méven Car --- We currently miss a proper way to support VMs cursors. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #2 from guimarcalsi...@gmail.com --- (In reply to Vlad Zahorodnii from comment #1) > Can you please run kwin with KWIN_FORCE_SW_CURSOR=1 and check whether the > cursor position is still off? Yes, forcing KWIN_FORCE_SW_CURSOR=1 does fix the issue. The shadows under the cursor are a bit buggy sometimes but the cursor position is fixed when using it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 --- Comment #1 from Vlad Zahorodnii --- Can you please run kwin with KWIN_FORCE_SW_CURSOR=1 and check whether the cursor position is still off? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427060] Cursor "hit box" is offset under Wayland (VMWare)
https://bugs.kde.org/show_bug.cgi?id=427060 guimarcalsi...@gmail.com changed: What|Removed |Added CC||guimarcalsi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
