So, this morning, after years and years of using the GUI in Linux, I gave up. The state of the GUI does nothing but deteriorate over time for accessibility, and it's exhausting. It's only getting worse. We're far, far away from what it used to be, years ago. Certainly, the QT framework has improved since 5 and now 6 came out, but GTK? Oh dear, oh dear... So, let's dive into it. #linux#xorg#wayland#a11y#accessibility#blind
I'm curious how many of you actually use a screensaver (not a lock screen) on #Linux, the screensaver fans are very loud about them but surely there isn't that many of them #Wayland#Xorg#Opensource
Will #NixOS allow me to keep #Xorg instead of forcing me to adapt #Wayland in the upcoming years?
Any opinions on that?
Background:
I do like x-forwarding within my LAN. I work on business machine, ssh to my personal host and simply start any application which pops up on my local machine. This also worked with sound forwarding.
I never play computer games and so I do think that Wayland doesn't necessarily offer me much advantage over Xorg while I've read that x-forwarding won't be possible.
#X11#Xorg is almost 40 years old. #wayland almost 15. And I still need to read thought-pieces that argue against adopting the latter with the same gate-keeping arguments.
The amount of effort put into whining together with the lack of effort put into maintaining Xorg (or any relevant software for that matter) is astounding and agonizingly agitating.
"If you are not part of the solution, you are part of the problem. Quit being a part of the problem!" - John McClane (slightly paraphrased)
"In 2024 [foo] will switch to #Wayland and remove #Xorg …"
Yeah, hmm ok, so how do I run that $25YearsOldApp I need?
And no, I won't go fix Xorg or Wayland, I already spent years cleaning up the X11 mess in Conky (for an hypothetical Haiku port I've yet to start) just so someone else can add Wayland support… I've done my share already.
Trying to set up a #Debian workstation again (I really want to get back to #Linux), and loving it already.
• #GDM doesn’t run in Wayland mode. Logs say something about a segfault in #gnome-shell.
• Using #Xorg instead works, but if I position my left monitor to (0, 420) (because the right one is taller), the output on screen moves down (with the menu bar now in the middle of the screen), the mouse cursor is offset.
TL;DR: What is causing my X.org keymap to change unsolicited for, and how can I prevent it?
When I log in to my X.org based desktop environment on Linux a custom keymap is set from ~/.Xmodmap. This is all fine and dandy.
However, at odd times — perhaps every day or two — the keymap mutates into something else, that could be the default X.org keymap, and I have to run “xmodmap ~/.Xmodmap” to get back to where I want to be.
I haven't been able to correlate these events with anything, but of course systemd is always a strong contender for such anomalies…
Has anyone else experienced the same thing and found a way to prevent it?
I want to love Wayland, I really do, but its keeps giving me reasons not to
I can live with the lack of power management because well, Nvidia sucks but OBS constantly crashing and Gnome keychain not working for PGP keys means its back to X11
The Kodi issue on X11 is resolved so there is no reason to use Wayland until it actually works properly
Silly question but if anybody I know has connections with #Xorg ... is there somewhere that old, pre-X.org mailing lists (from the X11 / XFree86 / X Consortium days) are still archived?
Watching every video promoting switching from #Xorg to #Wayland gets me moving with a plan, later only to face multiple hurdles of medium to high complexity.
I spent the evening switching from #i3 (#xorg) to #sway (#wayland) and had to find alternatives to some tools I was using. Maybe this will help others doing the same:
My old monitor died recently and I bought a #CRG9 to replace it. I have a #AMD#Radeon 6500XT, I run #Arch#Linux with #Xorg and #EXWM and the #Compton/#Picom compositor. I bought the monitor for productivity issues as I'm not much of a gamer, the only games I play these days are Tagpro, a simple capture-the-flag browser game, and Chess.
After months of using the #Wayland version of GNOME Shell 44.x on my workstation with open source AMD #mesa drivers, I have to go back to the #Xorg / #X11 version for a while, as the stutters (with the mouse cursor and most UI interactions) after some hours/days of uptime are unbearable, even with the "patched for triple-buffering" version of Mutter + Shell at https://copr.fedorainfracloud.org/coprs/calcastor/gnome-patched/
I'd like to sysprof it, but probably only makes sense in F39 + GNOME 45
Innocent old me. It’s been years since I have even thought about /etc/X11/xorg.conf and I thought I never would have to again. Wrong.
Today I updated Fedora Linux on my PPC workstation and on reboot, I had lost my GUI login. That turned out to be because the systemd gdm.service had failed, because the X server had failed, because… well, because it had no conf file.
These days you’re not supposed to need one (it’s meant to auto-detect stuff during boot) but after the updates, this install needed one.
I generated one with the Xorg command, and while that command errored out, it seemed to generate a complete-looking config file. With fingers crossed I dropped it into place and rebooted and it Just Worked[tm].
Not a fun thing to debug, but I am glad to have solved it. #linux#fedora38#power9#xorg