IF you have the space, go for a projector. I got a nice short throw 1080 Benq with a decent 120 inch screen. And wow, it’s incredible. It’s amazing for shows, movies, and games. I paid 800 total for everything. There’s everything from 200 dollar to 5k dollars, depending on what quality you want.
TDE (for those who haven’t encountered it before, the Trinity Desktop Environment forked from KDE3 more than a decade ago). It might not be the flashiest or the newest, but it has a decent selection of features and applications, and presents a traditional desktop environment whose interface doesn’t get changed for the sake of change. In other words, it stays out of the way and lets me get things done.
(If I’d liked Gnome 2 better than KDE 3 rather than vice-versa, I probably would have gone for MATE instead.)
The TDE crew have also taken on responsibility for maintaining TQT (formerly QT3). If you’re aware of any open bugs, go ahead and file them to the TQT3 repo on TDE’s Gitea and someone will have a look.
My suspicion is that a kernel update broke it and that downgrading to LTS (or even an older LTS) kernel would fix it. I didn’t bother to troubleshoot further because I don’t need suspend that badly (desktop).
I would honestly just back up my files and start over with a fresh new install. I have never been successful in copying everything over, especially not if you are planning on changing the file systems. I know you mentioned that you don’t really want to do that, but that’s my 2 cents
29 years here, get my first computer in 2011 after using it sometimes in my sister’s house. Never used ctrl+backspace in my life and did not know it existed. Edit maybe you can try something like that? addons.mozilla.org/en-US/firefox/…/shortkeys/
Make the new filesystem, rsync the old SSD to the new one (making sure to use rsync -ax to copy everything properly, also add -H if you use hardlinks), update fstab UUID, regenerate GRUB configuration and you’re good to go.
I have a 10 year old install that’s survived moving several disks and computers, it works just fine.
This is likely what I will do now that I have given it some thought. This will bring over all of my installed apt and snap packages, right? And they will both be aware and know how to update from there?
I have the NVMe prepped. It has a fresh Ubuntu install of the same version, but on btrfs. I could probably even snapshot it before I get started to make sure I can roll back and try again if I fuck up. And worst case, I can just reinstall the OS on that partition, as it would touch my existing install. It feels pretty safe to try. Worst thing that can go wrong is I waste my time.
Yeah, from the software’s point of view unless you need some extra rsync flags as some have pointed, you end up with an identical view of the files on there, they’ll be mounted exactly at the same places and everything. Just a different filesystem and drive behind it. People have been doing that for decades, before even Linux.
As long as all the attributes like user/group/mode and symlinks are preserved, most distros won’t notice a thing with that method. There’s no filesystem-specific special sauce to make it work or hidden flags or anything, even snaps and flatpaks.
This is not like Windows where your options are clone the partition or reinstall. Linux is a lot simpler and only cares that the files are where they should be with the right permissions.
Specifically, the weak spot is in “maple tree,” a new data structure system for VMAs introduced in Linux kernel 6.1 that replaced the “red-black trees” and relied on the read-copy-update (RCU) mechanism.
Maple Tree also recently caused intermittent failures in some of my CPU-intensive tasks, in such an obscure way that I only found out by dumb luck that it was a kernel bug. I expect it will be great eventually, but it’s feeling pretty rough at the moment. I’m thinking this code should have had more testing and maturing before going mainline.
Damn. If the Maple Tree code is bugging out under CPU-intensive tasks, that would explain a lot about how my system’s been behaving since I moved to 6.1. Thanks for the heads-up, and I guess I should compile another new kernel.
This is off topic, so I will leave it as a comment below, but last week I had the bright idea to wipe the NVMe SSD to prepare it for this migration. I totally forgot that I had my MBR and grub on that SSD. So the next time I rebooted, it wouldn’t boot back up. It took me like two hours to get grub back on it and boot it back up.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.