KDE Plasma 6.2

[Beerislife]

That was quick!

Plasma 6.2 was announced in a FB group yesterday and this morning it was ready to install!

No problems to report, yet!

Had to "sudo apt autoremove" to get rid of some old packages!

[claydoh]

I'm on noble, so I am still waiting

lol.

[notabug]

I'm on Neon. The new Plasma 6.2 wallpaper is the prettiest one I remember seeing.

[GreyGeek]

Thumbs up on KDE Neon 6.2 !!!!!
Running faultlessly.

[Snowhog]

Thumbs up on KDE Neon 6.2 !!!!!
Running faultlessly.

I'm having problems with it in an Oracle Virtualbox VM. I downloaded the neon-user-20240929-1217.iso, created a new VM, and installed. The installation was fine; no issues, no errors. But, when rebooting the VM, it came up with an error window saying it couldn't find a bootable medium! That's the first time EVER with a VM I've created.

Fresh attempt. Deleted all files of the previously created VM and created a new one. Installed from the same downloaded .iso. No reported issues. I'm told:


I click the Done button, I'm told to remove the installation media and press Enter. I do, the Live session closes, and the VM is rebooted, and I'm presented with this:


As I stated, I've NEVER seen this before in all the times I've created VMs in Oracle Virtualbox. I have to conclude that there is something wrong with the .iso.

[claydoh]

They work fine in virt-manager for me, so I'd say it is a combo of things. The errors look exactly like what I have seen in the past where an MBR or EFI install of a VM for whatever distro I was looking at didn't boot. I'd just switch to the other for a new install, and it usually would be ok. I have not seen this myself in ages, but I also have not used Virtualbox in ages.

I *think* Virtualbox defaults to mbr, which is usually a solid choice for VM usage. Virt-manager does as well.
I don't think I have ever seen this in virt-manager, but I can't say for sure.

I'll test later if I find some time. What version of virtualbox are you using?

[claydoh]

I'm on noble, so I am still waiting

lol.

Not for long, though. Got the updates last night. I do like the wallpaper.

[Snowhog]

The errors look exactly like what I have seen in the past where an MBR or EFI install of a VM for whatever distro I was looking at didn't boot. I'd just switch to the other for a new install, and it usually would be ok.

This install is GPT, just as my other KDE neon VM is. That VM boots just fine. So I don’t understand why this one would not.

[claydoh]

Software bug? A weird bit on the image?

GPT? no, I mean the emulated firmware/BIOS VB will use for the OS install -- checking or unchecking the "Enable EFI" (special OSes only) option"

Here is my install using the version of Virtualbox from the 24.04 repos, using whatever the defaults are everywhere, and the neon-user-20240929-1217.iso:


So BIOS booting

A different install Using EFI for booting:

[Snowhog]

claydoh On my Desktop PC (Kubuntu 24.04), I downloaded neon-user-20241010-1519.iso. I installed Virtualbox (7.0.16-dfsg-2ubuntu1) from Synaptic Package Manager and created a 75.00 GB VM.


I started the VM and installed KDE neon. Installation was without incident, just as the previous (now) four attempts were on my iMac with Oracal Virtualbox 7.0.

Restarting the VM still ends up with the same issue as shown in image #2 in post #5.

I'm choosing to use gpt and not mbr when I create a new partition table. Why then, do I see this:



If I don't change anything, the default is Master Boot Record of VBOX HARDDISK (/dev/sda). I have two other options as shown. On my iMac, my last attempt at installing neon was to select System Partition (/). Didn't make any difference. When the VM was restarted, the same issue.

What the hell is going one! I have NEVER had this problem in all the years I've been using Virtualbox. Never!

[claydoh]

You checked the option "EFI (special OSes)" or whatever?

I am on the same version of VB.

What the hell is going one! I have NEVER had this problem in all the years I've been using Virtualbox. Never!

Stuff happens?
And by stuff, I mean oracle, maybe?
I found Virtualbox to be more sluggish and VMs needing more resources, so a few years back I moved to virt-manager.
Not polished, in terms of the UI, but I can run machines on this low spec, low-wattage pc without any stuttering or anything.
it is basically a GUI for Qemu and other things.
No, it is not a 100% drop in replacement for everyone (no easy simple file sharing between guest<>host), but it is worth a look if the other stuff is being a pita.

My fave thing is running a machine remotely on the local network, and almost not being able to tell that it is running on the 6th gen i3 NAS box

[GreyGeek]

An automatic update on my KDE Neon installation borked KDE, so I had to rollback to yesterday's BTRFS snapshot.

[Snowhog]

You checked the option "EFI (special OSes)" or whatever?

No, I didn’t. My host machine is EFI, so I’ll make that change and see what happens.

[claydoh]

My host machine is EFI, so I’ll make that change and see what happens.

That shouldn't matter, I think, since this is all emulated.

I can only guess that there may be combinations of little things stacking on top of each other, *and* you have displeased some gnu god somewhere, maybe?

[Snowhog]

Well, checking "EFI (special OSes)" and starting the VM results in this:



I can understand this one though (I think), as when I created the partitioning, it was based on just what specifying GPT required, as shown in the second image in post number 10.

I'm giving up for now. Something has to have changed in KDE neon, that is causing this mess.