apt-get dist-upgrade, and X issues

[Tom H]

>> Note: ran across this today while checking what the new gdm update was
>> related to.
>> 2.28.1-0ubuntu2
>> Publishing details
>>
>>     * Published on 2009-11-30
>> Changelog
>>
>> gdm (2.28.1-0ubuntu2) karmic-proposed; urgency=low
>>
>>   * Don't respawn gdm on failure; this lets us capture X failures
>> instead and
>>     trigger the bulletproof X handler here.  LP: #441638.
>>   * re-export any XORGCONFIG value passed to the upstart job, needed to
>>     complete integration with bulletproof X.  LP: #474806.

> Thanks, this is almopst certainly my problem.
>
> I am starting to think about moving off of Ubuntu. It seems that they are
> trying to re-engineer a great many things that have a long standig history
> of working well in *NIXsystems, and the re-emgeneered efforts seem of
> questionable value to me. The example ehre is upstart, what is the
> compleeing reason to create a system where all teh worlds *NIX admins will
> be presented with something thta does not conform to well establishe
> practice?
>
> Evewn teh BSD's are moving to SysV init these days. Theonly outlyer that I
> am aware of, besides Ubuntu is Solaris.

OS X also has its own init-replacement, launchd.

Fedora has moved partially to upstart and might be moving completely
for its next release, F13, which most likely means that RHEL will move
to upstart in a few years too. Of course, in Fedora, upstart jobs are
in /etc/event.d (where they were pre-Karmic) whereas in Karmic they
are in /etc/init. No comment...

Debian has moved to insserv for its next version, Squeeze. I landed on
some debian-devel thread, when I was googling insserv two months ago,
where the lead dev was being attacked quite vehemently for this change
but it is set to happen.

IMO upstart is not to blame here. The Ubuntu devs would have probably
done the "don't respawn..." if they were still using sysvinit because
the reason for the "don't respawn..." is to use the new Xorg
bulletproof X handler, if I understand the error correctly. So you
should blame X or the way that the devs are implementing bulletproof
X! :)