Bug 746594

Summary: init 5 from runlevel 3 boot aborts all tty sessions
Product: [openSUSE] openSUSE 12.2 Reporter: Felix Miata <mrmazda>
Component: BasesystemAssignee: Frederic Crozat <fcrozat>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: jeffm, lmuelle, pth
Version: Factory   
Target Milestone: ---   
Hardware: PC   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: 12.2M1 y2logs from host big31

Description Felix Miata 2012-02-11 20:00:09 UTC
Created attachment 475750 [details]
12.2M1 y2logs from host big31

To reproduce:
1-boot with 3 on Grub cmdline
2-login on tty(s) (I did tty2 & tty3, started mc on tty2, did 'init 5' on tty3)
3-'init 5'

Actual results:
1-KDM appeared on tty7
2-screen cleared to login prompt on tty2
3-screen cleared to login prompt on tty3

Expected results:
1-KDM appeared on tty7
2-mc remained running on uncleared tty2
3-shell prompt remained on uncleared tty3

Notes:
1-splashy not installed
2-bootsplash not installed
3-gfxboot is installed
Comment 1 Felix Miata 2012-02-11 20:27:12 UTC
After logging back in on a tty, 'init 3' not only shuts down KDM, it aborts all tty sessions.
Comment 2 Jeff Mahoney 2012-03-06 08:09:59 UTC
This isn't a kernel issue - it's a systemd issue.
Comment 3 Frederic Crozat 2012-03-06 10:56:36 UTC
similar bug on fedora : https://bugzilla.redhat.com/show_bug.cgi?id=708537
Comment 4 Frederic Crozat 2012-04-24 15:45:21 UTC
I've included a fix for 12.1 in systemd package available at home:fcrozat:systemd , please test.
Comment 5 Felix Miata 2012-04-24 17:29:11 UTC
I reported this against 12.2. I have no 12.1 systems using systemd. On host big31 reporting 12.2M3 I just installed systemd and systemd-sysvinit from that repo, and rebooted.

# rpmqa systemd
systemd-44-4.1.i586
systemd-presets-branding-openSUSE-0.1.0-10.1.noarch
systemd-sysvinit-44-4.1.i586

I tried startx, but X aborted without starting KDE, and no tty sessions were terminated. Then I did init 5, which started KDM, which in turn aborted all tty sessions.
Comment 6 Frederic Crozat 2012-04-25 08:35:46 UTC
and I only talked about 12.1, not 12.2. I've pushed similar patch in Base:System / systemd today.

closing as fixed
Comment 7 Felix Miata 2012-04-25 08:51:08 UTC
.
Comment 8 Felix Miata 2012-04-25 08:55:05 UTC
Nothing you've written explains to me how 12.2 is fixed or why when I tested your home rpms the complaint in this and bug 746595 remained unaddressed. Does "Base:System / systemd" mean 12.2?
Comment 9 Frederic Crozat 2012-04-25 09:04:40 UTC
it is fixed because the package in Base:System/systemd will be pushed to Factory.
Comment 10 Bernhard Wiedemann 2012-05-03 12:00:07 UTC
This is an autogenerated message for OBS integration:
This bug (746594) was mentioned in
https://build.opensuse.org/request/show/116331 Factory / systemd
Comment 11 Frederic Crozat 2012-05-25 11:52:49 UTC
pushed to maintenance team : mr#122366 for openSUSE 12.1
Comment 12 Swamp Workflow Management 2012-05-30 14:08:48 UTC
openSUSE-RU-2012:0664-1: An update that has four recommended fixes can now be installed.

Category: recommended (low)
Bug References: 727771,746594,746595,747931
CVE References: 
Sources used:
openSUSE 12.1 (src):    systemd-37-3.14.1, systemd-gtk-37-3.14.1
Comment 13 Frederic Crozat 2013-03-11 15:17:21 UTC
*** Bug 727236 has been marked as a duplicate of this bug. ***