Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Apr 2012 10:54:07 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        David Wolfskill <david@catwhisker.org>
Cc:        Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: xdm failing to start on FBSD 10.0 r2340030 erratically
Message-ID:  <4F82A3AF.3050207@zedat.fu-berlin.de>
In-Reply-To: <20120408152915.GU1420@albert.catwhisker.org>
References:  <4F8176A0.807@zedat.fu-berlin.de> <20120408152915.GU1420@albert.catwhisker.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD4CE7B7E49B209A3FD9D4820
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

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 X=
11
>> 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.
>> ....
>=20
> I am not having trouble starting xdm via /etc/ttys; my environment is
> known to differ from yours in the following ways:
>=20
> * 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.)
>=20
> * I am running FreeBSD/i386, vs. FreeBSD/amd64.
>=20
> * My last 2 updates were r233994 (yesterday) and r234031 (today).
>=20
> * 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.

>=20
> * I don't know that this is different, but it may well be:  my xorg.con=
f
>   includes a stanza:
>=20
>   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.

>=20
>   because my experiences with hald & dbus were so unpleasant.  I don't
>   use them; I don't even try to start them.
>=20
> Peace,
> david

Regards,
Oliver


--------------enigD4CE7B7E49B209A3FD9D4820
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBAgAGBQJPgqO1AAoJEOgBcD7A/5N8/sUH/3v8yz+6fKMcTgHypPugRW3k
1DIHPANEXkrn8af10uZlNPxIr9PX95CBNZDDvQ7R8gfRcmu5nM5i+hZ9PbDv0Tp4
1jatoiEnV9UUDhrlSyzjpHNNiM2rti4uyXjxOiLzsUtd0Nz4966XBws90GUUj+0r
2AaIEC/jkf80V9dV3kz4ZghKJRv8IgP2WyaOpnNun9nr0ucL2N3m/mpz3dQcxdz7
IloAyOy10Jskq2hL3NSUIrv+c0/jVuvS6Xnzi0BAnpwTA4vrDxyjqCT1rECFmYcs
KZZnwxYOH72CAZNnY46Q0/dkNWxkgqDBixPTGD8BNvqyrmkbQn72yVqOLeQ67QI=
=9Twu
-----END PGP SIGNATURE-----

--------------enigD4CE7B7E49B209A3FD9D4820--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F82A3AF.3050207>