AnIndefiniteArticle

I didn’t see it in display settings, but maybe I missed it!

In desktop mode you can change the resolution of the connected display. It goes back to 720p if you go back to gaming mode, but you can always just launch games from the desktop if you want higher resolution for a specific game.

Thanks for the leads and the good conversation. I have found that being an idiot in public and then deescalating is one of the fastest ways to gather information.

Thanks for pointing out that in this case the DM is using X regardless of whatever graphical environment gets loaded when the user logs in. This really is a moot point/discussion. I’m still glad I raised it to get perspectives like yours.

You’re right that I should play around with wlroots a bit more. It’s been a while, personally. Mostly because it’s been a while since I’ve had time to just play around with my system. My life is at a point that it looks like I’ll have that free time soon, for better or for worse.

I’ll note that I do like alternative init systems for diversity and competition and because systemd was very hungry and rigid. An init system is also a bit more fundamental to system stability than a display server, so I think it’s reasonable to be critical of systemd and Wayland for contradictory reasons. Systemd has also come a very long way in the past decade plus. I have also seen it learn from the other ideas implemented in its competition, mirroring your argument. Diversity and unification are not at odds with each other, but are different parts of the same cycle of improvement.

Good to know that this has been implemented in your favorite DE! Considering how Wayland often implements things, it’s probably implemented on the DE-level, leading to a fractured configuration ecosystem. Being implemented in Wayland is different from being implemented in some of the DEs that use Wayland.

edit: if I’m wrong about that, and it is implemented in Wayland itself, please continue to correct me!

It’s not just about it being a config file, it’s also about having access to a powerful tool like xrandr within that config file.

That’s kind of my point. Something like randr is more fundamental than the DE, and its configuration shouldn’t be fractured by being DE-dependent. I personally don’t like DEs at all, and like the ability to control a more minimal system.

I’ve never needed any of those things.

I do need to change monitor configurations.

I once had an old TV that I used as a monitor that had 1027p worth of pixels instead of 1080p. Auto detection tools said it was 1080p. With xrandr I was able to modify the output to 1027p so I didn’t lose the edges of the display to the TV’s broken forced overscan design. Could you do that with Wayland?

I am serious, and I’ll tell you exactly what will change my mind. I need real tools instead of “upgrades” that have less functionality and are less usable. If Wayland (or whatever comes next) can deliver on functionality, I’ll sing its praises. For now I’m on X.

Give me real tools or get off my lawn rewilded patch of native plants and bugs!

This is why X11 is better. I’d rather have settings like this in a text file that I can copy over to my next machine than have to navigate a UI that will change on a different DE or the next upgrade.

Backwards compatibility, portability, and text-based interfaces are a virtue.

X config files aren’t “hacky scripts”, they are fundamentally more powerful, customizable, usable, and future-proof. Xrandr is a powerful and capable interface with applications across the system.

When Wayland adopts these kinds of powerful interfaces with decades of refinement I’ll switch to it. I don’t want to keep track of whether my DE uses wlroots or gnome or plasma and their independent/redundant/feature-lacking randr alternatives. Randrs should be more fundamental to the display operation than the DE. Wayland is fundamentally hacky and broken.

Edit: thank you all for the discussion. I’d like to clarify a point. I don’t just want a text file with configuration settings that implement features that I need to beg/bother the devs for. They are likely to have better things to do and it might not be a priority for them. I want access to powerful tools via the configuration files that I can make do pretty much anything if I read the documentation. Xrandr is such a tool. I don’t want setting for a feature that has to be baked into the DE which I have to beg to have implemented and which will be implemented differently across different DEs. I want flexible, dynamic, modular tools.

Try switching to different versions of your graphics driver and/or kernel. Nvidia cards get really finicky about the version matchups, especially as they age. Try different combinations of the versions that are available via pacman, and maybe it’ll work. You may need to start keeping an eye on updates to your kernel and graphics driver to see if a new update fixes your issue. Welcome to life with an nvidia card. I bought an nvidia card once in 2013. By 2016 I had to start playing this game on upgrades. At one point, the graphics driver was causing kernel panics until I downgraded both and waited a few months. Very happy with AMD.

The CLI has many advantages over a gui. For one, actions are reific, repeatable, and scriptable. This saves time as you can reuse previous commands and edit them appropriately for the current situation. This makes it easy to look back and verify what you have done. The command line is also a much more stable interface. GUIs change all the time and it’s hard to remember where things might be located. The structure of the gnu operating system accessed via the command line facilitates the discovery of installed commands/programs and documentation. You can record these actions once and repeat them on many machines. You can script common activities (eg bulk file renaming) that make file and data management easier.