This morning there were updates to install on our new LL 3.0. One of the updates was to 'Lite Tweaks'. There is a new addition to it for the 'number lock' problem some people get. There is a slight problem. When you run lite tweaks you are asked to enable/disable numberlock whether you select it from the list or not. When this happened the first time I selected disable, which is the correct choice. I rebooted & ran lite tweaks again to see what would happen. Even though I did not select the choice it asked me again to pick enable/disable numberlock. Slight reoccurring problem.

  A LTS is supported for 5 years from issue.    After that date the  user  is in freefall if he/she doesn't upgrade to next LTS?  However if user stays with an older LTS but keeps upgrading Kernel, does this extend the life if the original LTS.

The reverse scenario – Take for instance LL3.0 – if user down grades the Kernel to say 3.13 for hardware compatibility reasons, After 2019 ( when the LTS for LL2.8 expires; Kernel 3.13 being the standard for LL 2. 8) does the system  become vulnerable, assuming all updates are maintained??

I.e what is the relationship between Kernel and LTS re longevity/security./vulnerability. ??

Objective to keep older machines working (safely/ non vulnerable) for as long as possible.

PS , not sure where the emoji came from; can't seem to get rid of it. 

The 3.0 Release Announcement proudly notes, "Numlock - Is enabled at the Login screen." Evidently, some code has been added somewhere to do this. The usual keyboard settings have no influence on this behaviour.

NumLock On makes sense on a desktop keyboard with a separate numeric keypad. On a laptop keyboard, NumLock On can make a mess of your password. For example, the "U" key will emit "4". It only makes sense that by default you want alpha keys to emit alpha characters and numeric keys to emit numerics.

I'd rather not have to hit Fn-NumLk every time I start a session. How can I make sure that on my laptop my session starts with NumLock OFF?

The Release Notes link on the first Install page brings up the Linux Lite Help Manual.
It might be interesting to see the Release Notes. I couldn't find anything by that name. Perhaps you call them "Release Announcements"?

The Check Install Media function never reports whether the CD or USB drive is OK or not.
It just tells you to press any key to reboot. There should be a clear conclusion.

Messages on the splash screen (the orange-y one with the feather) are in white text which is almost impossible to read against the light background. Only by tilting my monitor to an extreme angle can I make out anything. I thought LL was hanging on shutdown. It was waiting for me to press ENTER. I suppose this won't matter after installation, but it might trip up some newbies.

Poor contrast colour choices and GUI decisions like borderless windows will cause problems for people with less than absolutely perfect vision.

I just installed LL3.0. After updating i installed xfce mailwatch and got the following error message after it installed.
W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)


I have absolutely no clue what it is and how to fix it. I googled but couldnt find anything usefull. Anyone got an idea what this is and what i need to do to fix it?
The program xfce mailwatch installed fine and is working.

When you install Linux Lite 3.0 (not the Beta) Firefox 46.0.1 for Ubuntu has a new default 'dark' theme. I don't like it, but that's not really the point. If you don't like the 'dark' look, and would prefer what you had 10 minutes before you installed LL 3.0 -
click on 3-bars, top right / click 'add-ons' tab / click 'appearance' tab
Where you see 'default theme' click 'enable' and restart Firefox
Just me, but when I started Firefox and had that big black bar at the top I found it distracting. If you find yourself agreeing, bounce that bar to the curb.

Have you fixed the problem with grub.i.e. Linux Lite versions 2 had been altered to be more friendly to shared boots with Windows 7. This alteration left Linux Lite 2 less compatible with multiple Linux Distro installations. Earlier versions of Linux Lite did not (according to this information)  link http://ubuntuforums.org/showthread.php?t=2318826 suffer from the same limitations.
This grub problem is is a real pain. If this is still the case (as it was on lite3 beta) ,Can someone paste a custom 40. boot instruction.

I've recently been trying to upgrade now I'm getting a black screen saying gave up waiting for root device

Alert dev mapper Linux root VG root does not exist dropping to shell!

Busybox v1.21.1

Enter 'help' for a list of commands

This is not full text as I'm using my phone to help

Cheers