New accounts work, you said! rm ~/.xinitrc and try logging in. I've had Yahoo Messenger break my .xinitrc before -- don't know which other applications do that.
Busingye. On Mon, 2005-03-14 at 12:11, Ndaula Ahmed wrote: > Hey, > > I have really tried all you have sent to me but still yet to resolve the > problem.... > > The time it failed to login, I went to the menu and selected all apart > from failsafe but things failed not until I selected the option of > Failsafe and fed in ma password.....then it finally opend a small window > where I typed the command startkde to start the KDE window. > > This worked well and took me the KDE window but small window still > existing that once you closs it, it finally completely logs out of the > system and you need to re-asign again..... > > Infact I get the following error in that small window; > > ***************************************************** > Hey, > > Below is the error that's displayed when I use FailSafe to force the > system to log me to the KDE. Without running the startkde command, it > can't proceed..... And when I run the KDE, this is the error that it > displays but proceeding to the KDE window; > > **************************************************** > konqueror: WARNING: KGenericFactory: instance requested but no instance > name passed to the construction > > X Error: BadWindow ( Invalid Window parameter) 3 > Major opcode: 20 > Minor opcode: 0 > Resource id: 0x3e002a6 > > X Error: BadWindow ( invalid Window parameter) 3 > Major opcode: 20 > Minor id: 0x3e00a6 > > konqueror: WARNING: KGenericFactory: instance requested but no instance > name passed to the construction! > > Kio ( KIOConnection): ERROR: Could not write data > > konqueror: WARNING: KGenericFactory: instance requested but no instance > name passed to the construction! > ******************************************************* > > Looking forward to hearing and solving this problem together. > > > Regards, > Ndaula Ahmed > > > Personally, I prefer starting from the simplest remedies. > > 1. On the splash screen where you enter your username and password, there > > are > > a number of options. Go to the menu option and restart KDE. In my case it > > has > > solved that problem on a number of boxes. > > 2. If that still doesn't sort it out, I suggest switching to runlevel 3 > > and > > running sax2. I did this once on one that refused to respond to 1 above. > > Hope this helps. > > > > On Friday 11 March 2005 14:28, Fred Bbaale wrote: > >> Tricky one there buddy , but my first take would be for you to check the > >> system log.(/var/log/messages parhaps). You could also cech the shell > >> you > >> are using , but then you say you are able to login and then it just > >> stops > >> after sometime. > >> > >> I would also think of you looking at the /etc/login.defs or you can use > >> the > >> YaST tool to check your security settings. Do you use any PAM > >> mechanisms ? > >> > >> But as I said it is a tricky one , but you could start with that . > >> > >> > >> Regards , > > > > -- > > ************************************************************************ > > Lule George William (Mr) > > Network and Systems Administrator > > Uganda Martyrs University, Nkozi > > P.O. Box 5498 Kampala > > Uganda > > /* If you are not living and learning, then you are dumb and dying*/ > > _______________________________________________ > > LUG mailing list > > [email protected] > > http://kym.net/mailman/listinfo/lug > > %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ > > > > _______________________________________________ > LUG mailing list > [email protected] > http://kym.net/mailman/listinfo/lug > %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/ _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
