Yes, that makes sense. Unfortunately, as far as I know, Mint doesn’t provide a list of obsolete or deprecated packages. Even the upstream Ubuntu release notes (https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890 for 24.04 / LM 22) don’t list removed packages.
What you can do after the upgrade is query for obsolete packages on your system using apt list ?obsolete. It’s generally recommended to remove those.
It seems that xplayer was abandoned after the last release in 2022. It is not present in the LM 22 repos. Maybe you still have a version installed from LM21?
I would expect the change in the default app to be mentioned in the release notes, but I can’t find anything on the removal of the package in LM22: https://linuxmint.com/rel_wilma.php
Ok, so you didn’t even get to the bootloader (Step 4 here: https://linuxmint-installation-guide.readthedocs.io/en/latest/boot.html). Indeed it seems most likely that your USB drive was not created correctly. I would go with the steps I pointed out above to debug the issue.
and while it was recognized in BIOS, it wouldn’t boot from it.
What exactly happened here? This approach should usually have worked.
The first thing I would suggest to do is verify the checksum of the ISO that you downloaded. I think you can use 7zip to calculate the SHA256 checksum on Windows.
Instead of trying to manually create a bootable USB disk, I would suggest to try a different tool, e.g. Fedora Image Writer.
If possible, you could also try a different USB stick and a different computer to troubleshoot the issue.
Interesting, I didn’t know that but it seems like Wayland is indeed CSD by default. However, all relevant compositors except for Mutter support xdg-decoration (https://wayland.app/protocols/xdg-decoration-unstable-v1). So in practice it’s still only a Gnome issue.
No, that’s Gnome, not Wayland. KDE still prefers SSD on Wayland.
I feel it has gotten much better in recent years. The first time I tried KDE 5 it looked weird to me. But now I acutally quite like KDE 6. Or maybe I’ve just learned to tolerate it…
What kind of issues did/do you encounter?
The VS Code/Codium essentially provide a separate development environment within the flatpak container. All the tools there, and the shell are separate from your actual system. There are some ways to work around this (https://github.com/flathub/com.vscodium.codium/blob/master/README.md). I gave up on the Flatpak and installed a native package. Containers are nice, but they have their limitations.
Sure, Bazzite has some nice features. But, I would argue that apart from the Nvidia images (there is no AMD image) those are all minor things. And for Nvidia cards, the Mint Driver Manager is pretty good. I don’t think any of those differences play a role here.
In general, I think it’s really unhelpful to present “switch to my favorite distro” as the first step in troubleshooting an issue.
Try CachyOS or Bazzite!
Bazzite, sure, but it’s not gonna magically solve these kind of issues.
However, if one is struggling as a beginner with Linux, I would strongly advise against switching to an Arch-based distro (CachyOS). Arch is great, but this is not its target audience.
I strongly disagree with u/brucethemoose here. You wrote below that you’re currently using Linux Mint, which is a great distro for beginners. In my opinion, Bazzite offers nothing essential that is not available on Mint. IMHO, the easiest ways to play games are:
You can - of course - still switch to a different distro if you like, but this is not necessary or helpful to run games.
In the specs for the Laptop 13, it says:
Fingerprint Reader (2nd Gen)
Same for the 16, but not the 12.
Unfortunately, the former is not possible due to asinine requirements by the HDMI Forum: https://www.phoronix.com/news/HDMI-2.1-OSS-Rejected The only option is to use DisplayPort instead (or perhaps an adapter).
I’ve created a small helper script to help me with this:
#!/bin/bash
USED_VER=$(uname -r)
echo "Kernel version in use: $USED_VER"
echo "Other installed versions:"
dpkg --list 'linux-image*' | grep ^ii | grep -v $USED_VER
echo "Remove unneeded packages above using the following command:"
echo "sudo apt remove linux-image-VERSION"
It prints a list of the installed kernels (excl. the running one) and prints the command to uninstall the packages (it doesn’t remove anything by itself).
That sounds pretty bad and probably means other things are broken too. The easiest option would probably be a reinstall at this point, but if you want to learn something you can also try to salvage your install.
To recover, it’s probably easiest to manually configure your Ethernet connection as described by InnerScientist and then re-install the network-manager package.
You can check the status of the network-manager package using dpgk. It should look like this (ii at the start, but it sounds like it’s not installed in your case):
$ dpkg -l | grep -i network-manager
ii network-manager 1.52.1-1 amd64 network management framework (daemon and userspace tools)
ii network-manager-l10n 1.52.1-1 all network management framework (translation files)
You can also check /var/log/apt/history.log to see what went wrong and if there are other things you need to fix.
I performed the upgrade in two steps apt upgrade --without-new-pkgs and apt full-upgrade (based on the release notes). I can see the following on the line Upgrade: for the command apt full-upgrade:
network-manager:amd64 (1.42.4-1+deb12u1, 1.52.1-1)
On the Remove: line you can see the packages that were removed. Unfortunately, the names of many libraries were changed in this release (e.g., libreadline8:amd64 to libreadline8t64:amd64), so there’s a lot of noise in there. Maybe you can look at that line and ignore everything that starts with lib to see if any other important packages were removed.
One thing that comes to mind is that the 50series is only supperted by the open version of the proprietary Nvidia drivers. The closed version doesn’t support your new GPU, but would work with your old GPU. Do you know which version you installed?
Plasma 6 is a significant upgrade for sure, especially on Wayland! I’d rate the crash frequency (on Fedora) at between once per week and once per month ;-)
Join the Debian Trixie upgrade fun today :) https://micronews.debian.org/
I’m running Ubuntu on a server. I’ve enabled the free Ubuntu Pro subscription to get ESM patches for the universe repository. Not sure if it really matters, but better safe than sorry.
How is this too long? I would consider it a reasonable amount of time to receive security updates on a computer.
I have a notebook that I bought in 2012. It can run Ubuntu LTS 24.04, which is supported until 2034, without issue. There is no indication that the next release will stop supporting this hardware. I don’t see why Microsoft couldn’t provide this.