@Zamundaaa - eviltoast
  • 0 Posts
  • 124 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle


  • 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.









  • 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.









  • Also, your blog is fantastic, I’m always happy when there’s a new post =)

    Thank you, I’m glad you like it!

    I feel like in SDR mode, the OLED is pushing brighter images. I almost feel like it’s underselling the capabilities at 270, but does so to give pixels a rest every now and then, in the hope that the bright spots don’t stay stationary on the screen. It’s a wild guess, I have no idea.

    It’s certainly possible, displays do whacky stuff sometimes. For example, if the maximum brightness in the HDR metadata matches exactly what the display says would be ideal to use, my (LCD!) HDR monitor dims down a lot, making everything far, far less bright than it actually should be.

    KWin has a workaround for that, but it might be that your display does the same thing with the reported average brightness.