Zamundaaa

joined 2 years ago
[–] Zamundaaa@discuss.tchncs.de 1 points 2 months ago

It's in the display settings

[–] Zamundaaa@discuss.tchncs.de 1 points 2 months ago (2 children)

If you're on Plasma, setting the color profile to "built-in" might be all you need to make them reasonably match

[–] Zamundaaa@discuss.tchncs.de 5 points 2 months ago (4 children)

No, colord does not handle color profiles on Wayland. You need to set the profile in the display settings.

If you have an ICC profile that doesn't work, please make a bug report about it for KWin.

[–] Zamundaaa@discuss.tchncs.de 4 points 2 months ago (10 children)

This protocol isn't relevant for your compositor to apply an ICC profile. If you're using KDE Plasma, you can just select it in the settings. I think Sway allows that now too. If you're on Gnome, you'll need to wait.

[–] Zamundaaa@discuss.tchncs.de 7 points 2 months ago (1 children)

You don't need a protocol for profiling, it's merely a nicer user experience if you have one.

[–] Zamundaaa@discuss.tchncs.de 2 points 2 months ago (1 children)

Chromium had it for qhite a while, but it isn't really relevant... Discord's implementation of screen sharing was custom on X11, if they had used the one that comes with Electron, this would've worked far earlier.

operating systems may not have implemented it umtil more recently

DEs that had a Wayland session (aka Gnome and Plasma) supported it very soon after the portal was made.

The real reason won't be anything external, but something in the company. Usually it's just that Linux isn't a priority for a given company, so even if there's a motivated engineer that wants to take care of it, it's hard justifying to their managers why they need to spend a lot of time on it.

This isn't exclusive to Discord, to use a very similar example, Zoom is kinda worse. In the past, Zoom misused a Gnome screenshot API to do screen casting very badly, and recently they ported to the desktop portal - not because they had a choice, but because Gnome locked down the API they were using. Screen casting still only works on Gnome though, because they still check for the desktop name. If you set it to Gnome, it works perfectly fine everywhere else too!

All it would take to fix that problem is removing an if statement, yet, despite many complaints, it hasn't happened... because no big customer has complained, so it's just one of the unimportant Linux bugs.

[–] Zamundaaa@discuss.tchncs.de 2 points 2 months ago (3 children)

The screen casting portal is 6 years old. 6 years is not recent...

[–] Zamundaaa@discuss.tchncs.de 4 points 2 months ago

Yes. The Mesa implementation for this stuff isn't merged yet. Once it is merged, the layer will be irrelevant.

[–] Zamundaaa@discuss.tchncs.de 16 points 2 months ago (4 children)

Well, HDR works in Wine Wayland, and X11 can never do it without gamescope.

[–] Zamundaaa@discuss.tchncs.de 5 points 3 months ago

Yes, they do. They're just better at pretending they don't.

[–] Zamundaaa@discuss.tchncs.de 10 points 3 months ago (9 children)

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

[–] Zamundaaa@discuss.tchncs.de 4 points 3 months ago (1 children)

The real one? It was fine on Xorg though

When an app (in your case, Steam) uses X11 APIs to move the cursor, that of course works on Xorg, but Xwayland merely emulates it - so it moves the X11 pointer for X11 apps, but not the pointer from the Wayland compositor.

Some compositors allow Xwayland to request moving the real pointer instead of doing emulation, but River apparently doesn't.

view more: ‹ prev next ›