Bug 424730 - My system won't start
Summary: My system won't start
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-28 05:56 UTC by Thallyssonklein
Modified: 2025-09-20 09:36 UTC (History)
4 users (show)

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


Attachments
Screen to select the system (2.88 MB, image/jpeg)
2020-07-28 05:59 UTC, Thallyssonklein
Details
Black screen (2.94 MB, image/jpeg)
2020-07-28 05:59 UTC, Thallyssonklein
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thallyssonklein 2020-07-28 05:56:24 UTC
I used Neon for months, and in the last days (I always keep the system up to date) after restarting my system it didn't start anymore. A screen appears that asks you to select a system to start, when i select it starts a black screen where it is not possible to do anything or even open the terminal mode. I reinstalled it once and managed to use the computer for a day until the same problem happened again. I tried to reinstall again today and now it doesn't even install. Attached is the photo of the screen that asks to select the system and the black screen.

Note: I am using a Lenovo Thinkpad T430u
Comment 1 Thallyssonklein 2020-07-28 05:59:00 UTC
Created attachment 130451 [details]
Screen to select the system
Comment 2 Thallyssonklein 2020-07-28 05:59:32 UTC
Created attachment 130452 [details]
Black screen
Comment 3 Carlos De Maine 2025-09-20 09:36:00 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!