Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hope I can get some help with this problem. I upgraded my Fedora Core 4 to KDE 3.5 and I cannot log back in on my user account screen. There is one other user who can log in fine (as well as root). The log in photo is gone but my name and log-in name are shown. When I try to log in it goes to a blue screen for thirty seconds and returns to the login screen.
All seemed ok when I rebooted the computer but this has just cropped up.
Anyone with any ideas on how I can restore my log-in?
Probably something in your user's KDE startup files causes a fatal error with the new KDE version. Try archiving your .kde directory and your .kderc (moving them out of your home directory) and logging on. KDE will recreate them.
As mentioned in my last post, after installing KDE 3.5 on redhat update, I cannot log back in. My user name is still on the login screen but the photo has been removed. When I try to login, the screen goes to blue for 30 seconds and returns to the login screen. All other users can log in OK.. When logging in without X (text screen) I can log in fine and can access my files in my home directory, so I have not been removed from the system, just not allowed on the graphical desktop, GNOME or KDE. When I type "startx" I get the following:
Keymap 0: Permission denied
Keymap 1: Permission denied
Keymap 2: Permission denied
Keymap 3: Permission denied
KDSBENT - operation not permitted
Xlib: Connection refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1
giving up
I have been using Linux only for a little while, but this is really strange to me. It seems I have been locked out for some reason.
Probably something in your user's KDE startup files causes a fatal error with the new KDE version. Try archiving your .kde directory and your .kderc (moving them out of your home directory) and logging on. KDE will recreate them.
Try logging on console ALT-CTRL F1 as user or root and try to start KDE using
Code:
Code:
startx
You may need to do something like:
Code:
Code:
# kdm --nodaemon
# pkill kdm
Just not to restart kdm or different diplay manager you use (gdm, xdm)...
after that post content of .xsession-errors file that you find in home directory of affected user.
It may be also helpful if you send content or last 10 lines from /var/log/Xorg.0.log file.
Thanks for all your suggestions, but for some reason the problems lies in a setfont: error at boot time. If I go to a text screen and try to restart, I cannot do it from regular user or root. The setfont error says it is missing libc.so.6(GLIBC_2.4). Any googling to this file leads me to glibc-2.3.93 which is already installed. The bug fix was supposed to be an upgrade to kbd-1.12-12.1, which I did from source rpm, to no affect.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.