| Summary: | On X11, pointer position offset after moving window outside the left edge of screen space | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Mio Nekoya <admin> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | bozic.erik, dashonwwIII, dev, fabianmuehlberger, fandrew, fanzhuyifan, florian, godsbball, johnramsden, jonstelly, kde-yyds, kokoko3k, mihai.bazon, nate, norbert, proxyx, tgnff242 |
| Priority: | HI | Keywords: | regression |
| Version: | 6.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=482920 | ||
| Latest Commit: | https://invent.kde.org/plasma/kwin/-/commit/369c3cbd7d843b6ce2901adf8b464158f84759a1 | Version Fixed In: | 6.0.2 |
| Sentry Crash Report: | |||
| Attachments: |
Offset in action
kwin x11 offset even with patch applied screencast |
||
*** Bug 482688 has been marked as a duplicate of this bug. *** *** Bug 482577 has been marked as a duplicate of this bug. *** *** Bug 482743 has been marked as a duplicate of this bug. *** Can reproduce on X11, on both master and 6.0.1 First bad commit is 904c33556b5a39e10e36d742c53d534e3d206f1b: https://invent.kde.org/plasma/kwin/-/commit/904c33556b5a39e10e36d742c53d534e3d206f1b A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/5382 Git commit ea4fa87bc61f14f159bda75bea2248731911a5ba by Yifan Zhu. Committed on 08/03/2024 at 19:25. Pushed by fanzhuyifan into branch 'master'. utils/xcbutils: Don't call toXNative with unsigned integer Instead use signed integers, to prevent the implicit cast from unsigned integers to qreal. M +4 -4 src/utils/xcbutils.h M +2 -2 src/workspace.cpp https://invent.kde.org/plasma/kwin/-/commit/ea4fa87bc61f14f159bda75bea2248731911a5ba Git commit 369c3cbd7d843b6ce2901adf8b464158f84759a1 by Yifan Zhu. Committed on 08/03/2024 at 19:34. Pushed by fanzhuyifan into branch 'Plasma/6.0'. utils/xcbutils: Don't call toXNative with unsigned integer Instead use signed integers, to prevent the implicit cast from unsigned integers to qreal. (cherry picked from commit ea4fa87bc61f14f159bda75bea2248731911a5ba) M +4 -4 src/utils/xcbutils.h M +2 -2 src/workspace.cpp https://invent.kde.org/plasma/kwin/-/commit/369c3cbd7d843b6ce2901adf8b464158f84759a1 *** Bug 482820 has been marked as a duplicate of this bug. *** *** Bug 482812 has been marked as a duplicate of this bug. *** *** Bug 482975 has been marked as a duplicate of this bug. *** *** Bug 482956 has been marked as a duplicate of this bug. *** *** Bug 482878 has been marked as a duplicate of this bug. *** (In reply to fanzhuyifan from comment #8) > Git commit 369c3cbd7d843b6ce2901adf8b464158f84759a1 by Yifan Zhu. > Committed on 08/03/2024 at 19:34. > Pushed by fanzhuyifan into branch 'Plasma/6.0'. > > utils/xcbutils: Don't call toXNative with unsigned integer > > Instead use signed integers, to prevent the implicit cast from unsigned > integers to qreal. [..] > https://invent.kde.org/plasma/kwin/-/commit/ > 369c3cbd7d843b6ce2901adf8b464158f84759a1 I pulled this patch into a local build of kwin on Arch, but it did *NOT* fix the misbehaviour. (In reply to Norbert Preining from comment #14) > I pulled this patch into a local build of kwin on Arch, but it did *NOT* fix > the misbehaviour. Humm I tested on both master and Plasma/6.0, and it fixes the problem for me on top of both branches. Could you share the steps with which you could still reproduce the problem? A screencast would be ideal. Are you still seeing this for all windows on X11? Thanks! *** Bug 482920 has been marked as a duplicate of this bug. *** *** Bug 482925 has been marked as a duplicate of this bug. *** (In reply to fanzhuyifan from comment #15) > Could you share the steps with which you could still reproduce the problem? > A screencast would be ideal. I attach one > Are you still seeing this for all windows on X11? I tested konsole and system settings, both in screencast to be seen. That is based on Arch Linux kwin 6.0.1-3 with 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch applied. Build log shows: > ==> Making package: kwin 6.0.1-3.1 (Mon 11 Mar 2024 08:55:03 AM JST) > ==> Checking runtime dependencies... > ==> Checking buildtime dependencies... > ==> Retrieving sources... > -> Found kwin-6.0.1.tar.xz > -> Found kwin-6.0.1.tar.xz.sig > -> Found 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch > ==> Validating source files with sha256sums... > kwin-6.0.1.tar.xz ... Passed > kwin-6.0.1.tar.xz.sig ... Skipped > 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch ... Passed > ==> Verifying source file signatures with gpg... > kwin-6.0.1.tar.xz ... Passed > ==> Extracting sources... > -> Extracting kwin-6.0.1.tar.xz with bsdtar > ==> Starting build()... > checking file src/utils/xcbutils.h > checking file src/workspace.cpp > Hunk #1 succeeded at 3020 (offset -1 lines). > -- The C compiler identification is GNU 13.2.1 > ... Created attachment 166925 [details]
kwin x11 offset even with patch applied screencast
(In reply to Norbert Preining from comment #19) > Created attachment 166925 [details] > kwin x11 offset even with patch applied screencast Yeah that definitely looks like this bug. So I can't reproduce if I use kdesrc-build to build kwin tag 6.0.1 + 369c3cbd7d843b6ce2901adf8b464158f84759a1. (I first verified that if I build kwin tag 6.0.1, I can reproduce) I am on arch linux, using Qt 6.7 (with all the testing repos enabled including kde-unstable). (In reply to fanzhuyifan from comment #20) > I am on arch linux, using Qt 6.7 (with all the testing repos enabled > including kde-unstable). Hmmm, looking at https://archlinux.org/packages/?sort=&repo=KDE-Unstable it seems only Qt is updated there at the moment. I am a bit nervous going to a beta version of Qt since this is my work computer. Do you think this is purely depending on Qt updated to 6.7? (In reply to Norbert Preining from comment #21) > Hmmm, looking at https://archlinux.org/packages/?sort=&repo=KDE-Unstable it > seems only Qt is updated there at the moment. I am a bit nervous going to a > beta version of Qt since this is my work computer. > > Do you think this is purely depending on Qt updated to 6.7? I would be very surprised since the relevant code doesn't seem to be related to Qt at all. I'll try testing by rebuilding the arch package with the commit, and also test on neon unstable, which uses Qt 6.6. Do you have any core-testing and extra-testing enabled, by the way? (In reply to fanzhuyifan from comment #22) > Do you have any core-testing and extra-testing enabled, by the way? No, only default repositories (core,extra,multilib) (In reply to Norbert Preining from comment #23) > (In reply to fanzhuyifan from comment #22) > > Do you have any core-testing and extra-testing enabled, by the way? > > No, only default repositories (core,extra,multilib) This might be worth a shot -- can you reproduce if you revert https://invent.kde.org/plasma/kwin/-/commit/904c33556b5a39e10e36d742c53d534e3d206f1b? For me that was the first bad commit. I can't reproduce on neon unstable, which uses Qt 6.6, so we could rule that out. I also can't reproduce if I build the arch package with the patch. None of the packages I installed from extra-testing or core-testing seem remotely related. *** Bug 483185 has been marked as a duplicate of this bug. *** Wait ... I blindly copied a test run to the PKGBUILD and it contained --dry-run ... let me rerun the test without the revert and see if it works Sorry for the confusion, now when I tried to add the other patch for reverting I found the --dry-run Sorry again, with properly applied patch 369c3cbd7d843b6ce2901adf8b464158f84759a1 I cannot reproduce the failure :-( Sorry for the noise! (In reply to Norbert Preining from comment #27) > Sorry again, with properly applied patch > 369c3cbd7d843b6ce2901adf8b464158f84759a1 I cannot reproduce the failure :-( > Sorry for the noise! Glad to hear it's working! You're all good *** Bug 483252 has been marked as a duplicate of this bug. *** *** Bug 483341 has been marked as a duplicate of this bug. *** Yifan's fix is included in kwin 6.0.2, tested from arch kde-unstable repo and it fixes this issue for me. Thanks Yifan! *** Bug 483527 has been marked as a duplicate of this bug. *** |
Created attachment 166569 [details] Offset in action SUMMARY When moving a window partially outside the left edge of the visible screen space, there is an offset between the visible window and cursor hitbox, as if the window is only moved "visibly" but not "actually". Quite annoying as I always move some window out the edge to save some spaces. STEPS TO REPRODUCE 1. Launch anything that has a window and some buttons (e.g. browsers, settings etc) 2. Move it to the very left edge of the screen 3. Move it further so that part of the window is outside 4. Observe the cursor not able to click on buttons OBSERVED RESULT There's an offset to the mouse position relative to the window by the exact distance the window moved outside the screen EXPECTED RESULT No offset of any kind, able to click on where the buttons are visibly at SOFTWARE/OS VERSIONS Arch Linux Linux/KDE Plasma: 6.0.1 KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION