Fedora 10 on Acer Aspire One : no graphical login after updates
FedoraThis forum is for the discussion of the Fedora Project.
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.
Fedora 10 on Acer Aspire One : no graphical login after updates
After updating my Acer Aspire One via 'yum update' I can no longer log in via the graphical logon screen (gdm).
When I hit ctrl+alt+F2 I can logon via the commandline.
tail /var/secure gives me an output that the logon fails.
Quote:
Feb 26 21:33:44 candy gdm-session-worker[2482]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=candy
Feb 26 21:33:58 candy login: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Feb 26 21:33:58 candy login: ROOT LOGIN ON tty2
Feb 26 21:43:20 candy login: pam_unix(login:session): session closed for user root
rsyslogd: [origin software="rsyslogd" swVersion="3.21.9" x-pid="1865" x-info="http://www.rsyslog.com"] exiting on signal 15.
rsyslogd: [origin software="rsyslogd" swVersion="3.21.9" x-pid="1860" x-info="http://www.rsyslog.com"] restart Feb 26 21:45:30 candy unix_chkpwd[2515]: password check failed for user (candy)
Feb 26 21:45:30 candy gdm-session-worker[2506]: pam_unix(gdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=candy
Feb 26 21:45:42 candy login: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
Feb 26 21:45:42 candy login: ROOT LOGIN ON tty2
UPDATE :
I've added a new user 'testuser' and I am unable to log in with this new user. Not in graphical login, not in commandline...
Last edited by jonaskellens; 02-26-2009 at 03:15 PM.
As root open your /etc/passwd file to see if 'testuser' is really added. Also try to find out what packages got updated, as one or more of these obviously mixed up your system. It is not necessarily gdm who is at fault - the problem is somewhere in the authentication tools.
Yum seems to have some option to undo updates, AFAIK, but I never used that function, so I can't tell the exact way to do it (try Googling on yum undo revert and similar keywords). Other way is to run another update: if one of the updated tools has the bug, then it should already be noticed by a couple of people, so maybe there is a patch already.
I have the same problem on another laptop and on my desktop, both also running Fedora 10.
I thought it might be a global problem... A bug that was not yet reported and fixed.
UPDATE : there were some updates when running 'yum update' that indicated gdm en gdm-user-switch
But my problem of not being able to log in via the graphical interface is not yet solved.
I'm now running in runlevel 3 and starting the x-server manually with 'startx'. This means however that some services and filesystems are not mounted automatically...
Last edited by jonaskellens; 02-27-2009 at 12:15 PM.
... Also try to find out what packages got updated, as one or more of these obviously mixed up your system...
var/log/yum.log :
Quote:
Feb 26 19:35:15 Updated: gvfs-1.0.3-5.fc10.i386
Feb 26 19:35:16 Updated: e2fsprogs-libs-1.41.4-1.fc10.i386
Feb 26 19:35:16 Updated: libgcrypt-1.4.4-1.fc10.i386
Feb 26 19:35:17 Updated: system-config-printer-libs-1.0.15-1.fc10.i386
Feb 26 19:35:18 Updated: hal-cups-utils-0.6.19-1.fc10.i386
Feb 26 19:35:18 Updated: libgcrypt-devel-1.4.4-1.fc10.i386
Feb 26 19:35:24 Updated: gparted-0.4.3-1.fc10.i386
Feb 26 19:35:25 Updated: e2fsprogs-1.41.4-1.fc10.i386
Feb 26 19:35:25 Updated: gvfs-archive-1.0.3-5.fc10.i386
Feb 26 19:35:25 Updated: gvfs-smb-1.0.3-5.fc10.i386
Feb 26 19:35:25 Updated: gvfs-obexftp-1.0.3-5.fc10.i386
Feb 26 19:35:26 Updated: gvfs-gphoto2-1.0.3-5.fc10.i386
Feb 26 19:35:26 Updated: gvfs-fuse-1.0.3-5.fc10.i386
Feb 26 19:35:39 Updated: gstreamer-plugins-good-0.10.13-1.fc10.i386
Feb 26 19:35:40 Updated: 1:wpa_supplicant-0.6.4-3.fc10.i386
Feb 26 19:35:40 Updated: crontabs-1.10-26.fc10.noarch
Feb 26 19:35:41 Updated: 6:kdelibs-common-4.2.0-15.fc10.i386 Feb 26 19:35:41 Updated: xorg-x11-server-common-1.5.3-13.fc10.i386
Feb 26 19:35:44 Updated: system-config-printer-1.0.15-1.fc10.i386
Feb 26 19:35:44 Updated: fontpackages-filesystem-1.20-1.fc10.noarch
Feb 26 19:35:56 Updated: 6:kdelibs-4.2.0-15.fc10.i386 Feb 26 19:35:57 Updated: xorg-x11-server-Xorg-1.5.3-13.fc10.i386 Feb 26 19:35:58 Updated: anacron-2.3-66.fc10.i386
Feb 26 19:35:58 Updated: rpm-libs-4.6.0-1.fc10.i386
Feb 26 19:35:59 Updated: rpm-4.6.0-1.fc10.i386
Feb 26 19:36:00 Updated: rpm-build-4.6.0-1.fc10.i386
Feb 26 19:36:00 Updated: rpm-python-4.6.0-1.fc10.i386
Feb 26 19:36:08 Updated: rpm-4.6.0-1.fc10.i386
Feb 27 18:29:08 Updated: 2:libpng-1.2.35-1.fc10.i386 Feb 27 18:29:31 Updated: 1:gdm-2.24.1-4.fc10.i386
Feb 27 18:29:31 Updated: 2:ntfs-3g-2009.2.1-2.fc10.i386
Feb 27 18:29:35 Updated: pygtk2-2.13.0-3.fc10.i386
Feb 27 18:29:36 Updated: libmusicbrainz3-3.0.2-4.fc10.i386 Feb 27 18:29:36 Updated: xorg-x11-drv-evdev-2.1.3-1.fc10.i386
Feb 27 18:29:36 Updated: pygtk2-libglade-2.13.0-3.fc10.i386
Feb 27 18:29:37 Updated: 2:libpng-devel-1.2.35-1.fc10.i386 Feb 27 18:29:37 Updated: 1:gdm-user-switch-applet-2.24.1-4.fc10.i386
Feb 27 18:29:38 Updated: setup-2.7.4-4.fc10.noarch
Can maybe someone also post his yum logs ??
Last edited by jonaskellens; 02-27-2009 at 12:55 PM.
When you are on cli and do a startx... I assume you get an error starting X.(That was what was happening in my case).
I have my laptop configured for dual screen so I need those "Virtual" entries in my xorg.conf.
Upon digging in the error logs /var/X... I found that it wasnt able to detect the modes for my laptop screen LVDS.
That brought me to xorg.conf because this is where you let X know about modes.
If you're getting *some* error while doing startx... then it would be great if you post the logs from /var/X...
The exact log name will be given in the error that is displayed.
When you are on cli and do a startx... I assume you get an error starting X.(That was what was happening in my case).
I have my laptop configured for dual screen so I need those "Virtual" entries in my xorg.conf.
Upon digging in the error logs /var/X... I found that it wasnt able to detect the modes for my laptop screen LVDS.
That brought me to xorg.conf because this is where you let X know about modes.
If you're getting *some* error while doing startx... then it would be great if you post the logs from /var/X...
The exact log name will be given in the error that is displayed.
-Sisir
Startx gives me no error... it works fine, like I stated earlier.
I have some new information :
I changed the password of my user 'jonas' from 'jonas' to 'jonaskl'. Now, neither of my passwords work. I can not log in graphically, neither via the commandline.
I'm now logged in as root, cause that's the only way I can get into my system. I guess if I change the password of my root also, I'm totally locked out !
The change of password was writen to the /etc/shadow -file :
See if fiddling around with System->Administrator->Users and Groups in Gnome helps.
Tried doing that indeed. But that did not change anything.
If there's a way of deleting the password, so I do not need to authenticate myself, there may be a way around.
However, deleting a password is not permitted. A password must be given on creation of a new user or when deleting the password of an existing user also a password must be given.
Tried editing /etc/shadow... read-only... even for root.
What I noticed in my /etc -directory was that there's a gshadow and a gshadow- file. Don't know which one is actually used and by what program but in one file my testuser exists, in the other my user 'testuser' does not appear.
Don't know which passwords are used here...
started up again in runlevel 5 and at graphical logon screen I changed my keyboard settings...
Guess what... we're back in business. Seemed to be the key-layout after all. Just didn't change it at the right place...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.