On Monday 14 March 2005 12:27, Joseph Mpora wrote: > I mainly use GNOME (so take my advice with a pinch of salt). > > I just delete .kde* from my home folder everytime I mess up KDE (fairly > often) and the next time I log in, everything is back to the default. > Warning: this will mess up any customisations you have done to your KDE > session (maybe even your kmail; --don't know, I use evolution---). Use it > as a last resort. Well, this will reset all your local kde settings. Next time you log in will be as if it s your first time. Yeah, this includes kmail. (I think, all kde applications)
-- Jonathan Kizito Chief Technical Officer, Socnet Solutions Ltd BIFRO HOUSE, Block 86, Plot 24, Sir Apollo Kaggwa Rd. P. O. Box 8135, Kampala, Uganda. URL: www.socnetsolutions.com Tel: +256-41-576785(O) +31-6-48368330(M) +31-50-5774753(H) > Joseph > > -----Original Message----- > From: Robert Itwara Busingye <[EMAIL PROTECTED]> > To: Linux Users Group Uganda <[email protected]> > Date: Mon, 14 Mar 2005 13:58:31 +0300 > Subject: Re: [LUG] Trouble Logging in on SUSE 9.1 > > > Did you try that? Removing your .xinitrc and see if it solved the > > problem? This sounds like an adulterated config file. > > > > Proof of concept: create a temporary directory in your home and move > > everything there (including hidden files & directories). Login in to > > see > > if the problem goes away. But first try the above. > > > > Busingye. > > > > On Mon, 2005-03-14 at 13:19, Ndaula Ahmed wrote: > > > New accounts work but after some time, they also goes to the same > > > behaviour........ > > > > > > Regards, > > > Ndaula Ahmed > > > > > > > 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/ > > > > > > _______________________________________________ > > > 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/ _______________________________________________ LUG mailing list [email protected] http://kym.net/mailman/listinfo/lug %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
