*BSD News Article 10541


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA277 ; Sun, 31 Jan 93 14:00:50 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!swrinde!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!math.fu-berlin.de!mailgzrz.TU-Berlin.DE!news.netmbx.de!Germany.EU.net!mcsun!sun4nl!tuegate.tue.nl!svin09!wzv!gvr.win.tue.nl!guido
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] X broken with new patchkit ?
Message-ID: <4376@wzv.win.tue.nl>
Date: 28 Jan 93 18:42:16 GMT
References: <4374@wzv.win.tue.nl>
Sender: news@wzv.win.tue.nl
Lines: 16

guido@gvr.win.tue.nl (Guido van Rooij) writes:

>I installed the new patchkit a few days ago. I also had keycap-0.1.1 (codrv)
>installed. This used to work fine, but now that I've installed the new
>patchkit, the keyboard isn't functioning quite well anymore when using X.
>Symptoms are that after pressing a key you have to wiat several seconds
>for the key to become visible on your xterm UNLESS you move your mouse..
>then the char immediately shows up. Anyone having the same behaviour?


Solved....it was due to a changed interface in the kernel. This was also
mentioned in another posting. For all of you out there using keycap-0.1.1
I suggest you get the latest buglist (BUGLIST.270193) and apply the
patch mentioned at Bug 15.

-Guido