Just tried the live MS1 of opensuse 11.4 and can’t login.
Anybody know what it takes to get in?
Tried blank/blank, guest/blank, guest/guest, root/blank, root/root
thanks - mike
Just tried the live MS1 of opensuse 11.4 and can’t login.
Anybody know what it takes to get in?
Tried blank/blank, guest/blank, guest/guest, root/blank, root/root
thanks - mike
This should be in Pre-release/Beta forum where you are more likely to find early testers hanging out. Hopefully, a kindly moderator will move this for you.
Kindly moderator moved this.
It should do an autologin, but the username is ‘linux’, AFAIK no password.
I’m having a similar problem. Installed Milestone 1, updated from the factory repo and auto-login takes me to a log in screen. Put in my password and it failed to start KDE and took me back to the log in screen. Created a new user and got the same result.
Same result if I log in as root also.
ditto - tried linux/blank and right back to the same screen.
P.S. I read in the comments at the download site that some intel hw items got fixed. I’m REALLY anxious to see if this fix includes my Intel video.
You’re running a Milestone release…which is under heavy development. So the fix may work, but you’re not even getting to the fix. That’s what can happen with Milestone releases.
This may be the same problem I had. Check bug report 637236. Xwindows was segfaulting and going back to the login screen.
Tom
Having the same problem with the KDE Live CD of 11.4 milestone 2.
It comes up with a Login screen with linux as the user, no password entered and comes back as login failed.
The Gnome Live CD has no login and works great, except for no email app.
Milestone 1 64-bit KDE live disk worked for me; however, no such love for milestone 2. I was able to log in to Icewm and did a system verification, hoping to fix the issue. Still no love.
I had the same problem and was able to solve it by installing the nvidia driver. I believe the problem is with kwin.
I had this issue in Virtualbox, so I don’t think it would quite resolve it specifically for my case. I’m sure it will help others, though. Thanks for the work-around, Pilotgi.