Not enough detail to say. That's standard output for trying to start
a second Xorg on :0 when there's already one there - if there's not one
there, and it exited cleanly, it would be a bug. If the user or gdm
did a kill -9 to kill Xorg without letting it clean up, then they shouldn't
do that.
-alan-
Brian Cameron wrote:
>
> Alan:
>
> Is this a known bug with the Xserver?
>
> Brian
>
>
> -------- Original Message --------
> Subject: Re: [desktop-discuss] b130 gdm failed after user logout
> Date: Mon, 04 Jan 2010 16:03:50 +0800
> From: Halton Huo <Halton.Huo at Sun.COM>
> To: solarg <solarg at laposte.net>
> CC: desktop-discuss at opensolaris.org
>
> This happens to me sometime, the reason is the X quits but the lock file
> under /tmp are not removed. X experts might has some clue.
>
> Another workaround is remove the lock file as root.
>
> Thanks,
> Halton.
>
> On Sat, 2010-01-02 at 14:01 +0100, solarg wrote:
>> hello all,
>> this problem appears on my machine, but not always. When a user (local
>> user i mean) logs out, there is only a black screen, and here is the
>> error message:
>>
>> # tail -f /var/log/gdm/\:0.log
>> Fatal server error:
>> Server is already active for display 0
>> If this server is no longer running, remove /tmp/.X0-lock
>> and start again.
>>
>>
>> Please consult the Sun Microsystems, Inc., based on X.Org Foundation
>> sources support
>> at http://sunsolve.sun.com/
>> for help.
>>
>>
>> actually, the "not" workaround is to restart gdm from a remote machine,
>> or reboot the machine...
>>
>> has anybody ever seen this problem?
>>
>> thanks,
>>
>> gerard
>>
>>
>> _______________________________________________
>> desktop-discuss mailing list
>> desktop-discuss at opensolaris.org
>
>
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
