Bugzilla – Bug 238604
xvkbd stays as root with tabletpc and auto-login enabled
Last modified: 2007-02-01 09:51:47 UTC
I have a tablet pc (toshiba portege m200), and have enabled auto-login in KDE. At startup xvkbd is started by xdm, and is not killed. So I have to su to root and kill it manually. The problem seems to be in /etc/X11/xdm/Xsetup on line 67 - 82 where xvkbd is started to be able to input username and password. I'm not good enough at scripting to fix it though. Regards, Hans Gunnarsson
Danny. Any proposal?
hm ... get /etc/X11/xdm/Xstartup (where xkvbd get killed on login) not called/executed on autologin? Any other script where we can add the same code like in /etc/X11/xdm/Xstartup which get also called on autologin?
Honestly I don't know, what's called during kdm/gdm autologin. xdm itself doesn't support any autologin.
Adding "echo XSETUP/XSTARTUP >>/tmp/xs.txt" to both of /etc/X11/xdm/{Xsetup|Xstartup} shows that both are executed. It's probably the fact that they're executed one after another that triggers this bug. The code in Xsetup looks like it does the xvkbd launching in the background and doesn't wait.
> At startup xvkbd is started by xdm, and is not killed. So I have to su to > root and kill it manually. kill/killall won't work. But can't you kill it with xkill or by using the buttons of the window decoration?
The buttons on the window decoration do not work. Haven't tried xkill, will do so this evening.
Tried xkill, and I can kill the window with it.
@Stefan: We can add maybe a check to Xstartup to avoid the start of the keyboard if autologin is enabled.
@Danny: How can I check if autologin is enabled?
quick and _dirty_ on SLED (I assume also on 10.2): grep DISPLAYMANAGER_AUTOLOGIN="" /etc/sysconfig/displaymanager If autologin is enabled the grep fail, because there is a username in this config variable
fixed for STABLE/Factory.