with multiply pointer settings, the only "all screen reuse" could not cause the after image, but will cause the "flashing cursor". environment: kubuntu 13.10 kde 4.11.3 nvidia 331.20 Reproducible: Always Steps to Reproduce: 1. xinput create-master New 2. use "xinput list" to check the second cursor 3. use "xinput reattach <id> <Master>" to attach the second cursor to the another master <id> is the second mouse id, <Master> is the second master id.
cursors are managed by X. I cannot see why KWin's rendering strategy affects the cursor. Sounds very much like a problem deeper in the stack to me.
please provide: - qdbus org.kde.kwin /KWin supportInformation - /var/log/Xorg.0.log "qdbus" maybe "qdbus-qt4" or you might have to install some "qtchooser" package
Created attachment 83839 [details] Xorg log
Created attachment 83840 [details] kwin information
this is the video tutorial for the multiply mouse. i only found the vsync settings will affect the multiply mouse render http://www.mediafire.com/download/svf111v13g6yq1f/kde_mouse.ogv
> [ 29.076] (==) NVIDIA(0): Silken mouse enabled Hardware mouse: check. Triple buffering, single screen. @l12436@yahoo.com.tw please try to disable blur caching ("kcmshell4 kwincompositing", 2nd tab, filter for blur, config button, the only checkbox in the dialog)
The "black block" artifact is (probably) bug #213281
yep, he has use the same function.
i have disable blur, it seems a affect with transparent window. but the afterimage cursor and flashing is not solved
I assume it's related. The driver will likely somehow "fake" the second cursor into the frontbuffer from where we (invalidly) read it back for the next frame. This should simply be gone with GLX_EXT_buffer_age preference.
i can not found that how to enable that extension in kwin. i just saw compiz.
(In reply to comment #11) > i can not found that how to enable that extension in kwin. you can't yet and it will be used by default.
By now the version 4.x is unmaintained. Our rendering infrastructure in KWin 5 changed a lot, e.g. buffer age support is available and used by default. It is unlikely that this problem still exists exactly like this for the newer code base. If you still experience it with KWin 5 I kindly ask you to report a new bug. Thank you for reporting this bug report and helping making KDE software better.