Do note that the yt-dlp version in stable will go out of date; I recommend installing it from the backports repo so it keeps updating.
data1701d
joined 1 year ago
I also use XFCE. My desktop’s currently on Forky and went through all of Trixie, and the emdia keys have worked fine.
I’ll have to fiddle around and see what’s going on, though it may take a few days to get back because I’m starting school again soon, so I’m quite busy.
For reference, what programs do you tend to use with media keys? For instance, VLC, Firefox, etcetera.
What desktop environment are you using?
And maybe just give device model for good measure.
To be fair to macOS, it’s still Unix-based, which at least makes it less miserable for development than Windows.
I would still go for Linux any time, though.
You’re right in some ways; Windows is closer to a microkernel than Linux, though it doesn’t perfectly adhere to the philosophy of - there’s supposedly weird things like drawing calls in the Windows kernel that should be in microservice, I’ve heard
However, I wouldn’t necessarily call microkernels a detriment; in fact, Linux is a bit of an odd duck for going monolithic - modern Apple operating systems also run on a microkernel. Monolithic is an older architecture, and there are worries about the separation between components and system resilience e.g the webcam driver can’t crash the whole kernel.
In practice, it’s less of an issue, and there really aren’t any open source microkernel operating systems that are practical for production desktop and server use, which has a microkernel though there are certainly solutions for embedded systems.
QubesOS is built on Xen hypervisor, which uses a microkernel design, but Linux is then run in multiple VMs on top of it, which makes it more of a technicality in my eyes. RedoxOS also runs on a microkernel and is certainly intended as a desktop operating system, but its hardware support is limited; GNU Hurd is even more limited in that respect and not really usable.
Neat. I love Debian, but its documentation is crap! I hope this works out and I can see an improvement.
Maybe it’s because I only use stable on my laptop with Flatpaks, but honestly, Bookworm never got that crusty to me until recently - it feels like new software versions didn’t introduce a lot of must have features in the past two years. Only hiccup was I had to install the backports kernel to get Wi-Fi working.
I used to use this, but I always found it really janky - window boundaries not updating, weird graphical glitches, etcetera.
It was especially annoying to use with Photoshop and GPU acceleration (I do GPU passthrough to my VM).
In the end, I just abandoned it and just used the monitor the VM’s GPU is plugged into.
As a completely new user who’s self-described as “not very tech savvy”, Arch is probably a terrible idea, and you should switch distros.
I really like Debian, but something like Linux Mint or Fedora might be wiser for you; all three hold your hand more, which would be very important in your case. Fedora and Debian specifically are designed to work well with KDE, although Fedora will have newer versions.
You certainly seem willing to learn (you got through the Arch install process), and I think you still have a great opportunity to enjoy Linux, but considering you’re calling the terminal emulator “Konsole”, your self-description is probably apt. FYI Konsole is just one application to access the terminal, kind of like how Firefox and Chrome are both web browsers, but you don’t use “Chrome” to refer to web browsers.
No.
I usually just use Bash; there’s a certain level of complexity where it begins to be more reasonable to just use Python.
Yes and no. I think connotation is important here; “stable” means different things in different contexts even within computing, and they both denote different but important things - kind of like free of cost verses freedom.
In the distro case, people need/want a distribution where they know a new version won’t come and break their config when they update at 2 AM and miss it in the changelog, and “stable” has been agreed upon as the term in that context. Of course, that can change, as all language does, but that’s just the current convention.
Also, Debian tends to make sure software is not unusable before stable is shipped (the Nvidia thing is an anomaly I’ll explain below); while they sometimes fail, as you’ve hinted, I find it quite rare that it actually happens. Also, the “static” of Debian isn’t absolute; if something really has a breaking bug or a security vulnerability that affects overall system usability (basically something that can’t be fixed by installing a Flatpak), they will put out a fix, like with the Linux kernel or a web browser (via the security repo, included by default in all installs).
Additionally, looking at this changelog, while the Nvidia situation is objectively a bit embarrassing, it looks like they were working on getting them updated, but just didn’t have much luck - I’m guessing a breaking change in the software that made it harder to package. Also, it’s in the non-free repo, which is on the back burner compared to the rest of the distro - something in the main repo will usually only be at most a few months behind at time of distro release.
179
Half of these exist because I was bored once.
The Windows 10 and MacOS ones are GPU passthrough enabled and what I occasionally use if I have to use a Windows or Mac application. Windows 7 is also GPU enabled, but is more a nostalgia thing than anything.
I think my PopOS VM was originally installed for fun, but I used it along with my Arch Linux, Debian 12 and Testing (I run Testing on host, but I wanted a fresh environment and was too lazy to spin up a Docker or chroot), Ubuntu 23.10 and Fedora to test various software builds and bugs, as I don't like touching normal Ubuntu unless I must.
The Windows Server 2022 one is one I recently spun up to mess with Windows Docker Containers (I have to port an app to Windows, and was looking at that for CI). That all become moot when I found out Github's CI doesn't support Windows Docker containers despite supporting Windows runners (The organization I'm doing it for uses Github, so I have to use it).
Another update: https://startrek.website/post/13283869 I found a fix for my issue. I'm annoyed that I had it in the first place, but I overall still like my laptop.
Important update in this post: https://startrek.website/post/14075369 I still consider this a good laptop, but this is an important fix if you're using this on Debian 12. When 13 comes out next year, the out-of-box support of this laptop should be basically perfect.
Anyhow, back to the original post: I recently got a brand new laptop, a Thinkpad 21JT001PUS, to consolidate/replace my array of various on-the-go-Linux devices, and I have to say, I'm impressed. I know Thinkpad and Linux aren't news, but for such a recent device, I am surprised how well it works. The price wasn't bad (which makes up for the fact that it's a Zen 3 chip with DDR4, in my opinion), it has good upgradability (I'll touch a bit on my experience later), and hardware support was really good.
I initially tested hardware support with Debian Testing Trixie XFCE (as that was the Live USB I happened to have on hand, since I often test devices and also keep it around as a backup for my desktop, which runs Testing). At first I couldn't get it to boot, but then I found the BIOS setting to enable non-Microsoft certificates. After that, I booted in and found everything worked out of the box (except the fingerprint sensor, of course, but that's extremely rare for any laptop anyway). However, after experience with my previous portable devices, I learned I prefer stable distributions on those, as during some parts of the year, I can go months without opening the laptop.
Thus, I retested with Bookworm. Almost everything worked still, except for the Wi-Fi (which seems to have been introduced in later kernel versions). Luckily, this thing has an ethernet port (From which it is HECK to remove cables - I've found I had to twist the end up a bit to get it out), so I was able to do an install and then add the Backports kernel to get Wi-Fi working.
One minor issue I had (a software fault rather than a hardware/kernel one) was Bluetooth headphones, but as it turned out, it was just that PulseAudio was installed instead of Pipewire, so after switching, it worked flawlessly with Blueman).
As for battery life, so far it seems okay (as I write this, it says 3:29 left at 51%), but I haven't rigorously tested it yet (though I threw on the usual tlp and stuff like that for good measure).
For performance, I once again haven't tested it too rigorously, but I did play some Civ VI, which it was keeping up with just fine.
The upgrabability of this laptop does have one caveat, though. The bottom is a bother to remove, and most Youtube crap conveniently glosses over them. For one, some of the screws would get loose but not come out all the way. I eventually found the trick was to throw some pry tool under the screw head to hold it up so I could get it the rest of the way out. After they were all out, the bottom cover STILL wouldn't budge. This too ended up being a matter of jamming a pick in one corner of the case and running another one to slowly pry up the bottom case on all sides. I lost a plastic tab or two in the process, but that doesn't show up on the outside, and I think 24 GB of RAM (and 2 TB of NVME 2280 storage + 256 GB, the Windows drive that I left in the 2242 bay) will be plenty for a long time.
Overall, I would say this is a great laptop for those who don't want to go the route of purchasing a used laptop for Linux. I'll say an 8.5 out of 10 due to the hard-to-remove bottom cover and weird ethernet port (Update: 8 out of 10 now due to the nasty Wi-Fi bug I had to fix with a few module options, see posts linked in top of page).
Here's the Linux Hardware probe: https://linux-hardware.org/?probe=1e50fb1862
view more: next ›
Which DE are you using? At least for XFCE, there’s HDPI and XHDPI themes you can choose in the Window Manager settings.