Bug 478949 - Neon Unstable + VMware Workstation = no boot after restart/update
Summary: Neon Unstable + VMware Workstation = no boot after restart/update
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-23 18:19 UTC by Eugene Savitsky
Modified: 2025-09-20 09:35 UTC (History)
4 users (show)

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

Attachments
screenshot of booting screen (4.48 KB, image/png)
2023-12-23 18:21 UTC, Eugene Savitsky 		Details
CPU has been disabled (4.08 KB, image/png)
2023-12-23 18:26 UTC, Eugene Savitsky 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Savitsky 2023-12-23 18:19:59 UTC 
STEPS TO REPRODUCE
1. Install Neon Unstable 
2. Run first time - OK
3. Run update. Restart
4. Boot variants appears, but choosing any option does nothing, just same screen. No errors whatsoever.
Comment 1 Eugene Savitsky 2023-12-23 18:21:29 UTC 
Created attachment 164409 [details]
screenshot of booting screen

BTW Before you press Enter, you can go thru options, but if you press enter all stalls.
Comment 2 Eugene Savitsky 2023-12-23 18:26:59 UTC 
Created attachment 164410 [details]
CPU has been disabled

Tried to press E for editing the Grub's settings and got this window...
Comment 3 Carlos De Maine 2023-12-26 11:57:28 UTC 
assuming this is offline updates.  known bug.  working on it.
Comment 4 Carlos De Maine 2025-09-20 09:35:18 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!