screen color calibration : no start button

[J-Paul BERARD]

I try to calibrate my screen using the utility of gnome-control-center, color section.
I have a Spyder3 Express probe connected by USB and the Calibrate… button become active.
So I click this button and the process begin with a dialog box giving several informations until it ask for the name of the further colour profile.

After that, a small window appears asking to put the probe on this window and to press "Start"… but there is no Start button.

I tried the same on Ubuntu 22.04 (on a VM) : the same window occupied all the screen and we can see a Start button at the bottom right and a Cancel one on the bottom left.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 9 15:58:51 2023
InstallationDate: Installed on 2020-04-10 (1308 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-10-13 (27 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[heynnema (heynnema)]

I just butted up against this same problem!!!

In fact, it may not work correctly in 23.04 and 22.10. I'm going off to test in 22.04.3 now.

[Daniel Tang (daniel-z-tg)]

I attempted to write a hotfix at https://askubuntu.com/a/1504361/1004020 . If it works, I might upstream in the next few days.

[Daniel Tang (daniel-z-tg)]

I sent a MR to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/2311 .

My fix still needs to be tested (I don't have a colorimeter), then backported.

[Daniel Tang (daniel-z-tg)]

Update: The button itself is tested to properly show up now. However, it's whether the whole process works. An `sudo apt install gnome-color-manager` may be able to fix that.

# https://askubuntu.com/questions/1504329/ubuntu-23-10-display-color-calibration-problem#comment2639103_1504361

@DanielT I just retried displaycal, only this time I went all the way to the end... and it failed... and the terse error looked like it was complaining that it couldn't communicate with the color-manager, so I installed gnome-color-manager and then displaycal worked properly when rerun. –
heynnema
32 mins ago

# Updated question https://askubuntu.com/q/1504329/1004020

Update #1 - 2/21/24:

This appears to be a bug that goes all the way back to Ubuntu 22.10. I'm told that it works fine in 22.04, but I haven't verified that yet.

Update #2 - 2/22/24:

After implementing the patch from the answer by Daniel T (thanks BTW), it does now get a "Start" button, but after clicking it, the color patch remains white, and it errors out with "internal error".

See the following information from the terminal, and syslog.

```
al@al-Inspiron-7700-AIO:~/Desktop$ sh askubuntu_color_calibration_fix.sh
09:18:10.5465 cc-color-panel[18961]: WARNING: calibration failed with code 1: Timeout was reached

al@al-Inspiron-7700-AIO:~/Desktop$ cd /var/log
al@al-Inspiron-7700-AIO:/var/log$ tail syslog
2024-02-22T09:18:26.993688-08:00 al-Inspiron-7700-AIO ubuntu-report[3390]: level=error msg="data were not delivered successfully to metrics server, retrying in 120s"
2024-02-22T09:18:35.407512-08:00 al-Inspiron-7700-AIO systemd[3355]: Started app-gnome-org.gnome.Settings-19159.scope - Application launched by gnome-shell.
2024-02-22T09:18:35.707775-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00004
2024-02-22T09:19:21.000134-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Can't update stage views actor <unnamed>[<MetaWindowActorX11>:0x56149c6b1f90] is on because it needs an allocation.
2024-02-22T09:19:21.000796-08:00 al-Inspiron-7700-AIO gnome-shell[3900]: Can't update stage views actor <unnamed>[<MetaSurfaceActorX11>:0x56149e0ec310] is on because it needs an allocation.
```

Post note: I have a Dell AIO with a touch screen.