41–48 of 48 posts
What is the solution regarding the display manager? As SDDMs Wayland support is considered experimental. What do you guys use/recommend?
Intel HD630 graphics in Kaby Lake Core i5 7500T & Core i7 7700T. CachyOS.
Earlier quoted context omitted.
It's actually wild that they're trying to sell lack of basic desktop features as "security features". Try explaining to an average person that when they are playing a game and want to capture a cool moment to share on Discord with their friends that by design the window server they are using will not let them do that and it's "for their own good". Like God forbid I want my computer to be actually usable. We had the s…
Wayland had the same odor a failed state has. It's a huge hairball with no easy fixes, but at the same time, that's of significant benefit to some specific players. You can have a very usable X11 desktop with positively pre-Cambrian software. But to keep up with Wayland's ever evolving omnishambles, you basically have to run KDE or GNOME, or maybe Sway.
If all the expected stuff was there, Sway (chosen because it's not tied to a desktop environmen) could be your X server equivalent.
Earlier quoted context omitted.
I'd say it's completely irresponsible to not have such features, claiming it's about security, rather than implementing it behind a permission system that puts the end-user in charge.
It is implemented behind a permission system. KScreenshot works perfectly fine and so will most of the applications using PipeWire I guess, same that screen captures. KDE is merely saying that some applications will have to be updated to use it so all of the current screenshot applications won't work out of the box. No idea of why some commenters here are implying screenshots don't work in Wayland. It seems their kno…
Earlier quoted context omitted.
The 1996 extension had severe limitations. Untrusted clients have no clipboard, but also no GPU acceleration at all and other features were barely tested using it so it was somewhat random if they would work. It breaks a ton of applications and was therefore used by approximately no one.
Ok, so instead of a couple UAC style prompts for screen readers, macro recording, desktop sharing, etc, and some tweaks to GDK, we got what? An entire new backend GDK windowing system, and a pile of broken applications? And its been decades? And its not like actual flaws people found couldn't be fixed. There is a word for this.
The flaws were not limited to the 1996 poor security extensions. These kind of half broken extensions are everywhere in X11. At some point, if the tweaks you have to do is basically rewriting the whole rendering pipeline and adding new APIs for the most significant systems, what you are doing is strictly équivalent to writing a new piece of software which is exactly what the people behind Wayland did.
And don't worry, the change adverse people you see here complaining about limitations fixed years ago would be complaining the same if the effort was on rewriting part of X11. That's life. Armchair complainers and keyboard warriors will complain while actual doers push things forward.
Earlier quoted context omitted.
It is implemented behind a permission system. KScreenshot works perfectly fine and so will most of the applications using PipeWire I guess, same that screen captures. KDE is merely saying that some applications will have to be updated to use it so all of the current screenshot applications won't work out of the box. No idea of why some commenters here are implying screenshots don't work in Wayland. It seems their kno…
I was talking in general. It's less about screenshots and screen recording, but more about drag-and-drop and global hotkeys like push-to-talk in Discord.
Global hotkeys are also supported perfectly fine. Applications just need to register with the compositor, which will transfer the key press to them. That's the feature working at it should. It prevents applications from hijacking keys when that's not what you want.
The issue is that Discord takes ages to ship anything on Linux and barely supports anything and the Linux community does it's best to keep supporting everything. Other plateformes would have just mandated the new way ages ago and be done with the transition by now.
What is the solution regarding the display manager? As SDDMs Wayland support is considered experimental. What do you guys use/recommend?
What I am uncomfortable with is the inability to run Wayland on older video hardware. X11 will happily run with Vesa driver on older hardware which no longer has functional 3D accelerated drivers. What is the way forward for the retro community to run a modern Wayland system on older hardware? Hopefully someone more knowledgeable can chime in or correct me
If your Linux distribution is handling Mesa packages correctly, you will never lack OpenGL/Vulkan drivers . The reason is that Mesa includes "software rendering" drivers for both OpenGL ("llvmpipe") and Vulkan ("lavapipe"). As the name(s) might suggest, they use LLVM to JIT shaders for your CPU (supporting SIMD up to AVX2, last I checked - although typical compositing shaders tend to get pattern-matched and replaced…