Hi. 9.1 using KDE desktop. The problem is a few days ago after shutting down the night before as usual on starting up the next evening the main account returns to the login screen after a second or so. A wrong password is indicated as expected a correct password results in the start of login and then back the the login screen. A Root KDE login works. A second account created while logged as root works. I can log into my main account from a console and also via vnc from my laptop and the /home/... directories all look OK. So what do I look for to solve this problem please. Regards Roger
roger2 writes:
9.1 using KDE desktop. The problem is a few days ago after shutting down the night before as usual on starting up the next evening the main account returns to the login screen after a second or so. A wrong password is indicated as expected a correct password results in the start of login and then back the the login screen. A Root KDE login works. A second account created while logged as root works. I can log into my main account from a console and also via vnc from my laptop and the /home/... directories all look OK. So what do I look for to solve this problem please.
Deleting all the following directories, if they exist: /tmp/kde-$USER /tmp/gconfd-$USER /tmp/ksocket-$USER /tmp/mcop-$USER /tmp/orbit-$USER /var/tmp/kdecache-$USER where $USER is the login name of the account with the problem. Also, if there is a /home/$USER/.qt/.qtrc.lock file, delete that too. Then, try logging in again. -Ti -- Ti Kan http://www.amb.org/ti Vorsprung durch Technik
On Sat, 2004-12-04 at 11:45, Ti Kan wrote:
roger2 writes:
9.1 using KDE desktop. The problem is a few days ago after shutting down the night before as usual on starting up the next evening the main account returns to the login screen after a second or so. A wrong password is indicated as expected a correct password results in the start of login and then back the the login screen. A Root KDE login works. A second account created while logged as root works. I can log into my main account from a console and also via vnc from my laptop and the /home/... directories all look OK. So what do I look for to solve this problem please.
Deleting all the following directories, if they exist: /tmp/kde-$USER /tmp/gconfd-$USER /tmp/ksocket-$USER /tmp/mcop-$USER /tmp/orbit-$USER /var/tmp/kdecache-$USER where $USER is the login name of the account with the problem.
Also, if there is a /home/$USER/.qt/.qtrc.lock file, delete that too.
Then, try logging in again.
-Ti No change. I will run through those deletions gain after a coffee and try again.Any other recommendations welcome.
On Sat, 2004-12-04 at 12:22, roger2 wrote:
On Sat, 2004-12-04 at 11:45, Ti Kan wrote:
roger2 writes:
9.1 using KDE desktop. The problem is a few days ago after shutting down the night before as usual on starting up the next evening the main account returns to the login screen after a second or so. A wrong password is indicated as expected a correct password results in the start of login and then back the the login screen. A Root KDE login works. A second account created while logged as root works. I can log into my main account from a console and also via vnc from my laptop and the /home/... directories all look OK. So what do I look for to solve this problem please.
Deleting all the following directories, if they exist: /tmp/kde-$USER /tmp/gconfd-$USER /tmp/ksocket-$USER /tmp/mcop-$USER /tmp/orbit-$USER /var/tmp/kdecache-$USER where $USER is the login name of the account with the problem.
Also, if there is a /home/$USER/.qt/.qtrc.lock file, delete that too.
Then, try logging in again.
-Ti No change. I will run through those deletions gain after a coffee and try again.Any other recommendations welcome.
I checked again and none of th deleted files had returned i found one other file in the /tmp that was -$USER and removed that as well. I have also searched for .lck and *.lck files the only 2 found being for a particular application and dated over a month before this problem started. I have also searched for *-$USER files the only one being .wine-$USER in the /tmp and again dated a couple of weeks before this problem. So it's back to the list for any further ideas. Any further replies I will trim. Regards Roger
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2004-12-04 at 13:10 -0000, roger2 wrote:
I checked again and none of th deleted files had returned i found one other file in the /tmp that was -$USER and removed that as well. I have
If you log in as root in text mode, you can probably delete everything in /tmp that is not from today - and maybe even them. If unsure (or you have users), login in runlevel 1. One of the options available is to automatically delete every thing in /tmp on every boot. Otherwise, it is typical to delete old files. This is handled by one of the daily cron jobs, I think. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFBswaFtTMYHG2NR9URAn2ZAJ9J5K2C1IphV0fzmQELfokRhE38kACeItSd bwEJkJLEcZxA9KaSLxZHces= =xXpS -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Saturday 2004-12-04 at 13:10 -0000, roger2 wrote:
I checked again and none of th deleted files had returned i found one other file in the /tmp that was -$USER and removed that as well. I have
If you log in as root in text mode, you can probably delete everything in /tmp that is not from today - and maybe even them. If unsure (or you have users), login in runlevel 1.
One of the options available is to automatically delete every thing in /tmp on every boot. Otherwise, it is typical to delete old files. This is handled by one of the daily cron jobs, I think. OK will try that. But. No users just multi accounts of me at the moment. I copied the /home/$USER/... directories and renamed the $USER3 and
On Sun, 2004-12-05 at 13:00, Carlos E. R. wrote: then made a new account giving the $USER3 account the copied and renamed directories and that instance does the log in either so it looks like the problem is somewhere in the /home/$USER/... directories. I have made another account set up evolution and copied the shortcuts and Vfolders. So I have a usable system as I can access all the $USER folders from the $USER1 account even if I have to copy files across and change permissions. So if I can't solve the login problem I will reach the point where the $user folders are no longer needed and can be removed. Any further hints mean time will be appreciated. Regards Roger
On Sun, 2004-12-05 at 11:14, Roger Beever wrote: > On Sun, 2004-12-05 at 13:00, Carlos E. R. wrote: > OK will try that. But. > No users just multi accounts of me at the moment. > I copied the /home/$USER/... directories and renamed the $USER3 and > then made a new account giving the $USER3 account the copied and renamed > directories and that instance does the log in either so it looks like > the problem is somewhere in the /home/$USER/... directories. Well if you just making a copy of home dir to another you need to do more that just change the name you need to chown all of the files in the dir as well as that login doesn't have rights to read/modify the files it doesn't own. > I have made another account set up evolution and copied the shortcuts > and Vfolders. So I have a usable system as I can access all the $USER > folders from the $USER1 account even if I have to copy files across and > change permissions. So if I can't solve the login problem I will reach > the point where the $user folders are no longer needed and can be > removed. > Any further hints mean time will be appreciated. > Regards Roger -- Ken Schneider UNIX since 1989 SuSE since 1998 * Only reply to the list please*
If you log in as root in text mode, you can probably delete everything in /tmp that is not from today - and maybe even them. If unsure (or you have users), login in runlevel 1.
One of the options available is to automatically delete every thing in /tmp on every boot. Otherwise, it is typical to delete old files. This is handled by one of the daily cron jobs, I think. I screwed up my kde setup my installing the files from gnupg for kmail. After that, I couldn't log in using KDE ! it stalled at "loading the
On Sunday 05 December 2004 8:00 am, Carlos E. R. wrote: panel" then crashed. after renaming .gnupg to something else, I can now login, but I have disabled gnupg agent, so I have to type my PGP key in for EVERY EMAIL I SEND. what can I do to get gnupg-agent working again, uninstall/reinstall it? re-run some script?? -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
participants (6)
-
Carlos E. R. -
Ken Schneider -
Paul Cartwright -
Roger Beever -
roger2
-
ti＠amb.org