Locked Out of KDE (OpenSuse 11.1)
in [Suse]
|
Prev: squid with login and password
Next: KDE 4.3.4 Desktops
From: Roger on 29 Jan 2010 02:02 Hi KDM is not allowing me to log in to my desktop. I can log in as root to both KDE and the console and I can login as myself at the console, but not through KDM. KDM just goes away for a think and then returns me to the login display. The only thing "unusual" that's happened lately is that I ran out of disk space earlier in the week, but that has now been resolved. Any suggestions as to what might be going on and where I should start looking? Regards
From: JohnK on 29 Jan 2010 05:58 On 29/01/10 07:02, Roger wrote: > Hi > > KDM is not allowing me to log in to my desktop. I can log in as root > to both KDE and the console and I can login as myself at the console, > but not through KDM. KDM just goes away for a think and then returns > me to the login display. > > The only thing "unusual" that's happened lately is that I ran out of > disk space earlier in the week, but that has now been resolved. Any > suggestions as to what might be going on and where I should start > looking? > > Regards Press Ctl + Alt + F1 to drop to a command line login. Login as yourself and run the following ... mv .kde .kde.bad Return to the graphic login screen using Ctl + Alt + F7 and try it now. You'll have a default KDE login again but you can bring in various settings as and when you want to try them from the files in .kde.bad Regards JohnK
From: Roger on 29 Jan 2010 06:35 On Jan 29, 12:58 pm, JohnK <johnk.dev.n...(a)gmail.com> wrote: > > Press Ctl + Alt + F1 to drop to a command line login. Login as yourself > and run the following ... > > mv .kde .kde.bad > > Return to the graphic login screen using Ctl + Alt + F7 and try it now. > You'll have a default KDE login again but you can bring in various > settings as and when you want to try them from the files in .kde.bad > I'd thought about that. Given that the error seems to be related to running out of disk space, I was wondering if there was a flag somewhere that just needs resetting? Regards
From: Roger on 29 Jan 2010 07:21 On Jan 29, 12:58 pm, JohnK <johnk.dev.n...(a)gmail.com> wrote: > > Press Ctl + Alt + F1 to drop to a command line login. Login as yourself > and run the following ... > > mv .kde .kde.bad > > Return to the graphic login screen using Ctl + Alt + F7 and try it now. > You'll have a default KDE login again but you can bring in various > settings as and when you want to try them from the files in .kde.bad > I'd thought about that. Given that the error seems to be related to running out of disk space, I was wondering if there was a flag somewhere that just needs resetting? Regards
From: JohnK on 29 Jan 2010 07:43
On 29/01/10 11:35, Roger wrote: > On Jan 29, 12:58 pm, JohnK <johnk.dev.n...(a)gmail.com> wrote: >> >> Press Ctl + Alt + F1 to drop to a command line login. Login as yourself >> and run the following ... >> >> mv .kde .kde.bad >> >> Return to the graphic login screen using Ctl + Alt + F7 and try it now. >> You'll have a default KDE login again but you can bring in various >> settings as and when you want to try them from the files in .kde.bad >> > > I'd thought about that. Given that the error seems to be related to > running out of disk space, I was wondering if there was a flag > somewhere that just needs resetting? > > Regards I'd say it was likely some file got corrupt due to the lack of disk space; either an empty file or incomplete in some way. I know it would be nice to know exactly what went wrong and fix it directly but it comes down to how much time you want to spend on fixing it. Regards JohnK |