NetBSD Problem Report #32271

From yamt@mwd.biglobe.ne.jp  Fri Dec  9 07:28:46 2005
Return-Path: <yamt@mwd.biglobe.ne.jp>
Received: from yamt.dyndns.org (FLA1Aai163.kng.mesh.ad.jp [61.193.102.163])
	by narn.netbsd.org (Postfix) with ESMTP id EF36F63B86D
	for <gnats-bugs@gnats.NetBSD.org>; Fri,  9 Dec 2005 07:28:45 +0000 (UTC)
Message-Id: <1134113295.868823.1399.nullmailer@yamt.dyndns.org>
Date: Fri, 09 Dec 2005 16:28:15 +0900
From: yamt@mwd.biglobe.ne.jp
Reply-To: yamt@mwd.biglobe.ne.jp
To: gnats-bugs@netbsd.org
Subject: xlock kills xserver
X-Send-Pr-Version: 3.95

>Number:         32271
>Category:       kern
>Synopsis:       xlock kills xserver
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 09 07:30:00 +0000 2005
>Originator:     YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
>Release:        NetBSD 3.99.13
>Organization:

>Environment:


System: NetBSD kaeru 3.99.13 NetBSD 3.99.13 (build.kaeru.xen.nodebug) #32: Mon Dec 5 07:11:12 JST 2005 takashi@kaeru:/home/takashi/work/kernel/build.kaeru.xen.nodebug i386
Architecture: i386
Machine: i386
>Description:
	i recently noticed that invoking xlock
	(xlockmore-lite-5.12 from pkgsrc) sometimes kills xserver.
	invoking "xlock -lockdelay 10" several times is enough to
	reproduce the problem.

	because the same /usr/X11R6 and xlock binaries used to work afaik,
	i vaguely suspect that it's due to incompatibility of
	kernel or libraries.  i can provide these binaries if wanted.
>How-To-Repeat:

>Fix:


>Unformatted:

Home	PR Database Search