From owner-freebsd-ports  Thu Oct  2 22:51:03 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA20014
          for ports-outgoing; Thu, 2 Oct 1997 22:51:03 -0700 (PDT)
Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA19823;
          Thu, 2 Oct 1997 22:49:32 -0700 (PDT)
Received: from fang.dsto.defence.gov.au (fang.dsto.defence.gov.au [131.185.2.5]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id PAA25373; Fri, 3 Oct 1997 15:17:37 +0930 (CST)
Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111])
	by fang.dsto.defence.gov.au (8.8.5/) with ESMTP id PAA22151;
	Fri, 3 Oct 1997 15:18:04 +0930 (CST)
Received: from dsto.defence.gov.au (localhost [127.0.0.1])
	by eddie.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id PAA27907;
	Fri, 3 Oct 1997 15:18:03 +0930 (CST)
Message-ID: <34348712.F0962930@dsto.defence.gov.au>
Date: Fri, 03 Oct 1997 15:18:02 +0930
From: Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au>
Organization: Defence Science Technology Organisation
X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 3.0-970618-SNAP i386)
MIME-Version: 1.0
To: freebsd-current@freebsd.org, ports@freebsd.org
Subject: xlock: caught signal 8 while running galaxy mode.
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Does anyone else have this problem or can anyone confirm that it
will be solved by a newer incarnation of -CURRENT or a newer
xlockmore ?

I run xlockmore-4.02 on a somewhat dated FreeBSD 3.0-CURRENT now
(3.0-970618-SNAP).

I always use the galaxy mode for screen locking (because I love it!)
and it often dies with the following error in my
.xsession-errors file:

"xlock: caught signal 8 while running galaxy mode."

Signal 8 appears to be a floating point exception (FPE) according to
kill -l.

I'm finding I can't rely on the screen being locked when I leave my
office.

Could this be a Pentium FPU bug ??  Dmesg output for my CPU:

CPU: Pentium (99.72-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x526  Stepping=6
  Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>

I will get around to updating my -CURRENT soon (maybe not that soon
given the recent instabilities with NFS client) and my installed
ports.  (I've got to work out the socks support for cvsup first
before I can keep my ports collection up to date easily).

Please reply directly as this address is not subscribed to the
current list.

-- 
 Matthew Thyer                                 Phone:  +61 8 8259 7249
 Corporate Information Systems                 Fax:    +61 8 8259 5537
 Defence Science and Technology Organisation, Salisbury
 PO Box 1500 Salisbury South Australia 5108