Comment 5 for bug 474806

That should be fine, I don't anticipate an xorg upload to lucid for a bit.

On Thu, Nov 05, 2009 at 03:26:39AM -0000, Steve Langasek wrote:
> Unless you're expecting an xorg upload soon, we'll probably be able to
> copy these packages from karmic-proposed to lucid once built.
>
> --
> New gdm does not have the FailsafeXServer config option
> https://bugs.launchpad.net/bugs/474806
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in ???gdm??? package in Ubuntu: New
> Status in ???xorg??? package in Ubuntu: Fix Committed
> Status in gdm in Ubuntu Lucid: In Progress
> Status in xorg in Ubuntu Lucid: Fix Committed
> Status in gdm in Ubuntu Karmic: In Progress
> Status in xorg in Ubuntu Karmic: In Progress
>
> Bug description:
> Binary package hint: gdm
>
> gdm 2.20 had options in /etc/gdm/gdm.conf (in particular FailsafeXServer) for specifying an action to take when X is failing to start up. We attached a failsafe session (aka bulletproof-x) to be invoked by gdm in these situations, which users could use to diagnose and work around issues.
>
> These options were implemented in the 'deal_with_x_crashes()' function in gdm.c. Near as I can tell, this gdm feature was not included in the new gdm rewrite, so we are seeing a regression here. The problem is that whereas in the past the user would be dumped into a debugging session, now gdm is simply trying multiple times, failing each time, and then exiting (which then leads to the quite severe bug 441638).
>
> Anyway, the end result is that we no longer have a debugging failsafe mode available for users, they're just left with a non-functioning system. Please either restore the missing functionality, or provide an analogous mechanism to which we can attach a debugging session mode.