This issue has only popped up in the last few days (probably last update). I have a machine running twinview using the nVidia binary driver and the nVidia control panel with a second monitor configured to the rightt. If I try to access a hot corner on the right side of the virtual screen the mouse warps to the left side of the secondary screen. Also when maximising a application by dragging it to the top of the screen it appears on the primary screen not the secondary. Reproducible: Always Steps to Reproduce: 1. enable twinview with secondary screen to the right of the primary. 2. attempt to activate a hot corner on the right side of the virtual screen. 3. attempt to maximise window on the secondary screen by dragging it to the top of the screen. Actual Results: 2.mouse warps to left edge of secondary screen 3. window maximises on primary screen rather than secondary. Expected Results: 2. mouse activates hot corner trigger (let's say show desktop). 3. window maximises to cover current screen. maximising the window by any other means works correctly.
new piece of information - if I try to maximise by dragging a window on the primary display. the cursor gets warped to the top left corner of the primary display.
bug #301777 resp. bug #180421 do you use a touchdevice?
yes I have a synaptics touchpad that is multitouch. I just tried it with the point stick and it did not display the same behaviour
Thanks for the update - see comment #29 in the dupe for a workaround. It's a bug in the synaptics driver - i don't knwo about the condition there, but if they refuse to or can't fix it, we may have to adjust the default value :-( *** This bug has been marked as a duplicate of bug 301777 ***
I think the duplicate marking might be a little hasty. Though it is probably related. 1) top left corner and bottom left corner work just fine. 2) I noticed the behaviour today, I am certain I didn't have this bug last week. I checked the package updates and there have been no updates to synaptics package for months. The kernel has been updated in the last week though
From our side, it's the same bug. KWin does absolutely not know or care about the pointer device. Situation is: "for some (synaptics) input devices pointer warping is broken" This can be related to twinview (what's not a "multihead" setup, but that's minor) in this case, but if increasing the pushback distance works for you, so that the y target becomes > 1 - it's essentially the same bug (though might be a different source in the kernel/driver, but that does not matter here)