Your message dated Thu, 14 Aug 2008 14:33:24 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#475717: Xorg does not run if xorg already runs on the
other chroot.
has caused the Debian Bug report #475717,
regarding Xorg does not run if xorg already runs on the other chroot.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
475717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475717
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: xserver-xorg-core
Version: 2:1.4.1~git20080131-3
Xorg does not run if xorg (2:1.4.1~git20080131-3) already runs on the
other chroot.
If I run startx, it says as follows:
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't
already running
giving up.
xinit: no such file or directry (errno 2): unable to connect X server
xinit: no such process (errno 3): Server error.
I am confirming that this phenomenon occurs on version:
2:1.4.1~git20080131-2 and version: 2:1.4.1~git20080131-3 of
xserver-xorg-core.
On version: 2:1.4.1~git20080131-1 of xserver-xorg-core, this phenomenon
does not occur.
Regards,
Hiroyuki
--- End Message ---
--- Begin Message ---
Hiroyuki Yamamoto wrote:
> Oh, I'm sorry.
>
> Only the xserver-xorg-core package doesn't cause this phenomenon.
> Actually it occurs on rebuilded package of 2:1.4.1~git20080131-1 on the
> present sid,
> though it doesn't occur on the same package downloaded from
> snapshot.debian.net.
> Maybe it occurs because of difference of dev library.
>
> After all, it was solved by typing of "startx -- :1".
> Thus, please close this bug.
>
Ok, done.
Brice
--- End Message ---
