FAIL: t-set-string FAIL: t-set-arrayv FAIL: t-set-boolean FAIL: t-set-stringlist FAIL: t-set-double FAIL: t-set-uint64 FAIL: t-set-int ============================================================================ Testsuite summary for xfconf 4.14.3 ============================================================================ # TOTAL: 7 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 7 Error is always: ** (process:706): CRITICAL **: 17:48:37.703: xfconfd is not running and can not be autostarted
Same for 4.14.4.
Is this with dbus running beforehand? I've noticed some things (mostly GNOME?) fail when I don't start it up. This is how I do it: https://wiki.gentoo.org/wiki/OpenRC#Chroot_support
Dbus is running when tests are failing.
Reproduced, needs itself to be installed. Probably PATH.
I could reproduce with 4.14.4 in clean chroot but can't with 4.16.0. Upstream has introduced a custom test driver that takes care of starting and stopping xfconfd, so that probably resolved the problem. Could you confirm that 4.16.0 works fine? I will stabilize it in 3 weeks or so.