141–150 of 202 posts
Hoping this transition to default will get the attention of developers at Zoom, and they can get screensharing to work in their native app without resorting to browser mode or some virtual camera hack. My biggest gripe for sure.
I enabled wayland recently and there’s been a lot of annoyances to the point that I wonder why I bother considering X11 works without these issues. For example: * Chrome needs a bunch of extra flags to launch in Wayland mode * Firefox needs extra flags to launch in Wayland mode * Xwayland is just broken on Nvidia with both sides refusing to compromise (implicit vs explicit synchronization - Nvidia refuses to add impl…
Maybe Firefox needing flags is a per-distro thing? I’ll have to check and make sure but I think Firefox works with Waylad sessions out of the box on my Fedora laptop. That’s using an Intel iGPU instead of an Nvidia GPU though so maybe that’s also a factor.
One thing is that the correct environment variables should be set, but all the wayland compositors have been setting these for ages AFAIK
Earlier quoted context omitted.
I'm surprised whenever I hear Wayland works flawlessly for someone, since I've tried using it on the NixOS unstable channel for a few releases now, and there are a few major bugs that make it unusable for me. A show stopping one is that the bottom panel is stuck in the middle of the screen, with no way to move it down that I could find, and clicks register in completely different parts of the screen. It's difficult t…
I recommend swapping your nix package to firefox-wayland -I've been using it for quite a while and it's been great. For me, it's been a huge improvement over X - thr lack of screen tearing when srolling and playing videos is huge. If an app uses one of the normal GUI toolkits, they don't normally have to do anything crazy to support wayland, so I'd be suprised if you need to swap to a whole new ecosystem (and there's…
I really haven't had major gripes with X for many years. It mostly just works, and is rock solid. Long gone are the days when you had to manually craft the perfect config file depending on your setup. It also works great with multiple monitors, though I think there are still some color management issues, which don't particularly bother me, and lack of HDR, obviously. Plus the client/server architecture is super useful, to this day. IME Wayland feels like a usability regression, forcing me to change many of the programs I use, and it has critical issues, which seemingly only affect me...
Earlier quoted context omitted.
More tiling managers is always great! The advantages of tiling window managers are so tied to muscle memory, I’m not sure many people will want to switch from, say, sway or i3 or whatever. But at least new people will be able to give it a try. I’m not sure how much work is involved in replacing the window manager inside a desktop environment. It would be nice to just drop sway into kde. Dunno if that is possible thou…
> The advantages of tiling window managers are so tied to muscle memory, I’m not sure many people will want to switch from, say, sway or i3 or whatever. Hear, hear ! I have been stucked with awesome for years now and even though I lost some functionalities between v2 and v4 I still can't switch. I tried i3 and regolith (was really looking for all the niceties of a DE: volume, bluetooth, screen, etc.) but tiling opera…
I enabled wayland recently and there’s been a lot of annoyances to the point that I wonder why I bother considering X11 works without these issues. For example: * Chrome needs a bunch of extra flags to launch in Wayland mode * Firefox needs extra flags to launch in Wayland mode * Xwayland is just broken on Nvidia with both sides refusing to compromise (implicit vs explicit synchronization - Nvidia refuses to add impl…
I have three laptops each with Intel graphics, each from a different generation. They all have the same show stopping (as in screen locking gotta reset) bugs after a fresh distro install, no adjustments. But ofcourse, Wayland isn't the problem...
Wayland doesn't fractionally scale chrome, discord, vscode, spotify, beeper, and other appimage and non-native applications. So even if KDE enables it by default, most users will have to switch back to X.
It doesn't scale the rest, because those are electron apps that either ship with old electron version, or disable wayland. Special mention goes to vscode, which ignores *-flags.conf and provides no other way to enable wayland, except for command line argument.
So basically it is maintainers of these apps dragging their feet.
Wayland doesn't fractionally scale chrome, discord, vscode, spotify, beeper, and other appimage and non-native applications. So even if KDE enables it by default, most users will have to switch back to X.
Isn't that more of an Electron problem than a Wayland problem? (honest question, no snark intended. It looks like those are all electron based apps)
Earlier quoted context omitted.
> The advantages of tiling window managers are so tied to muscle memory, I’m not sure many people will want to switch from, say, sway or i3 or whatever. Hear, hear ! I have been stucked with awesome for years now and even though I lost some functionalities between v2 and v4 I still can't switch. I tried i3 and regolith (was really looking for all the niceties of a DE: volume, bluetooth, screen, etc.) but tiling opera…
I wasn't exactly an awesomewm power user, so I'm sure there's awesomewm functionality you couldn't mimic in kde, but my most used keyboard shortcuts I was able to import in to kde.
Does screen capture actually work reliably yet? I hope they leave X11 as an option until it does.
It does not in the general case. For KDE, it works for some programs, but not all of the common ones including Discord.
It doesn't work those, that call XGetImage on X11 root window and think, that they will get away with it.
Wayland has a few glitches, but in general it's good to use. For example, it doesn't have an API to get current cursor position (which breaks keepassxc's browser popup, goldendict's query popup), an API (which most compositor implements) to get current window state, which makes me unable to find an alternative of autokey (kwin script can do this, though, but it lacks the ability to execute arbitary commands..). On th…
The other feature for me is security. Sandboxes can access the wayland socket and run GUI stuff, without the ability to read the entire screen or run commands that effect outside of the sandbox.
The wayland socket is a unix socket, exists as a regular file. Gating access to the socket works like any other file.
X11 has some interesting issues here. It creates an "abstract socket". These exists as files on the file system, but they are not regular files.
An interesting exmaple: A sandbox that starts with a fresh root and bind mounts in only what is required. Even when you don't bind the socket into the sandbox, the sandbox can still access it!
There are ways to prevent sandboxes from accessing the x11 socket, but this is definitely not what I would have expected!
With wayland, if the socket is not bind'ed into the sandbox, it can't be accessed, it behaves as expected!
This might not seem that important, but these features bring Linux desktop out of the 1900s with regards to security. Software like flatpak would not be able to effectively sandbox GUIs at all without wayland, a feature other platforms have supported for at least a decade or more!
The Linux desktop isn't making great use of this and related technology yet, on the standard distro, by default, applications can read your GPG keys and other important data, or even delete it. Wayland is a step towards fixing this!