Bug 434229 - neon-user-20210304-0945.iso doesn't show "Start KDE neon live" on boot, so user thinks installer failed.
Summary: neon-user-20210304-0945.iso doesn't show "Start KDE neon live" on boot, so us...
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (other bugs)
Version First Reported In: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-10 11:18 UTC by Tony
Modified: 2025-09-20 09:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tony 2021-03-10 11:18:33 UTC
SUMMARY
Iso image neon-user-20210304-0945.iso fails to show "Start KDE Neon. Press Enter to start" so user is facing a black screen and thinks installer is stuck. Pressing Enter successfully starts live image.

STEPS TO REPRODUCE
1. Burn the ISO in the title on a usb stick with Rosa image writer, dd or usb-creator-gtk.
2.Choose the appropriate usb disk on the boot menu of your computer. 
3. A black screen appears with no information, so you think live image failed tonstart. Blindly pressing Enter makes it to work properly, instead. 

OBSERVED RESULT
Live image seems to fail on boot.

EXPECTED RESULT
A "Press Enter to start" message should appear. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Carlos De Maine 2025-09-20 09:35:59 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!