Date: Mon, 4 Nov 2019 20:11:09 +0100 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: Jan Beich <jbeich@freebsd.org> Cc: Antoine Brodin <antoine@freebsd.org>, svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r516629 - head/net/liferea Message-ID: <20191104191109.GB2476@elch.exwg.net> In-Reply-To: <d0e7-22pk-wny@FreeBSD.org> References: <201911041019.xA4AJYqc047310@repo.freebsd.org> <20191104103901.GA2476@elch.exwg.net> <d0e7-22pk-wny@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
## Jan Beich (jbeich@FreeBSD.org): > >> Unable to init server: Could not connect to 127.0.0.1: Connection refused > >> Command '['./liferea', > >> '--introspect-dump=/tmp/tmp-introspectpgy0ihjn/functions.txt,/tmp/tmp-introspectpgy0ihjn/dump.xml']' > >> died with <Signals.SIGABRT: 6>. > > > > Even if no GUI is requested, "something" tries to connect to Wayland > > and (of course) fails. > > libwayland doesn't support TCP sockets, so "127.0.0.1: Connection refused" > comes from libX11. Even better: that's the "broadway" (HTML5/websockets) backend which produces this message. (Changing GDK_BACKEND can make the "Connection refused" go away, but the crash stays). And the SIGABORT looks like it came somewhere out of webkit2gtk. Great. > It can be silenced by setting up DISPLAY variable but > the crash breaking build wouldn't disappear. There was no DISPLAY set to begin with - one of the advantages of poudriere is that we get a sanitized environment. Regards, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191104191109.GB2476>