libcolord-gtk:ERROR:cd-self-test.c:45:cd_window_get_profile_cb: assertion failed (error == NULL): failed to connect to colord: Could not connect: No such file or directory (cd_window_error, 0)
FAIL cd-self-test (exit status: 134)
But of course, there's no system bus inside the chroot and colord lives on the system bus.
I think this could in theory be an autopkgtest. If you compile just the test:
$ gcc $(pkg-config --cflags colord-gtk) -DCD_COMPILATION cd-self-test.c $(pkg-config --libs colord-gtk) -o cd-self-test
$ dbus-run-session -- xvfb-run -a ./cd-self-test
[...]
ERROR:cd-self-test.c:45:cd_window_get_profile_cb: assertion failed (error == NULL): no device with that property: property match 'XRANDR_name'='screen' does not exist (cd_window_error, 0)
it doesn't quite work, but nearly. Maybe upstream would have an idea here.
It does help. It changes the error message to:
libcolord- gtk:ERROR: cd-self- test.c: 45:cd_window_ get_profile_ cb: assertion failed (error == NULL): failed to connect to colord: Could not connect: No such file or directory (cd_window_error, 0)
FAIL cd-self-test (exit status: 134)
But of course, there's no system bus inside the chroot and colord lives on the system bus.
I think this could in theory be an autopkgtest. If you compile just the test:
$ gcc $(pkg-config --cflags colord-gtk) -DCD_COMPILATION cd-self-test.c $(pkg-config --libs colord-gtk) -o cd-self-test cd-self- test.c: 45:cd_window_ get_profile_ cb: assertion failed (error == NULL): no device with that property: property match 'XRANDR_ name'=' screen' does not exist (cd_window_error, 0)
$ dbus-run-session -- xvfb-run -a ./cd-self-test
[...]
ERROR:
it doesn't quite work, but nearly. Maybe upstream would have an idea here.