Red Hat Bugzilla – Bug 447352
Unable to log on with existing or new user after yum upgrade from F8 to F9 (KDE and terminal)
Last modified: 2008-07-28 16:39:38 EDT
Description of problem:
The login/password is refused under terminal or KDE, for existing or new user,
after yum upgrade from F8 to F9.
Version-Release number of selected component (if applicable):
rpm -qa |grep -i kde
rpm -qa |grep -i kde
Upgrade from F8 to F9, and try to log in with no-root user.
Steps to Reproduce:
1. Update fedora-release-*.noarch.rpm and livna-*.rpm
2. Other steps from http://fedoraproject.org/wiki/YumUpgradeFaq
3. yum upgrade
No log-in possible but for the root user.
No log-in issue
There is still problem even having changed the password, having created another
user, and having tried with QWERTY or AZERTY keyword configurations.
kdebase-workspace is present, anything in /var/log/messages or ~/.xsession-errors ?
It is very strange, after reboot (I'm working into VMware), there is absolutely
no more log-in problem. It is a good news because it is finally not so "highly
important" but I ensure this problem was real when I post this report.
The only interesting differences I see between the day I report, and now are :
- have removed the existing user and created a new one (with same name, home
It could be explained for the existing user (in case there would be a problem
with existing files (from kde for instance)), for there was a problem with just
created user, and I have performed the test a new time, and it is perfectly
There may have been something broken, which has been automatically "cleaned up"
after reboot. It is hard to say.
I'm going to attach my full /var/log/messages file.
Created attachment 306230 [details]
The full /var/log/messages since the OS has been installed, then upgraded
Have not seen any other bugs filed in regard to this issue. How do you want to
proceed Rex, Kevin or Than?
With the impending release of KDE4.1 going to close this bug. If after
upgrading you find this is still an issue please feel free to reopen this bug.