From owner-freebsd-x11@FreeBSD.ORG Mon Apr 9 12:27:50 2012 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35F6A106564A; Mon, 9 Apr 2012 12:27:50 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7D3F98FC15; Mon, 9 Apr 2012 12:27:49 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so4257075bkc.13 for ; Mon, 09 Apr 2012 05:27:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=E2Rl2azNtyZapf9zlpvKe8VtXCjFZO2oI5iTSm9lnoA=; b=D2Y+zgxboyJAHy0ITDRx8hfhKmjhsMtJ7Y5YRsh/NR+2llB5U6V6sCdTG7hXPLMAfZ DlkZW17tTPnmJZEJB5kR7I5QQXM3Za29FfVXpXhzi3k/VwBBnhQ0STkFF6INiP4gskVZ ChHsQR4ZO3DdtK9rK4gzZNhSDOQ9ffUMh/OSZqA+MV2xzO8j/t5PbmeBPzA6teMo8ipz FlLAru6WkSBWgfacoA4XPaRuY9MRAhL+YF0S2vbxjYN8YfdL+3vosMPOyLMAqN5RkbN9 E+FeAfo3eGsd05n2J8YtWXO5BKriB1qOqshHR89GRaJvMtm/p+WYjeNtn57dqzLxzYvA ATMg== MIME-Version: 1.0 Received: by 10.205.117.15 with SMTP id fk15mr2933529bkc.133.1333974468332; Mon, 09 Apr 2012 05:27:48 -0700 (PDT) Received: by 10.204.202.142 with HTTP; Mon, 9 Apr 2012 05:27:48 -0700 (PDT) Received: by 10.204.202.142 with HTTP; Mon, 9 Apr 2012 05:27:48 -0700 (PDT) In-Reply-To: <4F82B315.3010408@zedat.fu-berlin.de> References: <4F8176A0.807@zedat.fu-berlin.de> <20120408152915.GU1420@albert.catwhisker.org> <4F82A3AF.3050207@zedat.fu-berlin.de> <20120409091507.GA55822@mech-cluster241.men.bris.ac.uk> <4F82B315.3010408@zedat.fu-berlin.de> Date: Mon, 9 Apr 2012 12:27:48 +0000 Message-ID: From: Chris Rees To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-x11@freebsd.org, Current FreeBSD , mexas@bristol.ac.uk, David Wolfskill Subject: Re: xdm failing to start on FBSD 10.0 r2340030 erratically X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Apr 2012 12:27:50 -0000 On 9 Apr 2012 11:00, "O. Hartmann" wrote: > > Am 04/09/12 11:15, schrieb Anton Shterenlikht: > > On Mon, Apr 09, 2012 at 10:54:07AM +0200, O. Hartmann wrote: > >> Am 04/08/12 17:29, schrieb David Wolfskill: > >>> On Sun, Apr 08, 2012 at 01:29:36PM +0200, O. Hartmann wrote: > >>>> I loose hair ... > >>>> Since yesterady's "make world" (last make world: the day before > >>>> yesterday), getting FreeBSD 10.0-CURRENT/amd64 to r234000 or so, the X11 > >>>> system on all of our FreeBSD 10.0-CUR/amd64 boxes start rejecting the > >>>> start of xdm display manager. xdm is started from /etc/ttys on ttyv7. > >>>> This worked before flawless. > >>>> > >>>> At this very moment, I do have X11 started via xdm - but this is a > >>>> erratic and non-reproduceable process! > >>>> > >>>> This morning, I update world and kernel to r234030. I recompiled many > >>>> ports via "portmaster -f xorg xdm", hoping the new kernel/world could > >>>> affect the ports, but this isn't. > >>>> > >>>> Starting Xorg X11 server works fine. xdm fails. The log in > >>>> /var/log/xdm.log looks like: > >>>> > >>>> Build Date: 07 April 2012 04:51:08PM > >>>> ... > >>>> > >>>> > >>>> I feel a bit helpless around here since I can not get close to what is > >>>> happening. The erratic behaviour of starting xdm is frightening. > >>>> Starting xdm via /etc/ttys doesn't work at all, but sometimes, with a > >>>> bit luck, xdm starts when started from the console. > >>>> .... > >>> > >>> I am not having trouble starting xdm via /etc/ttys; my environment is > >>> known to differ from yours in the following ways: > >>> > >>> * My ports (save for x11/nvidia-driver and misc/compat8x) are built > >>> under stable/8. (I track stable/8, stable/9, and head on a daily > >>> basis, and have a common /usr/local among them. I also update > >>> any installed ports that have updates available daily.) > >>> > >>> * I am running FreeBSD/i386, vs. FreeBSD/amd64. > >>> > >>> * My last 2 updates were r233994 (yesterday) and r234031 (today). > >>> > >>> * I have a mildly hacked-up startup script for xdm. I doubt this is an > >>> issue -- I've been doing this since 2006/03/05 19:04:03 (according to > >>> the RCS log), though I have modified the script a few times > >>> since its inception. But the point here is that I'm not directly > >>> invoking the xdm executable from /etc/ttys. > >> > >> When I start xdm via console, it starts up, but only with a "Xservers" > >> file that contains nothing but comments. If there are the lines > >> > >> localhost > >> 127.0.0.1 > >> 192.168.0.128 > >> !* > >> > >> it will will probably start not. Since xdm does not show this behaviour > >> in a reproducible manner I susepct a bug. > >> > >>> > >>> * I don't know that this is different, but it may well be: my xorg.conf > >>> includes a stanza: > >>> > >>> Section "ServerFlags" > >>> Option "AutoAddDevices" "False" > >>> EndSection > >> > >> I should go with this and try. But as far as I know, since I have USB > >> devices (mouse, keyboard), unpluggin and pluggin them is then, without > >> hal and dbus, not recognized anymore, isn't it? > >> > >> There was a discussion once going one for this subject. > >> > >> > >> Either way, at this very moment I do not know whether the OS or the X11 > >> is faulty and I'd like to report this as a bug. > >> > >>> > >>> because my experiences with hald & dbus were so unpleasant. I don't > >>> use them; I don't even try to start them. > >>> > >>> Peace, > >>> david > >> > >> Regards, > >> Oliver > >> > > > > I see the same (or similar) behavior on r231158M amd64 > > Compaq 6715s laptop. > > > > I've: > > > > BUZI> pkg info xdm > > xdm-1.1.11: X.Org X display manager > > BUZI> > > pkohartmann@thor: [~] g_info |grep xdm > xdm-1.1.11 X.Org X display manager > > > > > Starting xdm from /etc/ttys: > > > > BUZI> grep bin/xdm /etc/ttys > > ttyv8 "/usr/local/bin/xdm -nodaemon" xterm on secure > > BUZI> > > ohartmann@thor: [~] grep bin/xdm /etc/ttys > ttyv7 "/usr/local/bin/xdm -nodaemon" xterm on insecure Hm, you know setting insecure on xdm still lets root login? Chris