Bug 34480

Summary: system hangs after killing xinit
Product: Ports & Packages Reporter: Matt Sykes <mattmsykes>
Component: Individual Port(s)Assignee: Eric Anholt <anholt>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Matt Sykes 2002-01-31 10:20:00 UTC 
After killing xinit, switching back to your X console will
leave you with a hung system.  Keyboard is unresponsive, so
you can't type into any xterms which happen to be open and you
can't switch back to a text console.  The mouse works.

Why would I kill xinit?  I have no idea.

How-To-Repeat: 1. startx
2. Ctl+Alt+F2 (some open console)
3. killall xinit
4. Ctl+Alt+F1  (back to your X console)
5. keyboard hung!
6. reluctantly power off your computer and hope for the best
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2002-01-31 10:23:55 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-ports

Mis-filed PR.
Comment 2 Sheldon Hearn freebsd_committer freebsd_triage 2002-01-31 10:24:19 UTC 
Responsible Changed
From-To: freebsd-ports->jmz

Over to maintainer.
Comment 3 jmz freebsd_committer freebsd_triage 2002-07-14 23:28:56 UTC 
Responsible Changed
From-To: jmz->anholt

Switch maintainer.
Comment 4 Eric Anholt 2003-01-10 05:07:25 UTC 
Tried this on a R128 system with 4.2.1 and couldn't reproduce it.  Does
it still happen for you with 4.2.1?  If it does, could you send me a
/var/log/XFree86.0.log from when it's running?

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/dri/     anholt@FreeBSD.org
Comment 5 Eric Anholt freebsd_committer freebsd_triage 2003-01-10 05:20:46 UTC 
State Changed
From-To: open->feedback

Waiting for more information from submitter
Comment 6 Eric Anholt freebsd_committer freebsd_triage 2003-04-06 10:07:20 UTC 
State Changed
From-To: feedback->closed

Feedback timeout (3 months)