Re: Report on X

[Steve Bowman <sbowman@frostwork.net>]

On Thu, Sep 28, 2000 at 12:29:38PM +0200, Mark Kettenis wrote:
>    From: "Frederico S. Muñoz" <fsmunoz@sdf.lonestar.org>
>    Date: Thu, 28 Sep 2000 11:03:29 +0100
> 
>    ----- Original Message -----
>    From: "Steve Bowman" <sbowman@frostwork.net>
>    To: <debian-hurd@lists.debian.org>
>    Sent: Thursday, September 28, 2000 5:57 AM
>    Subject: Re: Report on X
> 
> 
>    > login as sbowman
>    > ps works
>    > su works
>    > startx fails
>    > su now fails ("Killed")
>    > ps now fails ("Killed")
>    >
>    > and now many other things seems to be failing, like ping.  ls is one
>    > thing that still works.  Logging out and back in again seems to reset
>    > the situation, a reboot isn't required.
>    >
>    > The output of startx is:
>    > _X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
>    > which repeats until interrupted.

Correction - it only repeats 6 times then gives up.  The complete output
log is:

_X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
_X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
_X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
_X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
_X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
_X11TransSocketUNIXConnect: Can't connect: errno = 1073741826
giving up.
xinit:  No such file or directory (errno 1073741826):  unable to connect to X server
xinit:  No such process (errno 1073741827):  Server error.

>    >
>    > I just upgraded to gnumach 1.2-6 and this behaviour still occurs.
>    > Is anyone else seeing this kind of instability?
> 
>    I am; the command failures don't happen to me, but when starting X with a
>    non-privileged user I get that error.
> 
> Looks like some authetication problem.  What does `ids' report before
> and after startx?

It reports:

effective uids: 1000(sbowman)
effective gids: 1000(sbowman)
available uids: 1000(sbowman) 1000(sbowman)
available gids: 1000(sbowman) 1000(sbowman)

before and afterwards it is also "Killed".  Same with 'id'.

It does seem like a(n) authentication/privileges problem.  Is there
any way to manipulate some of the hurd servers into giving up more
information?  The following servers seem to be interesting candidates:
auth exec password proc .  Ideas?

Steve

> 
> Mark

-- 
Steve Bowman  <sbowman@frostwork.net> (preferred)
Buckeye, AZ   <sbowman@goodnet.com> <bowmanc@acm.org>
              <http://www.goodnet.com/~sbowman/>

Powered by Debian GNU/Linux and GNU/Hurd <http://www.debian.org>