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!
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!
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
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
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
Thst might change with Flathub's ambitions to become an actual app store though
No. Source 2 still uses some X11 specific stuff and has to be ported over to Wayland before it can work Wayland-native
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
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
There have been incidents involving malicious code downloaded through Plasma global themes.
No malicious code was involved, just buggy code.
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
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.
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.
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).
via the Wayland protocol
There's no Wayland protocol involved, Mutter directly talks to the kernel
Of course apps can and do restore their window sizes. Don't spread misinformation
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.
Please start a gdb console for the last crash with coredumpctl debug kwin_wayland, get a backtrace in there with "bt full" and create a bug report with the backtrace at bugs.kde.org
It is repeated in every single damn "Linux phone" thread, and in every single thread an answer like this is needed: No, it fucking isn't. You know exactly what everyone means, stop being a dick about it.
Debian still ships version 5
Debian ships 5.27.5 - it's not just not updating often, but it's not shipping bugfix releases (latest 5.27 version is 5.27.11!). I recommend to avoid it and maybe look at KUbuntu LTS instead
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
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
When I use multiple monitors I get a range of odd behaviours, including a white screen, lock ups, failure to display anything on second screen. I've unplugged the second screen for now and all is OK except that adaptive sync does not work properly.
Sounds like a driver problem. What kernel are you using, and have you tried running Mesa-git?
When I set adaptive sync to "Always" in the settings the screen sort of flickers when I move the mouse. To be more precise the screen gets a bit brighter when the mouse is moved, then returns to previous slightly dimmer brightness when the mouse is stopped. There are no errors that I've found.
You can't find any errors because there are none. The brightness changing with the refresh rate is sadly how most monitors work today, and can't really be fixed. It's the whole reason for why adaptive sync is not set to always by default.
Why doesn't automatic work for you though?
Multi monitor VRR has never been problematic in Wayland, but the NVidia kernel driver doesn't support it at all yet, Xorg or Wayland doesn't matter.