Re: xdm receives no input

2019-03-13 Thread Chavdar Ivanov
Awesome, thanks! That's a thing which pops up from time to time, I've
had it myself.

On Wed, 13 Mar 2019 at 15:04, Patrick Welche  wrote:
>
> On Tue, Mar 12, 2019 at 05:17:10PM +, Chavdar Ivanov wrote:
> > /etc/ttys ?
>
> Absolutely right. This laptop's xdm worked before the update, so I doubted
> your suggestion.
>
> What happened is that the update replaced my /etc/X11/xdm/Xservers.ws
> in which I had carefully set vt08 as the terminal to use. The update
> changed it to vt05, which was inconsistent with my /etc/ttys.
>
> Editing /etc/X11/xdm/Xservers back to vt08 fixed things.
>
> mystery solved!
>
>
> Cheers,
>
> Patrick



-- 



Re: xdm receives no input

2019-03-13 Thread Patrick Welche
On Tue, Mar 12, 2019 at 05:17:10PM +, Chavdar Ivanov wrote:
> /etc/ttys ?

Absolutely right. This laptop's xdm worked before the update, so I doubted
your suggestion.

What happened is that the update replaced my /etc/X11/xdm/Xservers.ws
in which I had carefully set vt08 as the terminal to use. The update
changed it to vt05, which was inconsistent with my /etc/ttys.

Editing /etc/X11/xdm/Xservers back to vt08 fixed things.

mystery solved!


Cheers,

Patrick


Re: xdm receives no input

2019-03-13 Thread Patrick Welche
On Wed, Mar 13, 2019 at 11:54:11AM +0100, Martin Husemann wrote:
> On Wed, Mar 13, 2019 at 10:44:46AM +, Patrick Welche wrote:
> > I stared at /etc/X11/xdm/Xresources, and
> > https://gitlab.freedesktop.org/xorg/app/xdm/blob/master/config/Xresources.in
> > and didn't spot additional fields (just our fonts are smaller and we
> > fiddle with the NetBSD logo) - what should I be looking out for?
> 
> postinstall(8) checks for inpColor:

Hmmm...

$ grep inpColor /etc/X11/xdm/Xresources 
xlogin*inpColor: grey80

and I didn't edit that file... (so postinstall already fixed it for me?)

$ ls -l /etc/X11/xdm/Xresources 
-r--r--r--  1 root  wheel  3438 Mar 12 12:40 /etc/X11/xdm/Xresources


I have to say, it seems to smell more of Xkeyboard...


Cheers,

Patrick


Re: xdm receives no input

2019-03-13 Thread Martin Husemann
On Wed, Mar 13, 2019 at 10:44:46AM +, Patrick Welche wrote:
> I stared at /etc/X11/xdm/Xresources, and
> https://gitlab.freedesktop.org/xorg/app/xdm/blob/master/config/Xresources.in
> and didn't spot additional fields (just our fonts are smaller and we
> fiddle with the NetBSD logo) - what should I be looking out for?

postinstall(8) checks for inpColor:

Martin


Re: xdm receives no input

2019-03-13 Thread Patrick Welche
On Wed, Mar 13, 2019 at 08:10:23AM +1100, matthew green wrote:
> Patrick Welche writes:
> > Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> > which no longer likes SNA but works with UX, and xdm seems to sit
> > at the prompt waiting for something:
> > ...

> is it a black input bar that doesn't appear to do anything?
> (it probably does work -- did you try typing blind?)

If you mean a text cursor input type thing inside the Login: text
field, yes? Blind typing doesn't do anything...

> the fix is to update /usr/X11/xdm/Xresources file -- it has
> new required entries.  i'm going to work on making this less
> awful when it isn't updated, but i've been busy working on
> the Mesa18 update :-)

I stared at /etc/X11/xdm/Xresources, and
https://gitlab.freedesktop.org/xorg/app/xdm/blob/master/config/Xresources.in
and didn't spot additional fields (just our fonts are smaller and we
fiddle with the NetBSD logo) - what should I be looking out for?

Cheers,

Patrick


Re: xdm receives no input

2019-03-12 Thread Chavdar Ivanov
/etc/ttys ?


On Tue, 12 Mar 2019 at 16:32, Patrick Welche  wrote:

> Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> which no longer likes SNA but works with UX, and xdm seems to sit
> at the prompt waiting for something:
>
> #0  0x7f7ff344285a in poll () from /usr/lib/libc.so.12
> #1  0x7f7ff6031f3d in IoWait (wt=0x7f7fcec0, wf= pointer>,
> wf=)
> at /usr/xsrc/external/mit/libXt/dist/src/NextEvent.c:356
> #2  _XtWaitForSomething (app=app@entry=0x7f7ff7e6,
> ignoreEvents=ignoreEvents@entry=0 '\000',
> ignoreTimers=ignoreTimers@entry=0 '\000',
> ignoreInputs=ignoreInputs@entry=0 '\000',
> ignoreSignals=ignoreSignals@entry=0 '\000', block=block@entry=1
> '\001',
> drop_lock=0 '\000', drop_lock@entry=1 '\001', howlong=howlong@entry
> =0x0)
> at /usr/xsrc/external/mit/libXt/dist/src/NextEvent.c:624
>
> The cursor is visible in the Login: prompt, but apparently Something never
> happens... (Switching to SNA, doesn't change anything.)
>
> Thoughts on how to debug?
>
>
> Cheers,
>
> Patrick
>
-- 



re: xdm receives no input

2019-03-12 Thread matthew green
Patrick Welche writes:
> Had a go with the shiny new X (thanks!) on the sandy bridge laptop
> which no longer likes SNA but works with UX, and xdm seems to sit
> at the prompt waiting for something:
> 
> #0  0x7f7ff344285a in poll () from /usr/lib/libc.so.12
> #1  0x7f7ff6031f3d in IoWait (wt=0x7f7fcec0, wf=, 
> wf=)
> at /usr/xsrc/external/mit/libXt/dist/src/NextEvent.c:356
> #2  _XtWaitForSomething (app=app@entry=0x7f7ff7e6, 
> ignoreEvents=ignoreEvents@entry=0 '\000', 
> ignoreTimers=ignoreTimers@entry=0 '\000', 
> ignoreInputs=ignoreInputs@entry=0 '\000', 
> ignoreSignals=ignoreSignals@entry=0 '\000', block=block@entry=1 '\001', 
> drop_lock=0 '\000', drop_lock@entry=1 '\001', howlong=howlong@entry=0x0)
> at /usr/xsrc/external/mit/libXt/dist/src/NextEvent.c:624
> 
> The cursor is visible in the Login: prompt, but apparently Something never
> happens... (Switching to SNA, doesn't change anything.)
> 
> Thoughts on how to debug?

is it a black input bar that doesn't appear to do anything?
(it probably does work -- did you try typing blind?)

the fix is to update /usr/X11/xdm/Xresources file -- it has
new required entries.  i'm going to work on making this less
awful when it isn't updated, but i've been busy working on
the Mesa18 update :-)

postinstall is not yet capable of properly updating it or
really suggesting what you need to do, so that would be the
first step, but perhaps also making /etc/rc.d/xdm fail to
run if the new entries are missing would be good too.

thanks.


.mrg.