[trinidad]

The workaround from F1 to F7 is simply handing off the mouse control to the operating system. It is an OEM EFI CSM SMM problem as I noted before, not a linux lite kernel problem. On some ASUS boards F1 is enough, as it initiates the handoff. If you can bring up a shell in EFI you can change the bin in the SMM, but that depends on your hardware version. Samsung is the most common offender with this issue. Check your OEM for version modifications, and RHEL. I haven't looked for the RHEL solutions for a while but I bet there is one. You will probably have to enable RPM functions in synaptic to use and compile the RHEL file, which is probably by the way OEM hardware specific. If you want to be careful adding RPM functions to synaptic use Alien to convert them to Deb, or a Porteus convert to Deb app. 

Trinidad

[firenice03]

The workaround from F1 to F7 is simply handing off the mouse control to the operating system. It is an OEM EFI CSM SMM problem as I noted before, not a linux lite kernel problem. On some ASUS boards F1 is enough, as it initiates the handoff. If you can bring up a shell in EFI you can change the bin in the SMM, but that depends on your hardware version. Samsung is the most common offender with this issue. Check your OEM for version modifications, and RHEL. I haven't looked for the RHEL solutions for a while but I bet there is one. You will probably have to enable RPM functions in synaptic to use and compile the RHEL file, which is probably by the way OEM hardware specific. If you want to be careful adding RPM functions to synaptic use Alien to convert them to Deb, or a Porteus convert to Deb app. 

Trinidad

??? UEFi issue? It can be replicated on a 32bit LL3.0 (non uefi)...
No issues with 2.2 thru 2.8 only occurred in 3.0
- Not saying it not relative to the items quoted and would agree not with the kernel but perhaps more with XFCE, Lite-Locker or a screen lock setting of sorts...
Similarly to the "black screen" after hibernate of previous..

Just my plugged nickel...

[blinkingbee]

I think I have found a solution to the cursor disappearing after sleep.
I found this here: https://bugs.launchpad.net/ubuntu/+sourc...mments=all

Essentially it involves updating the video driver as described here: https://launchpad.net/~oibaf/+archive/ub...cs-drivers

This is what I did:
In terminal:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt-get upgrade
sudo reboot

et voila the cursor now appears after sleep.

My system:
System:
Kernel: 4.4.0-21-generic i686 (32 bit) Desktop: Xfce 4.12.3 Distro: Ubuntu 16.04 xenial
Machine:
Mobo: Dell model: CN0Y53 v: A04 Bios: Dell v: A04 date: 06/22/2009
CPU(s):
Single core Intel Atom N270 (-HT-) speed/max: 800/1600 MHz
Graphics:
Card: Intel Mobile 945GSE Express Integrated Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
Resolution: [email protected]
GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 11.2.0

YMMV

[valtam]

I think I have found a solution to the cursor disappearing after sleep.
I found this here: https://bugs.launchpad.net/ubuntu/+sourc...mments=all

Essentially it involves updating the video driver as described here: https://launchpad.net/~oibaf/+archive/ub...cs-drivers

This is what I did:
In terminal:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt-get upgrade
sudo reboot

et voila the cursor now appears after sleep.

My system:
System:
Kernel: 4.4.0-21-generic i686 (32 bit) Desktop: Xfce 4.12.3 Distro: Ubuntu 16.04 xenial
Machine:
Mobo: Dell model: CN0Y53 v: A04 Bios: Dell v: A04 date: 06/22/2009
CPU(s):
Single core Intel Atom N270 (-HT-) speed/max: 800/1600 MHz
Graphics:
Card: Intel Mobile 945GSE Express Integrated Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
Resolution: [email protected]
GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 11.2.0

YMMV

Nice share

[torreydale]

Wish I knew this four days ago.  On Friday, I reverted my laptop to LL2.8 64bit for this very reason.  The ctrl-alt-F1 and ctrl-alt-F7 workaround was becoming inconvenient for me.

[firenice03]

I'll go ahead and jinks myself..
BUT I haven't had to use the work around for a while and actually forgot about it.. But I've turned off all the locking features...

I may try enabling locks, to initiate the problem and test blinkingbee's fix +1 on the share

[Le000]

I think I have found a solution to the cursor disappearing after sleep.
I found this here: https://bugs.launchpad.net/ubuntu/+sourc...mments=all

Essentially it involves updating the video driver as described here: https://launchpad.net/~oibaf/+archive/ub...cs-drivers

This is what I did:
In terminal:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt-get upgrade
sudo reboot

et voila the cursor now appears after sleep.

My system:
System:
Kernel: 4.4.0-21-generic i686 (32 bit) Desktop: Xfce 4.12.3 Distro: Ubuntu 16.04 xenial
Machine:
Mobo: Dell model: CN0Y53 v: A04 Bios: Dell v: A04 date: 06/22/2009
CPU(s):
Single core Intel Atom N270 (-HT-) speed/max: 800/1600 MHz
Graphics:
Card: Intel Mobile 945GSE Express Integrated Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
Resolution: [email protected]
GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 11.2.0

YMMV

Thx man....I was just about to unistall LL3.0....luckily you came for the rescue .... funny that DEV seems to not mind people ditching his OS for something so easily fixable and yet so complicated for non-programmers.... no wonder LL has fallen down so much on distrowatch.

[torreydale]

Le000,

It might be too soon to start throwing rocks. 

Furthermore, following your Distrowatch logic, Slackware, openSUSE, CentOS, and Arch are higher on the list because they're less complicated for non-programmers than Linux Lite.  Must be frustration talking.  You can't really believe that.

[valtam]

No worries, I'll just add every graphics driver PPA in existence to the next LL  ???

Sent from my Nexus 6 using Tapatalk

[technomancer]

[quote author=blinkingbee link=topic=3075.msg25306#msg25306 date=1469432567]
I think I have found a solution to the cursor disappearing after sleep.
I found this here: https://bugs.launchpad.net/ubuntu/+sourc...mments=all

Essentially it involves updating the video driver as described here: https://launchpad.net/~oibaf/+archive/ub...cs-drivers

This is what I did:
In terminal:
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get update
sudo apt-get upgrade
sudo reboot

et voila the cursor now appears after sleep.

My system:
System:
Kernel: 4.4.0-21-generic i686 (32 bit) Desktop: Xfce 4.12.3 Distro: Ubuntu 16.04 xenial
Machine:
Mobo: Dell model: CN0Y53 v: A04 Bios: Dell v: A04 date: 06/22/2009
CPU(s):
Single core Intel Atom N270 (-HT-) speed/max: 800/1600 MHz
Graphics:
Card: Intel Mobile 945GSE Express Integrated Graphics Controller
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
Resolution: [email protected]
GLX Renderer: Mesa DRI Intel 945GME x86/MMX/SSE2 GLX Version: 1.4 Mesa 11.2.0

YMMV

Thx man....I was just about to unistall LL3.0....luckily you came for the rescue .... funny that DEV seems to not mind people ditching his OS for something so easily fixable and yet so complicated for non-programmers.... no wonder LL has fallen down so much on distrowatch.
[/quote]

SEE below. This is not a linux lite or any other linux system issue. Have you tried other distros and have you had the same issue on them ?
If you have and the issue does not happen, maybe you could post your hardware config and mouse configuration to see what is different and it can be either fixed or added to linux lite. Give us info and we can help you, and at the same time, improve linux lite !  8)

The workaround from F1 to F7 is simply handing off the mouse control to the operating system. It is an OEM EFI CSM SMM problem as I noted before, not a linux lite kernel problem. On some ASUS boards F1 is enough, as it initiates the handoff. If you can bring up a shell in EFI you can change the bin in the SMM, but that depends on your hardware version. Samsung is the most common offender with this issue. Check your OEM for version modifications, and RHEL. I haven't looked for the RHEL solutions for a while but I bet there is one. You will probably have to enable RPM functions in synaptic to use and compile the RHEL file, which is probably by the way OEM hardware specific. If you want to be careful adding RPM functions to synaptic use Alien to convert them to Deb, or a Porteus convert to Deb app.

Trinidad