That fixed "startx".
It did not fix the Graphical Login. Rebooting, failsafe, or no failsafe, when it goes to launch the graphical login it is totally insane still. If I start text mode "kde3 <enter>" and "startx <enter>" both work now after applying your instructions, whereas just "kde3 <enter>" worked before. What is the stuff that kicks off the graphical login ? How does that work exactly ? I'm happy to figure it out if someone just points me at the starting thing that I can trace through... source if necessary. Something in the initrd ? I hate that... ? -AEF On Saturday 10 August 2002 11:02, Charles A Edwards wrote: > On Sat, 10 Aug 2002 10:36:50 -0500 > > allen <[EMAIL PROTECTED]> wrote: > > Somehow I have messed up the graphical boot so that I have to > > boot a failsafe and then "kde3 <enter>" in order for X to work. > > If you are running current cooker this is caused by the last xinitrc > update. > The resulting files were created as rpm.new. > You will need to rename the files created and existing, you should then > be able to login normally from the GUI. > > You can also take the lazy man way and cheat, which is what I did. > rpm -e --nodeps xinitrc > urpmi xinitrc > > All files will then be properly created and named.
