Search:

This is referring to the issue in this thread: https://ubuntuforums.org/showthread.php?t=2456520

It's easier if you keep your issue in a single thread.

The bold word "that" refers to the entire preceding sentence.

Instructions:
1: Make a plan. What partitions do you need, on which drive do you want them, where do you mount them.
2: Use the...

There's some unexpected output from sudo apt update, but, as the tools itself notes, this may be caused by a mirror sync in progress. Trying again may fix it, unless there really is a problem with...

Something about your package management is messed up and you package manager refuses to do anything until you tell it how to fix it. So, let's find out what exactly is going on:
sudo apt update...

Automatically mounting your hard drive will be the easy solution. Create an empty directory to use as a mountpoint in whatever location you consider convenient (there are some directories to avoid)...

Could it be a snap issue? Software packages can come as deb packages and snap packages. Snap packages are restricted in the directories they can access, and /media may or may not be accessible. Maybe...

If you have the linux-generic package pulling in new kernel versions, you stay on the 5.4 kernel series. If you have linux-generic-hwe-20.04 pulling in new kernel versions, you upgrade to 5.8 and...

ctrl++ (or actually ctrl+=), ctrl+- and ctrl+0 control zooming in Firefox, zoom level going from 30-300%.

You cannot change a partition when it's mounted and you cannot unmount a partition when you run the system installed on it. So the procedure is to boot Windows and use that to shrink the Windows...

It appears that your system is in partition 2 of your nvme drive, but several important files and directories are missing. Boot-repair says there's no boot directory (explaining the error) nor fstab,...

The "attempt to mount a file system" error isn't important. You can just wipe the drive clean before installation using the live disk.

The other error, "Initramfs unpacking failed", suggests...

I don't see what you mean by your first and second sentence. But you can try running the upgrade again and hope it works better this time. If something doesn't work, we need precise error messages.
...

I've never used Wine myself, this was something I picked up on this forum. But maybe it's no longer true; I haven't checked.

Edit: Just checked it. ttf-mscorefonts-installer is suggested by...

You could at least try the live usb. If sound works there, it should work in the installed system too.

It appears that the Ubuntu 20.04 installer (but not the Xubuntu 20.04 installer) installs the hwe kernel series by default. I'm quite sure that's the cause of some additional instability.

The user interface of disk usage analyser isn't very intuitive to everybody, but maybe it is to you.

If disk usage analyser doesn't see the files taking all the disk space, there are several...

The ttf-mscorefonts-installer package is required if you want to use MS core fonts or Wine, as the Windows applications running in Wine are guaranteed that those fonts are available. I don't have...

In that case I suggest you stick to the standard (5.4) kernel for 20.04 and don't install the hwe (5.8) kernel. That will install security patches, but won't install any big upgrades, so it's less...

The other program could be a shell script.

Can you boot an older kernel? Do you actually need the 5.8 kernel supplied by the hwe package, or does the standard 5.4 kernel work too?

It appears this is a common problem this week.

There are several threads on the forum now about problems with 20.04 with hwe, which just moved to the 5.8 kernel.

Can you use the grub menu to boot in recovery mode? (Apparently, you can.) Can...

Have you tried an older kernel? The grub menu must list them next to recovery mode. There may be a problem with your kernel.

3 days ago I got a new kernel with my regular upgrades, 5.4.0-58...

Assuming you don't run them as root (never do that), there's no way Libreoffice or Firefox could cause boot problems. And it's not normal to get random filesystem errors. This smells like a hardware...

This sounds more like a problem with the window manager than with the kernel.

Old kernels aren't removed automatically (at least, not at once). You can use the grub menu to boot an older kernel...

They all get the updates at approximately the same time. There may be a few hours difference, but not days.