Mailinglist Archive: opensuse (4020 mails)

[Anders Johansson <andjoh@xxxxxxxxxx>]

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?