What are you reinstalling? New haos on old kvm? Old haos on new kvm? New deployment?
From the logs I read that your user chris
has no rw perms within the haos.
What are you reinstalling? New haos on old kvm? Old haos on new kvm? New deployment?
From the logs I read that your user chris
has no rw perms within the haos.
Then what happened? What a cliffhanger! /s
I somehow missed this to be a flatpak via Discover. Granted this may not be usual in distros with a traditional update model, downgrading packages may be present in rolling distros, or distros with overlapping minor versions, or having 3rd party repos providing conflicting packages to those of the distro.
I offer my system as example:
The following product is going to be upgraded:
openSUSE Tumbleweed 20240211-0 -> 20240313-0
The following 14 packages are going to be downgraded:
ghc-binary ghc-containers ghc-deepseq ghc-directory ghc-exceptions ghc-mtl ghc-parsec ghc-pretty ghc-process ghc-stm ghc-template-haskell ghc-text ghc-time ghc-transformers
It is called “downgrading”, and it is not uncommon to have some packages downgrading when updating/upgrading a system, due to several reasons.
That is why I also mentioned the latch/sensor, it may got stuck.
It sounds like the issue is with the lid latch/sensor, not with the graphics. Some laptops may not boot if the lid is closed, and some have options on the firmware to enable to boot when the lid is closed / on a docking station.
Not the same as 10hr nyan cat or bacon pancakes
Only when shared via yahoo! news
With vbox I don’t think you can do that, nor with any other hypervisor delivering full virtualization. You could try with a paravirtualization, like Xen, and see if you can trick the OS
Note that I don’t know if windows is supported as a paravirtualized guest.
Maybe Wikiloc fits the bill here
It would be General Failure reading the disc. I would fsck him up, and replace disc if necessary.
Yes, I know those may be different oses, but I was thinking multiplatform