X terminal saga continues

[J. Seth Henry]

Thanks much for the help so far, but this X terminal project is
reminiscent of the dutch boy and dike. Everytime I get one thing working,
something else goes screwy.

I now have X starting automatically by initd, and it connects to an xdm
application server. This works correctly, and I can log in as any user on
the server from the terminal. (Note, the console doesn't have a monitor,
but it should also be displaying an xdm login)

Presently, I have a local .xsession in every user's home directory, which
starts icewm. This is OK, as I can add it to /etc/skel, but it would be
nice if there were an override file, which automatically started the wm.

Also, I've noticed that some applications, such as Mozilla, aren't
recieving keyboard shortcuts anymore. When I log into the terminal
console, manually start X, and connect to the server, Mozilla runs fine -
responds to CTRL+ALT+L, ALT+RIGHT/LEFT etc. When I log in graphically,
Mozilla doesn't see any of these commands. I have used xev, running
from the application server, to verify that the X server is sending the
keystrokes. I also checked PINE, and it responds to the keystrokes.

So, it would appear to be a problem with Mozilla, but I can't figure out
why it works when I start the application via an xterm?

Did I misconfigure xdm?

Notes:
I am using Xfree86 4.2.x libraries on the server (the default for FBSD
4.7-REL), the terminals are running Xfree 3.3.6 for memory reasons. The X
server on the terminals were modified slightly to remap special keys to
normal keys, but are otherwise unmodified. The server has worked before,
so I don't suspect it is the problem, and xev on either the server or the
client reports that the keystrokes are, indeed, being generated correctly.

All the systems involved are running 4.7-REL with custom kernels.

problem only occurs when the wm is launched via xdm - launching via xterm
after manual login doesn't appear to result in the problem

I am using the Linux Mozilla binary

No errors are being reported in either the terminal or app server's
syslog, or xdm-errors log.

Any help would be greatly appreciated, as ironically, Mozilla was the
primary purpose for these terminals. :)

Thanks,
Seth Henry


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message

Re: X terminal saga continues

[Dirk-Willem van Gulik]

On Thu, 6 Feb 2003, J. Seth Henry wrote:

 Presently, I have a local .xsession in every user's home directory, which
 starts icewm. This is OK, as I can add it to /etc/skel, but it would be
 nice if there were an override file, which automatically started the wm.

Check out /usr/X11R6/lib/X11/Xsession which is the beast which kicks off
the .xsession. I've used an extra check at the end of the file:

global_startup=/usr/X11R6/lib/X11/xinit/xinitrc
startup=$HOME/.xsession
resources=$HOME/.Xresources

if [ -f $startup ]; then
exec $startup
if

if [-f $global_startup]; then
exec $startup
fi

if [ -f $resources ]; then
 xrdb -load $resources
fi

 So, it would appear to be a problem with Mozilla, but I can't figure out
 why it works when I start the application via an xterm?

You may (not) pick up a .Xmodmap; see /usr/X11R6/lib/X11/xinit/xinitrc
which you do not pick up with an ~/.xsession (for xdm) or ~/.xinitrc (for
startx) start method.

Dw


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message