Zamundaaa

joined 1 year ago
[–] Zamundaaa@discuss.tchncs.de 3 points 11 hours 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 14 points 23 hours ago (3 children)

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

[–] Zamundaaa@discuss.tchncs.de 5 points 1 week ago

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

[–] Zamundaaa@discuss.tchncs.de 10 points 2 weeks 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 1 month 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.

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

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.

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

Then you're using Xorg, not Wayland.

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

What problems do you have with per screen scaling on Wayland?

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

Stop using Xorg and your scaling problems are gone.

[–] Zamundaaa@discuss.tchncs.de 10 points 1 month ago (1 children)

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.

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

This is about dragging a tab out of or into a browser window, and letting the compositor know about it, so it can move and place the window accordingly. Apps don't get to place windows themselves.

view more: next ›