• 0 Posts
  • 178 Comments
Joined 1 year ago
cake
Cake day: August 7th, 2023

help-circle

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


  • that has nothing to do with metric vs imperial:

    “Lumber manufacturers typically cut a tree into the various standard types of dimensional lumber very shortly after the tree is felled. At this point, the 2 x 4 is actually 2 inches x 4 inches, a 2 x 10 is actually 2 inches x 10 inches, etc. But then the newly-sawn (but soaking wet) lumber is then kiln-dried until it reaches the desired moisture level. During this process, it shrinks as the moisture in the wood is removed and the wood cells shrink. Once the drying is complete, the boards are then planed to a standard size. Hence, what started out as a 2 x 4 now measures 1 1/2 inches x 3 1/2 inches.”

    https://www.thesprucecrafts.com/why-isnt-a-2x4-a-2x4-3970461










  • sodium. gravity. carbon capacitors. lead acid. molten salt. air pressure. flywheel.

    there’s alllll kinds of battery storage solutions, and for grid storage just about anything other than lithium can be used because lithium is really only useful for power density applications where weight and size of the battery matters like cars and planes.

    nuclear fission is dead. fusion is the only nuclear worth talking about and that’s still years, probably decades away from being actually useful.

    so then: solar, wind, wave, hydro, geothermal, and all kinds of batteries is what we have now and can do cheaply and do everywhere and do it now.



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