← Back to team overview

desktop-packages team mailing list archive

[Bug 1297144] Re: Invisible cursor after resume from suspend


Hi, I also have the same issue on my eeepc 1225. When Xubuntu 14.10 was release I upgraded from 14.04 (32 bit).
On 14.04 I did not have this issue; however after the upgrade to 14.10 I also switched fglrx for the radeon driver, so I cannot say that it is not related to that.

I suspend my laptop by closing the lid, and the pointer has always disappeared when I resume...
I have disabled screen locking on resume, but I have not made any changes when it comes to choice of screensaver software.

Also, I can get the pointer back by either changing resolution (runnig
xrandr in a terminal) och by connecting and enabling a second monitor.
Or using x2x with another machine. Anything that change the resolution
in one way or another...

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.

  Invisible cursor after resume from suspend

Status in “light-locker” package in Ubuntu:
Status in “xorg” package in Ubuntu:

Bug description:
  I am using the daily build of Xubuntu 14.04 x64 on a Lenovo Thinkpad
  x230. If I wake up the computer after it spending some time in the
  suspend state, the cursor will be invisible.  The courser still works
  (I can click on stuff and hover the invisible cursor over stuff), but
  the little arrow is not visible.  This bug showed up a few days ago
  after an update.  Putting the computer back in suspend state and
  immediately waking it back up resolves the issue until the next time
  the computer is put in suspend state for an extended period of time.

  It is possible that this bug has something to do with Whisker Menu.
  Sometimes when the courser is invisible it will still show up over
  Whisker Menu.  Most of the time it is invisible there too.

  Description: Ubuntu Trusty Tahr (development branch)
  Release: 14.04
  xfdesktop version 4.11.4, running on Xfce 4.10

To manage notifications about this bug go to: