Kind of unrelated, why does c sometimes fail to print if it hits a breakpoint right after a print while debugging? Or if it segfaults right after too iirc
Kind of unrelated, why does c sometimes fail to print if it hits a breakpoint right after a print while debugging? Or if it segfaults right after too iirc
They literally said the issue was an unintentional bug and then fixed it. How is that damage control?
Will it not use it even after the ram fills up? I wouldn’t want the compressed part be prioritised anyways
Do you need a swappiness over 1 if you don’t have another swap device?
Isn’t this already a thing on Wayland?
“Can’t live without” is an overstatement, but here are mine:
Kvaesitso, search focused android launcher. I used to really like nova launcher’s local search and navigated my phone mostly using that. But once gensture navigation became a thing I had to stop using nova and replicate the experience in Samsung launcher with various local search apps that were lacking in comparison. Tried to go back a couple times once gestures with 3rd party launchers got better but found my old setup still too ugly and sluggish to go back to. Recently I randomly came across Kvaesitso on fdroid and it was everything I ever wanted out of a launcher.
Amberol music player. Not the ideal music player I’d like but at least it’s not Elisa.
Kid3, audio file tag editor. It has much better workflow/automation than mp3tag that I used in windows, and it seems if you spend some effort on it you could add more automation to make it even better.
Guessing from how this change required 3+ implementations before it became official according to the gitlab page, maybe it’s a chicken and egg situation. Hdr is a lot of work so maybe people don’t want to implement an unfinalized version that might change
Wow the icon saga is finished!?
If anyone wants to throw away a couple hours, there was SO much discussion (and initially drama) over it: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269
4chan, and it’s maxxing. It’s used used for ‘productive’ things incels do (for the improvement of their life) instead of dooming over how they’re incels
Gpu brand shouldn’t be a factor, just buy whatever’s better value.
I’ve used nvidia on Wayland for a year and the issues are greatly exaggerated, and if you have a cpu with an igpu you can plug your monitor(s) into the motherboard to get around wayland-related ones (there’s probably some latency impact for games but I can’t tell).
Currently the problems (that I know of) with nvidia drivers are that colors get muted if you enable hdr, steam’s web interfaces appear corrupted or flicker unless you resize them, there is no memory spillover to ram, and the nvidia ‘x server’ settings app doesn’t support wayland.
And keep in mind that issues tend to get resolved over time. When I first built my PC the nvidia gpu would cause xwayland apps to flicker and didn’t support nigth light or transparent panels in kde. The amd igpu would turn the screen pure white if I changed windowing related kde settings. These don’t happen anymore.
This worked. Apparently I had all the usb devices connected to the same controller and it seems linux initialises them controller by controller. Thanks
I did try messing with the hook order but it’s already as early as it can be.
How would bios change how linux loads usb devices?
It works fine in bios and bootloader. This only happens during boot
Reeder tablet that came as a promotion with something. Could barely keep a single app open, sometimes. At some point low spec just means e waste
I had thought it was about the color profile because with hdr disabled from system settings, enabling the built in color profile desaturates colors quite a bit and does some kind of perceived brightness to luminosity mapping that desaturates bright / dark hdr content even more. Although I don’t think that’s the cause of my problems anymore.
Thanks to your tip about kscreen-doctor, I could try different combinations of hdr / wcg / edid and see how the colors look with different combinations:
I think there must be something wrong with my screen since the hdr reduces saturation more than anything else. Anyways, thanks for the good work
Edit: Tried this with an amd gpu. hdr+wcg works as expected without muted colors. hdr without wcg still significantly desaturates colors, so I guess that’s a monitor bug. Now to figure out gpu passthrough… (Edit 2: It seems to just work??)
Side note, when I turn off hdr only from kscreendoctor the display stays in hdr mode until it turns off and on again, that didn’t happen with nvidia
Edit 3: Found something weirder… Hdr colors are muted on nvidia gpu and seems vibrant with the amd igpu. If I plug the monitor to the motherboard (amd), enable hdr, then unplug and plug it into the nvidia gpu, the colors are still vibrant??? I can disable and enable hdr again and again and they aren’t affected. They’re even fine when hdr is enabled without wcg??? But if I fully turn off the monitor and back on they once again become muted with hdr. Weird ass behavior
You can’t with hdr as I said. Check it yourself if you want
This doesn’t mention the part where if you enable hdr, it sets the color profile to edid without an option to change it, which for my monitor makes everything very desaturated even in comparison to srgb mode (with no color profile)
I don’t know, I just use printf