Lost ability to login as user
I was trying to resolve a conflict while upgrading with apt-get. In the process I removed gdm2-2.4.1.6-92.ximian.8.5. I had tried XD2 for awhile, but had changed my session back to kde some time ago. I have tried changing my grom GDM to KDM and XDM, but can login to my user account only in failesafe mode to a dingle Xwindow. I can login to a KDE session as root, and I created a new user, which can login just fine as well. Seems I read in the past that something needed to be deleted in /tmp or something for a similar problem, but so far I haven't hit on the resolution. Mel
Op maandag 18 oktober 2004 04:04, schreef Mel Andres:
I was trying to resolve a conflict while upgrading with apt-get. In the process I removed gdm2-2.4.1.6-92.ximian.8.5. I had tried XD2 for awhile, but had changed my session back to kde some time ago. I have tried changing my grom GDM to KDM and XDM, but can login to my user account only in failesafe mode to a dingle Xwindow. I can login to a KDE session as root, and I created a new user, which can login just fine as well. Seems I read in the past that something needed to be deleted in /tmp or something for a similar problem, but so far I haven't hit on the resolution.
Remove the files: /tmp/mcop-<user> /tmp/kde-<user> /tmp/ksocket-<user> Where <user> is your login. This may solve it. -- Richard Bos Without a home the journey is endless
Richard Bos wrote:
Op maandag 18 oktober 2004 04:04, schreef Mel Andres:
I was trying to resolve a conflict while upgrading with apt-get. In the process I removed gdm2-2.4.1.6-92.ximian.8.5. I had tried XD2 for awhile, but had changed my session back to kde some time ago. I have tried changing my grom GDM to KDM and XDM, but can login to my user account only in failesafe mode to a dingle Xwindow. I can login to a KDE session as root, and I created a new user, which can login just fine as well. Seems I read in the past that something needed to be deleted in /tmp or something for a similar problem, but so far I haven't hit on the resolution.
Remove the files: /tmp/mcop-<user> /tmp/kde-<user> /tmp/ksocket-<user>
Where <user> is your login. This may solve it.
Tried that, but it didn't help. I'm considering a re-install of the OS. My hard drive is a 60gb which I have divided into thirds. First part is for WinXP, next is SuSE 9.0 Personal, and the last 20gb I have set aside for future use. I am thinking that I might as well upgrade at the same time, but I was hoping to wait for 9.2 first. At any rate, I would but the new image in the reserved space. That way I could mount the old / home/my_login, and copy/migrate mail etc. There is probably a simpler solution, but this would clean up a lot of stuff. Mel
Am Montag, 18. Oktober 2004 19:22 schrieb Mel Andres:
Richard Bos wrote:
Op maandag 18 oktober 2004 04:04, schreef Mel Andres:
I was trying to resolve a conflict while upgrading with apt-get. In the process I removed gdm2-2.4.1.6-92.ximian.8.5. I had tried XD2 for awhile, but had changed my session back to kde some time ago. I have tried changing my grom GDM to KDM and XDM, but can login to my user account only in failesafe mode to a dingle Xwindow. I can login to a KDE session as root, and I created a new user, which can login just fine as well. Seems I read in the past that something needed to be deleted in /tmp or something for a similar problem, but so far I haven't hit on the resolution.
Remove the files: /tmp/mcop-<user> /tmp/kde-<user> /tmp/ksocket-<user>
Where <user> is your login. This may solve it.
Tried that, but it didn't help. I'm considering a re-install of the OS. My hard drive is a 60gb which I have divided into thirds. First part is for WinXP, next is SuSE 9.0 Personal, and the last 20gb I have set aside for future use. I am thinking that I might as well upgrade at the same time, but I was hoping to wait for 9.2 first. At any rate, I would but the new image in the reserved space. That way I could mount the old / home/my_login, and copy/migrate mail etc. There is probably a simpler solution, but this would clean up a lot of stuff.
Mel
Before you reinstall a system you will reinstall again when 9.2 comes out, then better create a new user on the existing system and delete or ignore the nonfunctional one. Much less work, same effect. Daniel
Mel Andres wrote:
Tried that, but it didn't help. I'm considering a re-install of the OS. My hard drive is a 60gb which I have divided into thirds. First part is for WinXP, next is SuSE 9.0 Personal, and the last 20gb I have set aside for future use. I am thinking that I might as well upgrade at the same time, but I was hoping to wait for 9.2 first. At any rate, I would but the new image in the reserved space. That way I could mount the old / home/my_login, and copy/migrate mail etc. There is probably a simpler solution, but this would clean up a lot of stuff.
Mel
This is not a solution to your problem but: - 9.2 is due out next month - it will not have a 'personal' version. Only full / update. The update will work just fine for you but I think it is missing some of the paper docs. I don't know the US pricing but the update is - as ever - cheaper than the full version. Your problem will either be something in /etc or in /home and I really should know which. Have you tried going in wwith runlevel 3 (boot with 'linux 3') and then doing a 'startx' once you have logged in? If that screws up then it is one of the .directories or .files in your /home directories. Look for the candidates and rename them one at a time ( mv .dir .dir.xxx ) and back again until you have the culprit. When you install 9.2, what I would do is (as root): format your spare partition with the Filesystem of your choice mount it as (for example) /mnt cd /home tar cf - . (cd /mnt; tar xf - ) edit /etc/fstab to point /home at the place you copied it to cd / umount mnt mv home oldhome mkdir home mount /home and once you have made sure that /home is fine, install 9.2 with /home as the partition you copied it to. That 'tar cf - . . .' line came from the O' Reilly Linux beginners book (I forget it's name) and it is a thing of beauty I have been using for years. It does not handle shambolic links across partitions correctly (I think) but that is hardly going to affect you here. -- opinions personal, facts suspect. http://home.arcor.de/36bit/samba.html
participants (4)
-
Andrew Williams -
Daniel Eckl -
Mel Andres -
Richard Bos