Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)Z
Posts
0
Comments
153
Joined
3 yr. ago

  • ICC profile is built-in in memory of my laptop screen?

    Yeah. Surprisingly, nearly every display comes with somewhat accurate color information in its EDID.

    Even Windows can't do it

    Afaik they did actually implement something in this direction in Windows 11, but it's not exposed in a user friendly way yet.

    There is no saturation slider, though. I've seen it on some screenshots.

    It's currently always shown if the built in color profile, HDR or an ICC profile is used. IIRC it wasn't visible with the color profile in some older version of Plasma though, maybe that's why you don't see it.

  • Afaik Youtube is doing that, not Pulseaudio, and there's nothing that can be done about it.

  • what about color managed apps?

    Colord isn't running and no icc profile is set on Xwayland, so they should assume sRGB as the target and be fine.

    Do note that nothing is applied "to the full screen", color management is done on each individual surface during compositing. If an app uses the color management protocol to use some colorspace, it gets taken into account.

  • Are you sure you can affect saturation system-wide with color profiles?

    Yes, I wrote the relevant code in KWin.

    Because in Gnome it's not possible.

    That's because Gnome's color management support is still limited, they don't apply the full ICC profile yet.

  • Sounds like you want color management, not just arbitrary saturation changes.

    Install KDE Plasma, select the "built-in" color profile, and you're done, no more oversaturated colors. If you want to test how it looks, just use a live boot.

  • Why would you run it in Proton? It's a native game.

  • Wayland as a protocol was designed around CSDs, protocols for SSDs came years later

    That's not an argument for anything. The core protocol isn't useful on its own, you always need extensions that came later to even create a window. As another example, Wayland as a protocol was designed around shared memory buffers, protocols for hardware acceleration came later. Doesn't mean you're supposed to leave that out.

    Modern apps tend to prefer CSDs anyway since it provides more flexibility, very common on MacOS and Windows

    That too is not an argument for not implementing what a ton of apps need.

    MacOS and Windows don't do the same sort of CSD as Gnome FYI, it's more of a hybrid approach, where parts of the decoration are rendered by the system and parts by the app.

    It's difficult to coordinate things between the client and compositor.

    That too isn't relevant, libdecor doesn't coordinate shit either. And if you want to (which is being looked into), you can absolutely sync things with SSD too.

    The actual and only reason Gnome doesn't support SSD is that they think CSD is a "better architecture".

  • Ddc/ci brightness changes are very often animated by the display firmware, so doing it fast is rarely possible.

    You can however disable ddc/ci in the display settings if you'd rather have software brightness.

  • Afaik you very much can not turn it off

  • I get way more spam on WhatsApp than on Matrix. Never been invited to a fake group chat on Matrix at least...

  • Quite good I'd say. I don't have other high end laptops for comparison though

  • Is the framework 13 really worth my money for the repairability and upgradability in comparison?

    Depends on what you upgrade for, and what you need in the first place.

    If you upgrade mainly for more CPU and GPU power, in my opinion that's a hard sell. The new mainboards from Framework are hella expensive!

    If you need a dGPU in a small form factor laptop, Framework just doesn't offer that. Same for touch or built-in tablet support.

    If you're ok with the built-in GPU and upgrade for better display, for better battery, and a better but perhaps not the absolute latest and best APU, yes, it's worth it.

    When I bought the FW13, a year later or so they brought out a new 120Hz higher resolution display. The first display being 60Hz was my only big annoyance with it, having a 120Hz monitor for comparison... So I just bought the new display, and swapping it only took literal 5 minutes.

    Similar story with the hinges, I wanted ones with more resistance, so I just bought stronger ones for 25€ and easily replaced them.

    If the battery gets worse, or they bring out a new one with decently improved capacity, I can similarly replace it in 5 minutes.

    No glue, no 10 types of special screws, just the screw driver that was shipped with the laptop, and basically zero risk of breaking anything when making modifications.

    You'll have to know yourself if these tradeoffs are worth it to you... but after my old HP Envy's display broke and even finding the correct replacement part was a challenge, let alone replacing it, I'm quite happy with the FW13.

  • Then when a game is started it starts another Gamescope session which launches the game in a second XWayland session.

    No, it doesn't start another gamescope. It starts a second Xwayland in the same gamescope instance.

  • This is still WIP, but will definitely get an option before it's enabled by default. I too much prefer apps just following my configured placement policy.

  • It's an issue from a change made a year ago, which you were just unlucky to hit (and indeed mostly hits Arch, because of live updates).

    It's been fixed in 6.4.1, won't happen again.

  • The screen brightness adapts automatically to the windows i focus on, which is a good idea.

    That's definitely not something Plasma is doing... Sounds like your monitor is dumb with "adaptive contrast" or just terribly implemented local dimming.

  • The screencast portal has been around for 7 years. How is it not enough? It is very much GPU-only (if the receiving program supports it, which nearly all do), and encoding the image is up to the app and does not depend on the API.

  • It was just moved into a separate repository, nothing's changed about it

  • No, nothing has been changed. You can opt in to default to copy because a lot of users asked for it. The default behavior is the exact same it's been ~forever.