From nobody@FreeBSD.ORG  Wed Oct 18 02:46:43 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id AC1E737B4E5; Wed, 18 Oct 2000 02:46:43 -0700 (PDT)
Message-Id: <20001018094643.AC1E737B4E5@hub.freebsd.org>
Date: Wed, 18 Oct 2000 02:46:43 -0700 (PDT)
From: certhas@ausworld.net
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: X-Windows broken
X-Send-Pr-Version: www-1.0

>Number:         22077
>Category:       bin
>Synopsis:       X-Windows broken
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 18 02:50:00 PDT 2000
>Closed-Date:    Thu Nov 30 12:36:05 PST 2000
>Last-Modified:  Thu Nov 30 12:36:41 PST 2000
>Originator:     Andrew Johnson
>Release:        4.1.1
>Organization:
>Environment:
>Description:
When trying the 4.1.1 Release I've installed & configured X-Windows. Started X with an user account and it's fine. Then I reboot & attempt to use startx again.
 This has been repeated with Trident and ATI video cards.

 X-Windows gets as far as setting the FontPath after which it then reports:
 Fatal server error:
 xf86OpenConsole: KDENABIO failed (Operation not permitted)

>How-To-Repeat:
Do an install and try to run X-Windows/KDE a second time.
>Fix:


>Release-Note:
>Audit-Trail:

From: P Kern <pak@utcc.utoronto.ca>
To: freebsd-gnats-submit@FreeBSD.org, certhas@ausworld.net
Cc: pak@utcs.utoronto.ca
Subject: Re: bin/22077: X-Windows broken (KDENABIO error)
Date: Wed, 18 Oct 2000 20:38:01 -0400

 Hi.
 I got the same error (KDENABIO).
 I was able to get the Xserver working again by adding  ...
 	kern_securelevel_enable="NO" 
 in my /etc/rc.conf file.
 
 (the KDENABIO error seems to come from within /sys/dev/syscons/syscons.c
 -- ie. if (securelevel > 0) .... etc. etc).
 
 Hope this helps.
 pak.
 
State-Changed-From-To: open->closed 
State-Changed-By: alfred 
State-Changed-When: Thu Nov 30 12:36:05 PST 2000 
State-Changed-Why:  
User should not enable high securelevel without realizing implications. 
Lowering securelevel should fix this problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=22077 
>Unformatted:
