April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1212909] New: unstripped-binary-or-object for binary libraries in Python directories
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1212909 Bug ID: 1212909 Summary: unstripped-binary-or-object for binary libraries in Python directories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is a zillion packages which end up with the warning like python311-scipy.x86_64: W: unstripped-binary-or-object /usr/lib64/python3.11/site-packages/scipy/spatial/_qhull.cpython-311-x86_64-linux-gnu.so (this is from https://build.opensuse.org/package/live_build_log/home:gladiac:mailman/pyth…) Interestingly the same package in the devel project doesn’t seem to present the same problem (https://build.opensuse.org/build/devel:languages:python:numeric/openSUSE_Tu…). Could we find out why these happen and do something about it? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1222450] New: Error: crun: opening file `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222450 Bug ID: 1222450 Summary: Error: crun: opening file `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: miika.alikirri(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874124 --> https://bugzilla.suse.com/attachment.cgi?id=874124&action=edit output of podman info On a fresh installation of tumbleweed (version 20240403), podman fails to run as a non-root user when `--memory` option is set. running: ``` podman run --rm --memory 4M tumbleweed echo it works ``` prints out: ``` Error: crun: opening file `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found ``` And running it as sudo runs it correctly and prints: ``` it works ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213929] New: zypper-changelog-plugin lacks dependencies (No module named 'rpm')
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213929 Bug ID: 1213929 Summary: zypper-changelog-plugin lacks dependencies (No module named 'rpm') Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installing the zypper-changelog-plugin in a TW container it says: > 21606fdb0e6d:/ # zypper changelog > Traceback (most recent call last): > File "/usr/bin/zypper-changelog", line 30, in <module> > import rpm > ModuleNotFoundError: No module named 'rpm' A bunch of dependencies were installed together with the package, but python311-rpm was missing. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222190] New: cron job does not send email (error message about pam_kwallet5)
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222190 Bug ID: 1222190 Summary: cron job does not send email (error message about pam_kwallet5) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I do not get email from cron jobs anymore. journalctl -u cron.service shows error message: pam_kwallet5(crond:session): pam_kwallet5: not a graphical session, skipping. Use force_run parameter to ignore this. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222189] New: kmail first uses wrong message header layout
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222189 Bug ID: 1222189 Summary: kmail first uses wrong message header layout Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873952 --> https://bugzilla.suse.com/attachment.cgi?id=873952&action=edit first attachment wrong layout of header KMail uses in View in the entry Headers the item Fancy Headers. However the header is shown a in the first attachment, without the blue band on top. After choosing Brief and back to Fancy Header, the second attachment shows the right layout of the header. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221576] New: Selecting Print in Okular or Kate only offers printing to PDF file
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221576 Bug ID: 1221576 Summary: Selecting Print in Okular or Kate only offers printing to PDF file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the upgrade to Plasma 6 of Tumbleweed when opening a PDF file in okular or a txt file in Kate and selecting Print the popup for printing only offers printing to a PDF file. When using YaST to configure the printer, a HP DeskJet 2720, I can print a test page. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222468] New: VUL-0: CVE-2024-22189: caddy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222468 Bug ID: 1222468 Summary: VUL-0: CVE-2024-22189: caddy: quic-go: memory exhaustion attack against QUIC's connection ID mechanism Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/400376/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: alexandre.vicenzi(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(a)suse.com, jkowalczyk(a)suse.com, security-team(a)suse.de, smash_bz(a)suse.de Blocks: 1222461 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1222461 +++ quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.42.0, an attacker can cause its peer to run out of memory sending a large number of `NEW_CONNECTION_ID` frames that retire old connection IDs. The receiver is supposed to respond to each retirement frame with a `RETIRE_CONNECTION_ID` frame. The attacker can prevent the receiver from sending out (the vast majority of) these `RETIRE_CONNECTION_ID` frames by collapsing the peers congestion window (by selectively acknowledging received packets) and by manipulating the peer's RTT estimate. Version 0.42.0 contains a patch for the issue. No known workarounds are available. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22189 https://www.cve.org/CVERecord?id=CVE-2024-22189 https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c… https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478 https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-manageme… https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s https://bugzilla.redhat.com/show_bug.cgi?id=2273513 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1215619] New: Request to include packets opendmarc and postfix-policyd-spf-perl in a standard openSUSE repository
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215619 Bug ID: 1215619 Summary: Request to include packets opendmarc and postfix-policyd-spf-perl in a standard openSUSE repository Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In The Netherlands recently hackers succeeded in getting a payment by sending an email supposedly coming from a boss, who asked for settling an invoice. It might have been unsuccessful if proper security measure were taken by implementing email security features like DMARC and SPF, next to DKIM. To make this more easy I find it highly desirable to have the packages opendmarc and postfix-policyd-spf-perl available in a standard repository of openSUSE; opendkim, next to DKIM support in Amavis, is already available. These packages, architecture noarch, are available o.a. in: https://download.opensuse.org/repositories/devel:/languages:/perl/15.4/ https://download.opensuse.org/repositories/server:/mail/15.5/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222376] New: JeOS ARM image for RPi4 gives errors after reboot
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222376 Bug ID: 1222376 Summary: JeOS ARM image for RPi4 gives errors after reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Image openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.aarch64.raw.xz downloaded Apr. 4 boots Ok when put on micro-SD card. However after some additions of a few software packages, a.o. udev-persistent-ifnames, a reboot is needed. During reboot the following error messages are shown several times: [FAILED] Failed to start Load AppArmor profiles. [FAILED] Failed to activate swap /dev/disk/…d79128-4998-45c6-8dac-4a12670b10f4. [FAILED] Failed to start Security Auditing Service. [FAILED] Failed to start auditd rules generation. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1221759] New: systemd fails to switch root
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221759 Bug ID: 1221759 Summary: systemd fails to switch root Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: schwab(a)suse.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This is a regression from the current tumbleweed snapshot (it works when building against openSUSE:Factory/snapshot). The only two differences between the kernel-obs-build initrds (from kernel-obs-build-6.7.9-1.1 and kernel-obs-build-6.8.1-1.1) are systemd (v254.9 vs v255.3) and the kernel. $ osc build --noservice standard x86_64 --vm-type qemu -j2 --clean Building aaa_base.spec for standard/x86_64 Getting buildconfig from server and store to /space/osc/openSUSE:Factory/aaa_base/.osc/_buildconfig-standard-x86_64 Getting buildinfo from server and store to /space/osc/openSUSE:Factory/aaa_base/.osc/_buildinfo-standard-x86_64.xml Updating cache of required packages 0.0% cache miss. 39/39 dependencies cached. Skipping verification of package signatures Writing build configuration Running build VM_ROOT: /var/tmp/build-root/openSUSE:Factory/standard/x86_64/img, VM_SWAP: /var/tmp/build-root/openSUSE:Factory/standard/x86_64/swap Creating ext4 filesystem on /var/tmp/build-root/openSUSE:Factory/standard/x86_64/img tune2fs 1.47.0 (5-Feb-2023) Setting maximal mount count to -1 logging output to /var/tmp/build-root/openSUSE:Factory/standard/x86_64/.build.log... [ 0s] Using BUILD_ROOT=/var/tmp/build-root/openSUSE:Factory/standard/x86_64/.mount [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] Doing qemu build in /var/tmp/build-root/openSUSE:Factory/standard/x86_64/img [ 0s] [ 1s] [ 1s] achrid-1 started "build aaa_base.spec" at Wed Mar 20 13:11:40 UTC 2024. [ 1s] [ 1s] [ 1s] processing recipe /space/osc/openSUSE:Factory/aaa_base/aaa_base.spec ... [ 1s] running changelog2spec --target rpm --file /space/osc/openSUSE:Factory/aaa_base/aaa_base.spec [ 1s] init_buildsystem --configdir /usr/lib/build/configs --cachedir /var/cache/build --prepare --clean --rpmlist /tmp/rpmlist.xjc128k6 /space/osc/openSUSE:Factory/aaa_base/aaa_base.spec ... [ 1s] unpacking preinstall image openSUSE:Factory/standard/preinstallimage-base [ca63a53d27093320ebf62ec5cf06d696] [ 4s] [ 4s] copying packages... [ 4s] reordering...cycle: libpython3_11-1_0 -> python311-base [ 4s] breaking dependency python311-base -> libpython3_11-1_0 [ 4s] done [ 4s] Detected virtio-serial support [ 10s] booting qemu... [ 10s] Using virtio-serial support [ 10s] /usr/bin/qemu-system-x86_64 -nodefaults -no-reboot -nographic -vga none -cpu qemu64 -runas qemu -net none -kernel /var/tmp/build-root/openSUSE:Factory/standard/x86_64/.mount/boot/kernel -initrd /var/tmp/build-root/openSUSE:Factory/standard/x86_64/.mount/boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime mitigations=off nmi_watchdog=0 rw rd.driver.pre=binfmt_misc oops=panic panic=1 quiet elevator=noop console=hvc0 init=/.build/build -m 4096 -drive file=/var/tmp/build-root/openSUSE:Factory/standard/x86_64/img,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk,drive=disk,serial=0 -drive file=/var/tmp/build-root/openSUSE:Factory/standard/x86_64/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk,drive=swap,serial=1 -device virtio-serial,max_ports=2 -device virtconsole,chardev=virtiocon0 -chardev stdio,id=virtiocon0 -chardev socket,id=monitor,server=on,wait=off,path=/var/tmp/build-root/openSUSE:Factory/standard/x86_64/img.qemu/monitor -mon chardev=monitor,mode=readline -smp 2 [ 21s] [ 9.370485][ T1] systemd[1]: Failed to start Virtual Console Setup. [ 21s] [FAILED] Failed to start Virtual Console Setup. [ 26s] [ 14.555504] dracut-pre-udev[290]: sh: line 1: /usr/lib/module-init-tools/unblacklist: No such file or directory [ 39s] [FAILED] Failed to start Virtual Console Setup. [ 41s] [FAILED] Failed to start Switch Root. [ 43s] [ 43s] Generating "/run/initramfs/rdsosreport.txt" [ 43s] [ 43s] [ 43s] Entering emergency mode. Exit the shell to continue. [ 43s] Type "journalctl" to view system logs. [ 43s] You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot [ 43s] after mounting them and attach it to a bug report. [ 43s] [ 43s] [ 44s] Press Enter for maintenance [ 48s] (or press Control-D to continue): :/root# systemctl [ 71s] UNIT LOAD ACTIVE SUB DESCRIPTION [ 71s] sys-devices-pci0000:00-0000:00:02.0-virtio0-block-vda.device loaded active plugged /sys/devices/pci0000:00/0000:00:02.0/virtio0/block/vda [ 71s] sys-devices-pci0000:00-0000:00:03.0-virtio1-block-vdb.device loaded active plugged /sys/devices/pci0000:00/0000:00:03.0/virtio1/block/vdb [ 71s] sys-devices-pci0000:00-0000:00:04.0-virtio2-virtio\x2dports-vport2p0.device loaded active plugged /sys/devices/pci0000:00/0000:00:04.0/virtio2/virtio-ports/vport2p0 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.0/tty/ttyS0 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.1/tty/ttyS1 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.10/tty/ttyS10 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.11/tty/ttyS11 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.12/tty/ttyS12 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.13/tty/ttyS13 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.14/tty/ttyS14 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.15/tty/ttyS15 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.16/tty/ttyS16 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.17/tty/ttyS17 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.18/tty/ttyS18 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.19/tty/ttyS19 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.2/tty/ttyS2 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.20/tty/ttyS20 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.21/tty/ttyS21 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.22/tty/ttyS22 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.23/tty/ttyS23 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.24/tty/ttyS24 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.25/tty/ttyS25 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.26/tty/ttyS26 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.27/tty/ttyS27 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.28/tty/ttyS28 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.29/tty/ttyS29 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.3/tty/ttyS3 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.30/tty/ttyS30 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.31/tty/ttyS31 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.4/tty/ttyS4 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.5/tty/ttyS5 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.6/tty/ttyS6 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.7/tty/ttyS7 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.8/tty/ttyS8 [ 71s] sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device loaded active plugged /sys/devices/platform/serial8250/serial8250:0/serial8250:0.9/tty/ttyS9 [ 71s] sys-devices-virtual-tty-hvc0.device loaded active plugged /sys/devices/virtual/tty/hvc0 [ 71s] sys-devices-virtual-tty-hvc1.device loaded active plugged /sys/devices/virtual/tty/hvc1 [ 71s] sys-devices-virtual-tty-hvc2.device loaded active plugged /sys/devices/virtual/tty/hvc2 [ 71s] sys-devices-virtual-tty-hvc3.device loaded active plugged /sys/devices/virtual/tty/hvc3 [ 71s] sys-devices-virtual-tty-hvc4.device loaded active plugged /sys/devices/virtual/tty/hvc4 [ 71s] sys-devices-virtual-tty-hvc5.device loaded active plugged /sys/devices/virtual/tty/hvc5 [ 71s] sys-devices-virtual-tty-hvc6.device loaded active plugged /sys/devices/virtual/tty/hvc6 [ 71s] sys-devices-virtual-tty-hvc7.device loaded active plugged /sys/devices/virtual/tty/hvc7 [ 71s] sys-module-fuse.device loaded active plugged /sys/module/fuse [ 71s] -.mount loaded active mounted Root Mount [ 71s] sysroot.mount loaded active mounted /sysroot [ 71s] init.scope loaded active running System and Service Manager [ 71s] emergency.service loaded active running Emergency Shell [ 71s] ● initrd-switch-root.service loaded failed failed Switch Root [ 71s] systemd-journald.service loaded active running Journal Service [ 71s] ● systemd-vconsole-setup.service loaded failed failed Virtual Console Setup [ 71s] -.slice loaded active active Root Slice [ 71s] system.slice loaded active active System Slice [ 71s] systemd-journald-dev-log.socket loaded active running Journal Socket (/dev/log) [ 71s] systemd-journald.socket loaded active running Journal Socket [ 71s] emergency.target loaded active active Emergency Mode [ 71s] initrd-fs.target loaded active active Initrd File Systems [ 71s] initrd-root-fs.target loaded active active Initrd Root File System [ 71s] initrd-switch-root.target loaded active active Switch Root [ 71s] [ 71s] Legend: LOAD → Reflects whether the unit definition was properly loaded. [ 71s] ACTIVE → The high-level unit activation state, i.e. generalization of SUB. [ 71s] SUB → The low-level unit activation state, values depend on unit type. [ 71s] [ 71s] 59 loaded units listed. Pass --all to see loaded but inactive units, too. [ 71s] To show all installed unit files use 'systemctl list-unit-files'. [ 80s] :/root# journalctl -u initrd-switch-root.service [ 80s] Mar 20 13:12:20 localhost systemd[1]: Starting Switch Root... [ 80s] Mar 20 13:12:21 localhost @ystemctl[383]: Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing. [ 80s] Mar 20 13:12:21 localhost systemd[1]: initrd-switch-root.service: Main process exited, code=exited, status=1/FAILURE [ 80s] Mar 20 13:12:21 localhost systemd[1]: initrd-switch-root.service: Failed with result 'exit-code'. [ 80s] Mar 20 13:12:21 localhost systemd[1]: Failed to start Switch Root. [ 80s] Mar 20 13:12:21 localhost systemd[1]: initrd-switch-root.service: Triggering OnFailure= dependencies. -- You are receiving this mail because: You are on the CC list for the bug.

1 6