Bug 441115 - init 3 does not kill X
Summary: init 3 does not kill X
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: upstart
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Casey Dahlin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-06 12:22 UTC by Need Real Name
Modified: 2014-06-18 08:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-09 21:34:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Need Real Name 2008-04-06 12:22:11 UTC 
Switching to runlevel 3 does not kill X.
Comment 1 Casey Dahlin 2008-04-06 19:05:40 UTC 
Could you please verify your version? We had this bug previously and it had
fixed it.
Comment 2 Need Real Name 2008-04-06 19:11:20 UTC 
upstart-0.3.9-15.fc9.i386
Comment 3 Bill Nottingham 2008-04-07 16:12:33 UTC 
How are you starting X? What display manager (not that it *should* matter, but...)
Comment 4 Warren Togami 2008-04-07 17:08:19 UTC 
upstart-0.3.9-15.fc9.x86_64

Just tested this switching between init 5 and init 3.  It seems to be doing the
right thing here.
Comment 5 Casey Dahlin 2008-04-09 20:21:43 UTC 
Looks good to me too. What version of event-compat-sysv? What's the output of
/sbin/initctl status prefdm before and after init 3?
Comment 6 Need Real Name 2008-04-09 21:11:25 UTC 
Almost works now, X exits, but I don't see the init script messages as I should.
Comment 7 Casey Dahlin 2008-04-09 21:21:24 UTC 
Is what you are now seeing potentially the same as this issue? :

https://bugzilla.redhat.com/show_bug.cgi?id=439699

If so, I'll mark this as a duplicate and have you CC'd in on that bug.
Comment 8 Need Real Name 2008-04-09 21:31:10 UTC 
Yes, but this bug is not a duplicate, this bug has been fixed, so I will add
myself to that bug, and this bug can be closed.
Comment 9 Casey Dahlin 2008-04-09 21:34:58 UTC 
Ok then.
Note You need to log in before you can comment on or make changes to this bug.