| Summary: | Monitor profile not settable when using appimage | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | bugs |
| Component: | ColorManagement-Profiles | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | metzpinguin, salsergey |
| Priority: | NOR | ||
| Version First Reported In: | 8.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.9.0 | |
| Sentry Crash Report: | |||
|
Description
bugs
2025-09-15 21:43:53 UTC
This isn't a bug. If the monitor color profile box is grayed out, digiKam has automatically detected your (system) color profile. What text is in the grayed-out box? Maik One more explanation: your Snap package from (K)Ubuntu uses a sandbox, and digiKam was unable to recognize your system-wide color profile. Now, with the AppImage, this is possible. So, if you previously configured a different color profile in digiKam than your system color profile, the result was incorrect. You need to change your system-wide color profile to the one you want. You can check which system color profile is being used using the tool button next to the grayed-out box. digiKam cannot change or remove installed system monitor profiles. Maik (In reply to Maik Qualmann from comment #2) > One more explanation: your Snap package from (K)Ubuntu uses a sandbox, and > digiKam was unable to recognize your system-wide color profile. Now, with > the AppImage, this is possible. So, if you previously configured a different > color profile in digiKam than your system color profile, the result was > incorrect. You need to change your system-wide color profile to the one you > want. You can check which system color profile is being used using the tool > button next to the grayed-out box. > > digiKam cannot change or remove installed system monitor profiles. > > Maik The greyed out box says "Monitor Profile From System Settings". In the details that come up when I press the I button, I see some odd behaviour. At first it showed the correct profile, but when I changed the system profile for the monitor I'm using Digikam to a test profile which swaps red and green, Digikam instead picked up the profile for my second screen. Using Gwenview on this system, it seems to be picking up the profile for my main monitor, even when I move the screen to my second monitor. Are you using X11 or Wayland? Maik (In reply to Maik Qualmann from comment #4) > Are you using X11 or Wayland? > > Maik X11. I've rebooted and the appimage is still seeing the profile for my second monitor. The primary monitor is set as such as well. I've now also tried on a different system (Fedora 42, Wayland). That has a profile set in the system and Digikam does show the monitor selection box. For Wayland, we don't yet have native detection for the system color profiles. In digiKam-8.8.0, we added a query to colord via DBus. What surprises me is that the wrong screen is recognized. Are you starting digiKam from a different screen than the one on which digiKam will later run? Maik I've tried launching from either window. It doesn't seem to make any difference what profile is picked. Today, it's getting the profile for my main monitor. I tried swapping the profile for a red/green swap profile, but restarting Digikam is still giving me the original profile. Would it be possible to have the selector default to selecting the system profile, but to allow an override? Would it also be possible to set a different profile for each screen? I have an SRGB office monitor and a wide gamut graphic monitor and they both require very different profiles. *** Bug 511092 has been marked as a duplicate of this bug. *** Fixed with Bug 511092 Maik |