Search

Items tagged with: Wayland

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

Jordan Sissel

2026-07-25 23:18:19

mastodon - Link to source

"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-…


Bringing Wayland Support to Avalonia - Avalonia UI Blog

A Pragmatic Approach to Linux's Display Server Future
Nikita Tsukanov (Avalonia UI)

#wayland #xorg #linux #x11

#wayland #amdgpu

Krita 5.3.2.1 is still not working well with touchscreen and stylus with GNOME 46 on Wayland :(

Whenever I try to move a layer by drag-and-drop, Krita completely stops accepting any pointer inputs. Not even restarting the program helps… I need to completely relog.

#krita #linux #wayland #gnome

#wayland #linux #gnome #krita

Ok, I think I've got this display card under control - or so it seems. It hasn't crashed since Wednesday.

I guess this is a combo AMD RDNA3 Navi23 and KDE Plasma (+ Wayland?) bug...

I backed out all my Linux kernel command line switches for AMD GPUs and it crashed to green screen in less than a half hour. So, re-adding them stopped that from happening.

... amdgpu.dcdebugmask=0x410 amdgpu.tmz=0 amdgpu.gpu_recovery=1 amdgpu.sg_display=0 ...

And then the cursor thing is fixed <?!> by adding

KWIN_FORCE_SW_CURSOR=1

Currently this is what is set:

`cat /proc/$(pidof kwin_wayland)/environ | tr '\0' '\n' | grep KWIN` :

KWIN_DRM_NO_AMS=1
KWIN_DRM_NO_DIRECT_SCANOUT=1
KWIN_FORCE_SW_CURSOR=1

From a user experience point of view I don't see any difference with that software cursor setting.

There's another wrinkle to this that might be a factor but I can't really test around it currently. This is a multi-head machine and one screen is connected via HDMI and one is DP.

Perhaps this wouldn't be a problem if both screens were connected via the same type of connector.

Both screens are set to the same refresh frequency. But, in the display control app one reads back at 60.00 Hz while the other is 60.000 Hz. Minor thing right? But in trying to make this work I've seen references to AMD GPU weirdness in multi-head configurations where the refresh rates were different between screens. Red herring perhaps.

Anyway, don't know if there are (or will be) any people trying to make a RX 5800 XT GPU behave under Linux but this seems to be what worked for me and my dual head setup. I'll update if anything changes.

#Linux #AMD #AMDGPU #KDE #KDEPlasma #Plasma #AlpineLinux #kwin #Wayland

#wayland #linux #kde #plasma #alpinelinux #amd #amdgpu #kdeplasma #kwin

I stumbled upon #seeqie , a terminal-based image viewer that uses Sixel Graphics. Written in #bash. It works fine with #foot #wayland on my desktop, but also on my #postmarketOS #sxmo phone. Nice!

cocz.net/seeqie/

Seeqie: A Terminal-Based Image Viewer Using Sixel Graphics

Explore Seeqie, my terminal-based image gallery browser that leverages sixel graphics for viewing images without leaving your terminal environment. Performance optimizations and lazy-loading provide a smooth experience.
Ben (Ben's Blog)
#wayland #seeqie #bash #foot #postmarketos #sxmo

After applying all recommendations from the article it still doesn't work, but I have found one setting different in my system than on every doc/article I found

XDG_DESKTOP_PORTAL is "sway:wlroots" in mine while everyone talks about "sway" value.
Could it be the reason?
I still didn't found where is set or how I can overwrite it.

#sway #wayland #linux #xdg_desktop_portal

#wayland #linux #sway #xdg_desktop_portal

Hi mastopeople,

I need help to have working screen sharing on my #debian laptop inside a #videoconference tab in #firefox or #chrome.
I'm sure it broke since I switched to #Sway on #Wayland.
I'm not sure if the browsers run natively or with Xwayland (they are not listed in `xlsclients`)

Any help appreciated, the simpler and more standard the better, I don't want to start downloading untrusted tools or compile things…

Please RT

#mastohelp

#wayland #chrome #sway #debian #Firefox #videoconference #mastohelp

Today on NovaLandia: "Seven Months Later, Pop!_OS COSMIC is a Mess"

Look. I’ve been a Pop!_OS user for years. I defended it. I recommended it. I even put up with the long, painful wait for COSMIC because the promise was real: a modern, Rust-based, Wayland-native deskt...

mkultra.monster/linux/2026/07/…

#popos #cosmic #wayland #desktop #gnome

#wayland #gnome #desktop #popos #cosmic

#wayland

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

I was asked about my beef with #Wayland and here it is: it's never worked for me. both CachyOS and GhostBSD runs just fine using X11 and the Xfce desktop on my system, which unfortunately is saddled with an Nvidia card. It's a hand me down system and I have no money to get a different video card. Anyway an ordinary Xfce session is perfectly functional but switching to Wayland on login breaks everything. with Linux it goes black as seen, with GhostBSD it thinks for a couple seconds then dumps me back at the login screen

I could start futzing around with rebuilding the Nvidia drivers but ugh. I just wanted the thing to work out of the box

#wayland

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.

#wayland #xorg #kde #x11 #plasma #sddm #hdr #plasmashell #yakuake #kdm

River is a Wayland compositor written in Zig that defines a window manager protocol so that, like with X11, write your own window management software. As with X11, the protocol is language-agnostic, so you can define your window manager using any programming language at all.

I have been gradually becoming more interested in Zig as a potential replacement for C in systems programming. Rust is another interesting potential replacement.

#tech #software #Zig #ZigLang #Linux #Wayland #WindowManager #WaylandCompositor #RiverCompositor #UnixPorn

river

A non-monolithic Wayland compositor
Codeberg.org
#wayland #linux #software #tech #Zig #RiverCompositor #unixporn #waylandcompositor #windowmanager #ziglang

#wayland #amdgpu

#wayland

#wayland

#wayland

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

Measuring input latency on Linux: X11 vs Wayland, VRR, and DXVK - Marco Nett

I built a device to measure end-to-end input latency, then used it to find out what actually moves the needle.
Marco Nett
#wayland #linux #x11 #hackernews #gaming #input #latency #dxvk #quake #ngated

#wayland #linux

I guess I'll relegate this account into my solutions dump, like a scratch paper, so uhh starting now, I've found that sometimes the "portal" for selecting a window for screen sharing doesn't pop up on KDE sometimes when I'm using OBS

Running "systemctl --user restart pipewire.socket xdg-desktop-portal.service" fixes it. I use Arch, btw.

I might investigate this problem when it pops up again cos it happens randomly...

#archlinux #kde #wayland #linux #freesofware #opensource

#wayland #linux #archlinux #opensource #kde #freesofware

Anyone using the latest version of River not the classic version but the compositor version? If so what WM are you using with it and how do you find it ? Feel free to share you configs and screenshots.

#RiverCompositor #RiverWM #Wayland

#wayland #RiverCompositor #RiverWM

Tip to self: Do not live-stream while using a #Wayland compositor, or my stream will be close to obliteration.
#wayland

Aaaaaaaaand I'm back to #xorg 🤓

I was getting frustrated with #darktable being so slow to the point that the mouse cursor would freeze.
I thought the newer versions were becoming too heavy for my old PC to handle.
Then, out of curiosity, I reinstalled xorg and plasma-x11-session and what do you know? Darktable works smooth af.

It's a shame because #wayland was seemingly working well for everything else.

#wayland #xorg #darktable

#wayland #jetbrains

#wayland

I'm still scratching my head about who thought that apps shouldn't know the monitors layout and not being able to move app's windows wherever app wants. In #wayland that is.
#wayland

#wayland

Man I cannot stand that #KDE does not remember window positions. I "understand" that it's some sort of #wayland thing and I do not care at all what the excuse is. We're talking Windows 3.1 level feature here. "Hey the new display manager is in such good shape that we're not including X11 anymore oh but don't expect it to remember where your windows were!"
#wayland #kde

#wayland

#wayland

#wayland

#wayland

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

#fedora #wayland #linux #kde #x11 #hdmi #usb #displaylink #desktop #kde6_7

#wayland

#wayland

Shot in the dark...

Anyone else having a terrible time with the AMD 7800 XT under Linux/Wayland?

Were you able to tame it?

Share your kernel params?

I've gotten no joy with various combo's and permu's of "amdgpu.tmz=0 amdgpu.sg_display=0 amdgpu.gfx_off=0 amdgpu.runpm=0 amdgpu.gpu_recovery=1 amdgpu.dcdebugmask=0x10 iommu=soft"

😵‍💫

#Linux #AMD #amdgpu #Wayland

#wayland #linux #amd #amdgpu

#wayland

#wayland

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?

#wayland #x11 #vmware #fusion

Updated my work desktop from RHEL 9 ➼ 10, which moved me from Xorg to #Wayland in order to get this security package to work. But now I have to disable graphics acceleration of my #GoogleChrome browser in order to get it to work.

Yes, I need to use Chrome to access some websites required for me to do work that only support that & Edge. *sigh*

#wayland #googlechrome

⇧