Bug 1323948

This seems like a light-locker/graphics driver bug. 

Does this happen any other times? Or only on unlock?

Thanks for your report. This seems to be a well known issue, as bug reports show from other distributions. I'm still not sure if it's a direct bug in light-locker and not in Xorg or kernel based graphics. An user writes that the command 'xset dpms force off' brings back the cursor.

Hi Kevin,

Sorry for the late reply.

This only happens on unlock.

And it doesn't happen always.  I tried it three times after installing light-locker and each time it took about 3-4 minutes before the cursor would reappear.  Since then, the problem has *not* happened several times and when it does happen, I'm able to coax it back more quickly by switching applications back and forth with SHIFT-TAB.

However, since reporting this, a second symptom has developed: Sometimes, when coming back from resume, light-locker is shown first for less than 1 second, then dark screen (not off, just black like a blank screensaver).  I cannot get light-locker back to be able to login.  I try changing virtual terminals which doesn't work, which is probably correct behavior, but...  Eventually, I try things like CTRL-ALT-DEL, but that causes the screen to go off, like DPMS or like Xorg crashed.  I am forced to use a hardware reset, so this is much more serious than the mouse cursor symptom.

I *may* have noticed a correlation between this new behavior and, when resuming from suspend, hitting the CTRL key multiple times instead of just once.  (I typically hit the CTRL key to cause a wake up from suspend, since opening the closed laptop doesn't seem to do it, automatically.  I don't think CTRL is significant, but perhaps any key too many times?)

Related? New bug?

What graphics card do you have?

Did you try the suggested command 'xset dpms force off' to bring back the cursor?

Intel Atom Z36xxx/Z37xxx integrated display controller

No, it had not recurred so I could try that.  But, I recurred just now and the command did seem to work: the display turned off and when I hit a key, it turned back on and the cursor was immediately visible.  Of course, I had to start up a terminal before locking the screen so that I could type the command after unlocking.  I guess you would have to set up a hot-key for this command in order to use it as a workaround.

Have you seen or heard of the other symptom?  I think I will make a new report.  It seems more like an interaction with i915 driver, not just light-locker.

Another user reported to upstream.
https://github.com/the-cavalry/light-locker/issues/80

I have experienced this too. With light locker installed and locking active the cursor is invisible. Switching to a text console e.g. ctrl + alt + F5 and back will make the cursor reappear. 

It can be fixed in 2 ways, disable locking in Xfce settings - Power Manager - Security, obviously this is not desirable.

Second fix is to downgrade xorg-x11-server* to version 1.18.0-0.4.20150907.

(reported on the upstream bug.)

Symptoms persist after upgrade to F24.

Now, a downgrade is no longer an available workaround.  So...no workaround.

I notice that switching applications (terminal to FF and back) seems to help.  This is an improvement; that didn't help back in F23.

in my case on F24 + XFCE + light-locker screen never goes blank at all.  

Any suggestions on diagnosing this?

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.