[vox-tech] Keyboard not functioning

[Peter Jay Salzman]

yeah, i was pretty sure it would.  glad he's up and running.  go ahead and
delete dot-kde if you like.  you no longer need (or want!) it.  unless you
really modified/tweaked your desktop, deleting .kde/ is to KDE as rebooting
the system is to Microsoft Windows.

on a side note, one has to wonder how kde devs can let something like this
happen.  this sort of thing should really be reported so they can take
appropriate steps to prevent it from happening to other people.  it's OK to
not treat people like drooling idiots (the way GNOME does) but kde devs
really ought to be protecting against catastrophic occurances, like losing a
keyboard due to what's most likely accidental config twiddling...

pete



On Sat 24 Dec 05,  7:15 AM, Hookand Crook <hookandcrook at gmail.com> said:
> THANKS!!!!!!!!!!!!!!!!!! This did the trick.
> 
> Pete and Henry -- thanks so very much for your help.
> 
> Have a great holiday!!!!!!!!!!!!!!!
> Kim and hubby
> 
> On 12/23/05, Peter Jay Salzman <p at dirac.org> wrote:
> > I'm not too knowledgable about KDE (or GNOME, for that matter) myself, but
> > you can try this.  If there's some setting that got hosed accidentially,
> > this will recover from it:
> >
> > 1. Have your husband log in at the virtual console
> > 2. Perform:   "mv .kde dot-kde"
> > 3. Press alt-f7 to return to X.
> > 4. Hit control-alt-backspace to kill X.
> > 5. X will restart.
> > 6. Have him log in.
> >
> > Hopefully, the keyboard will work since KDE will have to generate new
> > settings.