Upgrade/update of SuSE 9.1 via red carpet results in login for 9.0 loop.
Today I used red carpet to update my SuSE9.1/KDE3.3. That resulted in a reboot that turned into a loop. The login screen showed SuSE9.0 and wouldnt let me login as user OR root. I had to boot with the rescue disk, go into INIT 3 and using yast, reinstall kde3. All my sources are for 9.1 so I dont know where or how it got me into 9.0 login screen. Interestingly, it killed my networking ability until I did the reinstall from the cd's. Has anyone else had a similar problem? My current solution is to get rid of red carpet and use Yast & apt exclusively. richard -- Old age ain't for Sissies!
On Friday, 8 October 2004 04.41, Richard wrote:
Today I used red carpet to update my SuSE9.1/KDE3.3. That resulted in a reboot that turned into a loop. The login screen showed SuSE9.0 and wouldnt let me login as user OR root.
I had to boot with the rescue disk, go into INIT 3 and using yast, reinstall kde3. All my sources are for 9.1 so I dont know where or how it got me into 9.0 login screen.
What does it say in your /etc/SuSE-release Also, that text on kdm is just that: text. You should have checked the rpm versions (rpm -qi kdebase3 for example, and check what it says for "Distribution" at the bottom) As for why you couldn't log in, well, you should have looked in /home/<username>/.xsession-errors and /var/log/kdm.log and /var/log/messages to see what went wrong. You could do this in text mode right after a failed login. If you really did get 9.0 packages, that is extremely odd, I have never seen that. The only way I could imagine that happening is if your SuSE-release said 9.0, or if the apt repositories were screwed up
On Thursday 07 October 2004 09:48 pm, Anders Johansson wrote:
On Friday, 8 October 2004 04.41, Richard wrote:
Today I used red carpet to update my SuSE9.1/KDE3.3. That resulted in a reboot that turned into a loop. The login screen showed SuSE9.0 and wouldnt let me login as user OR root.
I had to boot with the rescue disk, go into INIT 3 and using yast, reinstall kde3. All my sources are for 9.1 so I dont know where or how it got me into 9.0 login screen.
What does it say in your /etc/SuSE-release SuSE 9.1 (586)
Also, that text on kdm is just that: text. You should have checked the rpm versions (rpm -qi kdebase3 for example, and check what it says for "Distribution" at the bottom)
As for why you couldn't log in, well, you should have looked in /home/<username>/.xsession-errors and /var/log/kdm.log and /var/log/messages to see what went wrong.
I just looked at my 32 meg .xsession-errors and see a huge amount of kbluetoothd errors: HciSocket:: open(): error creating socket. which is interesting since I dont have any bluetooth stuff.
You could do this in text mode right after a failed login.
It was in a continuous loop so I never got to the any login prompt til I used the rescue disk. At that point it indicated some file errors which couldnt be fixed automagically so I decided to start yast and redo kde. But first I tried to get the network to work but nothing would go. Ifconfig got me nothing but the localhost and wouldn't fire up eth0.
If you really did get 9.0 packages, that is extremely odd, I have never seen that. The only way I could imagine that happening is if your SuSE-release said 9.0, or if the apt repositories were screwed up
I looked at the apt sources and the yast settings and they both were pointed at suse 9.1. The end result was a reinstall of kde3 followed by an online update by Yast and everything was back to normal. Thanks Anders for the pointers. Am off for a week for holiday so will address this when I return. Glad to have you back. Nice to hear a sane voice in the Linux wilderness. Regards, Richard -- Old age ain't for Sissies!
Richard, On Friday 08 October 2004 22:16, Richard wrote:
...
I just looked at my 32 meg .xsession-errors and see a huge amount of kbluetoothd errors: HciSocket:: open(): error creating socket. which is interesting since I dont have any bluetooth stuff.
I just noticed those in my .xsession-errors file, too (likewise, I have no Bluetooth hardware on this system). I'd like to get rid of them (i.e., turn of whatever is generating them), but when I went into the Control Center and activated the Bluetooth module, I got an error alert. This hasn't been a big enough problem for me to look into further. If someone were to drop the answer on me, I'd use it. Otherwise, this will have to become a bigger problem then simple log file bloat to get me to put more effort into diagnosing the problem and finding a solution.
...
Regards, Richard -- Old age ain't for Sissies!
Being a sissy isn't for sissies! Randall Schulz
On Saturday, 9 October 2004 07.16, Richard wrote:
On Thursday 07 October 2004 09:48 pm, Anders Johansson wrote:
On Friday, 8 October 2004 04.41, Richard wrote:
Today I used red carpet to update my SuSE9.1/KDE3.3. That resulted in a reboot that turned into a loop. The login screen showed SuSE9.0 and wouldnt let me login as user OR root.
I had to boot with the rescue disk, go into INIT 3 and using yast, reinstall kde3. All my sources are for 9.1 so I dont know where or how it got me into 9.0 login screen.
What does it say in your /etc/SuSE-release
SuSE 9.1 (586)
OK, then the presence of 9.0 on your system is beyond me.
Also, that text on kdm is just that: text. You should have checked the rpm versions (rpm -qi kdebase3 for example, and check what it says for "Distribution" at the bottom)
As for why you couldn't log in, well, you should have looked in /home/<username>/.xsession-errors and /var/log/kdm.log and /var/log/messages to see what went wrong.
I just looked at my 32 meg .xsession-errors and see a huge amount of kbluetoothd errors: HciSocket:: open(): error creating socket. which is interesting since I dont have any bluetooth stuff.
Yeah, .xsession-errors is reset when you log in, so the messages you see there now won't have any bearing on your previous failed login If you don't have any bluetooth you might want to uninstall kdebluetooth, or at least remove kbluetoothd.autostart.desktop from /opt/kde3/share/autostart
You could do this in text mode right after a failed login.
It was in a continuous loop so I never got to the any login prompt til I used the rescue disk.
You mean you couldn't switch to a text login with ctrl-alt-f1?
On Sunday 10 October 2004 10:12 am, Anders Johansson wrote:
On Saturday, 9 October 2004 07.16, Richard wrote:
On Thursday 07 October 2004 09:48 pm, Anders Johansson wrote:
On Friday, 8 October 2004 04.41, Richard wrote:
Today I used red carpet to update my SuSE9.1/KDE3.3. That resulted in a reboot that turned into a loop. The login screen showed SuSE9.0 and wouldnt let me login as user OR root.
I had to boot with the rescue disk, go into INIT 3 and using yast, reinstall kde3. All my sources are for 9.1 so I dont know where or how it got me into 9.0 login screen.
What does it say in your /etc/SuSE-release
SuSE 9.1 (586)
OK, then the presence of 9.0 on your system is beyond me.
I updated all my linux systems when 9.1 came out. One of them shows SuSE 9.0 in the login screen. I was concerned at the time and asked the list how to tell what version of SuSE is actually loaded. But the reboot loop didn't happen to me. Jerome
participants (4)
-
Anders Johansson -
Jerome Lyles -
Randall R Schulz -
Richard