From owner-freebsd-questions@freebsd.org Thu Jul 13 00:34:17 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8A89DA9564 for ; Thu, 13 Jul 2017 00:34:17 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay13.qsc.de (mailrelay13.qsc.de [212.99.187.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5ED3F7ED95 for ; Thu, 13 Jul 2017 00:34:16 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay13.qsc.de; Thu, 13 Jul 2017 02:34:13 +0200 Received: from r56.edvax.de (port-92-195-13-67.dynamic.qsc.de [92.195.13.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id A9E863CC3F; Thu, 13 Jul 2017 02:34:12 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6D0YBqC005433; Thu, 13 Jul 2017 02:34:12 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Thu, 13 Jul 2017 02:34:11 +0200 From: Polytropon To: Anton Shterenlikht Cc: freebsd-questions@freebsd.org Subject: Re: Error opening terminal: xterm Message-Id: <20170713023411.ca82e375.freebsd@edvax.de> In-Reply-To: <201707121640.v6CGetvf055238@jail0199.vps.exonetric.net> References: <20170712183128.9cb516c9.freebsd@edvax.de> <201707121640.v6CGetvf055238@jail0199.vps.exonetric.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay13.qsc.de with 0C66668345D X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1329 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2017 00:34:17 -0000 On Wed, 12 Jul 2017 16:40:55 GMT, Anton Shterenlikht wrote: > > Date: Wed, 12 Jul 2017 18:31:28 +0200 > > From: Polytropon > > To: Anton Shterenlikht > > Subject: Re: Error opening terminal: xterm > > Cc: freebsd-questions@freebsd.org > > > > On Wed, 12 Jul 2017 15:49:17 GMT, Anton Shterenlikht wrote: > > > I'm trying to use ports-mgmt/synth. > > > I get: > > > > > > # synth build net/mpich > > > Error opening terminal: xterm. > > > > Is the "xterm" program installed on your machine? > > Yes, I know, stupid question, but might be relevant. ;-) > > yes, it is, use it every day: > > # pkg info -xo xterm > xterm-330 x11/xterm > > However, I never launch xterm as root, > because I don't allow root access to X: > > # xterm > Warning: This program is an suid-root program or is being run by the root user. > The full text of the error or warning message cannot be safely formatted > in this environment. You may get a more descriptive message by running the > program as a non-root user or by removing the suid bit on the executable. > xterm: Xt error: Can't open display: %s > xterm: DISPLAY is not set Fully correct. > Again John told me this error has nothing to do with X anyway. It doesn't really look like an X error, but it also doesn't look like a termap/terminfo error, because those errors tend to give a hint through their error message. The message "Error opening terminal: xterm." isn't very helpful. Can you provide some context from where (within the overall construct) this message is coming? What tries to start xterm, and how does it try to do so? Can the maintainer explain? > > > Anybody has a suggestion? > > > > Can you manually start xterm? From within an xterm (or > > whatever terminal emulator you are using)? > > yes, sure. Good. > > Maybe the port in question expects /usr/bin/xterm to be > > the executable ("hardcoded Linuxism")? > > unlikely. ports-mgmt/synth was recently strongly > recommended by some experienced users in ports@ > as a replacement of portmaster. So I guess this > must be a well behaved port. I'd think so, too - but still the error message (which doesn't provide the _actual_ error) might suggest that there is still something not working as intended. As you can manually start xterm, xterm probably isn't the problem; starting xterm as root _could_ be, but there are no X-related error messages (such as $DISPLAY not set, or missing X access permission). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...