New user

[drrdf]

Hi newtus maximus,

Thanks for your reply. I will try that on the laptop; but of course there is exactly the same problem on my desktop PCs.

[trinidad]

Many laptops actually hibernate rather than shutdown thus making certain changes can be confusing to new Linux users. Generally, (even though this is not a normal Linux function) NICs and a few other functions still run a while after shutdown. If you are confused by certain changes not taking effect immediately, try the following. To shut a laptop down completely press the shift key down and hold it before clicking shutdown, click shutdown and don't release the shift key until the laptop goes off. Laptops conveniently have battery power and many modern lap BIOS have this feature OEM default. It doesn't matter whether or not Windows is still on the machine. Numbers lock is often an issue on laptops because of  fn keys some even with triple functions. Common sense and knowing your laptop usually makes numbers lock a non-issue. Install the suggested default. Other things that can mess up changes to installs on machines that hibernate for a while at shutdown are dysfunctional cmos clocks and drive changes. Because of the nuisance of battery removal with laptops, it's best to reset the BIOS to factory default first, set the cmos clock, shutdown, restart and then make the changes you need to the BIOS, and then install Linux via a media boot.

Also any Linux system using lightdm will display the same issue with numbers lock, and you should always use whatever the BIOS default is for numbers lock during installation. The fact that you are having the same issue on several machines tells me you are not using the BIOS default numbers lock setting during installation. I'm approaching 100 installs, and have only had to deal with the numbers lock issue once, but then I always default the BIOS and set the clock before installing LL on any machine that I am preparing for someone else.

TC 

[drrdf]

Hi Jerry,

No, I have just tried setting the BIOS to numlock ON and it does not make one iota of difference to Linux Lite. Despite all the options in Linux Lite being set to set to numlock OFF they are still disregarded and Linux persists with setting to numlock ON at log in. Thanks for your help.

[drrdf]

Hi trinidad,

Thanks for your reply. I can assure you that I am using the same BIOS default numlock setting in all installations. It may be that this problem in Linux Lite only occurs with certain hardware  I have just noticed after searching that there are several other earlier topics posted on this forum concerning the same problem with numlock settings.

[drrdf]

Hi newtusmaximus,

Thanks for your further reply. I will try what you suggest, Thanks.

[skippy95]

Hi, drrdf. As to the autostart files and directories, I have a custom LXDE setup so most of my autostart files/directories do not match to the default. The one directory I am certain matches is /home/[username]/.config/autostart which contains .desktop files of programs that are autostarted. You can delete any program file from that directory that you do not want autostarted. Sorry I can't help more.

This may sound strange, but you might try completely removing numlock then reinstalling to give numlock a new configuration. My thoughts are: numlock came preinstalled and any programs having dealings with numlock knew that (for example, Lite Tweaks and LightDM). If you completely remove and then do a new install of numlock, the mystery setting that keeps turning it on might dissapear, note I said maybe

Command to completely remove numlock:  sudo apt-get purge numlock
(Purge removes all configuration files for that package.)
To error on the side of caution, I would reboot so other programs that have dealings with numlock see that it is no longer installed and adjust accordingly (hopefully).
Now reinstall numlock:  sudo apt-get install numlock
Then go to Lite Tweaks and ensure that numlock is turned off.

I cannot promise this will work, but at this point, almost anything is worth a try. When I was using straight up Ubuntu, I did this once or twice for some programs and it actually worked, but then other times it didn't seem to change anything. Please let us know.

Good luck, skippy95