kybd input suddenly not working after login; OK if 'startx' from console
 

hi all,

i've been running SuSE 9.2Pro without any issue.

after a YaST update yesterday eve, i've lost the ability to type any keystrokes when auto-logged-in.

specifically,

if i start in failsafe mode, i can type at the console.

if from the console i 'startx' as either ROOT or MYUSER, up comes my usual desktop and everything works great. i can open any application and type ...

however, if i use my standard auto-login set up to boot into user MYUSER, the desktop comes up as i'd expect.

i can mouse around, point-n-click & launch apps, but keyboard input is DOA -- nothing.

not in konsole, browser, etc. -- just nothing.

to troubleshoot, i've gone the usual route of moving my /home/MYUSER/.kde out of the way, and deleting all .x*, .X* and .ICE* files ...

after reboot, absolutely the same behavior as above.

any wisdom/suggestions as to where to look/what to do here? this is driving me nuts :-S

cheers,

richard

Richard, since your mouse still works, try this:
Open something like the file manager. Clear the address area
and then right click it. You will get the option to select 'input method.'
Depending on what your options are in that dropdown menu, try XIM as you most certainly have that option. If not or if that doesn't change anything, try the others and then report back your findings../peter

hi drumvudu,

your reply snuck by ... didn't notice a notice! sorry abt no reply :-S

per your suggestion, i opened "Run command ..." while at the auto-logged-in desktop.

right-click shows my options to be:

[ ] Simple Composing Input Method
[X] XIM

as checked, i'm UNable to type anything, so I switch/selected to:

[X] Simple Composing Input Method
[ ] XIM

unfortunately, still no dice.

AND, still, rebooting into console mode then 'startx'-ing as myUser, all's fine.

thx!

richard

hi peter (didn't see your name there b4 ...),

while i'm poking abt, it dawns on me that this might well be a result of something starting differently (or not at all) on auto/complete-login-to-desktop vs. login-to-console-then-startx ...

question:

on autologin, is the X launch actually invoked "simply" w/ startx? isn't a different script responsible for launch?

just randomly thrashing abt here 4 the moment ...

richard

Richard, are you booting to runlevel 3 and then invoking <startx> OR using autologin where when you boot, your system goes directly to the desktop? Have you tried setting your system to boot to runlevel 5 with the graphical login? As far as what code autologin invokes, that I can't tell you off the top of my head. Autologin is a function of KDE's kconfig login mngr. I would think that it invokes startkde which I believe is separate from the standard startx but I'm not THAT familiar with the inner workings of KDE code.

hi again,

> are you booting to runlevel 3 and then invoking <startx> OR using autologin where when you boot, your system goes directly to the desktop?

both. in the former case, no troubles. in the latter -- no typing!

> Have you tried setting your system to boot to runlevel 5 with the graphical login? As far as what code autologin invokes, that I can't tell you off the top of my head. Autologin is a function of KDE's kconfig login mngr. I would think that it invokes startkde which I believe is separate from the standard startx but I'm not THAT familiar with the inner workings of KDE code.

turns out that this is, in fact, a known/new issue. finally found a ref @:

http://lists.suse.com/archive/suse-k...-Feb/0010.html

good news is ... its not just me =) and, using gdm is a short term workaround.

so, 4 now, its wait-n-see.

thx! 4 your help !!

cheers,
richard

good deal Richard, I read the entire thread.good luck../p

hi,

for closure's sake (and so that I can find this again when I've forgotten what the solution is ...), there's now a well-behaved fix for this @:

http://lists.suse.com/archive/suse-k...-Feb/0035.html

cheers,

richard