Is there any way to solve this problem without reloading the OS? Is my file system corrupt?
The lappy is ok as I can boot into the other os Mandriva 2007 and use it flawlessly.
good test - rules out any real hardware problem with the keyboard.
i am also assuming the x keyboard layout was not changed, or the file being edited at the time was not xorg.conf or some xinput config one (;-) )
could be a kde specific setting (slow keys got enabled accidently or something?)
try to rename the .kde directory inside $HOME for the user, and then restart. would reset all kde app settings for the user, but u can restore them later individually.
"Could not start kstartupconfig
this could be due to issues with missing home dir, kde config files, or some permissions in the new user's home dir.?
Vivek Rai wrote:
Is there any way to solve this problem without reloading the OS? Is my file system corrupt?
The lappy is ok as I can boot into the other os Mandriva 2007 and use it flawlessly.
good test - rules out any real hardware problem with the keyboard.
i am also assuming the x keyboard layout was not changed, or the file being edited at the time was not xorg.conf or some xinput config one (;-) )
No no. It was used safely only for documents.
could be a kde specific setting (slow keys got enabled accidently or something?)
It just goes dead.
try to rename the .kde directory inside $HOME for the user, and then restart. would reset all kde app settings for the user, but u can restore them later individually.
In order to avoid touching the setup files I created a new user but that GUI login failed.
"Could not start kstartupconfig
this could be due to issues with missing home dir, kde config files, or some permissions in the new user's home dir.?
I had just created the user and password from console using sudo admin rights.
Vivek Rai wrote:
try to rename the .kde directory inside $HOME for the user, and then restart. would reset all kde app settings for the user, but u can restore them later individually.
I renamed the .kde dir and that solved the problem. I got the default kde desktop and everything works fine. Keyboard is typing normally. Thank you very much. I was planning to re-install the OS. :)
I still cannot figure out why it happened mid-way during an OO document editing.
"Could not start kstartupconfig
this could be due to issues with missing home dir, kde config files, or some permissions in the new user's home dir.?
Whats happening is that a new user created in console works in console only. The new user account is listed in GUI user account settings in KDE's 'System Settings' but it cannot initiate a GUI for that user. I deleted the new user in KDE and set a new one in KDE itself. This new user can log into a proper desktop. This may be some feature or restriction in KDE.
Sometime on Sunday 22 Jul 2007, Rony said:
Whats happening is that a new user created in console works in console only. The new user account is listed in GUI user account settings in KDE's 'System Settings' but it cannot initiate a GUI for that user. I deleted the new user in KDE and set a new one in KDE itself. This new user can log into a proper desktop. This may be some feature or restriction in KDE.
How are you adding the user from command line? "adduser" normally initialises everything required for a user to login from gui.
Anurag
Anurag wrote:
Sometime on Sunday 22 Jul 2007, Rony said:
Whats happening is that a new user created in console works in console only. The new user account is listed in GUI user account settings in KDE's 'System Settings' but it cannot initiate a GUI for that user. I deleted the new user in KDE and set a new one in KDE itself. This new user can log into a proper desktop. This may be some feature or restriction in KDE.
How are you adding the user from command line? "adduser" normally initialises everything required for a user to login from gui.
I did that and was able to log that user into the console. It was the GUI that would not start for this user. However a user created in GUI got a full gui desktop. It could be the same or similar bug that knocked off my keyboard support.
-
Anurag -
Rony -
Vivek Rai