Bug 97100 - Mouse Cursor Accuracy Off & Screen Lock Up Logging out of X
Summary: Mouse Cursor Accuracy Off & Screen Lock Up Logging out of X
Status: RESOLVED MOVED
Alias: None
Product: Spice
Classification: Unclassified
Component: spice-gtk (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-27 19:54 UTC by XorgBug
Modified: 2018-06-03 10:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
spice-gtk.jpg (176.13 KB, image/jpeg)
2016-07-27 19:54 UTC, XorgBug
Details

Description XorgBug 2016-07-27 19:54:57 UTC
Created attachment 125353 [details]
spice-gtk.jpg

Hello,

My Host System Specs:

Slackware 14.2 x86_64 (multilib)
Openbox 3.6.1
Nvidia GTX 660M - nvidia-driver-352.63
xorg-server-1.18.3
QEMU 2.6.0
celt051-0.5.1.3
pyparsing-2.0.3
six-1.10.0
spice-0.12.8
spice-gtk-0.32
spice-protocol-0.12.11
vala-0.32.1

Guest Specs:

Slackware 14.1
Xfce 4.10.1
xorg-server-1.14.3
spice-protocol-0.12.11
xf86-video-qxl-0.1.4

Guest Start Script:

qemu-system-x86_64 -rtc base=localtime Slackware\ 14.1\ x64.img \
-vga qxl --enable-kvm -smp 2 -soundhw ac97 -m 4096 \
-device virtio-serial-pci \
-spice port=5900,disable-ticketing,addr=127.0.0.1 \
-chardev spicevmc,id=spicechannel0,name=vdagent \
-device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0

lsusb for my usb plugged in mouse

Bus 003 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse

When I log into Xfce I noticed when I left or right click on the mouse, the action is happening about an inch away from the cursor, and I noticed when I click at different times, the location changes. Sometimes I see the action happen to the left, right, above or below the cursor, with the opening of a desktop menu happening at these different locations. So for now I don't know how to get the mouse to work properly, making using the guest impossible.

When I log out of Xfce the screen goes bad and locks up, then I close spice-gtk, open up htop and look for all the running instances of QEMU and sigkill them, but then if I restart spice-gtk, and then log into Xfce, most of the time it then crashes and gives me this error at the terminal;

Spice-ERROR **: mem.c:99:spice_malloc: unable to allocate 131176 bytes
zsh: trace trap  spicy -h 127.0.0.1 -p 5900

The only way I've been able to then get back into X working is I have to reboot my host, which is really annoying.

Please see the attached screen shot of how the console looks when I log out of X and it locks up.
Comment 1 XorgBug 2016-07-27 20:10:24 UTC
I forgot to add that I also have installed for the Slackware Guest;

spice-vdagent-0.17.0
Comment 2 Pavel Grunt 2016-07-28 07:46:39 UTC
Hello XorgBug,

I would try adding a usb-tablet, it should help with the mouse:
    -device usb-tablet

Since you are using spicy, you can also try changing mouse mode (in the Options menu)
Comment 3 XorgBug 2016-08-04 02:57:13 UTC
Spice support for a Slackware guest is not good. I knocked myself out for several days, trying everything possible I could find online, nothing works...

The system is not useable...

Also when logging out of X to the console, it locks up at the console and the screen goes bad, so then you can't do anything in the console, there is no console, you have to shutdown then restart qemu.

Someone that really has a care/concern for improving Guest support for Slackware guest should trying installing Slackware 14.2 and testing it out, because it doesn't work for me.
Comment 4 GitLab Migration User 2018-06-03 10:21:20 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-gtk/issues/24.


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.