Open LinuxOnTheDesktop opened 5 years ago
Any news for this issue ? Still present in Linux Mint 20 Cinnamon. I have to activate the icc manually every reboot :(
I am also experiencing this, as reported in the Linux Mint forum here.
Both colord
and csd-color
are running when I start my system but the profile I use is not loaded. Running htop
as soon as I boot and filtering with the keyword 'color' produces:
When I open the app Colour, the only profile available for my monitor is the ICC profile I use in my system. At this point, although the checkbox by the profile is checked, the profile is not loaded. Once I double click on it, the colours of my monitor change, meaning it got finally loaded.
At that point, running htop
again and filtering for 'color' shows a new instance of csd-color
:
This same colour profile ran fine in Linux Mint 18.3 before I upgraded.
Would anyone know here if it is possible to set an ICC profile using the terminal? Because if it is, a temporary fix for this would be to create a little bash script executing that command on startup,
@gilbertohasnofb
I find that on one of my Mint PCs I have the command xiccd
running at startup and that startup command shows with this comment within the Startup Applications program: 'Applies color management profiles to your session'. It seems to work. I do not know - though perhaps I have a note on it somewhere - how I came to have that startup program.
@LinuxOnTheDesktop Thank you so much for your reply. xiccd
wasn't installed by default, and after installing it I was able to get my profile to load on startup by executing xiccd -e
after boot. I'm happy to have my profile on by default now, but Colour now shows two monitors instead of one (I've only got one), and also show a default profile which I am not able to delete:
Ideally, loading profiles by default shouldn't be too much of a hassle so this looks like a bug to me.
Just adding my experience with color profiles, not just a problem when booting. On Linux Mint Cinnamon 20.1.
I found out that (at least) Redshift and NVIDIA X Server Settings programs affect the color profiles.
When Redshift is running, if the user changes/applies a color profile from the Color application, it is applied, BUT Redshift, when it "polls" (5sec?) the color profile completely resets. So in order to truly apply a color profile, Redshift must be first closed completely. After color profile is applied, starting and running Redshift keeps the applied profile. Not a huge problem, but it might be hard to catch why this is happening and then properly apply the color profile.
Next, NVIDIA X Server Settings, it too resets the color profile completely. Opening the GUI or just loading config (Startup Applications), both reset the color profile. This time Redshift actually comes to rescue. If the correct color profile was applied before running Redshift, Redshift always loads the color profile when it does its "polling" (5sec? interval). So, if a user opens Nvidia Setting GUI, the color profile gets reset, but Redshift quickly applies it back. Booting is another problem, user needs to enter a small delay (I used 5 seconds) to NVIDIA X Server Settings in Startup Applications. This way Redshift starts at boot before Nvidia Settings application and applies/keeps the correct color profile after Nvidia Settings application starts at boot.
This is way too convoluted for normal users. I don't know if it's possible at all but it would be great if applied color profiles would not be allowed to reset like these two programs do, or color profile would be somehow always applied back if a change is detected.
Can someone post something useful!
[leigh@mpd ~]$ killall csd-color
[leigh@mpd ~]$ killall csd-color
[leigh@mpd ~]$ killall csd-color
csd-color: no process found
[leigh@mpd ~]$ csd-color -v
** (csd-color:4789): DEBUG: 12:18:20.379: Using logind
(csd-color:4789): GLib-GIO-DEBUG: 12:18:20.380: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(csd-color:4789): dconf-DEBUG: 12:18:20.380: watch_fast: "/org/cinnamon/settings-daemon/plugins/color/" (establishing: 0, active: 0)
(csd-color:4789): dconf-DEBUG: 12:18:20.382: watch_established: "/org/cinnamon/settings-daemon/plugins/color/" (establishing: 1)
** (csd-color:4789): DEBUG: 12:18:20.383: Starting color manager
(csd-color:4789): dconf-DEBUG: 12:18:20.383: watch_fast: "/org/cinnamon/desktop/interface/" (establishing: 0, active: 0)
(csd-color:4789): dconf-DEBUG: 12:18:20.384: watch_established: "/org/cinnamon/desktop/interface/" (establishing: 1)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.418: Initialized GnomeCrtc: 63, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.418: Initialized GnomeCrtc: 64, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.418: Initialized GnomeCrtc: 65, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.418: Initialized GnomeCrtc: 66, at 0, 0, with a scale factor of 2.00 (2 global scale)
** (csd-color:4789): DEBUG: 12:18:20.421: Registered client at path /org/gnome/SessionManager/Client40
** (csd-color:4789): DEBUG: 12:18:20.424: connected to colord
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.427: Initialized GnomeCrtc: 63, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.427: Initialized GnomeCrtc: 64, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.427: Initialized GnomeCrtc: 65, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.427: Initialized GnomeCrtc: 66, at 0, 0, with a scale factor of 2.00 (2 global scale)
(csd-color:4789): CinnamonDesktop-DEBUG: 12:18:20.429: loading: /usr/share/hwdata/pnp.ids
** (csd-color:4789): DEBUG: 12:18:20.429: output xrandr-LG Electronics-LG TV-16843009 added
** (csd-color:4789): DEBUG: 12:18:20.430: failed to enumerate directory /home/leigh/.color/icc: Error opening directory '/home/leigh/.color/icc': No such file or directory
** (csd-color:4789): DEBUG: 12:18:20.430: emit add: /home/leigh/.local/share/icc/edid-6e274120915899cfcc60e74b80946c23.icc
** (csd-color:4789): DEBUG: 12:18:20.430: profile /home/leigh/.local/share/icc/edid-6e274120915899cfcc60e74b80946c23.icc added
** (csd-color:4789): DEBUG: 12:18:20.453: assign for /org/freedesktop/ColorManager/devices/xrandr_LG_Electronics_LG_TV_16843009_leigh_1000 already in progress
** (csd-color:4789): DEBUG: 12:18:20.475: need to assign display device xrandr-LG Electronics-LG TV-16843009
** (csd-color:4789): DEBUG: 12:18:20.475: auto-profile edid /home/leigh/.local/share/icc/edid-6e274120915899cfcc60e74b80946c23.icc exists
** (csd-color:4789): DEBUG: 12:18:20.478: not a GCM profile for xrandr-LG Electronics-LG TV-16843009: /var/lib/colord/icc/edid-6e274120915899cfcc60e74b80946c23.icc
** (csd-color:4789): DEBUG: 12:18:20.478: setting root window ICC profile atom from /var/lib/colord/icc/edid-6e274120915899cfcc60e74b80946c23.icc
** (csd-color:4789): DEBUG: 12:18:20.567: falling back to dummy ramp
@leigh123linux: what are you deeming useful? Output of the sort that you yourself posted? Presuming 'yes': please specify exactly what you want.
EDITED for English, clarity and tone.
Color profiles just straight up doesn't work here. Like there is ZERO change when jumping between profiles. Broken for years at this point, i wonder why they just don't remove it.
Mint's current focus upon appearances might usefully extend to fixing this bug.
Can also report the same problem on multiple machines here.
I have this issue on an intel gaming laptop with an nvidia card, and an amd workstation with an nvidia card. Thinking back, I've never managed to get colour management to work correctly in the ~8 years I've been using mint.
For me, only applying the "Test profile: Blue" (bluish.icc) to my displays has any effect. All other profiles are ignored in the "Colour" management panel. Can anyone suggest why bluish.icc works, while nothing else does?
Would love to see a solution.
Comparing icc profiles with gnome-color-manager, I see that bluish.icc has a VCGT tab, while my monitor profile does not. Looking through the other default profiles, D50, D55, and D65 (Gamma5000K.icc etc) all have this tab and work. Maybe it's possible to convert a profile to apply the TRC curves to VCGT curves?
Bug still present on Mint 22.
Bug still present on Mint 22.
that's exactly .. tried to remove QRedshift, it seems to ok
Issue
One can add colour profiles using Settings -> Colour (although it is easy to end up adding the wrong one - the UI is counter-intuitive). However, no added profile is applied on reboot. The following sources say that profiles are not applied automatically and they sketch the hackery one needs to get the profile working:
Steps to reproduce
Manage to apply a colour profile, in any which way. Observe that the profile is not applied on boot.
Expected behaviour
The profile should be applied on boot.
EDITED to remove a heading that had nothing under it.