Reported originally by Michal Haško in RH bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=631769 Description of problem: In WindowsXP or Windows7 guest with multimonitor functionality and RHEL6 client, it is impossible to draq (window, icon) from one screen to the other. Not even in fullscreen. It seem there is kind-of transitions between guest <-> client <-> guest when moving mouse cursor from one screen to the other, so the drag is dropped somwhere in between. Version-Release number of selected component (if applicable): WindowsXP guest with sm84 tools RHEL6.0 client: spice-client-0.4.2-18.el6.x86_64 spice-xpi-2.4-1.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Configure 2 monitor RHEL client 2. Configure 2 monitor WindowsXP / Windows7 guest 3. Connect to the guest 4. Try dragging a window from one monitor to the other Actual results: The window is not dragged, stays split on two monitos Expected results: Window should be dragged to the other monitor
Hello is still problem in 0.8 is there anybody going to fix this? This is definitely breaking multi monitor feature.
This is still a problem in 0.8.2. I've reported this in the Debian bugtracker [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641772] but I'll paste my report in here too: When using spice-client in fullscreen mode to connect to a dual head KVM instance (Windows 7; vdservice in use), when I drag items from one screen to the other, the item being dragged stops moving after the pointer crosses to the second screen. When the mouse button is released, the item being dragged is dropped where the pointer was released. If the mouse button is held down and the item is dragged from screen 1 to screen 2 and then back again, the ceases movement while the pointer is on screen 2 but restarts moving when the pointer returns to the first screen. I've tested this mostly with dragging windows around between screens. It happens no matter which screen the dragging starts on: the item always stops moving when the pointer reaches the other screen. Tcpdump shows that no spice protocol traffic occurs while the dragging is occurring over the second screen (i.e. the screen which the dragging did not start on), suggesting that the issue is the client not sending mouse movement events rather than a problem on the server end.
Have you tried this with the gtk-client as well? The underlying problem is that we stop getting the movement event once the cursor leaves the first window, i.e. the window where the click occurred. I'm not sure this is fixable without creating a new invisible window on top of all the windows and using that to catch events, I think that's what is generally done (with compositing managers for instance), but I'm no X guru.
*** Bug 41856 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Have you tried this with the gtk-client as well? current spicy in Fedora 16 works fine, spice-client still contains the bug. Versions: spice-client-0.9.1-1.fc16 spice-gtk-0.7-39-1.fc16
spicec is deprecated. If you hit this bug, we highly recommended virt-viewer http://virt-manager.org/download/ http://www.spice-space.org/download.html
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.