The last time the Dems held a primary was in 2008.

Why the fuck do people upvote this misinformation? They held primaries literally this year, which is information everyone can trivially look up

The 1 second present timeout still only works for XWayland

Oof, I thought the corresponding MR for Wayland was merged… But it was from Sebastian and after he got into a heated discussion again and started cursing, the MR got closed by someone else :|

realistically unless SDL2, GLFW or whatever engine a gamedev is using handles it for them they just don’t have the time to worry about what GTK, Qt, or XDG shell does

SDL does handle it, but only for OpenGL; it can’t do anything about Vulkan. GLFW doesn’t do anything about it either, so that is pretty annoying.

I believe in the glorious Wayland future… I just wish it would get here a bit faster

Don’t we all. Let’s hope the current upstream approach to fix this issue gets somewhere sooner than later…

Sorry, but Debian stable is a terrible recommendation! They don’t even ship bugfix releases of KDE Plasma… It’s stuck with a months old version that has lots of known and long fixed bugs in it

Debian doesn’t ship bugfix releases of our software. If you want a stable experience in the actual meaning of the word instead of just something that doesn’t change, almost every other distro will be a better choice

Yes. Flathub wants to become a platform where people and companies can sell their software

Thst might change with Flathub’s ambitions to become an actual app store though

No. Some people wanted to change it to that for Plasma 6, but on Xorg there’s apparently no way to make that happen, as the cursor is always decided on by the window you’re hovering over…

What are the not-a-bugs? Things like covering up a Wayland window will block it’s rendering thread indefinitely with no way to detect it happens to handle it. This can lock up some games, or cause you to time out in a networked application. Some Wayland core folks don’t want applications to know if their window is visible or not because it’s mild information about a user’s attention that should be private. Every game dev on the other hand is asking “WTF!?” as it causes their games to break randomly

Please don’t make up what “Wayland core folks” think. You don’t know it, and your claims are waay off.

It’s not about security. It was intended to allow the compositor to throttle apps to improve efficiency… Which of course in practice doesn’t work like this at all, because OpenGL swap buffers and Vulkan FIFO presentation modes were never intended to be used this way.

As for why that hasn’t been fixed yet, it’s not as big of a problem anymore:

• Mesa (at least for Vulkan) and Xwayland gurantee one frame per second as a minimum refresh rate
• toolkits and libraries use mailbox presentation internally and check frame callbacks themselves for when to render
• xdg shell now contains a flag for apps to know to inhibit rendering because they’re hidden. That doesn’t guarantee that presentation won’t otherwise block though
• a (set of) protocol(s) is being worked on to replace frame callbacks with a mechanism actually suited for OpenGL and Vulkan

Another mild example is that windows cannot be raised except by the user or by launching them. This is supposed to be a mild security precaution so a program can’t pop up a legitimate looking dialog over another application and trick the user. Realistically it means that applications can’t open and focus URL in your web or file browser. Instead they have to give you a notification telling you “Firefox is Ready” and make you do it manually.

That’s not even close to how activation works on Wayland, and no, it’s not just a security thing, it’s a usability thing. Apps can only raise themselves if the currently focused app gives them focus, so that random apps can’t cover up what you’re working on just cause they need to show you an ad or an “important” pop up question or whatever. If it doesn’t work for a specific app, make a bug report about it to the app.

That sounds like your TV is temporarily disconnecting at random, or at least doing something that the GPU detects as a disconnect.

Most likely, AMD’s hotplug detection is too aggressive. You can report that at https://gitlab.freedesktop.org/drm/amd/-/issues

Yes, they did. Neal has been pushing for Wayland by default upstream for a while, and getting that in for Plasma 6.0 was and is the plan.

No, they’re not a feature from X, quite the opposite. They’re Wayland only.

If the hardware works, you might want to check sudo libinput debug-events for whether or not the driver works as well. If it does report gesture events with 3 and 4 fingers and KWin doesn’t react to them, please open a bug report at bugs.kde.org about it

KWin had four finger touchpad gestures since 2017. If they don’t work for you in the Wayland session, your touchpad most likely simply doesn’t support detecting more than two fingers

Neither of these things are true, if you’re using Wayland for both sddm and the session

Afaik that’s a bug in Firefox, it doesn’t cope well when middle click paste is disabled… As a workaround you can enable it again

Even finding a decent and working FTP/SFTP/FTPS desktop client (similar WinSCP or Cyberduck) is an impossible task as there a few, but they all fail even at basic stuff like dragging and dropping a file.

Of course you’ll have trouble finding a dedicated desktop client… that functionality is literally built into most Linux file managers.

I’d recommend you to make backups either way. I’ve had a SSD with SMART status “good” very suddenly die before, so don’t take any chances!

All it ever was intended for was to make us feel like something was being done while doing absolutely nothing.

It certainly does help a little bit. But it’s of course still not a coincidence that companies are pushing for it instead of more effective measures… It’s not just cheap but it also pushes people to believe that measures to save the environment are all useless and annoying, and makes them less likely to want more to happen.

Are you on Wayland, or Xorg?

While I agree with your conclusion, your explanation is not right.

X11 is the 11th version of the X protocol, it is not an implementation. The Xorg server is the only relevant implementation for the server side of things, and for X11 window managers and X11 compositors there’s only libx11 (which is very horrible) or libxcb (slightly less horrible). Both of those are about as high level as libwayland-server + libwayland-scanner - which is to say, nearly as low level as it gets.

wlroots in contrast provides comparatively high level libraries / components, which make the implementation of compositors less of a headache than having to mess around with barely documented xcb functions.

The very next words are “but it was my responsibility”… what exactly is bad about that statement if you don’t intentionally cherry pick a bad quote?