From owner-freebsd-current Sat Apr 18 17:54:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13591 for freebsd-current-outgoing; Sat, 18 Apr 1998 17:54:21 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chaotic.ultra.net.au (totally.damaged.org [198.142.63.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA13545 for ; Sun, 19 Apr 1998 00:54:13 GMT (envelope-from simon@chaotic.ultra.net.au) Received: (from simon@localhost) by chaotic.ultra.net.au (8.8.8/8.8.8) id KAA00320 for freebsd-current@freebsd.org; Sun, 19 Apr 1998 10:52:02 +1000 (EST) Message-ID: X-Mailer: XFMail 1.3-beta-041398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sun, 19 Apr 1998 10:52:01 +1000 (EST) Organization: Chaotic Software From: Simon Coggins To: freebsd-current@FreeBSD.ORG Subject: Problems with X windows, and Shared memory Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi I'm running -current last updated FreeBSD chaotic 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Thu Apr 16 19:33:14 EST 1998 I'm seeing the following problems, X windows locks up, and I have to ctrl alt backspace to get out of it, and if I run x windows again the whole machine locks up and I have to reboot. If I edit a file after I ctrl alt backspace then reload xwindows that file i edited is trashed. This problem also arises if I just close down X windows then reload it it'll lock solid and I have power cycle. On a separate note, I saw someone talking about a shared memory problem. I've been experiencing the same problems with Quake, you run quake and it won't free the shared memory I have to do it manually. Regards Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message