![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.kde.social/pictrs/image/19e6d51f-5131-409e-8990-827d3d29e4d3.png)
The virtual keyboard is hidden by default, unless you’re using touch. You can change that by setting the KWIN_IM_SHOW_ALWAYS=1
environment variable, until there’s a proper setting for it
The virtual keyboard is hidden by default, unless you’re using touch. You can change that by setting the KWIN_IM_SHOW_ALWAYS=1
environment variable, until there’s a proper setting for it
It hasn’t operated at a loss anymore for years you mean?
What kind of flickering? Does the display support adaptive sync? If so, try turning that off
I wouldn’t read that much into it. Valve isn’t Nintendo, I doubt they’d launch a new Deck without OLED
That is not NATO starting any war, anyone wirh the reading comprehension of a six year old understands that. Don’t fall for Russian propaganda, FFS.
Quite the opposite, bigger grids are much more stable. When faults happen, tiny subsets of the grid get disconnected from the rest, it does not take the whole thing down at all…
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.
I understand that it’s an absolute brightness standard, not like the relative levels in SDR
The standard is also relative brightness actually, though displays (luckily) don’t implement it that way.
why does it end up washing out colors unless I amplify them in kwin? Is just the brightness absolute in nits, but not the color?
It depends. You might
Why does my screen block the brightness control in HDR mode but not contrast?
Because displays are stupid, don’t assume there’s always a logical reason behind what display manufacturers do. Mine only blocks the brightness setting through DDC/CI, but not through the monitor OSD…
Why is my average emission capped at 270nits, that seems ridiculously low even for normal SDR screens as comparison
OLED simply gets very hot when you make it bright over the whole area, the display technology is inherently limited when it comes to high brightness on big displays
That’s just a law of computers, the default arrangement of monitors must always be wrong.
You can just sync your Plasma settings to SDDM though, and it’ll use the same output settings as your session
Fedora just has
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.packagekit.package-install" ||
action.id == "org.freedesktop.packagekit.package-remove") &&
subject.active == true && subject.local == true &&
subject.isInGroup("wheel")) {
return polkit.Result.YES;
}
});
in /usr/share/polkit-1/rules.d/org.freedesktop.packagekit.rules
. If you put the same file in there, it should work.
Yes, and many distros have a polkit rule set up to allow installing or updating without a password. You can likely just copy it from Fedora or sth
Writing graphics code in a unified model is quite a bit different from the conventional x86 model.
It isn’t. The difference is pretty small, and it’s just optimizations for when copies can be skipped and not a radical change in the approach of how rendering is done.
Intel would need their own equivalent to Metal if they wanted to do a similar move.
Not at all. If big-ish changes were required, they could be exposed as Vulkan extensions.
I don’t know enough about Vulkan to say if it’s compatible with this kind of approach
Of course Vulkan, the graphics API used on all modern phones except Apple’s, supports using integrated graphics efficiently.
Just use Wayland, then you don’t have to care about this
Setting the speed to the max does turn them off
The only effects relevant for performance are blur and background contrast. Turn those off if you feel the system is slow, maybe increase the animation speed and you’re done
You can probably implement it in the script itself, but there’s no external functionality to do it
Almost every output setting “may seriously break things” in my experience. Display drivers are sadly quite fragile
Changing the output config file should work, as long as KWin isn’t running while you make the change (in which case the change will just be overridden)
Edit: Also, please make a bug report about this for KWin. It’s probably not a KWin issue, but we can usually figure out where it’s coming from
Many monitors allow you to turn off HDR, they just claim they don’t support it to the computer when you do that
No, only when you click on an input field and have it enabled in the system tray