Here is my new GNU/Linux distribution guide about Debian KDE 12, the right GNU/Linux distribution for professional digital painting in 2024! Also about three major problems with GNU/Linux distros that will drive away all professional artists, IMO, and how I got kicked out of the Fedora KDE ecosystem with F40, which imposed Plasma6 and Wayland. I hope it helps other artists here!
So @gnome is removing the x11 session, leaving just the Wayland one.
If this goes out before Orca, the GNOME screen reader, is fixed to work on Wayland, it will mean that people who rely on screen readers will have no way to use one on GNOME. And thus on the major Linux distributions.
So I’m hoping the plan is that this change will not land until GNOME has a working screen reader.
I am once again considering to write my own window manager
...unless the setup I am thinking of is already possible, let me construct this in your head:
On the top of the screen, there is narrow status bar, which is split into two parts. On the right side of the bar, you have your clock, your battery, your signal strength and so on.
On the left side, there is a clickable tab for every window you have opened. It's like browser tabs: Every window always uses the entire space below the status bar.
On the far left, there could be an icon which opens a searchable list of applications, kind of like #dmenu but vertical. Everything supports mouse input as you would expect.
Does that exist? Should I make it? It would be awesome for smaller screens, like phones.
Edit: I should add that I'm planning to run it on a Nokia N900 with a single 600 MHz CPU core, 256 MB RAM and a resolution of 800×480 pixels. Existing full desktop environments like Xfce4, LXDE, and so on are way to heavy to run.
sometimes i miss simpler days. this is a fresh install of netbsd in a vm. /sbin/init is 36K. there is no desktop environment beyond vanilla x11 with ctwm. by all appearances, this could pass for #retrocomputing.
#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)
I can't even login to #Google. After entering my password, the tab just stops working. It stops interacting. No clicks, no tabbing, no arrow cursor.
I can't event open about:support it hangs.
I can't use #Facebook, eventually the tab will stop interacting. No clicks, no tabbing, no arrow cursor.
I can't watch videos on #YouTube. If the YT ads play first, it will get stuck there. If the actual video plays first, after a few seconds it will either get stuck at some frame, or just keep playing without any interaction (can't stop, etc.)
I have a nice set of packages ready for KDE Plasma6 Beta2 which was just announced two days ago.
As you see from below screenshot, it runs nicely as a Wayland session, both logged in via the SDDM login manager and by running "startkwayland" from a console in runlevel 3.
GPU acceleration isn't always faster. Wayland is supposed to be faster because it utilises the GPU. Well, Firefox had the same idea with WebRender. Now, when I scroll on my poor laptop's Intel HD 4000, both Firefox and Wayland are fighting over GPU resources resulting in less FPS compared to X11. The CPU is almost idle. 😅
Anyone knows how to properly start a multiseat wayland with a desktop environment or window manager running?
I just need simple stuff such as profile initialization of the user and if it's possible to just share the same discrete GPU across multiple seats?
The end result? I want to isolate my current user space from the gaming space where I can just connect using moonlight/sunshine. I want it all headless.
In this one, the infamous “Wayland breaks everything” posts gets roasted, alongside with the efforts to basically reimplement #X11 inside #Wayland, we have more #AI regulation efforts, this time in the USA, and we have an interesting look at how to make our #FOSS licenses more relevant in today’s world:
Anyone knows how to properly start a multiseat wayland with a desktop environment or window manager running?
I just need simple stuff such as profile initialization of the user and if it's possible to just share the same discrete GPU across multiple seats?
The end result? I want to isolate my current user space from the gaming space where I can just connect using moonlight/sunshine. I want it all headless.
Before bed, I want to tell a quick troubleshooting story:
I switched to Wayland!
But DCS: World has a weird frame flickering issue.
I try Proton, doesn't help.
I try different Wine version, doesn't help.
I try messing with DXVK, doesn't help.
It's an NVIDIA driver issue related to XWayland.
I admit defeat and go back to X11.
But: Wine can be run in native Wayland mode!
I find out how to run Wine without XWayland.
It works flawlessly and more performant than ever before!
Toller Vortrag von Rouven Czerwinski zu #Wayland. Ich habe mich da bisher immer drum gedrückt. Aber im Vortrag wird sehr schön erklärt, was es ist, wieso es entwickelt wird. Warum welche Probleme existieren, etc.
Würde ich allen empfehlen die bisher auch noch auf #X11 sind und sich der Thematik bisher verschlossen haben oder noch Vorurteile oder Halbwissen haben.
Wayland is nice and all, but on my 11 year old laptop I get much better performance under X11 with compositing disabled. Wayland can barely go beyond 30 FPS while X11 easily hits 60.
Seeing so many #linux distros moving to #Wayland by default... I love Wayland, it does feel nicer to use by default than #X11, but until the Nvidia driver mess is fixed (and windows stop flicking on Nvidia machines under Wayland), and gaming performance is on par with X11, I just can't use it!
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?
10 years from now when all the little annoyances in Linux regarding hardware video decoding, video drivers, applications, Wayland and x11 are sorted....
I can sit here and think, "I wasted hours for weeks each work evening trying to piece all of this together and make it work"
Bold of me to assume that it will all be sorted 10 years from now though 😂
(no, not looking for help. I'm happy with what I've managed!)
I imagine #X11 had some fairly restrictive assumptions in the early days, but after 10 years there was a foundation (ICCCM 2.0) on which it was possible to build a variety of different desktop environments (DE). I dare say it was possible to reproduce an other DE or make something very different at that time.
After 15 years, #Wayland may be about to get window icons, but it still doesn't support a screensaver.
I think there's room for a competitor, but I certainly don't have what it takes.