Keyboard stops working
barius.drubeck at gmail.com
Wed Feb 28 03:59:19 PST 2007
On Tuesday 27 February 2007 23:15, Tijnema ! wrote:
> Thanks anyway, and please have a look at my ps -A result.
First weird thing:
1882 tty2 00:00:13 X
1936 tty1 00:00:00 agetty
1937 ? 00:00:00 agetty
1938 tty3 00:00:00 agetty
1939 tty4 00:00:00 agetty
1940 tty5 00:00:00 agetty
1941 tty6 00:00:00 agetty
Normally X runs on virtual console 7 and shows up in ps listing
without a controlling terminal. Somehow, you managed to start X on
tty2, I'm not sure if that is intentional or not. But anyhow, you
shouldn't be spawning a getty on the same tty as you run X. That is
IMHO almost guaranteed to cause a conflict.
1927 ? 00:00:00 smbd
1932 ? 00:00:00 smbd
1919 ? 00:00:00 winbindd
1928 ? 00:00:00 winbindd
You seem to be running multiple copies of certain daemons. It is
possible that these daemons start child processes but I can't tell,
since your ps output doesn't use the -H option nor give the PPID. If
they are indeed duplicate instances, I can't predict the result but I
don't think it is healthy.
See again Dan's earlier posting. KDM and startx are normally
alternative ways to start X. By alternative, I mean mutually
exclusive, one or the other but not both.
More information about the blfs-support