Search:

Could be an electric interference, like a desktop light/modem/printer/usb reader ....

Mine works; have some warnings (yellow lines) but not errors (red lines from 'journalctl -b' output.

Be sure to only use 'hirsute' entries inside /etc/apt/sources.list
Avoid non genuine source...

Are you booting the latest hirsute kernel from proposed archive ?

it has now the required nvidia 460 driver:

linux (5.8.0-36.40+21.04.1) hirsute
* CVE-2021-1052 // CVE-2021-1053
-...

broken package: know about it via synaptic

Glance at errors (red lines) from 'journalctl -b' output into a terminal.

Did 'journalctl -b' expose some usefull errors (red lines) ?

crash file is stored into /var/crash/

to know what have happened, you can watch the 'journalctl -b' output into a terminal: red lines are errors, yellow ones ares warnings and can be mostly...

i suppose you have installed non genuine package/app from ppa/... that still need to use the old libsensors4. So be sure to deactivate/purge this(these) app(s) and downgrade their dependencies if...

if kernel 5.7 is working but not 5.10, then the problem is with 5.10 kernel not supporting mixed gpus

1) https://www.howtogeek.com/287014/how-to-create-and-use-symbolic-links-aka-symlinks-on-linux/
2) https://askubuntu.com/questions/361741/what-are-dependencies
3) update means 'get newer version(s)...

maybe the 'au' archive is actually down; try the main one (without 'au') and you can remove all the deb-src entries if you never compile softs

note that bionic is near end of life in a few months...

Welcome here

i understand you have a great experience with Pippermint (which i dont) but your future device will have plenty room to install what you want. Indeed the Pippermint forum is the right...

Nowadays all these devices work by default with linux; myself using all-in-one since years on ubuntu :p

1) check /etc/apt/sources.list for possible mixed releases entrie(s)
2) purge /var/cache/apt/archives/
3) update again

here is a guide : https://www.wikihow.com/Format-a-Hard-Drive-Using-Ubuntu#

So start to clean the system first, via disabling all external sources (ppa,...) and running 'sudo apt-get autoremove'. Then update again.

Howto:

https://askubuntu.com/questions/1260465/how-to-install-ubuntu-base
https://wiki.ubuntu.com/Base/InstallationExample

Goto the 'journalctl -b' output to know what is going on when the lid is closed as you said.
maybe do some ghost hunting too.

From the icon menu, select "system monitor", then select the upgrade process to kill it.
Or follow the solutions given here:...

Hm, already discussed, and yours marked as dupe of https://gitlab.gnome.org/GNOME/nautilus/-/issues/949
but lot of possible workaround too :p

Glance at 'journalctl -b | grep Brave' output into a terminal, and pay attention to red lines (errors) too.

You have a good point to discuss on https://gitlab.gnome.org/GNOME/nautilus/-/issues :P

Myself have not digged around internal nautilus conf via dconf, sorry.

Why don't you let the installer (ubiquity) doing its stuff itself ? Your own way may break the rules :o

For each hitted problem, glance at 'journal-b' output from a terminal. Pay attention to red line(s) as 'error'; yellow line(s) are warnings. You might found something pointing to your browser...

Via 'synaptic' (install it if not yet done) search for 'gnome-shell-extension-the.one.you.want' and select it for installation.
'gnome-shell-extension-ubuntu-dock' will install a few extensions....