![]() The first Ctrl+Alt+F2 Ctrl+ALt+F1 sequence didn't get cursor again the second sequence gave me it. resolution has been correctly changed but cursor disappeared again. select "apply changes" (without mouse cursor) One quick test gave the VM pointer ok both on gdm login and then in session.īut this kind of operation caused cursor disappearing again in the same session: Ноя 21 16:51:35 localhost.localdomain vmusr: The vmusr service needs to run inside a virtual machine. Ноя 21 16:51:35 localhost.localdomain vmusr: Attempt to add property ToolsCoreService::tcs-prop-thread-pool after class was initialised Ноя 21 16:51:35 localhost.localdomain gnome-session: Entering running state Ноя 21 16:51:35 localhost.localdomain vmusr: Attempt to add property ToolsCoreService::tcs-app-ctx after class was initialised Ноя 21 16:51:35 localhost.localdomain gnome-session: Tracker-Message: Importing config file to GSettings Ноя 21 16:51:35 localhost.localdomain gnome-session: vmware-user: could not open /proc/fs/vmblock/dev Ноя 21 16:51:35 localhost.localdomain gnome-session: Gjs-Message: JS LOG: GNOME Shell started at Thu 16:51:35 GMT-0800 (PST) Ноя 21 16:51:35 localhost.localdomain polkitd: Registered Authentication Agent for unix-session:2 (system bus name :1.107, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale ru_RU.UTF-8) Ноя 21 16:51:35 localhost.localdomain gnome-session: (gnome-settings-daemon:2852): GnomeDesktop-WARNING **: Failed to acquire idle monitor proxy: GDBus.Error.UnknownMethod: Интерфейс «» для пути /org/gnome/Mutter/IdleMonitor/Device10 объекта не найден Ноя 21 16:51:35 localhost.localdomain gnome-session: (gnome-settings-daemon:2852): power-plugin-WARNING **: failed to turn the panel on: Display is not DPMS capable Ноя 21 16:51:35 localhost.localdomain spice-vdagentd: opening vdagent virtio channel Ноя 21 16:51:35 localhost.localdomain kernel: input: spice vdagent tablet as /devices/virtual/input/input5 Ноя 21 16:51:34 localhost.localdomain goa: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KEYRING' Ноя 21 16:51:34 localhost.localdomain goa: goa-daemon version 3.10.2 starting Ноя 21 16:51:34 localhost.localdomain pulseaudio: pid.c: Daemon already running. Ноя 21 16:51:34 localhost.localdomain gnome-session: GNOME_KEYRING_CONTROL=/run/user/1000/keyring-q5p5Qw Ноя 21 16:51:34 localhost.localdomain rtkit-daemon: Supervising 7 threads of 3 processes of 2 users. Ноя 21 16:51:34 localhost.localdomain gnome-session: SSH_AUTH_SOCK=/run/user/1000/keyring-q5p5Qw/ssh 'journalctl -b | grep -10 monitor' extract: I'm going to attach an Xorg.log with that output, maybe it'll help * all alarms trigger as expected, but events aren't always enabled, so the client may miss out here on what it expects * the client never enables events for the IDLETIME alarm on value 1 until after login * when swapping devices between the QEMU tablet and the emulated mouse, the right alarms triggerĪt this point it looks like the server is doing the right things and this is on the client side, notably: * the server writes the event for the respective device * alarms for the QEMU tablet, QEMU mouse and my emulated mouse are enabled for events (that appears to be the 5 min blank alarm) * another alarm is created for the IDLETIME counter, value 30000, events enabled. * an alarm is created for the IDLETIME counter for value 1, events disabled * an alarm is created for each device for value 1, events disabled deactivating the cursor plugin, ran the gsd-test-cursor from gnome-settings-daemon-devel and that works as expected.Īdded a bunch of printfs to the server code: ![]() Emulated PS/2 mouse and events through evemu, mouse cursor is not visible.Īfter login, cursor is visible. So, here's what I'm seeing (with the test build from comment #27). boot Fedora (in a VM, better chance of seeing this) Version-Release number of selected component (if applicable): Some of my colleagues have seen this problem (in VMs) as well. I saw this mainly in virtual machines (virt-manager+spice+qxl), but I saw it on bare metal as well (Intel graphics, although it was F19). Usually, switching to tty2 and back solves the problem. The cursor was still present (mouse over effects worked and I could click on widgets), but the cursor itself was invisible. During my testing, I several times saw a problem when mouse cursor was present in gdm, but disappeared on login.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |