Can you check the system journal (just like before) to see whether there were any logs about it?

Most graphical system updaters (e.g Discover) use packagekit instead of calling on apt directly. This may lead to them having conflicting list of upgradable packages. Updating through either way will eventually refresh the cache and things will go back to normal.

I have never had to share a computer with other people, so can’t really comment on that.

I did try messing around with my Plasma desktop to try and replicate that, but did not find that option. Though, I am sure that’s configurable and you changed it accidentally. You should ask around KDE forums about that.

I understand your frustration as an end-user, coming from other operating systems. But, you should keep in mind that Linux is just the kernel and it was made to be as modular as possible. Since you can use it with many different desktops, there needs to be a common way apps from those desktops can perform this. I believe Gnome can do this graphically through its Disks utility, which just edits the /etc/fstab file in the background. You could request this feature from the KDE developers though.

Edit: sorry, I now remember KDE Partition Manager and it can do the same, like Gnome Disks.

Since you are new to Linux, the differences Fedora and Ubuntu will have for you will come down to the package manager (dnf vs. apt), and since you prefer to update your system graphically, you shouldn’t notice any difference.

You can find your kernel version by searching “About this System” in KDE Plasma, or using the following command:

$ uname -r

The latest version of the kernel can be found in the official website of the Linux kernel.

Hmm, let me clarify some of the challenges you had.

Lack of touchpad gestures is due X11. It simply does not support anything you may be used to from Windows or macOS. X11 is currently regarded as a legacy display system due it’s lack of modern features (such as VR, VRR and HDR) and security issues. Firefox supports your typical Wayland gestures since it is one of the few apps implementing new Linux features properly. On Windows and macOS you are locked down to a particular windowing system, so applications can expect such features being available on every single system reliably. The number of choices Linux presents to its users is also the greatest weakness of it, in my opinion. Wayland is still relatively new in most used distributions and I expect things to get better in the next five years.

Majority of the drivers are baked into the kernel on Linux. Without knowing the version of Kubuntu you were using, it is hard to judge why Tuxedo OS played better with your headphones. I am using Sony WH-1000XM5 on Fedora with kernel 6.13 and works perfectly.

Regarding updates: almost every package on nearly every Linux distro (except the kernel) can be updated without rebooting. It is just that Ubuntu (Kubuntu is just Ubuntu with KDE Plasma desktop) is configured to apply updates at reboot to minimize any breakages. So is Fedora that I am using and I really like it. You can update the system through a terminal if you want to do so without rebooting.

The login issue you encountered is due to SDDM - login manager used by KDE Plasma. KDE is planning to replace it with something they develop themselves.

I don’t really understand this one. Did the toolbar just disappear from all apps? They usually do that when you add a global menu widget to your desktop, but shouldn’t otherwise.

Automatic mounting of drives is done easiest through editing the /etc/fstab file in Linux. I am not aware any other methods that are more user-friendly.

Unless you have a specific reason for using Tuxedo OS, I would highly recommend Fedora with KDE Plasma desktop environment. Tuxedo OS is still pretty niche and targets Tuxedo’s (the company) own laptops. Fedora has much larger user base so issues like this are solved faster. It also ships with the latest versions of the kernel, so you’ll have less driver issues.

Thanks.

Unfortunately, your system printed absolutely no logs when waking up.

Though, looking at them, I can see that your BIOS is wildly out-of-date:

mar 30 11:45:37 HostName kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E26/B650 GAMING PLUS WIFI (MS-7E26), BIOS 1.10 05/23/2023

In fact, it is the one it was shipped with from the factory. First and foremost, you should update it to the latest one available from MSI’s website. Latest one is from a week ago.

Also, try your best to undo any changes you made to your system following this post, including the grub config change. It is best to troubleshoot making as little change as possible at every step.

Did you nuke your Tuxedo OS install? It would have been better to, at least, have a look at system logs to see if there’s anything there.

What problems exactly did you have with Kubuntu?

I assume your issue is reproducible every time, right? If yes, do so and reboot. Use the following command to obtain logs from the previous boot, where you had the problem:

$ journalctl -r -b -1

Before resuming from sleep, wait for about a minute or so to check for that time gap in the logs to easily find the logs of the resuming process.

You can append >> file_name.log to the command above to output logs to a file, in case that makes copy and pasting easier for you.

Did you try any other distro or Windows on this system to narrow down the issue to Tuxedo OS itself? It could be an issue with your motherboard.

What’s your hardware? And did you regenerate grub’s config after editing the file you mentioned?

Arch Wiki is all you need.

I am aware of the perks of having your /home not tied to your root filesystem. In my case, I have a single LUKS2 encrypted btrfs partition with separate subvolumes for root and home.

I just don’t see the reasoning for having it on a separate drive, as the OP explicitly states in their post. Both drives would have the same likelyhood of failing and it makes encryption (though, only slightly) harder.

What?

Why do you need /home to be on a separate drive?