Bug 481056

Summary:	In a Virtualbox VM, performing offline updates with Discover causes the system to hang at GRUB after the next boot
Product:	[KDE Neon] neon	Reporter:	Nate Graham <nate>
Component:	Packages User Edition	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	grave	CC:	akselmo, jr, neon-bugs-null, sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Critical error log

Description Nate Graham 2024-02-08 15:10:37 UTC

STEPS TO REPRODUCE
1. Download Neon User ISO
2. Install Virtualbox
3. Use Virtualbox to set up a new VM with the intention of installing Neon User in it. 2 GB Ram, 2 CPU cores, 25 GB virtual disk
4. Boot up Neon User (so, using Plasma 5) from the ISO
5. Launch the installer and install the system using all default settings except for changing the timezone to Denver
6. When prompted, reboot the system
7. In the installed OS, open Discover and check for updates
8. When updates appear, install them
9. When prompted by Discover, click the Restart button


OBSERVED RESULT
Offline updates are installed. After the installation, the GRUB screen appears, but with no interactivity. I cannot use the arrow keys to select another option, or select the active one with the return/enter key. As a result I am stuck and cannot boot into the system again.


EXPECTED RESULT
The GRUB screen let me select "Neon GNU/Linux" and I get taken to the SDDM login screen

Comment 1 Nate Graham 2024-02-08 15:16:30 UTC

Created attachment 165669 [details]
Critical error log

I powered down the guest OS and tried powering it on again. This time the GRUB screen was responsive but selecting "Neon GNU/Linux" with the return key causes the screen to go black and then I was returned to the GRUB screen again. I repeated this two more times with the same results. After the third try VirtualBox itself informed me that a critical error had occurred and directed me to a log file, which I have attached.

Comment 2 Akseli Lahtinen 2024-02-08 15:22:52 UTC

Just to add, I had same issue, but when I used terminal to update with `sudo apt dist-upgrade` I did not get this bug. (Same VM image, just cloned)

Comment 3 Nate Graham 2024-02-12 17:02:09 UTC


*** This bug has been marked as a duplicate of bug 478295 ***