I must have deleted the last digit by mistake, sorry kneekoo: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262.
Bug #190726 from 2008?! :)) That's certainly not the right link.
Ok, new ISO coming up.
We'll backport gnome-font-viewer 3.28 into 20.1.
OK https://bugs.launchpad.net/ubuntu/+source/linux/+bug/190726 is quite concerning. We'll update the package base and switch to a newer kernel.
- gnome-font-viewer looks really buggy alright...
- it looks like the kernel used here was pulled from the repositories upstream.
- I'm not sure what the /root error messages are for but they don't matter. I checked 19.3 and they were already there. We'll be auditing our tools next cycle so I'll add this to our roadmap.
- btrfs will stay, the delay was an important issue but it doesn't really matter if we get fd0 errors.
- the firefox error is ok, it's just FF checking its APT version.
- LSB is ok, we use DESKTOP to mean toolkit really here.
- The sha256sum is correct but be careful, integrity check can succeed even if the sum is wrong. A wrong sum still means you've got a corrupted download.
#048: All applications (live sessions)
Accessories -> Fonts
- VM, 1 core, 2GB RAM, the app hangs before showing fonts, the OS becomes unresponsive, although System Monitor didn't show high CPU/RAM usage
- VM, 2 cores, 2GB RAM, the app hangs but the OS is still responsive, no high CPU/RAM usage; once I killed it with System Monitor, the app started, worked normally; I closed it, started it again and it worked normally, so I closed it; I started it again, I scrolled a bit and it froze for a few seconds, it recovered and then it worked; repeating the open/close a few times it worked normally
- laptop (Core 2 Duo T9550), 2 cores, 4GB RAM, the app hangs after you scroll through the list of fonts, but the OS is still responsive; once killed with System Monitor, the app started and worked normally; I closed the app and started it back again, and it froze again, killed it again, started it again, it froze again, then again and again... so it's more of a mess, and sometimes it shows fonts, sometimes the window is empty
Notes on the hardware:
- The laptop has a Core 2 Duo T9550 CPU;
- The VM was run on a Core i5-4690K
VM startup: qemu-system-x86_64 -m 2G -enable-kvm -cdrom linuxmint-20.1-Cinnamon-amd64-202012121225.iso -soundhw hda -smp 2 (or without smp for 1 core)
#046: Foreign packages https://i.imgur.com/ZqVLtU5.jpg
#029: Firefox branding
Start Firefox from the terminal and you'll get this:
touch: cannot touch '/home/mint/.mozilla/83.0+linuxmint1+ulyana.dpkg_version': No such file or directory
#019: LSB and info file
Is this correct in /etc/linuxmint/info? DESKTOP=Gnome
Shouldn't it be Cinnamon?
R.e. "check floppies on boot" -- last I checked in mint20, btrfs-progs seems to cause this.
I know this because earlier 5.4.0 kernels had a deadlock/bug with floppy support (only occured with floppy present, bug now fixed), and a partial/temporary workaround was to take out btrfs-progs (which consequently removes timeshift too)) or to actually take out the floppy drive temporarially.
#003: Plymouth text theme
https://i.imgur.com/N3HvJLq.png - the fd0 issue is displayed there as well
Booting a live session...
https://i.imgur.com/JyLBxG5.png - several errors caused by a bat path prefix '/root/' instead of '/'
touch /root/var/crash/crash.init: No such file or directory
rm: can't remove '/root/var/crash/crash.init': No such file or directory
ln /root/usr/lib/update-notifier/apt-check: No such file or directory
ln /root/usr/lib/ubuntu-release-upgrader/check-new-release: No such file or directory
ln /root/usr/lib/ubuntu-release-upgrader/check-new-release-gtk: No such file or directory
grep: /root/etc/default/apport: No such file or directory
grep: /root/etc/apt/apt.conf/50unattended-upgrades: No such file or directory
and an unnecessary? umount:
[FAILED] Failed unmounting /cdrom
https://i.imgur.com/INmwldi.png - I see no reason to check floppies on boot, on a system that runs a modern 64-bit OS
blk_update_request: I/O error, dev fd0...
The SHA256 checksum doesn't match. It seems wrong, considering the integrity check went fine.