From owner-freebsd-questions@FreeBSD.ORG Fri Feb 25 05:38:35 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A78216A4CE for ; Fri, 25 Feb 2005 05:38:35 +0000 (GMT) Received: from smtp.wiredcity.com.au (adsl-105-192.wiredcity.net.au [203.161.105.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A19D43D49 for ; Fri, 25 Feb 2005 05:38:34 +0000 (GMT) (envelope-from g_glasson@wiredcity.com.au) Received: from kosh.glastech.com.au ([192.168.1.1]) by kosh.glastech.com.au with esmtp (Exim 4.24; FreeBSD 4.8) id 1D4YB6-0000DT-3M; Fri, 25 Feb 2005 13:38:16 +0800 From: Geoff Glasson To: lichtner@9online.fr Date: Fri, 25 Feb 2005 13:38:14 +0800 User-Agent: KMail/1.7.2 References: <20050225051042.CCB7616A57A@hub.freebsd.org> In-Reply-To: <20050225051042.CCB7616A57A@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200502251338.14575.g_glasson@wiredcity.com.au> X-Spam-Score: 0.0 X-Spam-Report: Spam detection software, running on the system "kosh.glastech.com.au", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.onthat( what I believe to be ) the same problem as you, and when I got it running within an xterm I discovered that KDE expects theproblem using the following ( not very efficient ) method: [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description -------------------------------------------------- cc: freebsd-questions@freebsd.org Subject: Re: freebsd-questions Digest, Vol 89, Issue 20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 05:38:35 -0000 Edward, I believe that this problem was discussed on the kde-freebsd mailing list. The simple answer to your problem is that there appears to be a defect in K= DE=20 that causes this to occur. I had ( what I believe to be ) the same problem= =20 as you, and when I got it running within an xterm I discovered that KDE=20 expects the /tmp/.ICE-unix/ directory tree to be owned by root. I fix this= =20 problem using the following ( not very efficient ) method: 1. Attempt a KDE login ( which will create all the .ICE-unix directories=20 before failing ) 2. Login as root using the failsafe session and issue the command chown -R root /tmp/.ICE-unix in an xterm 3. Log out of the failsafe session 4. Log back as the original user I do it this way because it's easier for my wife and kids to use the comput= er=20 by logging in via KDM rather than giving them a shell login. Since my=20 machine doesn't get rebooted very often this is not a drama for me ;) Hope this helps...Geoff On Fri, 25 Feb 2005 01:10 pm, freebsd-questions-request@freebsd.org wrote: > Message: 9 > Date: Thu, 24 Feb 2005 23:00:36 +0100 > From: Edward Lichtner > Subject: How do I get KDM to launch KDE ? > To: > Message-ID: > Content-Type: text/plain; charset=3D"ISO-8859-1" > > Hi, > I selected KDM to run at startup by editing /etc/ttys : > ttyv8 =B3/usr/local/bin/kdm =ADnodaemon=B2 xterm on secure > I also created a .xsession file both in /root and in my home directory wi= th > the line : > exec startkde > When I reboot, KDM starts up but when I login (correct password), the log= in > windows disappears, the KDM background remains and KDE doesn=B9t start. > However, KDE starts fine when I run startx in a terminal session. > Is there something I didn=B9t do properly ? > Thanks, > Edward > > BTW, I use FreeBSD 5.3, Xorg 6.7.0-9, KDE 3.3.0-4 > Geoff Glasson g_glasson@wiredcity.com.au