FS#34901 - [gnome-shell][gdm] No visible mouse pointer in gdm/gnome shell
Attached to Project:
Arch Linux
Opened by Michael Wilson (meowfaceman) - Tuesday, 23 April 2013, 05:22 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 07 February 2014, 05:55 GMT
Opened by Michael Wilson (meowfaceman) - Tuesday, 23 April 2013, 05:22 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 07 February 2014, 05:55 GMT
|
Details
Description: When using gdm or gnome shell, no mouse pointer
is visible. The mouse pointer is active and functional, but
there is no visual representation.
Disabling the HWCursor does not solve the issue. The mouse pointer is visible using lightdm and Xfce. If I select the Gnome desktop from lightdm, the mouse pointer disappears. If I select Xfce from gdm, the mouse pointer appears. Basically, as soon as anything Gnome desktop related enters the equation, it looks like the mouse pointer disappears, and when Gnome leaves, it reappears. If I enable zoom in Gnome, the mouse is visible. Other than that, there does not appear to be any way to induce the mouse pointer to become visible in any way. Additional info: * gnome-shell 3.8.1-1 * gdm 3.8.1.1-1 * Running a Radeon HD 5450 using open source ATI/Radeon drivers * Xorg 1.14.0 * Kernel 3.8.8 * synergy 1.4.10-2 Steps to reproduce: Run gdm or Gnome. The mouse is not visible. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Friday, 07 February 2014, 05:55 GMT
Reason for closing: Won't fix
Friday, 07 February 2014, 05:55 GMT
Reason for closing: Won't fix
I think the problem comes with synergy. You should report this in the Gnome bug tracker as the Arch Linux devs won't be able to do anything for you. The relevant product should be Core/gnome-settings-daemon.
https://bugzilla.gnome.org/
just unset setting /org/gnome/settings-daemon/plugins/cursor/active (set to FALSE), f.e.:
dconf write /org/gnome/settings-daemon/plugins/cursor/active false
A related bug (
FS#37416) sometimes prevented the cursor from reappearing when switching devices, but that should be fixed now.