Workaround: KDE 3.3 startup problem

[Alex de Kruijff]

On Sat, Sep 04, 2004 at 12:32:52AM +0200, Alex de Kruijff wrote:
> Hi,
> 
> I've updated my system to kde 3.3. This all when well. Then I had some
> problem with startin it and deceded to start with a new desktop. I.e.
> new home directory, and removing every other kde file related to my
> user. This worked and I was able to login a couple times. Now i'm in the
> middle of reconfiguring my system and I can't login anymore. The last
> thing I did was enabling KDE socks (client) for kopete (which seems to
> be broken since kopete isn't able to load). I don't have a clue what to 
> do next. (I'm used configuring kde from within kde.) I was kinda hoping 
> any of you whould.
> 
> 
> This is the output from 'startx':
> 
> XFree86 Version 4.4.0
> Release Date: 29 February 2004
> X Protocol Version 11, Revision 0, Release 6.6
> Build Operating System: FreeBSD 5.2.1 i386 [ELF]
> Current Operating System: FreeBSD alex.lan 5.2.1-RELEASE-p4 FreeBSD
> 5.2.1-RELEAS
> E-p4 #0: Sat Apr  3 00:59:35 CEST 2004
> akruijff at alex.lan:/temp/obj/disk/worl
> d/src/sys/I686 i386
> Build Date: 02 September 2004
> Changelog Date: 29 February 2004
>         Before reporting problems, check http://www.XFree86.Org/
>         to make sure that you have the latest version.
> Module Loader present
> Markers: (--) probed, (**) from config file, (==) default setting,
>         (++) from command line, (!!) notice, (II) informational,
>         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/XFree86.0.log", Time: Sat Sep  4 00:17:34 2004
> (==) Using config file: "/etc/X11/XF86Config"
> Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing
> from li
> st!
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
> from li
> st!
> startkde: Starting up...
> QPixmap: Cannot create a QPixmap when no GUI is being used
> QPixmap: Cannot create a QPixmap when no GUI is being used
> kdeinit: Communication error with launcher. Exiting!
> Warning: connect() failed: : Connection refused
> KWrited - Listening on Device /dev/ttyp3
> ^C
> waiting for X server to shut down ksmserver: Fatal IO error: client
> killed
> kded: Fatal IO error: client killed
> GOT SIGHUP
> startkde: Shutting down...
> Warning: connect() failed: : Connection refused
> Error: Can't contact kdeinit!
> startkde: Running shutdown scripts...
> startkde: Done.
> 

I found a workaround. Edit the file ~/.kde/config/kdeglobals and set
SOCKS_enable to false.


-- 
Alex

Articles based on solutions that I use:
http://www.kruijff.org/alex/FreeBSD/