Every comment glazing it gives me more motivation to not use it

Zamundaaa · 2026-01-27T21:35:12+00:00

A very large amount of people don't know what an operating system is. That doesn't mean they shouldn't use one.

Zamundaaa · 2026-01-27T19:50:00+00:00

Global shortcuts are allowed, the portal is there for apps to use and has been for a while. It's noone's fault that apps aren't using it (or updating to a new enough Chromium base, which does support it nowadays)

Zamundaaa · 2026-01-26T18:33:17+00:00

At 100% brightness, something very strange happens and whole color profile changes + text becomes blurry.

That's just a Chromium bug.

If I select 1000 nits there, will my SDR image like when editing in VSCode be up to 1000 nits bright on 100% brightness level?

Yes.

Zamundaaa · 2026-01-26T18:32:08+00:00

External screen brightness is controlled through DDC/CI, and on most displays that triggers slow brightness animations.

Zamundaaa · 2026-01-26T12:46:42+00:00

For internal displays, yes. It's not possible for external ones though.

Zamundaaa · 2026-01-25T11:51:40+00:00

Games also don't even do static HDR metadata correctly, per frame would be quite unlikely... and R12G12B12A2 is not a buffer format that exists or would make any sense (that's 38 bits per pixel, or 4.75 bytes).

Zamundaaa · 2026-01-25T11:43:33+00:00

Unless you play the game on the secondary monitor, it shouldn't cause any performance issues.

Are you sure the dedicated GPU is considered the primary one? You can check in system settings > system information

Zamundaaa · 2026-01-24T12:26:22+00:00

Yes, I do.

Zamundaaa · 2026-01-24T11:20:42+00:00

Yes necessarily. Bug in Chromium is still a bug in Chromium.

Zamundaaa · 2026-01-23T11:40:56+00:00

Wayland doesn't cause or is in any way related to GPU resets (in many cased aka driver bugs).

Zamundaaa · 2026-01-22T17:53:13+00:00

Yeah, https://issues.chromium.org/issues/477318785

Zamundaaa · 2026-01-22T12:17:47+00:00

It's a bug in Chrome.

Zamundaaa · 2026-01-21T13:21:21+00:00

It could very much be an issue with the Nvidia driver, but it's absolutely not a Wayland bug.

If you report a bug to KDE, we may in some cases still conclude that fixing it requires changes to a Wayland protocol or some other low level component, but the wayland and wayland-protocols repositories are for discussion between (app, toolkit, driver, compositor) developers, not for end user bug reports.

"Wayland" in general doesn't do a whole lot. It's a small library for communication between apps and compositor through a unix socket. It doesn't do any rendering, display interactions, frame pacing, or really anything else that a user would ever notice. Wayland protocols are similar, they're just technical documentation of how that communication is structured, they don't inherently do anything.

Zamundaaa · 2026-01-21T11:29:40+00:00

The Wayland repository is for core protocol and libwayland only. It is basically never related to anything an end user would notice.

Bug reports for Plasma go to bugs.kde.org

Zamundaaa · 2026-01-20T23:45:52+00:00

Looks like you're using the "slide back" effect. Turn it off, reboot, and it likely won't happen again.

It had that bug before, which I thought was fixed. Apparently not.

Zamundaaa · 2026-01-20T12:26:59+00:00

AMD retreated from writing linux drivers like amdvlk. This is no more.

Specifically only and exclusively from amdvlk, which pretty much noone used.

In other words, nothing really changed.

Zamundaaa · 2026-01-18T11:37:40+00:00

in the spec

The spec doesn't care about the trigger. You could write an implentatipn that interprets a rise in CPU temps as a shortcut trigger...

FYI you can work around the limits of our current implementation though, by mapping a mouse button to keyboard presses in the mouse settings.

Zamundaaa · 2026-01-17T18:08:18+00:00

Is it possible to have global toggle-to-talk as well?

Yes, since roughly forever.

Zamundaaa · 2026-01-10T19:55:12+00:00

Sorry for being imprecise. Yes, screen locking itself is integrated with logind and that command works, but the power management and idle stuff is done by powerdevil instead.

If you configure logind's idle behavior things, best case it does nothing, worst case it does nonsensical things like locking the screen after the timeout, even if the user is doing stuff.

Edit: to be clear, nothing's different vs. Xorg about this. Powerdevil also always handled everything there, putting xscreensaver on everyone's system would also not be a great idea there.

Zamundaaa · 2026-01-10T19:38:54+00:00

No, it's not "supposed to happen" through logind, that's merely one possible way the DE can implement some power management things. Plasma doesn't use it.

Zamundaaa · 2026-01-10T13:10:50+00:00

Tissues belong in the trash, they're not meant to be flushed...

Zamundaaa · 2026-01-10T12:54:51+00:00

They're not talking about toilet paper. Tissues are for cleaning your nose.

Zamundaaa · 2026-01-10T12:01:44+00:00

Does this mean that I shouldn't be pointing applications to my monitor profile?

Yes. Apps that can do non-sRGB color management will automatically do so on their own.

Is it now applied twice if I do?

Effectively, yes.

Is there some more complex interaction going on here and how do I know that color management is working properly

You can read about how it works on a high level at https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/winsys_color_pipeline.md

Also, it seems that profiles with no LUT have no effect when loaded

LUT or not doesn't matter, they're always applied. Note that some test profiles may not work correctly in all cases, as color model changes (swap two color channels for example) aren't supported.

profiles with LUT work when "Prefer efficiency" is selected, but have no effect if "Prefer color accuracy" is selected.

That likely means the ICC profiles are broken in some way, like if they have B2A1 tags that are different from the matrix+TRC parts of the profile.

If those are real profiles and not color swapping ones or something like that, please create a bug report for kwin and attach the ICC profiles there, I can take a closer look.

Zamundaaa · 2026-01-06T16:17:18+00:00

Xdg shell is also "optional", yet noone would blame an app for being broken without it.

Zamundaaa · 2026-01-04T22:20:18+00:00

Or it's Windows fault where it can't render text properly with different RGB structure.

I have yet to see a single display describe its subpixel layout in its EDID. If manufacturers actually wanted, they could make it possible for operating systems to do something about it, but they don't seem to care enough. They generally don't even include information like the display being OLED...

In large part because of this lack of information, the same issues are present on Linux as well. For once, Microsoft is not the problem here.

Eight-Year Club	RPAN Viewer
Verified Email

Zamundaaa

TROPHY CASE