Hi there, I’m fairly new to working with KDE and I was trying to update a VM that I had on my laptop for a while as I hadn’t logged into it in so long that it had accumulated a system update. On the original VM the only thing aside from the base settings that I had changed was that I had downloaded Cura slicer (3D modelling/printing software) and I had added a shortcut to a website onto the desktop. When I opened the update installer, I saw that there was a system upgrade available and that there was an available update to Cura. I tried to ‘update all’ and got an error for Cura but the system upgrade started just fine. After the download I restarted using the button in the application, and upon restarting the login screen looked completely different, the screen size/resolution wasn’t updating to fit my screen, the on-screen keyboard was active by default and it covered 2/3 of the screen, and when I pressed enter on either the physical keyboard on my laptop or the OSK in the VM nothing happened. After this, I tried to boot the VM into the terminal by pressing Ctrl+Alt+F2 and nothing happened. I re-installed the OS from the .iso file that I originally used to create the VM and it worked, so I downloaded and installed the system using system install and it worked. I then tried to update the system using the installer and the same thing happened as before. Next, I created a brand new VM using the latest .iso file on the KDE neon download page, but when I tried to install the system calamares crashed with a segmentation error 11. When I tried to create the crash report the debugger ‘quit unexpectedly’. So now as it stands I have 2 VMs and neither of them work as they should. I have one that is running an updated version of the original .iso file but that does not let me log in or access the terminal, and one that won’t even install the OS.
I’ve done a little more messing around on the VM that I updated from the original .iso image and none of the Ctrl+Alt+Fn keybinds work, but with Ctrl+Alt+F2 for some reason it’s suddenly started giving me the terminal’s login prompt for about half a second before launching the GUI and even when I’ve been quick enough to type while the prompt is onscreen it doesn’t look like it’s accepting any inputs as none of the text is appearing onscreen. The last part may be because I’m being stupid and misremembering whether it was asking for a username/password as passwords aren’t shown, but either way I can’t do anything with this as it immediately loads the GUI and forces me out pf the terminal as a result.
If I press F12 during the splash screen the only options I see are boot drive options which don’t help as that’s not what I’m trying to do (although I may have to resort to booting from a mounted drive and reinstalling).
I would also like to clarify that both of the VMs are running the user edition, neither of them have had any changes made to them aside from updating the original VM and trying to install the new VM, as I reinstalled the base .iso file for both of them as I was troubleshooting.
Additionally, as mentioned earlier, I can’t get logs for either of the VMs as the original won’t allow me to access the console or login, and the new one’s crash handler quits.
I hope I’ve given all the information needed for some of you who are much better at this than me to help a newbie 
I hate posting constantly because it makes me look like I like the sound of my own voice, but by spamming [esc] I have managed to get into BIOS and from there I’ve accessed GRUB console, but now the issue is i have no idea what I’m doing to try and fix this mess. Any help is much appreciated, but for now I’m going to try sudo apt update and sudo apt full-upgrade.
Edit: I have no idea how I could have been this stupid, ignore the last part of the comment.
Tried a new VM on the newest user version (20250427-0106) and the testing version I had access to yesterday (20250422-0430) and the same installer issue. I’ve put in an issue report on calamares’ github page but I don’t think it’s necessarily a calamares issue.
First, welcome to the KDE Discuss forum.
You’re using KDE Neon as your OS –
- Where did you get the Oracle VirtualBox package?
- Did you remember to enable Virtual Machine support in your Laptop’s UEFI/BIOS?
- If you’ve enable Secure Boot, you’ll need to ensure that, a KMP key is loaded into the Laptop’s UEFI/BIOS – check the contents of ‘/etc/uefi/certs/’ to see if the installation of the Oracle VirtualBox package has dropped a suitable Key certificate into that directory.
I’m not using KDE Neon – here on openSUSE Leap, there’s a “mokutil” application which is used to manage the system’s UEFI/BIOS keys.
I have absolutely no idea if KDE Neon has something similar or, not …