Zamundaaa @ Zamundaaa @discuss.tchncs.de

Posts

0

Comments

158

Joined

2 yr. ago

Ah, you're on Xorg. This feature is only available in the Wayland session

Go into system settings > mouse > select your mouse > rebind buttons

NVidia still hasn't implemented support for adaptive sync with multiple monitors in their driver. If you can connect the second screen to the integrated GPU, that would work though

Please make a bug report to KWin about that issue then, and attach one of the ICC profiles you tried to the bug report. Maybe something's wrong in KWin's profile parsing and it gets silently ignored.

regardless, the whole point of my og comment was color management protocol isn't only hdr stuff

Yes, nothing wrong with that.

like how color profiles are under 'color management' in the system settings you're telling me to use

No, I'm telling you to use the display settings. The color management page is hidden on Wayland starting with Plasma 6.3, because it's misleading and confusing.

the wiki says

The wiki is very outdated, it's about Plasma 5.

It's in the display settings

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

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.

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.

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

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.

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

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

The real question is though... if you haven't noticed the TV using YCbCr420 until it was pointed out to you, why would you spend more time looking into it?

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

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

Some day it will make it's way to banking apps/sites being unusable on OSes other than approved "secure" ones.

That day was years ago. Many banking apps refuse to start if you even just have your bootloader unlocked, and some banking websites only support Chrome, some really crappy ones even only Chrome or Edge on Windows specifically.

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.

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.

That's because Windows has a system provided toolkit that most apps use