Bug 193228

Summary: Users cannot login to gnome or kde after building kernel from source
Product: [Fedora] Fedora Reporter: fizzyfanta
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-18 18:33:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description fizzyfanta 2006-05-26 12:21:03 UTC
Description of problem: After building a kernel from source, whether an fc5 
source rpm or kernel.org tar.bz2 regular users cannot login to gnome or kde.

Version-Release number of selected component (if applicable):


How reproducible: Constantly


Steps to Reproduce:
1.Download kernel source from kernel.org 
2.extract, make menuconfig, make rpm
3.rpm -ivh kernelname.rpm
4.mkinitrd initrd-kernelname.img kernelname
5. edit gurb.conf, add kernelname to menu and set as default
6. Reboot

Actual results: System will boot normally, to login acreen. Enter user name 
and password, and enter / click on login. Screen will flicker, GDM will fail 
to start and return the user to the login screen.

However login as root and you will be taken to your desktop environment.

Expected results: Regular Users should be able to login to desktop.


Additional info: Current workaround, Boot at runtime level 3, login as a 
regular user and issue the command startx. User will successfully be taken to 
their desktop environment. Have not experienced this with FC4.

Comment 1 Ray Strode [halfline] 2008-03-18 18:33:39 UTC
Hi,

We no longer support Fedora Core 5 and I am currently trying to get my open bug
count down to a more manageable state.  I'm going to close this bug as WONTFIX.
 If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?

(this is a mass message)