This is the system settings application for the KDE desktop environment.
This is the system settings application for the KDE desktop environment.
Literally yes. And you don’t even need to know the exact pixel resolution of the TV.
Edit: Here are the problems with you “Wayland isn’t good enough” people.
First, you don’t use Wayland, so you don’t even know if it’s fixed whatever weird issue you encountered with it before or if it supports a niche use case, for example.
Second, Wayland won’t get good enough for you until you start using it and reporting bugs. You think X11 was a bed of roses when it first started? Or do you think they bumped the version number 11 times for fun?
Not sure if you’re a troll, but if you’re serious, nothing I say is going to change your mind, so I won’t bother.
If you’re using Wayland, you can go to Settings -> Colors & Themes -> Login Screen (SDDM) and click “Apply Plasma Settings…”
If you’re using X11, it looks like you’ll have to resort to hacky scripts, unfortunately.
Source: https://discuss.kde.org/t/how-to-change-monitor-layout-and-orientation-in-sddm/3377
I could go in-depth, but really, the best way I can describe my docker usage is as a simple and agnostic service manager. Let me explain.
Docker is a container system. A container is essentially an operating system installation in a box. It’s not really a full installation, but it’s close enough that understanding it like that is fine.
So what the service devs do is build a container (operating system image) with their service and all the required dependencies - and essentially nothing else (in order to keep the image as small as possible). A user can then use Docker to run this image on their system and have a running service in just a few terminal commands. It works the same across all distributions. So I can install whatever distro I need on the server for whatever purpose and not have to worry that it won’t run my Docker services. This also means I can test services locally on my desktop without messing with my server environment. If it works on my local Docker, it will work on my server Docker.
There are a lot of other uses for it, like isolated development environments and testing applications using other Linux distro libraries, to name a couple, but again, I personally mostly just use it as a simple service manager.
tldr + eli5 - App devs said “works on my machine”, so Docker lets them ship their machine.
That work has already started with Fediseer. It’s not automatic, but it’s really easy, which is probably the best we’ll get for a while.
My ISP says my IP is technically dynamic, but it hasn’t changed once in the 6 years I’ve had their service. But that’s for the best, since they’re the only choice for symmetrical gigabit and their only option for static IPs is for business accounts.
So I continue to trust that they won’t change it. Fingers crossed.
complexities of Distrobox
they unironically say in comparison to the arcane language of fucking Nix, lmao
In addition to what’s been mentioned, Bazzite also updates the kernel and graphics drivers more often than SteamOS, so yes, while things are slightly more likely to break every now and then, there are some decent performance gains to be had.
I love Bazzite, but I wish they would fix the no audio after wake on the OLED. I encountered it often while running the testing release, so I went back to SteamOS to wait for a stable release with the fix. Imagine my disappointment when they released a new stable version with the bug still present. :(
The Arch wiki has you covered.
You also don’t have to reboot when Discover says to. It’s just saying that the updates won’t take effect until you reboot. It could probably be worded better, for sure.
Look into Distrobox. It allows me to use just about any AUR package via a local Arch container on my Tumbleweed system. You can even export apps and binaries to your local path and applications so that they integrate natively with the base system. I’ve only run into a handful of packages that didn’t work correctly, but I wasn’t surprised at all - they were all pretty low level system packages.
Yes, I’ve got community icons and avatars working. Which are actually the only things I see in my pictrs volume.
Huh, do I have that misconfigured by some happy accident? My pictrs volume is only around 50Mb after running my instance for over a month. I have both LCS and Lemmony federating popular content, too…
Also, are the images even federated? I know the current line of thinking is that they are, but I could not find them in my local pictrs volume. Not that I wanted to, mind you. But I looked and only saw one picture in there from the problematic time period, and it happened to be one of my user’s avatars. And one of the CSAM posts federated with me, I know for a fact, because I saw the comments even though I couldn’t see the picture (and I feel horrible for those users who saw it, some of them were obviously traumatized).
I’m keeping a close eye on my pictrs volume and really scrutinizing who I allow on my instance after this whole thing, but on the whole, I’m not overly concerned, even as a US-based self-hoster. I registered with the DMCA and will fully comply with any and all takedown requests, even silly ones like copyright. I don’t have the finances or time for prolonged legal battles.
Edit: Figured it out. My pictrs container didn’t have an external network definition, so it was timing out while retrieving external images.
That’s actually really fucking cool.
Some third party apps don’t display the user’s domain by default.
Arch is great, but it can be a bit much for someone to jump straight into. It’s definitely gotten easier in the past few years, but there can be quite a bit of optimization to do to bring gaming performance up to (or past) Windows levels.
My recommendation for a newcomer would be Nobara. It’s a version of Fedora heavily customized specifically for gaming, and it’s run by a developer who does a ton of work for the Linux gaming scene (all hail GloriousEggroll).
Correct. Unfortunately, it’s something that each desktop environment or window manager has to implement themselves. But all the button is doing is moving some config files around, so you can probably do some digging to figure out what it’s copying to where.