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 [details]
/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: