Bug 425394

Summary: Latest Neon User Edition ISO image is 18.04 based, not 20.04.
Product: [KDE Neon] neon Reporter: Clay Weber <clay>
Component: Live/Install imagesAssignee: Neon Bugs <neon-bugs>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: jdally987, jr, neon-bugs, sitter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Image showing the output of lsb_release, as well as the iso file name
md5sum.txt

Description Clay Weber 2020-08-15 18:11:14 UTC
SUMMARY
Downloading the ISO from the link on the KDE Neon website is a Bionic image

STEPS TO REPRODUCE
1. Go to https://neon.kde.org/download
2. Click the link to download  the User Edition Live/Install Image
3. Create live USB stick, or use in a virtual machine, and boot the image
4. Check the resulkt from the command :  lsb_release -a 

OBSERVED RESULT
Result shows a system based on Ubuntu 18.04 Bionic


EXPECTED RESULT
The image should be based on 20.04 Focal




The last image version built was Focal based.
Comment 1 Clay Weber 2020-08-15 18:13:42 UTC
Created attachment 130896 [details]
Image showing the output of lsb_release, as well as the iso file name
Comment 2 jdally987 2020-08-15 19:11:28 UTC
Created attachment 130897 [details]
md5sum.txt

Yep same here - attached md5sum.txt from root of "neon-user-20200813-1119.iso" (sha256: 946123A877C1514E68E910A137DFB69E69D854DD447344A9962992DA6FB3DE14)
Comment 3 Clay Weber 2020-08-20 22:13:45 UTC
The current iso 20200820-1117 is also 18.04 based.
Comment 4 Carlos De Maine 2025-09-20 09:35:16 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!