Why would they do that? They're intentionally not supporting OpenGL, so that people use their proprietary API
Why would they do that? They're intentionally not supporting OpenGL, so that people use their proprietary API
Not 30%, it's 30g or 5% lighter!
You'll need to specify what DE you're using. This comes built in with KDE Plasma: Meta+left and then quickly also up for top left corner, Meta+right and then quickly also down for bottom right corner etc.
I don't knowt what exact shortcuts other DEs use, but I think most that aren't Gnome support quarter tiling too
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?
KDE did bother, this does neither happen with KScreenlocker, nor do non-screenlocker windows show in another way, because the screen locker is integrated with the compositor.
If the compositor crashes or gets disabled somehow ofc though, that integration doesn't help either and you have to rely on a mountain of bad hacks as well as the hope that the screen locker doesn't also crash for nothing to happen in that case, but it's as close to secure screen locking as you get on Xorg... in the end the solution for secure screen locking is still Wayland.
Telemetry wasn't a factor iirc. The biggest reasons for this change were that
I was especially surprised to find that Gnome would turn the screen around correctly by itself. With KDE Plasma I had to set the correct screen orientation myself. And unfortunately Plasma also did not come with any on screen keyboard so it was effectively unusable.
You just need to use a distro that follows our upstream defaults - namely Wayland, and having the virtual keyboard Maliit installed by default - then everything will work out of the box with KDE Plasma too.
S3 is standby. Hibernate is S4
In the case of one project in paticular, that being the Sunshine game streaming project
That's a terrible example, because they completely ignore the many many years old standardized APIs (screen casting and remote desktop portals) that they could use, in favor of doing hacky and broken things that require root access instead.
I have some problems with X11 cursors and that's quite normal with Wayland obviously
It's not. There is no Wayland specific cursor format, it's all just images on disk, and the most widely used format hasn't changed away from Xcursors yet.
For example, my cursor can become invisible if my screen sleeps
That's either a compositor or driver bug, please report it (as I've never seen that on Plasma, to your compositor first).
Additional controllers that control mouse cursor don't control X11 cursor, however they still work, I just don't know where the cursor is unless it highlights something.
That's because it moves the X11 pointer but not the real one. A cursor theme can't change that.
Professionals call it a "layer 8 problem"
It's been possible for a long time, but yes, now you can do it intuitively in the shortcuts GUI
Xwayland doesn't get input in some special way, it uses the exact same Wayland protocols to get input events as native Wayland apps. All claims about it being more complete or anything like that are nonsense.
Krita forces Xwayland because they have some X11 specific code they haven't bothered porting away from, that's all.
No. Source 2 still uses some X11 specific stuff and has to be ported over to Wayland before it can work Wayland-native
Thst might change with Flathub's ambitions to become an actual app store though
Most displays provide settings to modify the colors of your screen; mine has like 10 different "picture modes" that strongly modify gamma curves, colors and the whitepoint. The EDID only describes colors of one of them, so if you change display settings, the data no longer applies.
More generally, the information isn't used by Windows or other popular video sources by default, so manufacturers don't have much of an incentive to put correct information in there. If it doesn't make a difference for the user, why would they care? Some displays even go so far as to intentionally report wrong physical size information, to make Windows select the default scale the manufacturer wants to have on that display (or at least that's what I think is the case with my cheap AliExpress portable monitor)...
That's not to say that the information is actually often completely wrong or unusable, but if one in tenthousand displays gets really messed up colors because we toggle this setting on by default, it's not worth it. We might add some heuristics for detecting at least usable color information and change this decision at some point though
Widgets aren't themes. They're things on your desktop that people are using for example for showing a folder - and if that can't interact with the system, that widget's functionality is broken.
Of course, that should not apply to install scripts or the like, which shouldn't be a thing at all really. And it should be made a lot more obvious which downloadable things can execute code / which ones are "guaranteed" safe and which ones may not be.
Another issue I have is that my touchpad doesn’t get detected if I’m holding down a key
That's a libinput feature, meant to prevent you from accidentally using the touchpad when you're typing. You can disable it if you want.
the fact that 1.8 was working tells me that it is possible for a window manager to work well for nvidia
Nope, it's a race condition for which the visible effects can appear or disappear for plenty of reasons. The only fix is explicit sync, which is being worked on for wlroots
Debian
... is not something you should ever use on a desktop PC. Due to its eternally very outdated nature and not even shipping bugfix updates**** it is not a good fit for anything but servers.
Wayland, for some reason, couldn't handle 4 monitors, with one above the other three.
"Wayland" doesn't handle monitors at all. What (because of Debian, wildly outdated) desktop did you use?
Oh, and the biggest issue I had with Windows was copied straight into Linux. I want my (single) taskbar on a monitor that isn't my primary.
Not a Linux issue, but a problem with the desktop environment you chose. KDE Plasma allows you to configure panels in any way you want.
FreeBSD isn't working on a Wayland port, that's already happened. The Plasma Wayland session has supported it for quite a while... KDE even runs a CI job on FreeBSD for every merge request, where kwin_wayland autotests are run.
Considering the amount of complaints we got when something broke recently though (which is to say, none), it doesn't look like it has a lot of users
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.
Why collect telemetry at all if you're not going to use it anyways?
Because we're sadly not collecting enough and actually useful telemetry. I think we know from telemetry that a big majority has double click set, but we don't know why (default setting vs user chose it explicitly).
And we can't easily add such things without breaking user trust. We need a new telemetry system that's more useful and extendable, but doing that is a lot of effort that noone has put in yet.
And if the distros are already having it as a default, it's even worse. We're setting it per default because it's set as the default.
No, we're setting it as a default because a bunch of people that are closer to the users than us decided to deviate from the upstream default. That's a super clear sign that we're doing it wrong
Fedora KDE 40 does not have an X11 session by default
Neither of these things are true, if you're using Wayland for both sddm and the session
There have been incidents involving malicious code downloaded through Plasma global themes.
No malicious code was involved, just buggy code.
I'll change it back anyways
You don't need to, this is only few new installations
It is not related to Wayland or the compositor in any way. This is a plasmashell extension.
Similar caveats do apply to KWin scripts and effects though
Coincidentally I also merged a kms thread into KWin late July. When dragging windows around, the cursor is now visibly ahead of the window.
I wouldn't read that much into it. Valve isn't Nintendo, I doubt they'd launch a new Deck without OLED
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.
Yes, there's an addon for Firefox that gives you Netflix 1080p without any downsides, probably just by changing the user agent for Netflix.
Really shows how utterly useless the restrictions are.
Of course apps can and do restore their window sizes. Don't spread misinformation
via the Wayland protocol
There's no Wayland protocol involved, Mutter directly talks to the kernel
Unfortunately Debian stable doesn't ship our bugfix releases after the major Debian version gets tagged - KDE Plasma in Debian is currently at 5.27.5, and 5.27.10 was released upstream two months ago.
In other words, you'll be experiencing bugs that have long been fixed... I'd advise to stay away from Debian for KDE Plasma because of that. If you want a Debian based distro with a good KDE Plasma experience, KUbuntu is likely a better choice, even with forced snaps. If you don't need Debian though I'd recommend taking a look at Fedora KDE or Arch (derivatives).
Partially, sure, but there's also a lot of KDE devs that are really convinced that it's objectively superior and wanted the default to convince more people to use it.
Yes. Flathub wants to become a platform where people and companies can sell their software
it falls to each and every individual app to (re)implement everything: accessibility, clipboard, keyboard, mouse, compositing etc. etc.
I haven't read so much nonsense packed in a single sentence in a while. No, apps don't implement any of these things themselves. How the fuck would apps simultaneously "implement compositing themselves" and also neither have access to the "framebuffer" (which isn't even the case on Xorg!) nor information about other windows on the screen?
Please, don't rant about things you clearly don't know anything about.
That has pretty much nothing to do with the color profile, when colors look very desaturated on HDR screens, that's the driver messing up the colorspace signaling.
What GPU do you have? Both Intel and NVidia still have major problems with this.
Many displays (but not all, which is why it's not exposed in the GUI) also support doing HDR without additional colorspace signaling, you could try enabling only hdr and disabling wcg with kscreen-doctor. IMO the color part is the more noticeable benefit of HDR, but you could at least have functional HDR until your GPU driver is fixed.
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!