[Bug 1194322] New: eth0 report update as boot completes causes screen to clear, in spite of --noclean agetty option
http://bugzilla.opensuse.org/show_bug.cgi?id=1194322 Bug ID: 1194322 Summary: eth0 report update as boot completes causes screen to clear, in spite of --noclean agetty option Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: mrmazda@earthlink.net QA Contact: qa-bugs@suse.de CC: sbrabec@suse.com Blocks: 1168405 Found By: --- Blocker: --- Created attachment 854979 --> http://bugzilla.opensuse.org/attachment.cgi?id=854979&action=edit /etc/systemd/system/getty.target.wants/getty@tty1.service Original Summary: eth0 report update as boot completes causes screen to clear, in spite of --noclean agetty option This began with TW very long ago and applies to 15.4 and 15.3 as well. 15.2 was OK. To reproduce: 1-uninstall or disable Plymouth 2-Include ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear %I $TERM in /etc/systemd/system/getty.target.wants/getty@tty1.service 3-boot without quiet or splash=silent, and with noresume added to, linu line in grub.cfg Actual behavior: 1-post KMS-engagement text messages appear onscreen ending with: a: Welcome to openSUSE...(tty1). b: eth0: c: <hostname> login: 2-screen clears to only: a: Welcome to openSUSE...(tty1). b: eth0: xxx.xxx.xxx.xxx c: <hostname> login: 3-EOF Expected behavior: 1-post KMS-engagement text messages appear onscreen ending with: a: Welcome to openSUSE...(tty1). b: eth0: c: <hostname> login: 2-EOF Other data: # systemd-analyze critical-chain ... ������multi-user.target @2.465s ������kbdsettings.service @400ms +2.064s ������basic.target @396ms ������sockets.target @396ms ������telnet.socket @396ms ������sysinit.target @394ms ������systemd-timesyncd.service @366ms +27ms ������systemd-tmpfiles-setup.service @356ms +8ms ������local-fs.target @355ms ������usr-local.mount @351ms +3ms ������systemd-fsck@dev-disk-by\x2dlabel-tm8p04usrlcl.service @330ms +19ms ������local-fs-pre.target @327ms ������lvm2-monitor.service @246ms +80ms ������dm-event.socket @239ms ������system.slice ������-.slice # systemctl status systemd-networkd ��� systemd-networkd.service - Network Configuration Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2022-01-04 20:35:46 EST; 9min ago TriggeredBy: ��� systemd-networkd.socket Docs: man:systemd-networkd.service(8) Main PID: 572 (systemd-network) Status: "Processing requests..." Tasks: 1 (limit: 4915) CPU: 47ms CGroup: /system.slice/systemd-networkd.service ������572 /usr/lib/systemd/systemd-networkd Jan 04 20:35:46 ab560 systemd[1]: Starting Network Configuration... Jan 04 20:35:46 ab560 systemd-networkd[572]: lo: Link UP Jan 04 20:35:46 ab560 systemd-networkd[572]: lo: Gained carrier Jan 04 20:35:46 ab560 systemd-networkd[572]: Enumeration completed Jan 04 20:35:46 ab560 systemd[1]: Started Network Configuration. Jan 04 20:35:48 ab560 systemd-networkd[572]: eth0: Link UP Jan 04 20:35:51 ab560 systemd-networkd[572]: eth0: Gained carrier # rpm -qa | egrep -i 'NetworkManager|Wicked' # -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1194322 http://bugzilla.opensuse.org/show_bug.cgi?id=1194322#c3 --- Comment #3 from Felix Miata <mrmazda@earthlink.net> --- (In reply to Stanislav Brabec from comment #1)
There is an easy work around:
You can edit /etc/sysconfig/issue-generator and change NETWORK_INTERFACE_REGEX to "^[^a-z]", and network lines will not be generated.
With upgrade to TW20221212, this causes the /etc/issue symlink to link to a non-existent /run/issue, resulting in naked login prompts on ttys2-6. (64bit host ab250) After determining this, I moved /etc/issue to /etc/issue.oem and copied /etc/from an old backup, resulting in the nice old behavior of not clearing tty1, and the Welcome to openSUSE Tumbleweed - Kernel <version> <tty> message at top of screen. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1194322 http://bugzilla.opensuse.org/show_bug.cgi?id=1194322#c6 --- Comment #6 from Felix Miata <mrmazda@earthlink.net> --- The problem is the /etc/issue symlink links to /run/issue, which doesn't exist. What does exist is /run/issue.d/. I have no idea how anything does or doesn't appear in /run/. Nothing owns /run/issue.d/, which contains nothing. This has freshly appeared on 3 more installations, all of which had last been dup'd in May and are now on 20221221. What could have replaced /run/issue with /run/issue.d/? # journalctl -u issue-generator.service Jan 17 18:32:52 gx27c systemd[1]: Starting Generate issue file for login session... Jan 17 18:32:53 gx27c systemd[1]: issue-generator.service: Deactivated successfully. Jan 17 18:32:53 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot 24df0727c31c4d99aec5c24c2e283505 -- Jan 17 23:51:22 gx27c systemd[1]: Starting Generate issue file for login session... Jan 17 18:53:33 gx27c systemd[1]: issue-generator.service: Deactivated successfully. Jan 17 18:53:33 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot ff8b495f8b104ffea0442221d07d4635 -- Jan 17 23:05:03 gx27c systemd[1]: Starting Generate issue file for login session... Jan 17 23:05:04 gx27c systemd[1]: issue-generator.service: Deactivated successfully. Jan 17 23:05:04 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot 3696c83e7eae481bb971a42fc4cf69a1 -- Mar 24 00:08:06 gx27c systemd[1]: Starting Generate issue file for login session... Mar 23 20:08:06 gx27c systemd[1]: issue-generator.service: Deactivated successfully. Mar 23 20:08:06 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot cefd34e663be469cb7c8cb6692965b4c -- Mar 24 01:45:19 gx27c systemd[1]: Starting Generate issue file for login session... Mar 24 01:45:28 gx27c systemd[1]: issue-generator.service: Deactivated successfully. Mar 24 01:45:28 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot db8cbe445c5a45c6a2fb466c2507df45 -- May 09 19:31:02 gx27c systemd[1]: Starting Generate issue file for login session... May 09 19:31:37 gx27c systemd[1]: issue-generator.service: Deactivated successfully. May 09 19:31:37 gx27c systemd[1]: Finished Generate issue file for login session. May 09 20:20:05 gx27c systemd[1]: Starting Generate issue file for login session... May 09 20:20:07 gx27c systemd[1]: issue-generator.service: Deactivated successfully. May 09 20:20:07 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot 1ee7ffe4bb2648f1842facde902c7849 -- May 09 23:12:47 gx27c systemd[1]: Starting Generate issue file for login session... May 09 23:13:22 gx27c systemd[1]: issue-generator.service: Deactivated successfully. May 09 23:13:22 gx27c systemd[1]: Finished Generate issue file for login session. -- Boot 98a0e65f46e046b98eea90c27d6e3f19 -- May 16 19:19:51 gx27c systemd[1]: Starting Generate issue file for login session... May 16 19:19:52 gx27c systemd[1]: issue-generator.service: Deactivated successfully. May 16 19:19:52 gx27c systemd[1]: Finished Generate issue file for login session. # ls -l /etc/issue lrwxrwxrwx 1 root root 12 Aug 15 2017 /etc/issue -> ../run/issue # ls -l /run/issu* total 0 # ls -l /run/issue.d total 0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1194322 http://bugzilla.opensuse.org/show_bug.cgi?id=1194322#c7 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://github.com/util-lin | |ux/util-linux/issues/2051 --- Comment #7 from Felix Miata <mrmazda@earthlink.net> --- Upstream bug report: https://github.com/util-linux/util-linux/issues/2051 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1194322 Felix Miata <mrmazda@earthlink.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|eth0 report update as boot |eth0 report update as boot |completes causes screen to |completes causes screen to |clear, in spite of |clear, in spite of |--noclean agetty option |--noclear agetty option -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com