There is a problem starting wmii 3.6p1 on OpenBSD 4.4
using startx:
wmii hangs while booting.
The function spawn_command of main.c of wmii uses the
double fork hack. This function will run wmiistartrc.
But the two initial processes, which will be started
by spawn_command, are login shells. See
"-%s"
in line 373 of main.c.
Starting login shells will start the shell script
.profile.
.profile of OpenBSD asks the user, which term is
going to to be used:
eval '/usr/bin/tset -sQ \$TERM'
That question is written to the tty/shell, which invokes startx.
But you do not see this question. You see the Xwindow-
surface, which normally uses another tty.
If you change to the tty, which runs startx, you see a
lot of messages about the Xserver. It is not easy to
find the question about tset, if ever. Because you even
do not know, that you must change the tty, in order to
answer a question of .profile.
The result: wmii is no working properly.
My question is:
What are the causes to use login-shells in spawn_command?
Using a standard-shell (whithout "-" in "-s%") works
well for me.
pv
Received on Fri Dec 12 2008 - 12:58:40 UTC
This archive was generated by hypermail 2.2.0 : Fri Dec 12 2008 - 13:00:08 UTC