[Bug 731594] New: mingetty virtual consoles don't start
https://bugzilla.novell.com/show_bug.cgi?id=731594 https://bugzilla.novell.com/show_bug.cgi?id=731594#c0 Summary: mingetty virtual consoles don't start Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: antoine.mechelynck@belgacom.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111120 Firefox/11.0a1 SeaMonkey/2.8a1 After the init sequences completes, /dev/tty2 to /dev/tty6 are seen to have empty display; they don't respond to the keyboard. ps -lC mingetty shows only one instance, on tty1. The tty1 console has been cleared of init messages, the motd and login prompt are at top. Sometimes (rarely) telinit to a different runlevel fixes the problem. But going to runlevel 5 may kill tty consoles 2-6 again. Reproducible: Always Steps to Reproduce: 1. Boot up and wait. 2. Hit Ctrl-Alt-F2 (or Ctrl-Alt-F3 to Ctrl-Alt-F6) Actual Results: Nothing: empty display, and no response to keyboard (except of course to Ctrl-Alt-F1, Ctrl-Alt-F10, or, in runlevel 5, Ctrl-Alt-F7). Expected Results: A motd and login prompt should have appeared. Additional info: 1. /etc/inittab looks normal; in particular, the following lines are present: 1:2345:respawn:/sbin/mingetty --noclear tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 2. Trying to start mingetty by hand-typing one of the above commands (with & at the end) at a bash prompt, aborts with exit code 1, logging "Cannot get controlling tty, operation not permitted" on /dev/tty10. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c1
--- Comment #1 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c2
--- Comment #2 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c3
--- Comment #3 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c4
--- Comment #4 from Tony Mechelynck
/etc/inittab is not used under systemd.
ttys are started on demand by systemd, (based on /lib/systemd/systemd/getty@.service), unless you create symlinks in /etc/systemd/system/getty.target.wants/ to /lib/systemd/systemd/getty@.service
What do you mean by "on demand"? AFAICT, unless I start them manually as shown in comment #1, in runlevel 5 (i.e. graphical multiuser) tty 2-6 don't react to the keyboard and don't display a login prompt. Is this "load on demand" the reason why system messages will appear "spontaneously" on any text console, possibly overwriting the output of a curses-based program like yast or vim being used there? I suppose the aliases in the [Install] section of getty@.service would have to be modified too.
to get --noclear, we would need to replace /etc/systemd/system/getty.target.wants/getty@tty1.service symlink with a copy of the file and add --noclear to it
OK, I made an edited copy as /lib/systemd/system/getty@tty1.service and linked it from /etc/systemd/system/getty.target/ -- we'll see how it works at next boot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c5
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c6
--- Comment #6 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c7
--- Comment #7 from Tony Mechelynck
sorry, I forgot to comment. [...] don't copy /lib/systemd/system/getty@.service as /lib/systemd/system/getty@tt1.service but put the file directly to /etc/systemd/system/getty.target.wants
you shouldn't store anything in /lib but use /etc
What about the last two lines: [Install] Alias=getty.target.wants/getty@tty1.service Keep them? Remove them? Keep one and remove the other? Don't care? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c8
--- Comment #8 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c9
--- Comment #9 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c10
--- Comment #10 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c
Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c11
--- Comment #11 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c12
Pawel Wieczorkiewicz
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c13
--- Comment #13 from Tony Mechelynck
Please re-test on openSUSE 13.1 and provide results - Thanks.
OK; but that will of course have to wait until I find time to upgrade to openSUSE 13.1 (or later) and have it succeed. If anyone else (already running openSUSE 13) is willing to do the same test, feel free to do so. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c14
--- Comment #14 from Pawel Wieczorkiewicz
OK; but that will of course have to wait until I find time to upgrade to openSUSE 13.1 (or later) and have it succeed. If anyone else (already running openSUSE 13) is willing to do the same test, feel free to do so.
Sure, I think this issue is gone a while ago. I cannot reproduce it myself on openSUSE 13.1. It would be good to hear it from the reporter though ;-). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c15
systemd maintainers
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c16
--- Comment #16 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c17
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c18
--- Comment #18 from Tony Mechelynck
You may give the latest util-linux[1] package from openSUSE Factory a try (compare with bug #774126). There I've added a workaround for a slow plymouth which may lead to a broken termios structure in the kernel. […]
OK I'm adding this to my TODO list. I'll also have to reread the above comments: after a little more than 2 years the details of the problem aren't very fresh in my memory. Maybe there was a misunderstanding on my part at some point, trying to understand that (then) new systemctl software. Could you please enlighten me on what "Plymouth" is? (probably by private mail to avoid spamming the bug). I notice that during boot there is a "Plymouth Boot Screen" which diverts startup messages to tty7 for a time, where they later get hidden by the X11 screen, but only the first time: if I log out of X11 the graphical login screen reappears on tty8 rather than on tty7, making the last page of boot text visible again on tty7, with "Starting Wait for Plymouth Boot Screen to Quit..." a few lines up from the bottom; and if I log out from X11 a second time the graphical screen remains on tty8. Unrelated to this, I suppose, but it has puzzled me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c19
--- Comment #19 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c20
--- Comment #20 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c21
--- Comment #21 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c22
--- Comment #22 from Tony Mechelynck
Use agetty not mingetty as the last one is not supported anymore. All features from the old mingetty had been ported to agetty at upstram util-linux by my self.
Including its small footstep (aka size) ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c23
--- Comment #23 from Tony Mechelynck
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c24
--- Comment #24 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c25
--- Comment #25 from Tony Mechelynck
agetty isn't that large and it can log on both serial lines and virtual consoles, it also accepts and obeys the --noclear and it can handle the escape sequences of you /etc/issue
In fact the discussion was done several years ago and mingetty was kicked out.
So I note that mingetty isn't "officially supported" anymore. If I decide to use it (like I use the Sunbird selfstanding calendar, whose latest Linux64 nightly is dated 2010-01-11 AFAIK, and for which I haven't found a replacement that satisfies me), it will be under my own responsibility. If I have specific problems with mingetty (as opposed to systemd or login, which _are_ supported), part or all of the answer will always be "mingetty is obsolete; use agetty instead". The point of serial lines might be moot since AFAIK I don't have any (though I'm not sure); but I regard being able to listen to logins from them as a security liability unless they are really known in advance to be needed as login devices. I don't know how big agetty is when running; its binary executable is only slightly larger than that of mingetty and vastly smaller than that of mgetty so you might have a point there. My other two points, apparently, make no difference between agetty and mingetty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c26
Anton Lefering
https://bugzilla.novell.com/show_bug.cgi?id=731594
https://bugzilla.novell.com/show_bug.cgi?id=731594#c27
--- Comment #27 from Dr. Werner Fink
participants (1)
-
bugzilla_noreply@novell.com