Linux Lite 7.2 RC1 Released

[Valtam]

Release Announcement

Linux Lite 7.2 RC1 is now available for testing.

We're really excited about what this release brings to you. See below for more details.

Linux Lite 7.2 Final will be released on 1st November, 2024.




Changes:

Lite Updates - Re-written in Yad

Lite Updates has been re-written in Yad as Yad provides more flexibility than Zenity and will help us to expand and add more options to it in the future.




Lite Theme Manager:

Brand new to the Linux Lite family of Applications is Lite Theme Manager.
Lite Theme Manager takes the guess work out of adding themes to your desktop, icons and mouse cursors with an easy point-and-click solution.
Thank you and credit goes to Huzaifa Qureshi for writing this application.













Lite A.I. Support:
Linus Lite is leading the way in which A.I. is complementing the Support portion of our operating system.
We're extremely happy with the way that it's turned out and a huge thank you again to Huzaifa Qureshi for his efforts on this.



Plus many other tweaks and changes.

Window Theme: Materia
Icon Theme: Papirus
Font: Roboto Regular

How do I know if my Windows PC has UEFI?

In Windows Search, type msinfo or msinfo32 and launch the desktop app named System Information. Look for the BIOS Mode item, and if the value for it is UEFI, then you have the UEFI firmware. If it says BIOS Mode Legacy, then that’s the firmware you’re running.

Secure Boot is supported, but unless you know exactly how to handle it, it is a P.I.T.A. at best so I am going to say...you must disable Secure Boot to enable stress free computing.

Some helpful snippets from the latest Help Manual:





UEFI Support link - https://www.linuxliteos.com/forums/uefi-secure-boot/

Details:

Kernel: 6.8.0-45 ( custom kernels also available via our Repository for versions 3.13 - 6.11 )
Chrome: 129.0
Thunderbird: 115.15
LibreOffice: 24.2.6.2
VLC: 3.0.20
Gimp: 2.10.36
Base: 24.04.1

Known Issues:

Please enter them into this thread. Thank you.


There is no upgrade to or from RC releases. RC releases are for testing only and it is not recommended to run them as your main or secondary operating system.

Downloads:

Release Name: Linux Lite 7.2 RC1
Size: 2.9Gb (DVD, USB)

Download Linux Lite 7.2 RC1 from one of the mirrors: (some may still be syncing)

HTTP & HTTPS:

https://sourceforge.net/projects/linux-l...s/7.2/rc1/

Brazil - http://sft.if.usp.br/linuxlite/isos/7.2/...-64bit.iso
China - https://mirrors.sjtug.sjtu.edu.cn/linuxl...-64bit.iso
Ecuador - http://mirror.cedia.org.ec/linuxliteos/i...-64bit.iso
Ecuador - http://mirror.ueb.edu.ec/linuxliteos/iso...-64bit.iso
Ecuador - http://mirror.uta.edu.ec/linuxliteos/iso...-64bit.iso
Ecuador - http://mirror.espoch.edu.ec/linuxliteos/...-64bit.iso
England - https://www.mirrorservice.org/sites/repo...-64bit.iso
England - https://mirror.vinehost.net/linuxlite/is...-64bit.iso
Germany - http://mirror.alpix.eu/linuxliteos/isos/...-64bit.iso
Germany - https://mirror.alpix.eu/linuxliteos/isos...-64bit.iso
Greece - http://ftp.cc.uoc.gr/mirrors/linux/linux...-64bit.iso
Greece - https://fosszone.csd.auth.gr/linuxlite/i...-64bit.iso
Hong Kong - http://mirror-hk.koddos.net/linuxlite/is...-64bit.iso
Hong Kong - https://mirror-hk.koddos.net/linuxlite/i...-64bit.iso
Hungary - http://quantum-mirror.hu/mirrors/pub/lin...-64bit.iso
Hungary - https://quantum-mirror.hu/mirrors/pub/li...-64bit.iso
Indonesia - https://pinguin.dinus.ac.id/iso/lite/iso...-64bit.iso
Netherlands - http://mirror.koddos.net/linuxlite/isos/...-64bit.iso
Netherlands - https://mirror.koddos.net/linuxlite/isos...-64bit.iso
New Caledonia - http://mirror.lagoon.nc/linuxlite/linuxl...-64bit.iso
Sweden - http://ftpmirror1.infania.net/linuxlite/...-64bit.iso
USA - http://mirror.clarkson.edu/linux-lite/is...-64bit.iso
USA - https://mirror.freedif.org/LinuxLiteOS/i...-64bit.iso
Vietnam - https://mirror.freedif.org/LinuxLiteOS/i...-64bit.iso

Checking the MD5SUM of the Linux Lite ISO:

Open a Terminal on Linux Lite and do:

Code:

md5sum linux-lite-7.2-rc1-64bit.iso

MD5SUM: 2d8359d0e15aef7c4f6a9cfd6ce3ac26

Check that it matches the exact characters in sequence above.


Checking the SHA256 of the Linux Lite ISO:

Open a Terminal on Linux Lite and do:

Code:

sha256sum linux-lite-7.2-rc1-64bit.iso

SHA256: a0cfbe8a0c3597f9247a5d27360e6ba51e86ec0856d8a9b2b06753f6a9a7ffbd

Check that it matches the exact characters in sequence above.


TORRENT (Fastest way to download the RC)


https://sourceforge.net/projects/linux-l...t/download


64bit Torrent - linux-lite-7.2-rc1-64bit.iso.torrent
Hash: aeaeac8d6f819e693b41b4c3abca6b4285d08171
Size: 2.9Gb (DVD, USB)

Live USB/DVD/VirtualBox/Vmware:

Login is automatic, no credentials are required. The image can be written to a 4gb or larger USB stick, or a writable DVD. Alternatively, you can use the dd command: sudo dd if=linux-lite-7.2-rc1-64bit.iso of=/dev/sdx bs=4M where 'x' is the letter of your usb stick. In linux to find out the letter of your usb stick, open a terminal and type: df -h It is usually listed as 'media' or similar. Please see the built in Help Manual if you require a more detailed explanation of this procedure.

A good, simple point and click USB ISO burner is https://www.balena.io/etcher/ or https://rufus.ie/
In our testing, Etcher and Rufus (for Windows only) have proven to be the most reliable. Etcher is available for Mac, Windows & Linux.

If the screen locks during Live mode, type linux into the user box and click on the Login button (no password required)

Minimum Recommended Specs:
1Ghz processor
2GB ram
20gb HDD/SD
VGA screen capable of 1024x768 resolution
DVD drive or USB port for the ISO image

Preferred Specs:
2GHz processor+
4GB ram+
40gb HDD/SSD+
VGA, DVI or HDMI screen capable of 1366x768 resolution+
DVD drive or USB port for the ISO image

Login to the live desktop is automatic.

The first thing you MUST do after a fresh install of Linux Lite is run Menu, Favorites, Install Updates.

As this is a RC release, there are bound to be bugs etc. Please help make the final stable for other people by participating in this RC. Please report any bugs and feedback in this thread.


Thank you

Jerry and the team.

[stevef]

Thank you for the new release.  Installed and testing.
While trying the new yad Lite Updates tool, I came across an issue which may be present in earlier versions as well.

At the end of the Lite Update run, if the user wants to save the log in a new folder, the folder that gets created appears to be owned by root.
The script appears to save the log in the new location, but the file doesn't appear to be present afterwards.

[Valtam]

Thank you for the new release.  Installed and testing.
While trying the new yad Lite Updates tool, I came across an issue which may be present in earlier versions as well.

At the end of the Lite Update run, if the user wants to save the log in a new folder, the folder that gets created appears to be owned by root.
The script appears to save the log in the new location, but the file doesn't appear to be present afterwards.

Thank you steve, we'll look into it. Is that live or installed where that occurs?

Sent from my Mobile phone using Tapatalk

[stevef]

It's a full installation to disk.
It may well be an issue in earlier versions - certainly seems to be present in 7.0, have not yet had chance to try on 5.x or 6.x.  Typically I make a directory for saving log files from the command line so not noticed this before.

On the subject, if there is a change, would you consider having the script format the file name so that date and time part is in the form 'yyyy-mm-dd hh:mm:ss' and placed nearer the start of the name. Seems more logical (to me) for sorting than having the 'day of the week-dd-month-year-time' format.
Thanks.

[Şerban S.]

It's a full installation to disk.
It may well be an issue in earlier versions - certainly seems to be present in 7.0, have not yet had chance to try on 5.x or 6.x.  Typically I make a directory for saving log files from the command line so not noticed this before.

On the subject, if there is a change, would you consider having the script format the file name so that date and time part is in the form 'yyyy-mm-dd hh:mms' and placed nearer the start of the name. Seems more logical (to me) for sorting than having the 'day of the week-dd-month-year-time' format.
Thanks.

 I installed it, but I skipped this. I only view the log if something seems weird and further more, I was focused on seeing the new Apps at work.
Since this might happen if the issue is a Root ownership I'll reinstall and see what happens. I'll get back with what I find.
Besides this, nothing to say. All went flawlessly.
Maybe it worths mentioning that the boot media, is a Ventoy disk (and has about 5 images on it).
Best regards!

[Şerban S.]

[...]
While trying the new yad Lite Updates tool, I came across an issue which may be present in earlier versions as well.
At the end of the Lite Update run, if the user wants to save the log in a new folder, the folder that gets created appears to be owned by root.
The script appears to save the log in the new location, but the file doesn't appear to be present afterwards.

I reinstalled, as I said before.

It seems that the issue is local. I saved the log file in a location where I usually keep machine related data.
File: LL-7.2-RC1-llupdates-Sat-28-Sep-2024-14:01.txt (Local time: UTC + 3)
Here is an excerpt:

Code:

Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following upgrades have been deferred due to phasing:
  file-roller python3-distupgrade ubuntu-release-upgrader-core
  xdg-desktop-portal
The following packages have been kept back:
  inxi zenity zenity-common
The following packages will be upgraded:
  cloud-init cups cups-browsed cups-client cups-common cups-core-drivers
  cups-daemon cups-ipp-utils cups-ppdc cups-server-common google-chrome-stable
  intel-microcode libcups2t64 libcupsfilters2-common libcupsfilters2t64
  libcupsimage2t64 libopenjp2-7 libppd2 libppd2-common linux-firmware
  python3-update-manager update-manager-core
22 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 607 MB of archives.
[...]

I have no clue to what happened on the machine you found this.
As I said above, I also use custom locations (different drive, different directories).
A common mistake I make sometimes is that after partitioning a drive, I forget to change ownership to my drives.
So might be a possible explanation. After partitioning, all new drives belong to Root. Nobody can write anything on them unless the ownership is changed to the intended user.
When I service some other's machine, usually having low resources, setup takes long and I get bored waiting. My attention gets fuzzy and I forget to change the ownership, mostly due to a different partition naming. (I use /home, /proiecte and /video).

The steps I followed are:
View log ---> Save log ---> Choose custom destination ---> Save into file.
Hope that might somehow help.

Best regards! Șerban.

[stevef]

Thank you for trying.
Just to confirm, did you use the Lite Updates Tool to create a new directory or select a directory that already existed ?

[Şerban S.]

Thank you for trying.
Just to confirm, did you use the Lite Updates Tool to create a new directory or select a directory that already existed ?

I think I see your point. 
Might there be a flaw in the script?
As I said, I used a partition that was already there and saved inside a directory on that partition (/video/Dell-T-1700/*).
I do this with almost all the files I save, then I move them where suitable.  Having the files in /video/ spares me of taking care of the file sizes (there are over 300 GB available there).
I will check at the next update to see if I use the Lite Dialog if this goes as "root". As far as I remember, this is possible since the MkDir is issued from inside the script and it used "sudo apt install *". Since the persistence of the Root session is long enough to allow the updates, we can have an answer here.
The only way out in this case, is adding a ChOwner after the Dir creation and before saving the file. A delay before the save instruction might also be necessary to allow the system to update the directory structure and prevent the "File Missing" error.
Also, invoking "SaveAs" dialog as Root (this is the case as I see it), will generate a chain of Root processes, hence the Dir owner is Root and the file owner is also Root.

Best regards, Șerban.

PS: I checked the file attributes. The owner is "serban". The glitch might be somewhere else. Anyway, I'll check again with the Lite Updates. Maybe if the Dir owner is Root, the file will inherit the ownership.

[Valtam]

Hi steve, I cannot reproduce your issue, in a VM and on my own install, the log defaults to home and is accessible/readable.

[Valtam]