| Summary: | Addtional mouse pointers disappear and cause corruption when compositing is enabled | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Alec Moskvin <alecm> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | alve, darupeter, kde.org, khonspam |
| Priority: | NOR | Flags: | mgraesslin:
X11+
|
| Version First Reported In: | 6.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=328242 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Screenshot of corruption
Screenshot of corruption Screenshot of corruption |
||
Created attachment 38117 [details]
Screenshot of corruption
Here's a screenshot of the corruption. Unfortunately, there's no way to capture the pointer, but it would be in the middle of the black square.
MPX is currently not yet supported in kwin. There is someone who wants to add support for it. Nevertheless this looks to me like an X bug. Is this still an issue with a later release of X server (e.g 1.7)? while i doubt MPX is supported in KWIn, or that this is a compositing/GL issue (but a framebuffer one) and repeating question from comment #3: is this still an issue? (i can create both pointers but only one moves - the other one is in the center of the screen and follows the shape of the moving one. This is however regardless of compositing) Created attachment 70271 [details]
Screenshot of corruption
Sorry, missed Martin's comment.
I tried it again, and yes, it still happens - see the attached screenshot.
This is with KWin 4.8.2 on X.Org server 1.12.0 with Intel graphics (the original report was with NVidia, most likely proprietary driver)
Not that it really matters since there's no MPX support...
Created attachment 70272 [details]
Screenshot of corruption
nope, i managed to get the mouse moving but the issue did not even occur with activated blur on a gma945. does it happen with the xrender backend as well? Have you tried switching windows (especially with windows of contrasting colors)? I didn't even need to move the second pointer. As for XRender - I can't reproduce with it, so it looks like it just affects the OpenGL backend. kwin, not kwin_gles, i assume? please post output of "kwin --replace &" and "grep -iC5 mouse /var/log/Xorg.0.log" and attach "~/.kde/share/config/kwinrc" and "glxinfo -l > myglx.info" *** Bug 341148 has been marked as a duplicate of this bug. *** This issue report is quite old. Can you please confirm, that it still persists with KDE 5.23? 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! (In reply to kde.org from comment #11) > This issue report is quite old. Can you please confirm, that it still > persists with KDE 5.23? I can confirm that this is still an issue in plasma 5.23 This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number. I know whole plasma moved to wayland, but would be cool if someone managed to fix this. Or maybe provide alternative for wayland how to have virtual pointers. Same thing, create virtual pointer using xinput. Core pointer looks fine but new one is flickering. Also, looks to me, the issue is worse on nvidia graphics (mine gtx 1660). I tried to recreate same thing on intel and it only flickers. On nvidia I got visual glitches in "10px" radius from cursor stucked window parts etc. |
Version: (using KDE 4.3.3) Compiler: gcc (Gentoo 4.4.2 p1.0) 4.4.2 OS: Linux Installed from: Gentoo Packages When there are two mouse pointers in X11R7.5, one of them randomly flickers, disappears, gets stuck and causes display corruption in a rectangle around it when compositing is enabled. This does not happen with compositing disabled. To reproduce: 1. Attach two mice to the computer (or a mouse to a laptop :) 2. $ xinput create-master blah 3. $ xinput list You should see both devices in "Virtual core pointer" 4. $ xinput reattach 6 11 (where the '6' is the if of one of the mice and '11' is the id of "blah pointer") 5. Do some stuff (move a window, for example) with each pointer. One of the will work fine, the other one will act badly. Again, this only happens with compositing enabled. Without it, they work mostly as expected.