GNOME Bugzilla – Bug 694758
Can't see the mouse pointer after login
Last modified: 2014-03-17 21:18:05 UTC
Filing against gdm because I don't know better. With gdm / gnome-shell / mutter / gnome-settings-daemon at version 3.7.90, sometimes the mouse pointer is invisible after logging in. I believe that we are hiding the pointer now, so this seems like a race.
maybe gnome_idle_monitor isn't working. We're supposed to show the mouse when you move it around.
The mouse pointer is supposed to be invisible until you move the mouse/wiggle the touchpad/etc. Does it appear again?
No, the pointer did not reappear though I could "see" its location when it moved over UI elements which get highlighted on hovering.
What's the /usr/libexec/gsd-cursor output when you reproduce the problem?
In my machine this triggers if I keep moving the mouse at the exact time it disappears during log-in, then it won't come back until I re-plug the mouse. Moving it just before disappearing (but not at the exact moment) won't trigger the bug. Also, moving just after it disappears, the pointer reapers just as intended.
I see a similar failure from time to time (with 3.8.4): 1. I reboot 2. I login in as fast as possible on my account 3. I see mouse pointer is missing (even if it seems to exist as I can still move it and select things) -> AT THE SAME TIME, I see that my battery looks undetected by gnome-shell (an empty battery dialog is shown). -> If I wait some seconds, all goes ok -> mouse pointer is shown and normal battery icon too (well, sometimes I need to restart gnome-shell... but maybe waiting a bit longer would be enough)
(In reply to comment #4) > What's the /usr/libexec/gsd-cursor output when you reproduce the problem? I can reproduce this problem always just after booting, but cannot find that executable
Looks like it's caused by this: ago 09 23:51:08 belkin4 colord[422]: Device added: xrandr-LVDS1 ago 09 23:51:09 belkin4 colord[422]: Automatic metadata add icc-86ad3d91c26e56ad840f0c7dcfa14fc6 to xrandr-LVDS1 ago 09 23:51:09 belkin4 colord[422]: Profile added: icc-86ad3d91c26e56ad840f0c7dcfa14fc6 ago 09 23:51:09 belkin4 colord[422]: Profile added: icc-12b9854d5b5afc2f58c0bde184ca971f Until that doesn't appear, the mouse pointer is hidden, as soon as messages are logged, mouse reappears No idea why colord takes so much time to run after boot
This is the full sequence at boot: # journalctl -b | grep colord ago 10 08:50:23 belkin4 dbus-daemon[227]: dbus[227]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' ago 10 08:50:22 belkin4 dbus[227]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' ago 10 08:50:23 belkin4 colord[421]: Using config file /etc/colord.conf ago 10 08:50:23 belkin4 colord[421]: Using mapping database file /var/lib/colord/mapping.db ago 10 08:50:23 belkin4 colord[421]: Using device database file /var/lib/colord/storage.db ago 10 08:50:23 belkin4 colord[421]: plugin /usr/lib64/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load ago 10 08:50:23 belkin4 colord[421]: loaded plugin libcd_plugin_camera.so ago 10 08:50:23 belkin4 colord[421]: loaded plugin libcd_plugin_scanner.so ago 10 08:50:23 belkin4 colord[421]: Daemon ready for requests ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-9641812b452fc79a145471df34e5133c ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-1bfefb24d1ee68493ac06cbb8261138a ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-6fb3a23d8d7d23908c613c556d3e10cf ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-4fc90f9c0cf37f23788380757ab3ef84 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-8e831ffae88095ca5e0a925ae48dfaf3 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-bc2d6f78dfa777ece4bda1ecabceefc6 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-5f3fa452c6ad51fc1b9b940602db91e2 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-2068fc2c9e34d665c1f23de15df67abb ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-9e18d5dc12cb0241af6ef9b91753582f ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-3cb33dc02a3c8c41a0141adcba595f9c ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-cf618b76f0288e759fcea8b8b7eb3a41 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-90bb3cf4d7f73e2aa1f2e7c93ca71710 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-12fa9fa796998fde58702b83dc68cf06 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-c3f7b1c952897dd0cea880a54292f0d1 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-fdede5c371fc2d8d2bea421dfa4001f3 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-014ceb163db1785be320671ffa87d01a ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-850712c881b2e091b4fe21bbbef42f09 ago 10 08:50:23 belkin4 colord[421]: Profile added: icc-5ed408334b2a73010c15d35d32b64f85 ago 10 08:50:24 belkin4 colord[421]: Profile added: icc-717e9871bf1c871fb76e95d952bf92ee ago 10 08:50:24 belkin4 colord[421]: Profile added: icc-a86a502a9fdc58f261eb321b40946488 ago 10 08:50:24 belkin4 colord[421]: Profile added: icc-e62f71e9c617ab379dd29f1a238f4b17 ago 10 08:50:24 belkin4 colord[421]: Profile added: icc-cc2c71090e82237b837fc6fae2beb31f ago 10 08:50:24 belkin4 colord[421]: Profile added: icc-fe0295e8c064e272a905799201f55920 ago 10 08:50:24 belkin4 colord[421]: Profile added: icc-43a83a947a078c5c0d60cbc0b1549846 ago 10 08:50:24 belkin4 colord[421]: Device added: xrandr-LVDS1 ago 10 08:50:25 belkin4 colord[421]: Automatic database add icc-3ea477e8832c838e2ed5605cc72799d9 to xrandr-LVDS1 ago 10 08:50:25 belkin4 colord[421]: Automatic metadata add icc-3ea477e8832c838e2ed5605cc72799d9 to xrandr-LVDS1 ago 10 08:50:25 belkin4 colord[421]: Profile added: icc-3ea477e8832c838e2ed5605cc72799d9 ago 10 08:50:35 belkin4 colord[421]: device removed: xrandr-LVDS1 ago 10 08:50:35 belkin4 colord[421]: Profile removed: icc-3ea477e8832c838e2ed5605cc72799d9 ago 10 08:50:37 belkin4 colord[421]: Profile added: Canon-PIXMA-MP280-Gray.. ago 10 08:50:37 belkin4 colord[421]: Profile added: Canon-PIXMA-MP280-RGB.. ago 10 08:50:37 belkin4 colord[421]: (colord:421): Cd-WARNING **: failed to get session [pid 594]: Error desconocido -2 ago 10 08:50:37 belkin4 colord[421]: Device added: cups-Canon-PIXMA-MP280 ago 10 08:50:37 belkin4 colord[421]: Profile added: Deskjet_2050_J510-Gray.. ago 10 08:50:37 belkin4 colord[421]: Profile added: Deskjet_2050_J510-RGB.. ago 10 08:50:37 belkin4 colord[421]: (colord:421): Cd-WARNING **: failed to get session [pid 594]: Error desconocido -2 ago 10 08:50:37 belkin4 colord[421]: Device added: cups-Deskjet_2050_J510 ago 10 08:51:37 belkin4 colord[421]: Device added: xrandr-LVDS1 ago 10 08:51:38 belkin4 colord[421]: Automatic metadata add icc-86ad3d91c26e56ad840f0c7dcfa14fc6 to xrandr-LVDS1 ago 10 08:51:38 belkin4 colord[421]: Profile added: icc-86ad3d91c26e56ad840f0c7dcfa14fc6 ago 10 08:51:38 belkin4 colord[421]: Profile added: icc-12b9854d5b5afc2f58c0bde184ca971f As you can see: ago 10 08:50:24 belkin4 colord[421]: Device added: xrandr-LVDS1 -> This comes from gdm, that successfully shows mouse pointer ago 10 08:50:35 belkin4 colord[421]: device removed: xrandr-LVDS1 -> This comes from starting the login in gnome session ago 10 08:51:37 belkin4 colord[421]: Device added: xrandr-LVDS1 -> As you see, it takes a minute until mouse is shown (login takes for me less than a minute, some times I have to wait longer until mouse is shown and device is added)
Does: gsettings set org.gnome.settings-daemon.plugins.color active false in the user session fix this? There should be no blocking calls in any of the plugins.
Sadly, after disabling the plugin the problem persist. I know see no message at all in journalctl but it still occurs. Then, I guess colord starting late was a consequence of some other problem :/ The other strange thing I see *while the mouse pointer is not shown* is that battery indicator is shown as empty, but I cannot take a screenshot as gnome-shell looks to not take it while this problem is occurring
Created attachment 251294 [details] journalctl -b output run as user I attach journalctl -b output run as user after editing /etc/xdh/autostart/gnome-settings-daemon.desktop to run /usr/libexec/gnome-settings-daemon --debug You can see how near a minute passes between ago 11 09:59:45 belkin4 gnome-session[537]: Advertencia del gestor de ventanas: Log level 16: Could not create object for (null): uid 1001 has no permission to perform this operation ago 11 09:59:46 belkin4 gnome-session[537]: Done! ago 11 10:00:34 belkin4 gnome-session[537]: (gnome-settings-daemon:578): media-keys-plugin-DEBUG: Starting media_keys manager ago 11 10:00:34 belkin4 gnome-session[537]: (gnome-settings-daemon:578): orientation-plugin-DEBUG: Did not find an accelerometer But I still can't see what is causing it :'(
as a side note, I am using a touchpad (don't have a USB mouse to test). I say that because looks like some people are workarounding this connecting a USB mouse: https://bugs.archlinux.org/task/34901
Also, if I temporally drop the pointer gsd plugin completely, the problem disappears -> looks like mouse pointer plugin is failing to reactivate pointer (anyway, I don't fully understand why the pointer is made hidden when devices like a touchpad are available and no touchscreen one is present) I have tried to modify plugin Priority without success. The same for power plugin that also looks to not detect my battery at login time. Please note that this problems only appear on the first login after booting Do you have any ideas?
$ /usr/libexec/gsd-test-cursor To deactivate: gsettings set org.gnome.settings-daemon.plugins.cursor active false To reactivate: gsettings set org.gnome.settings-daemon.plugins.cursor active true (gsd-test-cursor:1007): cursor-plugin-DEBUG: Starting cursor manager (gsd-test-cursor:1007): cursor-plugin-DEBUG: Attempting to hide the cursor (gsd-test-cursor:1007): cursor-plugin-DEBUG: Device 10 'SynPS/2 Synaptics TouchPad' became active (gsd-test-cursor:1007): cursor-plugin-DEBUG: Attempting to show the cursor ^C That is the output while running it and pointer is invisible, the problem is that it's exactly the same as when it's shown properly :(
I guess this is the commit that introduced the problem: https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=285b0e497af18b853c9f67f93f3b3bbab7a6c241 But looks like a bit important to revert :S
For now, I have simply disabled the plugin as I don't have a touchscreen: gsettings set org.gnome.settings-daemon.plugins.cursor active false Is this plugin useful when wacom is not available? If not, maybe it could also be disabled (as wacom) when it's not present :/
There were bugs in the XSync protocol (used to determine which input device was used last) and in the QXL driver that didn't show a cursor in some cases. Update your systems.
What versions did fix that problems? (to let us ask people to update to at least some version) Thanks!