20.04.4 to 22.04.1 upgrade: dovecot-core, libdvd-pkg, VirtualBox, amdgpu

[Liam Proven]

On Thu, 25 Aug 2022 at 04:49, Andrew J. Caines <A.J.Caines at halplant.com> wrote:
>
> Liam,
>
> Thanks for taking the time to read and respond to my post with some good
> questions and observations.

Well, I am trying, but bear in mind this is not my day job and I only
dip into the group occasionally. You seem to be asking for a mixture
of eidetic memory and near-omniscience from us and that's why nobody
else is replying, I think.

> >> It has LVM,
> > Uhoh.
> >
> >> LUKS encryption,
> > Double uhoh.
>
> If one day the wrong bit flips and I can't decrypt /, it's going to be a
> pain, but no critical data will have been lost. I shall summon Murphy by
> saying that it hasn't happened in the six or so years since the initial
> install.

As you wish.

>  As for LVM and LUKS, both are mature and stable.

Look, all I am doing is pointing out the bits that make me nervous.

There are tons of xNix tech that is mature and stable that I
personally still do not trust and avoid using.

I am just pointing out the bits in your list that I would not use myself.

> > Btrfs *and* ext4? Why? Which is on which?
>
> ext4 on / from what was (and still is) the Ubuntu default on install,
> btrfs for a couple of data volumes.

If you want us to try to work out what's wrong and what might have
happened, you need to tell us. Vague generalisations like this are not
enough.

If we can't form a picture of what you have we can't even suggest anything.

Right now, I have no picture whatsoever, except a hissing tangle of
venomous snakes surrounded by warning signs.

> > What packages?
>
> Listing all 2064 installed packages would be excessive and saying
> "Ubuntu packages" would be unhelpful. What would be a useful answer?

You said some packages had problems. We need to know which ones. Not
all of them but the ones that have problems.

You are not even sketching the issues here, you're just saying that
there are some and asking for advice.

I can't advise without specific info.

All I can do is give general overall tips.

Which I am doing and you are rejecting.

I left this email a long bank holiday weekend without answering
because your vague, elliptical, specific-avoiding replies made me very
angry.

Normally I'd just mark read and walk away but I thought it would be
helpful and useful to you to tell you that this happened and why and
how you could avoid it happening again in future.

At this point, where you actively protest being asked for more info, I
am VERY close to just walking away.

But I have started to answer so I will give  it another few lines.

> Don't worry, they are not critical infrastructure services, just local
> mail management... or were you gulping at Snaps and/or Flatpaks?

YES!

LVM = bad
Btrfs = bad
Mixed filesystems = bad
Snap = bad
Flatpack = bad
Snap + Flatpak = bad²

What do you want from me here?!

> > How much free space did you have before you started?
>
> Plenty in / and I don't mind clearing out /boot when needed.

"Plenty" is not an answer.

OMG, no, this is doing bad things to my blood pressure. Deleting to
end and pressing Send.

-- 
Liam Proven ~ Profile: https://about.me/liamproven
Email: lproven at cix.co.uk ~ gMail/gTalk/FB: lproven at gmail.com
Twitter/LinkedIn: lproven ~ Skype: liamproven
UK: (+44) 7939-087884 ~ Czech [+ WhatsApp/Telegram/Signal]: (+420) 702-829-053