John_Phillips Posted March 22, 2010 Report Share Posted March 22, 2010 Was running KDE 4.4.0 on Mandrviva 2010 Powerpack. Installed KDE 4.4.1 using the command lines as previously recommended. Boots up ok, but the log in screen is now the issue. As well as myself as user, it ists "nobody", "adm"; "bin"; "daemon"; "games"; "mail"; "news" etc as users with password. I log in with my name and password, get error message : "A critical error occurred. Please look at KDM's logfile (s) for more information ....etc" How do I look at this logfile if I can't log in? More importantly, what can I do to enable me to log in? Pretty new to Linux, so I hope I can solve this with some help so I can keep running it. All help greatfully received, please be knd as I am a new user! And please excuse the spelling, spell checker not working on this rudimentary version of Windows 7! Quote Link to comment Share on other sites More sharing options...
speedball2 Posted March 22, 2010 Report Share Posted March 22, 2010 How do I look at this logfile if I can't log in? You can try pressing Ctrl+Alt+F1, login as root and then: less /var/log/kdm.log Quote Link to comment Share on other sites More sharing options...
John_Phillips Posted March 23, 2010 Author Report Share Posted March 23, 2010 Thanks, now all solved. Follows advice from another forum which fixed:- "At the log in screen press ctrl+alt+F2 (through F6, any one of them) and get a non-graphical log in. Then log in as root and run this Code: urpmi icewm It will install any dependencies needed. When that's done it's just easiest to reboot with ctrl+alt+del. When it gets back to the log in screen, click the pencil and paper icon and change (select) to icewm for the session, then log in as your normal user. Run mcc ("configure your computer") and on the "boot" page select "set up display manager." Click the gdm box and OK. (you'lll need to log out at min, but I just reboot, gives me time to grab another coffee =] ) Once back to the log in page you should see a normal set of options, if the error you received is correct in that kdm is the culprit. Note that if gdm is not an option simply install it, either in the package manager or in a terminal (as root):Code: urpmi gdm Once you have a normalized environment you can begin figuring out how to fix it, or if you even want to try to fix it. Nothing wrong with using gdm or xdm, any dm can handle any environment on top of it. The main difference is the default log in/log out options. kdm is more 'user friendly' in this respect, but gdm can be altered to suit your taste." BTW how do I mark topic as "Solved"? Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted March 23, 2010 Report Share Posted March 23, 2010 Edit the first post in full edit mode, and then edit the subject. However, I've done it for you :) Quote Link to comment Share on other sites More sharing options...
John_Phillips Posted March 23, 2010 Author Report Share Posted March 23, 2010 Thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.