bret is nyt’s go-to cryptofascist. he’s always got these bootlicking propaganda pieces.

tried again, and yeah display settings was where i first tried, and no, ‘none’, ‘icc’ with multiple diff profiles, and ‘built-in’ all change absolutely nothing but the keep changes popup shows up like it worked fine; no errors or anything. then i went into trying with colord and colormgr cli commands like i said before. it does see my monitor under display and resolution and whatnot are correct and do change, just not the color profile.

everything works as it should under x11 session.

regardless, the whole point of my og comment was color management protocol isn’t only hdr stuff. even in the significant issues page for kde it says color management and HDR protocol in the bullet point about programs that need accurate color profiling.

it seems pretty obvious to me on word meanings alone that ‘color management protocol’ isn’t only for relatively new hdr tech, but instead everything to do with color management, like how color profiles are under ‘color management’ in the system settings you’re telling me to use that the wiki says isn’t ready yet…

from https://wiki.archlinux.org/title/ICC_profiles

"Wayland

Wayland supports color management through color profiles, but the user interface for managing these profiles is currently not implemented properly. However, you can manually add a color profile through the following steps: Firstly, copy your .icc color profile file to the /usr/share/color/icc/colord/ directory. Run colormgr get-profiles to obtain the available color profiles, and colormgr get-devices to obtain the IDs of the attached devices. To assign a color profile to a device, use the command colormgr device-add-profile Device_ID Profile_ID. The device ID is obtained from the output of colormgr get-devices and the profile ID from colormgr get-profiles. For example, if your device ID is “DP-3” and the profile ID is “icc-5fb87663ba378cadf463ba64d92dced3”, the command would look like: $ colormgr device-add-profile DP-3 icc-5fb87663ba378cadf463ba64d92dced3 With these steps, you can manually manage your color profiles in Wayland until the user interface is fully implemented. Once the ICC profile is added with this method, it will show up and work as expected in system settings like Color Manager in the KDE Plasma settings. "

copy to colord folder, eh?

the part i have trouble with is colormgr shows no devices and nothing happens trying commands to load an icc profile. it’s no big deal, i’ll just use x11 until this gets fixed but others on arch forums and reddit threads has this same issue with kde wayland, and judging by the ‘user interface isn’t ready yet’ i’m guessing it’s just not ready yet.

but sure, colord has nothing to do with it and color management protocol is ONLY for hdr tech.

am i taking crazy pills?

i’m using kde on endeavouros. when using wayland the color profiles section in settings does nothing. you can go pick a profile and click ok but it just doesn’t load it. colord is the daemon that handles color profiles entirely and that’s what this is about.

not just hdr stuff, it’s all color profiling. my old monitor is dark af with wayland because it’s not loading its color profile and i can’t adjust gamma or apply color profiles in settings or with colord like you can in x. i really need this to be able to switch to wayland.

deleted by creator

deleted by creator

don’t know why you’d want to? you may trust your dns server but without dns over https the dns requests themselves are sent plaintext and are vulnerable to man-in-the-middle attack. with dns over https the dns requests are encrypted and that encryption would have to be broken for a MITM attacker to see your requests. more security is better and dns over https costs virtually nothing to use in terms of cpu resources.

edit: oh do you mean whole system mullvad VPN? if so, then yeah dns over https doesn’t really help much but it’s also still a case of why bother turning it off when there’s no benefit to it.

linux typically won’t hard freeze on errors like that no matter the distro. it can, but rarely. being an all amd build i suspect there’s some cpu bios feature auto scaling core clock or voltage and in my experience ryzen cpus need to have a manually set stable clock and voltage to perform properly no matter the os. try checking your bios and disabling any powersaving or auto-scaling features for your cpu and manually set it for stock clock and voltage. you may need to look up what these values are as the bios might not have a default value for you. this might not be your issue but it’s worth trying. good luck!

seems similar to the set up for systemd snippets, where you can avoid changing default config files for systemd units and instead use a drop in file in that created .d dir to load and overwrite the defaults on boot for whatever specific thing. don’t know anything that uses this for bashrc, tho. most likely harmless, especially if there’s no created bashrc.d yet.

this may help, if you’re using apparmour.

https://serverfault.com/questions/667426/pass-an-usb-hub-from-a-kvm-host-to-a-guest-with-libvirt

cinnamon, lxde, kde, and mate are all desktop environments that mimic the basics of windows ui like the taskbar, start menu, and windows with minimize, maximize, and exit buttons at the top. and all can be installed/selected during install on pretty much every popular distro. there’s prolly some others i’ve forgotten but those are all solid choices.

edit: whoops had mint listed but that’s not a de that’s a distro

sounds like maaaaybe too little ram and no swap? what is your ram size and do you have any swap or zram enabled? i kinda doubt it because multiple distros should have a swap space or zram on by default on a fresh install but maybe not or you explicitly chose not to and it’s running out of memory.

fighting for bitcoin to get an emoji is stupid, but fighting against it might be even stupider. surely there are more important things to spend your time and energy on. it’s a fucking emoji. who cares?

yup, and both bluesky and threads will be/are exactly as bad, too.

fuckin yikes

uh, the drama being what it is about people in positions of power blocking efforts to make a welcoming and diverse nixos community, persisting right wing concern trolling, and especially what appears to be maybe a military tech company takeover of nixos, it’s hella understandable people would want to reconsider using this tech on their own hardware and it’s pretty sus to respond to this with ‘ah just drama it’ll blow over’…

shit box or luxury car, this article is not talking about motor controller or battery controller software.

battery controllers and motor controllers are available as cheap, simple, stable, off-the-shelf dedicated hardware and there’s no reason budget evs would need to do any coding for them, maybe just some variable adjustment. those things are not controlled by the user facing software being talked about here.

bonkers this shit has 10 upvotes lmao