Search

Items tagged with: X11


Oh my, I didn't realise the state of develop-for-Wayland was this bad. As a sometimes hobbyist developer I can feel the pain.

It really does feel like one of the Linux non-profits could usefully somehow "take ownership" of the protocol level to at least standardise on one way to do things like virtual keyboard input. You'd think at least Gnome and KDE could have saved both their selves some time by co-operating on these things.

I'll continue with Xorg-based X11 until there's good reason not to. Yes, I know about recent security issues, lack of maintainer-ship, and the shit show that has been the forks/alternatives...

... but my current X11+fvwm3 setup *works for me*.

#wayland #linux #x11 #xorg


"Supporting Wayland isn't a one-off feature. Every compositor update, every new distribution release, every configuration change adds to the testing matrix. The thousands of permutations we described aren't a historical problem; they're an ongoing reality that demands permanent engineering commitment."

Avalonia did the math on Wayland support and the numbers weren't good, lol... best of luck to us all. <3

avaloniaui.net/blog/bringing-w…

Same math I did 8 months ago and with the same conclusion: semicomplete.com/blog/xdotool-…



This morning I did get #kde #plasma #wayland up and running, had first fight with #sddm , this for my old monitors had really big colour difference, one darker and a grey/yellow taint. So I thought one of the monitors was breaking down, I spent weeks to looks for what next and spent money on new monitors. I have the same issue, so I decided to switch #Xorg for wayland, sure the issue is till there... and gosh wayland ain't the best on handling sessions IMHO, as which VT seems to be a bit randomish, you are stuck with "Switch User" and gosh it's SLOW like hell and easy to make plasmashell to crash on a session you are switching to. sddm don't allow you to specify the VTs you want to use, not even which VT to start with.

Plasma had the nice feature where you could scale old #X11 applications that don't have built in scaling, but then it would affect all X11 applications, this should have been a Special Window/Application rule, then it had been a lot more useful. Enabling #HDR , it works just for one monitor.

When #plasmashell crashes when you try to switch back, the view port seems to change to something a lot smaller. I can't get #yakuake to appear (either it's for it's far outside the view port or shift-f12 don't work when plasmashell wyaland crashes (in Xorg it works and the view is still full resolution).

It feels like everyone nowadays only develops a single user experience, desktop manager that can't handle multiple session (darn I miss #KDM , best ever desktop manager), desktop environments just don't handle that they aren't active. Multi monitor setups is nowadays a lot more experimental than it was in the 1990's.

As my main issue didn't get solved, I will revert back to Xorg and get a bit more stability. Maybe there will come something better to replace wayland, once in the time I was enthusiastic about it, but with time I just think it's just been a waste of time which could have been spent on gutting out all the old in Xorg and add new features.


Prepare for a riveting saga of #Linux #input #latency, where #X11 and #Wayland battle for supremacy 🏆, yet somehow everyone still uses Windows for #gaming anyway. The author bravely ventures into realms of VRR and #DXVK, only to realize that the true enemy is their own patience 😩. Meanwhile, the rest of us just want to play #Quake without summoning the tech gods. 🎮
marco-nett.de/blog/measuring-i… #HackerNews #ngated


The media in this post is not displayed to visitors. To view it, please go to the original post.

Trying out NextSpace on Slackware -current with XLibre.

A modern implementation inspired by the classic NeXTSTEP desktop. It's interesting to see how its design and workflow still feel relevant decades later.

Definitely a fun project to explore.

#Slackware #NextSpace #XLibre #Unix #X11


The current version of #KDE on my machine (6.7) seems to be very buggy in terms of what happens when I try to add extra monitor(s) in the #Wayland version, whether it’s via #HDMI or #USB with #Displaylink. The screens go haywire and I can even get a terminal open. I’ve had to revert back to the #X11 version just as I’d got used to Wayland. I’m no fanboy of Wayland or X11 but when such a major breaking of the system happens, it forces my hand. Not good at all.

#Fedora #Linux #Desktop #KDE6_7



The media in this post is not displayed to visitors. To view it, please go to the original post.

SonicDE Launches as a KDE-Based Desktop for X11 Holdouts

「 The project’s main goal is to maintain compatibility with X.Org Server for as long as possible and to adopt new XLibre features when feasible. Plus, to serve those who still rely on a full X11 session and wish to retain that experience in a KDE-based environment 」

linuxiac.com/sonicde-launches-…

#kde #x11 #sonicde #xlibre #opensource


OK, so finally ~migrated to #wayland from #x11 on my #vmware #fusion VM, but since it's a Fusion VM I hit the seemingly unresolved clipboard problem between host and guest machines.

As far as I can see based on my searches, it's pretty much unfixable. How are folks working this around today? Clipboard over network? Just use x11 and hope for a fix in our lifetime?


apart from the clear fallacy of #KDE claiming most their users use #wayland over #x11 , how are they getting that telemetry eh? Isn't that inherently flawed...


SonicDE

We forked the #KDE Plasma Login Manager. It now runs on #X11, drops privileges after init, and supports #systemd-free too. We tested it on Artix Linux with OpenRC, CachyOS with systemd, and on the #FreeBSD-based GhostBSD. #SonicDE sonic-login-manager

x.com/SonicDesktop/status/2056…


#kde #x11


Need to use an ‘input method’ for Japanese characters, but said ‘input method’ forces only a single keyboard layout on the system level, so I can no longer type Czech characters using Alt Gr on the Czech layout without first turning off the option that adds Esperanto characters to Alt Gr on the first system keyboard layout. :gutkato_flucerba:

Incidentally, I can add another system keyboard layout in KDE, but it’s automatically deleted on startup. My solution would be to write a script which either turns the Esperanto characters on/off or adds a keyboard layout, but it seems like there is nothing like setxkbmap under Wayland, so my best option would be poking at KDE settings with severely underdocumented command-line tools. :gutkato_renversa:

Why does technology always have to turn ugly?

#lang_en #KDE #setxkbmap #technology #Wayland #X11



Uuurgh... why does everything run like crap on #wayland? Or rather #kde on #wayland.
I never had any major performance problems on #xfce and #x11. Here kwin_wayland keeps using at least 20% or often 40% CPU. Chromium even hogs all the CPU time it can get when open.
Firefox only runs well through XWayland.
Who said wayland is stable? #archlinux #ThinkPadX260
(Also.. suggestions are appreciated. I already tried looking up my sympoms online)