DisplayCAL: vanhemmat versiot ja versiohistoria

A quick follow-up to 3.9.18, this release adds Linux AppImage/Flatpak packages and fixes 20 issues, mostly stability and crash fixes surfaced by users right after the last release, plus several latent Python 3 bytes/str bugs found during a code audit.
Warning
In MacOS, after installing DisplayCAL you need to run the following in Terminal:
xattr -dr com.apple.quarantine /Applications/DisplayCAL
✨ Highlights
- AppImage and Flatpak packages are now built and published alongside the existing DEB/RPM installers. (#232 by @eoyilmaz)
🚀 Improvements
- DEB/RPM postinstall now prints progress instead of running silently, installs prebuilt wxPython wheels from the wxPython extras index, and pulls in the dbus-python build dependencies, fixing installation on Ubuntu 24.04/26.04. (#805 by @eoyilmaz)
🐛 Bug Fixes
🧩 General
- Fixed displaycal.ini becoming mangled and ballooning to gigabytes in size, eventually crashing the app from memory exhaustion. Config writes are now atomic and lock-protected, oversized config files are quarantined instead of parsed, and the config is explicitly read as UTF-8 so mismatched locale codepages can no longer corrupt it further. (#828, #828 by @eoyilmaz)
- Fixed several pip-installed console scripts (displaycal-vrml-to-x3d-converter, displaycal-scripting-client, displaycal-eecolor-to-madvr-converter and their console variants) crashing with AttributeError because their entry-point functions didn't exist. (#797 by @eoyilmaz)
- Fixed invalid filename characters from surviving into color profile names. (#819 by @eoyilmaz)
- Fixed unsupported format string passed to tuple.__format__ error when generating a cube 3D LUT. (#827 by @eoyilmaz)
- Fixed a TypeError crash and incorrect CTI3 file-type comparisons in measurement/profile handling caused by leftover Python 2-to-3 bytes/str bugs. (#811 by @eoyilmaz)
- Fixed the profile.unsupported dialog showing a raw bytes value (e.g. b'mntr') instead of the decoded text, across 12 sites. (#815 by @eoyilmaz)
- Fixed three latent bytes/str Python 3 port bugs in load_cal_handler/import_session_archive_producer. (#817 by @eoyilmaz)
- Fixed four more bytes/str bugs that made load_cal_handler's 3D LUT/profile B2A metadata-restore block unreachable dead code. (#820 by @eoyilmaz)
- Fixed a TypeError from str regex patterns matched against bytes content in the ReShade/MasterEffect 3D LUT install patchers. (#808 by @eoyilmaz)
- Fixed an Event is undefined error when the number of worker threads is 1. (#799 by @lexxxel)
🍎 macOS
- Fixed a crash when the first measurement taken after launch is a Measurement Report or Colorimeter Correction. (#822 by @ethanbrookins)
- Fixed an infinite black-screen ping-pong across multiple displays during VideoLUT recovery, by reloading the clobbered LUTs via CoreGraphics from a single persistent process instead of spawning dispwin. (#824 by @eoyilmaz)
🪟 Windows
- Fixed DisplayCAL.mscms.manager's logger writing to sys.stderr, which made the frozen windowed .exe falsely show an "Errors in..." dialog on every close even though nothing had actually failed. (#804 by @eoyilmaz)
🙏 Thanks
Thanks to everyone who contributed to this release, including @lexxxel for their first contribution, and @ethanbrookins.
Full Changelog: https://github.com/eoyilmaz/displaycal-py3/compare/3.9.18...3.9.19

It's been almost 10 months since 3.9.17, and this release reflects that: 72 merged pull requests and 524 commits worth of work, adding support for a new colorimeter, ArgyllCMS 3.5.0 compatibility, and a large batch of accumulated stability and accuracy fixes across Windows, macOS, and Linux.
Warning
In MacOS, after installing DisplayCAL you need to run the following in Terminal:
xattr -dr com.apple.quarantine /Applications/DisplayCAL
✨ Highlights
- New instrument support: Datacolor Spyder2024 (SpyderX2). (#620 by @g4bri3lDev)
- ArgyllCMS 3.5.0 support, including the new spectral plot (specplot) option. (#645 by @jaminmc)
- The simplified splash screen (previously macOS-only) is now available on all platforms, fully translated. (#787 by @ethanbrookins, #791 by @eoyilmaz)
- Windows ARM64 builds (#741, #747 by @eoyilmaz) and Linux DEB/RPM installer packages (#739 by @eoyilmaz) are now available.
🚀 Improvements
- Improved Web @ localhost remote calibration: fixed freezing/retry issues, corrected color accuracy shown in the browser, and improved handling when multiple devices are connected. (#647 by @jaminmc)
- Automatic retry when a spectrophotometer's ambient light diffuser interrupts a measurement. (#733 by @eoyilmaz)
- Added a warning in the measurement report when the display's actual white point drifts noticeably from the profile's target. (#761 by @eoyilmaz)
- You can now sort the colorimeter corrections table by clicking its column headers. (#752 by @eoyilmaz)
- Sped up 3D LUT (B2A) table generation. (#781 by @eoyilmaz)
- Your saved "2012" observer settings are now migrated automatically to the "2015" naming used by ArgyllCMS 3.4+, no action needed. (#760 by @eoyilmaz)
- ArgyllCMS downloads and version checks now use a new, more reliable GitHub-hosted source. (#750 by @eoyilmaz)
🐛 Bug Fixes
🧩 General
- Fixed profiles sometimes crushing near-black shadow detail together. (#724 by @eoyilmaz)
- Fixed a startup crash some users hit right after launching the app. (#726 by @eoyilmaz)
- Fixed a spurious warning and a crash in the 3D VRML view/export. (#725, #783 by @eoyilmaz)
- Fixed profile creation failing on machines with more than 60 CPU cores/threads. (#717 by @eoyilmaz)
- Fixed corruption and an overly strict white point check that could affect XYZ LUT-based profiles. (#721 by @Youfffeng)
- Fixed duplicate "please calibrate your instrument" prompts. (#765 by @eoyilmaz)
- Fixed the app losing track of colorimeter correction measurement progress after a crash. (#767 by @eoyilmaz)
- Fixed saving the log file so it no longer gets corrupted. (#744 by @eoyilmaz)
- Fixed an error that could occur when applying calibration/profile associations. (#754 by @eoyilmaz)
- Fixed a crash when a profile's filename included the %crc32 placeholder. (#777 by @eoyilmaz)
- Fixed uploading/checking colorimeter corrections online. (#789 by @eoyilmaz)
- Fixed 3D LUT settings being unexpectedly reset when creating a new profile. (#655 by @Adam-Color)
- Fixed profiles not reloading correctly after changing certain settings. (#678 by @jaminmc)
- Fixed the testchart editor grid on newer Python versions (3.10+). (#677 by @jaminmc)
- Removed excessive debug output that could slow things down. (#699 by @Adam-Color)
🪟 Windows
- Fixed build/compatibility issues on Python 3.13+, including Windows color management integration. (#646 by @jaminmc)
- Fixed the ARM64 installer refusing to install on ARM64 systems. (#747, #748 by @eoyilmaz)
- Fixed the monitor name showing as a generic "Plug and Play" device instead of its real model name. (#740 by @eoyilmaz)
- Fixed the on-screen color patch being positioned incorrectly at display scaling above 100%. (#743 by @eoyilmaz)
- Fixed gamut coverage not being displayed, caused by a file path bug. (#746 by @eoyilmaz)
- Fixed oversized "fancy" text rendering at certain scaling levels. (#755 by @DamoyY)
- Fixed a Profile Loader crash when monitors are reconnected or rearranged. (#763 by @eoyilmaz)
- HDR calibration prof

Warning
In MacOS, after installing DisplayCAL you need to run the following in Terminal:
xattr -dr com.apple.quarantine /Applications/DisplayCAL.app
Release Notes
- [ALL] Added support for ArgyllCMS 3.4.0+ in regards of the update on the observer names of CIE 2012 2° and CIE 2012 10° being CIE 2015 2° and CIE 2015 10°. Depending on the ArgyllCMS version the old names are still going to be accessible through the UI.
- [ALL] Fixed an issue related to the black point correction being applied even if it is disabled introduced in DisplayCAL 3.9.15.
- [ALL] Fixed dispread arguments not being added to argument list by @Anulap
- [ALL] Fixed unnecessary argument quoting in DisplayCAL.wexpect.spawn_windows.__init__() by @eoyilmaz
- [ALL] Fixed IndexError in a string formatting in DisplayCAL.worker by @vastunghia
- [Windows] Fixed the issues related with displays with scaling value more than 150%, where DisplayCAL errors out on startup by @eoyilmaz
- [Windows] Fixed Profile Loader "Identify Monitor" and "Exceptions" dialog crash by @Anulap
- [Windows] Fexed output level reporting for and some other issues related to madVR by @eoyilmaz
What's Changed
- 556 update osx install instructions by @eoyilmaz in https://github.com/eoyilmaz/displaycal-py3/pull/558
- 553 anybutton error by @eoyilmaz in https://github.com/eoyilmaz/displaycal-py3/pull/559
- Windows specific fixes for various feature by @Anulap in https://github.com/eoyilmaz/displaycal-py3/pull/579
- 580 a bytes like object is required not int when trying to verify with colormunki by @eoyilmaz in https://github.com/eoyilmaz/displaycal-py3/pull/582
- Fix issue #577 by @vastunghia in https://github.com/eoyilmaz/displaycal-py3/pull/589
- 585 displaycal can not start after first install by @eoyilmaz in https://github.com/eoyilmaz/displaycal-py3/pull/598
- [#583] Added support for the new names given for the CIE 2012 2° and … by @eoyilmaz in https://github.com/eoyilmaz/displaycal-py3/pull/599
- [#570] Fix for #570. Removed the skipping of the -b parameter in `D… by @eoyilmaz in https://github.com/eoyilmaz/displaycal-py3/pull/600
New Contributors
- @Anulap made their first contribution in https://github.com/eoyilmaz/displaycal-py3/pull/579
- @vastunghia made their first contribution in https://github.com/eoyilmaz/displaycal-py3/pull/589
Full Changelog: https://github.com/eoyilmaz/displaycal-py3/compare/3.9.16...3.9.17