Bug 739506

Summary:	xfce-base/xfconf fails all tests: xfconfd is not running and can not be autostarted
Product:	Gentoo Linux	Reporter:	Thomas Deutschmann (RETIRED) <whissi>
Component:	Current packages	Assignee:	XFCE Team <xfce>
Status:	CONFIRMED ---
Severity:	normal	CC:	mgorny, sam
Priority:	Normal	Keywords:	TESTFAILURE
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	733994, 754834

Description Thomas Deutschmann (RETIRED) gentoo-dev

2020-08-29 15:56:34 UTC

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

Comment 1 Thomas Deutschmann (RETIRED) gentoo-dev

2020-11-17 21:30:57 UTC

Same for 4.14.4.

Comment 2 Sam James archtester

2020-11-18 00:41:58 UTC

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

Comment 3 Thomas Deutschmann (RETIRED) gentoo-dev

2020-11-18 21:18:23 UTC

Dbus is running when tests are failing.

Comment 4 Sam James archtester

2021-01-18 20:26:14 UTC

Reproduced, needs itself to be installed. Probably PATH.

Comment 5 Michał Górny archtester

2021-01-19 09:42:06 UTC

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.