After Pensor is loaded you should be able to click on the icon located on the panel and it should pull up your Temperature readings.  Instead of it doing that it brings up the entire monitor.  Which isn't terrible, but it isn't right.  Because I use that little icon to give me a quick glimpse of what my current cpu temps are.

I recently switched language preferences on my LL 4.0 machine. I switched it to Esperanto. The only problem is that I can't figure out how to keep English as the language for the other 2 users on the machine. How should I do that? Currently when either of my other 2 family members log into their accounts, everything is in Esperanto, when they need to use English. Any advice would be much appreciated! Thanks so much.

When I boot LinuxLite 4.0 in VirtualBox, The desktop is not displayed full screen even though it is set to such. I have to go to the VirtualBox Menu and select View > Show Full Screen (the VirtualBox window becomes smaller to surround the LinuxLite Desktop). I then Select View > Show Full Screen and then watch the screen flicker, then displays full screen.

Isn't a show stopper but just a tad bit irritating.

There are very few Linux Distros I recommend to Windows users and this is one.

Currently running Linux Lite 4.17 due to notices on Softpedia from Linux Lite that it was possible to upgrade to 4.17.  This followed later by notice that 4.16 had reached update 18 and was no longer supported, as was in April 2018 that 4.15 had reached update 18 and one should update to 4.16.  Well on 4.17 and now Virtual Box is not working.  Have reloaded that app a couple times and still not working.  Say to reload the dkms and the  modprobe, but modprobe is not in the system.  Any suggestions?

Hello

As title says, I just can't install any Linux Lite or any other Linux distro on my Acer Aspire ES 17 ES1-732. The installation client runs ok up until grub2. It just gets stuck on "Installing grub2 package..."

I dissabled "Safe Boot" on my Bios, enabled again, etc. It has UEFI, which I think is made for Windows installations only, but it won't let me dissable UEFI.

My laptop is a 17.3" Acer Aspire ES 17 ES1-732.

N3350 @1.1 ghz
4gb DDR3L
1TB Toshiba HDD

This is just too slow to run windows 10, I get a lot of lags. So I was looking for a lighweight OS such as Linux Lite or Lubuntu.

Running a trial of LL on both a virtual machine and live boot, I cannot change the prompt. PS1="\$ " works on any other distribution I've used but not on LL. No error message, just no change. Even put it in .bashrc. I've checked shell and it is bash. Any ideas or is this a bug.
Currently using Mint 18.3, but seriously considering LL.

I have a Dell Latitude D610 running Linux Lite 3.8. My primary network connection is through a USB NIC dongle. See output following:

Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

The performance on the RTL dongle is good but when the system starts BIOS also starts up a PCI card with the old Dell b/g wireless connection. At restart, both of the wireless connections start and internet access slows substantially.  I have to manually disconnect the Dell card so that the dongle works properly.

I tried to switch off the WIFI in BIOS but then it also disables the RTL adapter and there is no network connection. Short of removing the original Dell WIF card, is there a way to disable it at login so that I just use the USB RTL adapter?

Thanks for your help.

Hey Jerry,
I took your advice and bought a new SSD.  I even bumped up RAM to a whopping 3GB.  :
However boot time is still sloooooooooooooow!

Here's the current analysis:

systemd-analyze blame
    1min 11.601s plymouth-quit-wait.service
        40.464s vboxadd.service
        31.669s lightdm.service
          5.029s NetworkManager-wait-online.service
          3.071s dev-sda1.device
          1.036s networkd-dispatcher.service
          875ms ufw.service
          756ms motd-news.service
          739ms lm-sensors.service
          714ms networking.service
          567ms upower.service
          546ms udisks2.service
          540ms apparmor.service
          525ms NetworkManager.service
          507ms systemd-rfkill.service
          487ms apport.service
          469ms grub-common.service
          442ms systemd-udev-trigger.service
          415ms keyboard-setup.service
          373ms pppd-dns.service
          371ms ModemManager.service
          367ms thermald.service
          355ms accounts-daemon.service
          354ms ubiquity.service
          332ms systemd-udevd.service
          330ms gpu-manager.service
          308ms systemd-journald.service
          290ms swapfile.swap
          279ms rsyslog.service
          269ms systemd-journal-flush.service
          222ms wpa_supplicant.service
          210ms avahi-daemon.service
          178ms systemd-resolved.service
          178ms systemd-modules-load.service
          164ms systemd-timesyncd.service
          145ms systemd-logind.service
          129ms lvm2-monitor.service
          120ms smbd.service
          109ms packagekit.service
          100ms [email protected]
          100ms systemd-sysctl.service
            93ms nmbd.service
            90ms polkit.service
            70ms blk-availability.service
            67ms dev-mqueue.mount
            65ms systemd-tmpfiles-setup.service
            64ms dev-hugepages.mount
            59ms systemd-remount-fs.service
            55ms kmod-static-nodes.service
            53ms sys-kernel-debug.mount
            40ms hddtemp.service
            39ms systemd-tmpfiles-setup-dev.service
            38ms plymouth-start.service
            37ms dns-clean.service
            35ms systemd-random-seed.service
            34ms iio-sensor-proxy.service
            32ms resolvconf.service
            31ms console-kit-daemon.service
            30ms systemd-user-sessions.service
            27ms console-setup.service
            27ms sys-kernel-config.mount
            27ms systemd-update-utmp.service
            27ms systemd-tmpfiles-clean.service
            26ms resolvconf-pull-resolved.service
            25ms sys-fs-fuse-connections.mount
            21ms bluetooth.service
            19ms openvpn.service
            16ms plymouth-read-write.service
            14ms console-kit-log-system-start.service
            13ms ureadahead-stop.service
            13ms systemd-backlight@backlight:acpi_video0.serv
            8ms systemd-backlight@backlight:intel_backlight.
            8ms systemd-update-utmp-runlevel.service
            7ms rtkit-daemon.service
            7ms setvtrgb.service
lines 60-75/75 (END)
            27ms console-setup.service
            27ms sys-kernel-config.mount
            27ms systemd-update-utmp.service
            27ms systemd-tmpfiles-clean.service
            26ms resolvconf-pull-resolved.service
            25ms sys-fs-fuse-connections.mount
            21ms bluetooth.service
            19ms openvpn.service
            16ms plymouth-read-write.service
            14ms console-kit-log-system-start.service
            13ms ureadahead-stop.service
            13ms systemd-backlight@backlight:acpi_video0.serv
            8ms systemd-backlight@backlight:intel_backlight.
            8ms systemd-update-utmp-runlevel.service
            7ms rtkit-daemon.service

systemd-analyze critical-chain
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha
The time after the unit is active or started is printed after
The time the unit takes to start is printed after the "+" cha

graphical.target @1min 13.708s
└─lightdm.service @42.038s +31.669s
  └─systemd-user-sessions.service @2.034s +30ms
    └─network.target @2.028s
      └─NetworkManager.service @1.502s +525ms
        └─dbus.service @1.392s
          └─basic.target @1.258s
            └─paths.target @1.258s
              └─resolvconf-pull-resolved.path @1.250s
                └─sysinit.target @1.234s
                  └─systemd-backlight@backlight:intel_backlig
                    └─system-systemd\x2dbacklight.slice @2.32

Any suggestions?

Hi all,
I'm new to LL. I needed to get an old laptop running to use as an audio player -- tried Mint and a couple of other flavours, but LL is the only distro that the wifi would work with. Now I'm up and running. Very straight forward.

Disclaimer - I'm playing around with VMs (using KVM on unRAID, if anybody cares) so there's nothing at stake here - I can wipe & reinstall without any issue.
I did a standard install of LL4 (to ext4) with no issues.  I then did a non-standard install to a BTRFS partition because I wanted to play around with Timeshift.
While the ext4 based install boots just fine, I find that the BTRFS install starts with the following message:

Quote:error: sparse file not allowed.
Press any key to continue...

Whether I press a key or let the message go away on it's own (takes about 20 seconds) the OS loads apparently without issue but seems to take a LOT longer to load than the standard ext4 installation (ext4 @ ~38 seconds vs. BTRFS @ ~6.5 min).

Does anybody have any thoughts on what the "Sparse file not allowed" message is about and whether it and/or the BTRFS OS is the cause for the LONG boot time?
Thanks!