From owner-freebsd-questions@FreeBSD.ORG Mon Aug 18 00:15:37 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED3B5106567D for ; Mon, 18 Aug 2008 00:15:37 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 772A38FC21 for ; Mon, 18 Aug 2008 00:15:37 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KUsPD-00028u-V8 for freebsd-questions@freebsd.org; Mon, 18 Aug 2008 00:15:31 +0000 Received: from pool-138-88-159-248.esr.east.verizon.net ([138.88.159.248]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 Aug 2008 00:15:31 +0000 Received: from nightrecon by pool-138-88-159-248.esr.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 18 Aug 2008 00:15:31 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Date: Sun, 17 Aug 2008 20:17:15 -0400 Lines: 47 Message-ID: References: <20080817220431.GA1187@thought.org> <20080817231959.GB3376@thought.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-138-88-159-248.esr.east.verizon.net Sender: news Subject: Re: kde troubles.... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nightrecon@verizon.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2008 00:15:38 -0000 Gary Kline wrote: [snip] > > the err message is gone, but KDE creates an /rmpty kdm.pid and > does nothing. This is not good. The file should contain a number. [snip] It would also be helpful to know how you are trying to run KDE. There are two ways, the first being to have a line like: ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure in /etc/ttys which starts kdm as a graphical login at boot. The other is to boot and login as user, then do the "startx" command which needs "startkde" to be in .xinitrc and/or .xsession in your Home directory. > Nothing else; what else neeeds cleaning? Not sure what got munged with your power glitch, but a couple of times in the past when I've had trouble getting KDE to start I would login as root (or su) without X running and delete some stuff. Look in your user home directory for something like .DCOPserver_hostname_:0; there will be two - one is a link to the other. Delete both of these and delete the ksocket-yourusername folder in /tmp. Also while in /tmp look for .X0-lock and delete. Look for the folders .ICE-unix and .X11-unix and delete all the sockets you find in these two folders. Make note both of these folders should have the sticky bit set. Also delete the /var/run/kdm.pid again like before. This is how I've gotten KDE to start in the past after an "uh-oh". It also may not pertain to your particular situation. One thing you can do to troubleshoot X if you are using "startx" (ie not starting kdm at login with the ttys line above) is to have an empty .xinitrc and/or .xsession. Then when you run X the twm window manager should come up, as it is the default for X. This way you can drive a wedge between "Is it an X problem or a KDE problem?" Good luck and I hope you get it going. -Mike