From owner-freebsd-questions  Mon Aug 14 12: 6:16 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from smtp.screaming.net (smtp.screaming.net [212.49.224.20])
	by hub.freebsd.org (Postfix) with ESMTP id 907A137BE46
	for <questions@freebsd.org>; Mon, 14 Aug 2000 12:06:10 -0700 (PDT)
	(envelope-from bigotfo@bigfoot.com)
Received: from lexx.my.domain (dyn254-ras27.screaming.net [212.49.250.254])
	by smtp.screaming.net (8.9.3/8.9.3) with SMTP id TAA29260
	for <questions@freebsd.org>; Mon, 14 Aug 2000 19:08:38 GMT
From: John Murphy <bigotfo@bigfoot.com>
To: questions@freebsd.org
Subject: SV (was TkDesk will not start as normal user)
Date: Mon, 14 Aug 2000 20:05:48 +0100
Organization: The Organisation
Reply-To: bigotfo@bigfoot.com
Message-ID: <UD+YOd+kBSIQt2hPe3MlGYzeyVSQ@4ax.com>
X-Mailer: Forte Agent 1.6/32.525
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Previously:
>> FreeBSD-4.1 Release, XFree86-4.0.1, TkDesk-1.2 pkg.
>>=20
>> TkDesk starts fine if started by root, but as user john (wheel & =
network)
>> no go.  As root or as john su'd it creates a directory in /tmp as
>> tkdeskPID where PID is the number of the tkdesk process.
>> (/tmp is a symbolic link to /usr/tmp)

The fix is to (as root) chmod go+w /var/tmp !


The error causing the problem was not generated by tkdesk.  Further back
in the error messages was:

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error: Cannot open "/var/tmp/server-0.xkm" to write keyboard =
description
> Exiting
Couldn't load XKB keymap, falling back to pre-XKB keymap

X started ok regardless.  Fvwm would start ok if required, but Tkdesk =
picks
up the error with (presumably) the following code:


# Temp dir to use by this TkDesk:
set tkdesk(tmpdir) /tmp/tkdesk[pid]
set err [catch {
    exec rm -rf $tkdesk(tmpdir)
    exec mkdir $tkdesk(tmpdir)
} errmsg]
if {$err} {
    puts stderr "TkDesk: Couldn't create temp dir $tkdesk(tmpdir)"
    puts stderr "TkDesk: errmsg: $errmsg"
    puts stderr "TkDesk: Exiting"
    exit 1
}


The exit 1 brings down the X server.

I'm quite surprised by this behaviour.  It's my fault for not clearing/
noticing the X error, but shouldn't tkdesk clear any previous errors
before the catch, or something?

John.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message