Well if you bothered to read the blog posts I put up, you’d see there are links to nearly ever one of the issues I mentioned, some of which I’ve contributed too. Some have been closed without any indication if they’ve been fixed. The DPMS issue is present across multiple Wayland composers (this has to do specifically with HDMI monitors and rescanning on input loss. X11 correctly prevents a reconnection after a dpms sleep, but Wayland will detect and reactive the connection. It doesn’t look like there’s a fix even planned).
Look man, I only have one main box and I can’t just close out everything, try it in KDE on every update, and then go back in and re-open everything I was working on and put it on the right workspaces. I am, right now, installing Fedora 42 on a spare NUC as part of some rpm packaging, so I might get around to testing that soon.
I’ve contributed to a lot of bug reports, mostly in Gentoo’s bugzilla since it’s my primary distro. I’m not someone who just complains. I’ve actively tried this stuff out, commented on issues and added debugging information. Don’t assuming I’m just bitching about shit. I do try to contribute and all of this wayland shit is still broken and hasn’t moved forward in a meaningful way in YEARS except for maybe Hyprland (whose community is fucking amazing BTW, and despite being treated unfairly by everyone) and even they’re limited by somethings totally outside of their control and that are core issues in Wayland.
Sorry for being lazy, I did read the entire thread but that was months ago now. So details are a bit hazy, apologies if that came across wrong. Many people don’t do exactly what you have done, so kudos to that.
That report on monitor unplugging worries me a little, a common use case is to connect a laptop to and from a dock, and the same can in theory be done with an actual PC and a USB C outlet. So this could have large ramifications on many people, potentially.
This might be specific to just desktop PCs though as laptops always have at least one monitor… Pure speculation from my part, but, well worth investigating, methinks. It could also be a problem of Nvidia/AMD/Intel/[InsertGPUVendorHere], Nvidia is known to still have quite a few Wayland troubles.
You might have uncovered one of Waylands blindspots here.
Yeah I shortened it. I meant to they might not have encountered the same issue as they don’t have the same setup.
Fine to dislike them, but I think it’s a net positive getting their audiences as potential users is a great way to get more support/attention for projects.
let us know how it goes. I’m curious if @wendell has encountered this with the l1kvm
Personally, and self-indulgently (is that a word?) I would very much welcome a working RDP server in KDE. As it stands krdp / krdpserver barely works.
On windows client I cannot connect to it via mstsc (even with one brought from win10). Can only connect via WSL → xfreerdp, but it doesn’t understand multi-monitor, and works 4x slower than xrdp/xorgxrdp setup that I continue to use (this implies “local remote desktop” while working directly on “remoted” machine).
That being said, I do understand upsides of wayland and I do wish that it achieves success.
Not a fix or replacement to krdpserver, but two of my boxes (different distribution families) shifted themselves to a wayland session and a side effect of that was knocking out krfb (vnc)'s unattended access (causing it to require to manually allow remote sessons every reboot. with headless devices).
There’s some wierdness with krfb as well, I think. regardless, resolved with resetting by rm ~/.config/krfbrc , then configuring with same access and unattended password. I also set ‘do not use kde wallet’ through settings to remove the complication, but might not have to.
One of the headless devices is a remote game VM, and sunshine/moonlight has been the most reliable with wayland for me. it has its own limitations.
Though i'm pleased remmina/xfreerdp is now handling multimonitor connections out, from within a wayland session.
I am running a dual monitor setup , I am running a 3840x1600 at 144hz in DP and a 2560x1440 @~ 100hz also connected DP.
I have not tried disconnecting monitors, nor do I have a KVM on my setup
I have swappy, grim and slurp, seems to work for what I need it to do . I have not tried flameshot.
no DAW installed
here is a screen using xrandr displaying active monitors ( I only have 2) total resolution of 6400x1600
Ok it went to lock screen and came back into the session here is the hypridle config that is being used and the notifications that it is supposed to act.
