From owner-freebsd-ports@FreeBSD.ORG Fri Sep 21 15:54:36 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B23816A41A for ; Fri, 21 Sep 2007 15:54:36 +0000 (UTC) (envelope-from freebsd@levsha.org.ua) Received: from expo.ukrweb.net (expo.ukrweb.net [193.125.78.116]) by mx1.freebsd.org (Postfix) with ESMTP id 0560C13C45B for ; Fri, 21 Sep 2007 15:54:35 +0000 (UTC) (envelope-from freebsd@levsha.org.ua) Received: from levsha by expo.ukrweb.net with local (Exim 4.52 (FreeBSD)) id 1IYkM4-000FDb-CP; Fri, 21 Sep 2007 18:23:44 +0300 Date: Fri, 21 Sep 2007 18:23:44 +0300 From: Mykola Dzham To: "[LoN]Kamikaze" Message-ID: <20070921152344.GL30765@expo.ukrweb.net> References: <46EA9419.4050402@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46EA9419.4050402@gmx.de> X-Operating-System: FreeBSD/5.4-RELEASE-p6 (i386) User-Agent: Mutt/1.5.6i Cc: freebsd-ports@freebsd.org Subject: Re: xorg-7.3 xdm ignores /etc/login.conf X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 15:54:36 -0000 [LoN]Kamikaze wrote: > Since the update xdm seems to ignore environment variables set in > /etc/login.conf such as PATH or LANG. I've tried inserting > > printenv > ~/.env > > into my ~/.xsession and the result looks rather bleak. E.g. PATH looks like this: > PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/gnu/bin:/usr/local/bin > > Which seems to be some kind of xdm default. LANG is not even set. > > Executing > su - $USER > > leads to the correct PATH and LANG settings: > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/kamikaze/bin > LANG=en_GB.UTF-8 > MM_CHARSET=UTF-8 > > But of course this will cast away variables like DISPLAY, so putting the line > into my .xsession is not really a satisfying solution. > > Does anyone else encounter this problem? Are there any suggestions how to get > behind the reason or even a solution? I hawe same problem after upgrade xdm. -- Mykola Dzham, LEFT-(UANIC|RIPE) JID: levsha@jabber.net.ua