[SOLVED] Mageia 6 in the VirtualBox - update problems

[wildlynx]

Hi!
I'm old Mageia 5 x64 user.
Mageia 5 is not updated any more, so I decided to prepare to update to Mageia 6.

For starters, I installed Mageia 6 x64 in the Virtual Box, 5.2.22, (latest for now)
Both VM config and installation itself were mostly yes - yes - yes - my usual - Plasma - OK - OK - OK style.
I did it for Mageia 5 x64 many times, and I don't think I failed somewhere in the process.

Installation looks OK, and new plasma look nice and so on, and looks like everything works ...

And updates available ... let's install them ...

GUI updater downloads the packets, time passes ... then .. oops .. the screensaver is black with label, that states something like:
Screensaver broken, cannot unlock, use ctrl-alt-f2 to go to console, etc...

OOPS!

I rebooted the VM and on boot X server is broken - black screen and no reaction to anything.

I decided to not to try to fix anything, because the sole purpose of installing Mageia 6 on the VM was to see if there is any problems.
Then next step I planned was to clone old Mageia 5 x64 VM install and see how 5 to 6 update works, but I not even got there.

Is it VirtualBox issue or Mageia 6 is kinda broken?

[jkerr82508]

You probably should have disabled the plasma screen locker:

https://blog.mageia.org/en/2018/05/10/t ... ourselves/

Jim

[martinw]

As Jim says, otherwise the update stalls when the screen locker kicks in, and you are left with a partially updated system. You can probably recover by switching to a text login (RightCtrl-F2 should do it in VirtualBox), logging in as root, and running

Code: Select all

urpmi --auto-select --auto-update

Repeat that command until it reports no more packages to update, then reboot.

[wildlynx]

You probably should have disabled the plasma screen locker:

https://blog.mageia.org/en/2018/05/10/t ... ourselves/

Jim

Thanks!

Looks like update is still running...

I was close to discovering it - I decided to blame the screensaver and disabled it in power management, but there is another place and now I found it.
The desktop behaviour is another place where it must be disabled.

I cloned the freshly installed VM and was trying to update it again when I was surprised, that screensaver is activated again.

[wildlynx]

As Jim says, otherwise the update stalls when the screen locker kicks in, and you are left with a partially updated system. You can probably recover by switching to a text login (RightCtrl-F2 should do it in VirtualBox), logging in as root, and running

Code: Select all

urpmi --auto-select --auto-update

Repeat that command until it reports no more packages to update, then reboot.

Thanks to you too!
I will wait for update to finish and then will post the result.

[wildlynx]

Thanks!
Looks like update was successful.
They probably need to alter the rpmdrake update, to make rpmdrake block the screensavers.