May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222534] New: No wired network after hibernation
by bugzilla_noreply＠suse.com 09 Jun '24

09 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222534 Bug ID: 1222534 Summary: No wired network after hibernation Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: jonzn4suse(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20240405 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.8.4-rc1-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5825U with Radeon Graphics Memory: 62.1 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP ProBook 455 15.6 inch G9 Notebook PC System Version: SBKPF I can turn on WiFi and it works, but to fix the wired issue, I have to reboot. The below logs keeps repeating until a reboot. LOGS: Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.4741] device (enp1s0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <warn> [1712657390.4744] device (enp1s0): Activation: failed for connection 'Wired Connection' Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.4744] device (enp1s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): canceled DHCP transaction Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5233] dhcp4 (enp1s0): state changed no lease Tuesday, April 9, 2024 6:09:50 AM EDT kernel r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon Files changed, reloading. Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon No service file found in /etc/avahi/services. Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5760] policy: auto-activating connection 'Wired Connection' (21000dbf-984d-4441-91e7-1f4c01a5b834) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5763] device (enp1s0): Activation: starting connection 'Wired Connection' (21000dbf-984d-4441-91e7-1f4c01a5b834) Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5764] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5766] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT kernel r8169 0000:01:00.0 enp1s0: Link is Up - 1Gbps/Full - flow control rx/tx Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5937] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Tuesday, April 9, 2024 6:09:50 AM EDT NetworkManager <info> [1712657390.5939] dhcp4 (enp1s0): activation: beginning transaction (timeout in 45 seconds) Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon Files changed, reloading. Tuesday, April 9, 2024 6:09:50 AM EDT avahi-daemon No service file found in /etc/avahi/services. I will also test sleep to see if it has the same issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222761] New: wxWidgets needs to be compiled with spellcheck
by bugzilla_noreply＠suse.com 08 Jun '24

08 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222761 Bug ID: 1222761 Summary: wxWidgets needs to be compiled with spellcheck Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am trying to build an updated kiCad 8.0 and it requires wxWidgets and wxPython with Python > 3.6. Kicad requires wxWidgets >= 3.0.5 so I am trying to build with wxWidgets 3.2. Unfortunately, the wxWidgets supplied with OpenSUSE is not built with spellcheck enabled which is required for wxPython. Can wxWidgets be built with --enable-spellcheck in the configure phase? -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1213370] New: tesseract-ocr should not be built with experimantal opencl support
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213370 Bug ID: 1213370 Summary: tesseract-ocr should not be built with experimantal opencl support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)titlis.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- opencl in tesseract-ocr is considered experimental, according to this thread (https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1BgAJ) it is considered just an entry point for possible developers. Their own doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.html) states: "Important note: OpenCL support in Tesseract is still considered experimental. There are some major bugs associated with it (see issue 837). Building Tesseract with OpenCL support is not recommended (for any version of Tesseract), unless you are a developer and want to improve the OpenCL code" Please remove the flag "--enable-opencl" from https://build.opensuse.org/package/view_file/openSUSE:Factory/tesseract-ocr… This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=1207570 PS: I indeed encounter problems with the opencl code path -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224165] New: AUDIT-0: openSUSE Leap 15.6 Gold Master security audit
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224165 Bug ID: 1224165 Summary: AUDIT-0: openSUSE Leap 15.6 Gold Master security audit Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello team this is a request to audit openSUSE:Leap:15.6 GoldMaster code deadline is same as for SLES 15 SP6 GM (May 16th). Our roadmap says: Wed, May 16, 2022 Gold Master code submission deadline built should be within a week from there. However it's all driven by GMC acceptance for SUSE Linux Enterprise 15 SP6 The poo tracker: https://progress.opensuse.org/issues/131864 Leap 15.6 Schedule https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224781] New: VUL-0: CVE-2024-35192: trivy: credential leak via malicious registry
by bugzilla_noreply＠suse.com 07 Jun '24

07 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224781 Bug ID: 1224781 Summary: VUL-0: CVE-2024-35192: trivy: credential leak via malicious registry Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/406773/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: dmueller(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Trivy is a security scanner. Prior to 0.51.2, if a malicious actor is able to trigger Trivy to scan container images from a crafted malicious registry, it could result in the leakage of credentials for legitimate registries such as AWS Elastic Container Registry (ECR), Google Cloud Artifact/Container Registry, or Azure Container Registry (ACR). These tokens can then be used to push/pull images from those registries to which the identity/user running Trivy has access. Systems are not affected if the default credential provider chain is unable to obtain valid credentials. This vulnerability only applies when scanning container images directly from a registry. This vulnerability is fixed in 0.51.2. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-35192 https://www.cve.org/CVERecord?id=CVE-2024-35192 https://github.com/aquasecurity/trivy/commit/e7f14f729de259551203f313e57d2d… https://github.com/aquasecurity/trivy/security/advisories/GHSA-xcq4-m2r3-cm… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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 1225298] New: systemd-boot fails to boot 6.9.1
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225298 Bug ID: 1225298 Summary: systemd-boot fails to boot 6.9.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875116 --> https://bugzilla.suse.com/attachment.cgi?id=875116&action=edit screen photo Installed TW with systemd-boot about a month ago, updated today to 20240523, rebooted, everything seemed to work but noticed it was still on 6.8.8. Rebooted, selected 6.9.1 from the systemd-boot menu and it gets stuck while booting. Reaches target Initrd File System Times out waiting for device /dev/gpt-auto-root Attached a photo of the screen with boot messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225299] New: systemd-boot doesn't display passphrase prompt for decryption until a key is pressed
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225299 Bug ID: 1225299 Summary: systemd-boot doesn't display passphrase prompt for decryption until a key is pressed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875117 --> https://bugzilla.suse.com/attachment.cgi?id=875117&action=edit no prompt Installed TW with systemd-boot on my laptop about a month ago. It has 1 drive (nvme), it has one partition for /boot/efi, one for root and an encrypted partition for /home, no LVM. When booting the kernel messages just stop and there's no indicator asking to enter the passphrase for /home partition unless I press a key, then the prompt "Please enter passphrase for disk..." appears. Or if I press escape then it displays this gray semi-graphical screen with the same message. The kernel command line contains 'splash=silent quiet' and Plymouth is installed, I didn't do any configuration there but it's not displayed, just plain kernel messages when booting. It would be nice to have a better passphrase prompt especially on a 14" 2880x1800 screen where the kernel messages are tiny. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224407] New: parcellite dumps core when clicking on one entry of the history list
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224407 Bug ID: 1224407 Summary: parcellite dumps core when clicking on one entry of the history list 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: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- parcellite-1.2.4.0-1.1.x86_64 crashes when one entry of the history list is left clicked. This is on XFCE as the desktop manager. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223624] New: [Build 20240501] podman bats user integration fails test suites
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223624 Bug ID: 1223624 Summary: [Build 20240501] podman bats user integration fails test suites Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4145118/modules/bats -user-local_tap/steps/47 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Since the latest changes, the tests look better, but not yet completely fixed. Theese are the current failures: bats-user-local: not ok 47 [012] manifest list --add --artifact # (from function `run_podman' in file test/system/helpers.bash, line 416, # from function `manifestListAddArtifactOnce' in file test/system/012-manifest.bats, line 167, # in test file test/system/012-manifest.bats, line 262) # `manifestListAddArtifactOnce' failed not ok 367 [200] podman pod cleans cgroup and keeps limits # (in test file test/system/200-pod.bats, line 750) # `assert "$(< $memory_limit_file)" = "268435456" "Contents of $memory_limit_file"' failed not ok 378 [252] quadlet - basic # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `assert' in file test/system/helpers.bash, line 929, # in test file test/system/252-quadlet.bats, line 174) # `assert "$output" == "STARTED CONTAINER" "exact/full match when using the 'passthrough' driver"' failed not ok 427 [280] podman update - test all options # tags: distro-integration # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `die' in file test/system/helpers.bash, line 813, # from function `run_podman' in file test/system/helpers.bash, line 423, # in test file test/system/280-update.bats, line 109) # `run_podman update "${opts[@]}" $cid' failed not ok 499 [505] No IPv4 # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `die' in file test/system/helpers.bash, line 813, # from function `run_podman' in file test/system/helpers.bash, line 423, # in test file test/system/505-networking-pasta.bats, line 271) # `run_podman run --net=pasta:-6 $IMAGE ip -j -4 address show' failed not ok 506 [505] IPv6 default route # (from function `bail-now' in file test/system/helpers.bash, line 235, # from function `assert' in file test/system/helpers.bash, line 929, # in test file test/system/505-networking-pasta.bats, line 363) # `assert "${container_route}" = "${host_route}" \' failed openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_podman_testsuite@64bit fails in [bats-user-local_tap](https://openqa.opensuse.org/tests/4145118/modules/bats… ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module 2023-08-10/dimstar: added QEMURAM=2048 (boo#1212824) ## Reproducible Fails since (at least) Build [20240308](https://openqa.opensuse.org/tests/3999689) ## Expected result Last good: [20240307](https://openqa.opensuse.org/tests/3997809) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1224120] New: [SELinux] AVC denial systemd-fstab-g on MicroOS
by bugzilla_noreply＠suse.com 06 Jun '24

06 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224120 Bug ID: 1224120 Summary: [SELinux] AVC denial systemd-fstab-g on MicroOS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: arvidjaar(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- mitmanek:~ # ausearch -m AVC -ts boot ---- time->Fri May 10 00:24:35 2024 type=AVC msg=audit(1715293475.979:21): avc: denied { map_read map_write } for pid=1237 comm="systemd-fstab-g" scontext=system_u:system_r:systemd_fstab_generator_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=bpf permissive=1 ---- time->Fri May 10 00:24:35 2024 type=AVC msg=audit(1715293475.979:22): avc: denied { map_read map_write } for pid=1245 comm="systemd-gpt-aut" scontext=system_u:system_r:systemd_gpt_generator_t:s0 tcontext=system_u:system_r:init_t:s0 tclass=bpf permissive=1 ---- time->Fri May 10 00:34:38 2024 type=AVC msg=audit(1715294078.083:118): avc: denied { unlink } for pid=1894 comm="bootctl" name="bfb41e21a4f34f10958f75adb1378666-6.8.7-1-default-75.conf" dev="nvme0n1p2" ino=43 scontext=system_u:system_r:snapperd_t:s0 tcontext=system_u:object_r:dosfs_t:s0 tclass=file permissive=1 mitmanek:~ # I don’t see any actual negative effects. Also mentioned on https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[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 1223900] New: sddm: issue with XAUTHORITY
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223900 Bug ID: 1223900 Summary: sddm: issue with XAUTHORITY 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: gcomes.obs(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In xfce I use redshift to adjust the monitor night color. If I use lightdm as displaymanager, redshift works normally. Typing the command: redshift -o gives the output: Trying location provider `geoclue2'... Using provider `geoclue2'. Using method `randr'. Waiting for current location to become available... etc... But if I use sddm as displaymanager, redshift doesn't work. Typing the command: redshift -o gives the output: Trying location provider `geoclue2'... Using provider `geoclue2'. Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified `RANDR Query Version' returned error -1 Initialization of randr failed. Trying next method... Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified X request failed: XOpenDisplay Initialization of vidmode failed. Trying next method... No more methods to try. The output of: strace redshift -o contains: access("/tmp/xauth_WYBTin", R_OK) = 0 openat(AT_FDCWD, "/tmp/xauth_WYBTin", O_RDONLY) = -1 EACCES (Permission denied) The failure of redshift is due to the fact that somehow it cannot access /tmp/xauth_WYBTin (the value of $XAUTHORITY) However such file is readable by the user running redshift and other xprograms work fine. Leap 15.5 (sddm 0.19) works fine as did the previous versions. The issue started with sddm 0.20 (https://build.opensuse.org/package/show/openSUSE:Factory/sddm?rev=64) and is currently present in Leap 15.6 and tumbleweed. I could not figure out what exactly in sddm 0.20 is causing the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1224773] New: Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 Bug ID: 1224773 Summary: Cannot install NVIDIA drivers in latest Aeon RC2 Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: sunscape1(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installing NVIDIA drivers in Aeon RC2 (https://en.opensuse.org/SDB:NVIDIA_drivers) fails because the MOK cannot be enrolled after boot. Error during installation using pkg is: SKIP: /var/lib/nvidia-pubkeys/MOK-nvidia-driver-G06-550.78-22.1-default.der is not in MokList Without the nvidia-pubkeys folder it is impossible to enroll the MOK or try to enable it after reboot. The key doesn't exist :( -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1223838] New: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau)
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223838 Bug ID: 1223838 Summary: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de CC: kernel-bugs(a)suse.de, qa-bugs(a)suse.de, tiwai(a)suse.com, variable_valuables761(a)simplelogin.com Depends on: 1217750, 1217716 Target Milestone: --- Found By: --- Blocker: --- Created attachment 874641 --> https://bugzilla.suse.com/attachment.cgi?id=874641&action=edit current dmesg output +++ This bug was initially created as a clone of Bug #1217750 +++ It seems the brightness keys (Fn+F1,Fn+F2) do not work in Tumbleweed with current 6.8 kernel series. This should have been reported rather long time ago. This has started happening in ~6.5 series I've attached the output of "brightnessctl -l",> which only shows keyboard (caps lock) key and several non-existent LEDs on keyboard. -- 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 1224995] New: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224995 Bug ID: 1224995 Summary: Native Firefox package on Plasma Wayland runs the KDE File Picker under XWayland, not respecting HDPI scaling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: radicalite(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875025 --> https://bugzilla.suse.com/attachment.cgi?id=875025&action=edit Filepicker comparsion between Native Firefox on TW and Flatpak Firefox When using the file picker from the native Firefox package, the file picker runs in XWayland, this isn't noticeable on non HiDPI displays unless there's a HiDPI display connected, or are simply using a HiDPI screen as the only screen, then this becomes instantly noticeable. This behaviour isn't consistent with applications from the rest of the system (moving aside VLC, but the app itself runs entirely under XWayland by default...), as they run the file picker under Wayland, following the correct scaling setting. the Firefox flatpak also runs the file picker under Wayland correctly (via Portal). This behaviour also doesn't happen with the native Firefox package on TWGNOME, running the GTK file picker under Wayland with respect to scaling, so I assume this happens from the OpenSUSE KDE patches added to Firefox? Install is a fresh TWKDE install. Comparison in image Operating System: openSUSE Tumbleweed 20240520 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6267U CPU @ 2.90GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® Iris® Graphics 550 Manufacturer: Apple Inc. Product Name: MacBookPro13,2 System Version: 1.0 Display config is 2560x1600@175%@60hz (Built-in Screen) set to left 1920x1080@100%@120hz (Acer Technologies VG242Y) set to right, set as primary display. -- 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 1224356] New: /usr/share/p11-kit/modules/softhsm.module contains garbage after installing softhsm
by bugzilla_noreply＠suse.com 05 Jun '24

05 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224356 Bug ID: 1224356 Summary: /usr/share/p11-kit/modules/softhsm.module contains garbage after installing softhsm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: daan.j.demeyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After installing the softhsm 2.6.1-1.1 package on opensuse Tumbleweed, /usr/share/p11-kit/modules/softhsm.module seems to contain garbage: ``` daandemeyer-fedora-PC1EV17T:/work/src # cat /usr/share/p11-kit/modules/softhsm.module �^�� A�#�O� ��%�Ė2��a2��X4~�Q��p�+��v��K�u�Ĥ�!��]\>��D/�7p>��>tb7��}��R�:w�Q?�▒��^�H▒.�Pl��s3i��Ϳ$��`d��4wRNw]�i�+�I��[�D��/��*=��֌��ǭ!�-p^1f�eW��j5%��Ұo�{��L�ht�'K��&�D�?��E05n-}�'i',pM-kPn31Wa�H��B!�=��t'��Js��ÓP&��O��ي�▒�h��Fx7w▒WGH5�� 5* �N+��C��Hu��Wp��kB~O��y�.� ��7k@&��.y��9��W�ѫF4�KX��9�)�2��v��#5W��FA��?L�s�(��m��_�W��C+N�_ �-��B�Ȑ�2$�j�:j�h�_(��f�a��(�� daandemeyer-fedora-PC1EV17T:/work/src # cat /usr/share/p11-kit/modules/softhsm2.module # This file describes how to load the pk11 module # See: http://p11-glue.freedesktop.org/doc/p11-kit/config.html module: /usr/lib64/pkcs11/libsofthsm2.so ``` ``` daandemeyer-fedora-PC1EV17T:/work/src # rpm -qi softhsm Name : softhsm Version : 2.6.1 Release : 1.1 Architecture: x86_64 Install Date: Thu May 16 11:08:08 2024 Group : Unspecified Size : 1546547 License : BSD-2-Clause Signature : RSA/SHA512, Sun May 12 22:02:14 2024, Key ID 35a2f86e29b700a4 Source RPM : softhsm-2.6.1-1.1.src.rpm Build Date : Sat May 11 16:00:16 2024 Build Host : reproducible Packager : https://bugs.opensuse.org Vendor : openSUSE URL : https://www.opendnssec.org/ Summary : Software version of a PKCS#11 Hardware Security Module Description : OpenDNSSEC is providing a software implementation of a generic cryptographic device with a PKCS#11 interface, the SoftHSM. SoftHSM is designed to meet the requirements of OpenDNSSEC, but can also work together with other cryptographic products because of the PKCS#11 interface. Distribution: openSUSE Tumbleweed ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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