February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1205978] New: Got Page-Fault exception when VM is booting with edk2-stable202211 ovmf
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1205978 Bug ID: 1205978 Summary: Got Page-Fault exception when VM is booting with edk2-stable202211 ovmf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: jlee(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Got Page-Fault exception when VM is booting with edk2-stable202211 ovmf : linux-691t:~ # virsh start opensuseTW; virsh console opensuseTW Domain 'opensuseTW' started Connected to domain 'opensuseTW' Escape character is ^] (Ctrl + ]) !!!! X64 Exception Type - 0E(#PF - Page-Fault) CPU Apic ID - 00000000 !!!! ExceptionData - 000000000000000B I:0 R:1 U:0 W:1 P:1 PK:0 SS:0 SGX:0 RIP - 000000007F2D44FB, CS - 0000000000000038, RFLAGS - 0000000000010246 RAX - 0000000000000000, RCX - 0000000000000001, RDX - 0000000000000000 RBX - 0000038280000014, RSP - 000000007FF05750, RBP - 000000007FF05948 RSI - 0000000000000000, RDI - 0000000000000000 R8 - 000000007FF05948, R9 - 0000000000000001, R10 - 0000000000000001 R11 - 0000000000000000, R12 - 0000000000000001, R13 - 000000007FF05948 R14 - 000000007F2D52FC, R15 - 0000000000000001 DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000030 GS - 0000000000000030, SS - 0000000000000030 CR0 - 0000000080010033, CR2 - 0000038280000014, CR3 - 000000007FC01000 CR4 - 0000000000000668, CR8 - 0000000000000000 DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000 DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400 GDTR - 000000007F9DC000 0000000000000047, LDTR - 0000000000000000 IDTR - 000000007F2DE018 0000000000000FFF, TR - 0000000000000000 FXSAVE_STATE - 000000007FF053B0 !!!! Find image based on IP(0x7F2D44FB) /mnt/working/source_code-git/edk2/Build/OvmfX64/DEBUG_GCC5/X64/UefiCpuPkg/CpuIo2Dxe/CpuIo2Dxe/DEBUG/CpuIo2Dxe.dll (ImageBase=000000007F2D3000, EntryPoint=000000007F2D4CFD) !!!! -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1208305] New: dnsdist 1.7.3-3.1 / aarch64
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208305 Bug ID: 1208305 Summary: dnsdist 1.7.3-3.1 / aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: drixter(a)e-utp.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Affected version: 1.7.3-3.1 / aarch64 dnsdist is compiled in wrong way, if someone using DoH it will reply with error with new build. Feb 15 12:10:09 heaven dnsdist[10291]: Fatal Lua error: [string "chunk"]:35: Caught exception: addDOHLocal() called but DNS over HTTPS support is not present! stack traceback: [C]: in function 'addDOHLocal' [string "chunk"]:35: in main chunk Feb 15 12:10:09 heaven dnsdist[10291]: Fatal Lua error: [string "chunk"]:35: Caught exception: addDOHLocal() called but DNS over HTTPS support is not present! Feb 15 12:10:09 heaven dnsdist[10291]: stack traceback: Feb 15 12:10:09 heaven dnsdist[10291]: [C]: in function 'addDOHLocal' Feb 15 12:10:09 heaven dnsdist[10291]: [string "chunk"]:35: in main chunk -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208662] New: uvesafb: Disable fbdev driver
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208662 Bug ID: 1208662 Summary: uvesafb: Disable fbdev driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: tzimmermann(a)suse.com Reporter: tzimmermann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1193250 Found By: --- Blocker: --- A userspace-based VESA driver. We've abandoned it with the switch to generic DRM drivers. Disable it on ppc64/ppc64le as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1193250] New: Fully switch TW to DRM graphics drivers and disable fbdev drivers
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193250 Bug ID: 1193250 Summary: Fully switch TW to DRM graphics drivers and disable fbdev drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: tzimmermann(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- In TW, we mostly use fbdev vesafb and efifb drivers for early-boot display output and as fallback. This has a number of problems, such as * Most modern Wayland compositors don't support fbdev any longer. Even X' support is bolted-on. Generally, userspace support for fbdev is slowly fading. See bug 1187154. * Handover from fbdev to native DRM drivers is unreliable and can result in stuck systems during boot. See bug 1181913. Therefore, replace TW's fbdev drivers with simpledrm and maybe other DRM drivers. -- You are receiving this mail because: You are on the CC list for the bug.

1 80

[Bug 1208071] New: SELinux: restricting kernel_t causes issues for the way we setup Micro
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208071 Bug ID: 1208071 Summary: SELinux: restricting kernel_t causes issues for the way we setup Micro Classification: openSUSE Product: openSUSE Leap Micro Version: 5.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: screening-team-bugs(a)suse.de Reporter: jsegitz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kukuk(a)suse.com Found By: --- Blocker: --- With 1e8688ea694393c9d918939322b72dfb44a01792 kernel_t isn't an unconfined domain anymore. This causes issues for us since we load the policy in selinux-microos-relabel.sh (of microos-tools) before we pivot. Previously that was okay since kernel_t could do whatever, but with the change kernel_t get restricted so much that this script doesn't work anymore. I tried moving part of the script that do the relabeling into a separate file and create a module that transitions away from kernel_t into something like dracut_t (for now unconfined). The problem is that the transition doesn't work properly in the franken-state of initrd, with half of the system believing not to be SELinux enabled and the /sysroot part already being aware of SELinux and the loaded policy. I smashed my head against this for a while now and want to bring in additional eyes. I see these options: - keep kernel_t as unconfined. Don't want to do this, as there's a real benefit in not having this unconfined. An attacker will be able abuse the kernel_t permissions, but it significantly raises the bar (try to work a bit with the current policy loaded in initrd and you'll see how limited you are). - Ensure a proper transition away from kernel_t for dracut modules. I tried at this today, but it doesn't work and the test environment is horrible due to the restriction placed by SELinux. I would prefer that, but I'll have to figure out why this doesn't work - Check if systemd's /run/systemd/relabel-extra.d mechanism could be used. I assume it can't be used directly, but maybe there's a way around this. Any other ideas on how to approach this? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1207736] New: Virtualbox udev-related files are misplaced
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207736 Bug ID: 1207736 Summary: Virtualbox udev-related files are misplaced Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: zhuravlov.ip(a)ya.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- How to reproduce: 1. Run Virtualbox from KDE as usually. 2. A warning is appeared about USB passthrough, and two alternatives are proposed: (1) enable it, (2) disable it. 3. Select to disable it. 4. A dialog with root password request is appeared to run /sbin/vbox-fix-usb-rules.sh . 5. After entering a password and pressing Enter, an error message is appeared: "No file /sbin/vbox-fix-usb-rules.sh found.". So I can't disable USB passthrough. In fact, the file vbox-fix-usb-rules.sh is located at /usr/sbin/vbox-fix-usb-rules.sh : # rpm -ql virtualbox | grep 'vbox-fix-usb-rules.sh' /usr/sbin/vbox-fix-usb-rules.sh # ll /usr/sbin/vbox-fix-usb-rules.sh -rwxr-xr-x 1 root root 327 Jan 26 19:57 /usr/sbin/vbox-fix-usb-rules.sh Its content refers to /etc/udev/rules.d/60-vboxdrv.rules file which is missing. That file has another location: # rpm -ql virtualbox-qt | grep '60-vboxdrv.rules' /usr/lib/udev/rules.d/60-vboxdrv.rules # ll /usr/lib/udev/rules.d/60-vboxdrv.rules -rw-r--r-- 1 root root 762 Jan 26 19:57 /usr/lib/udev/rules.d/60-vboxdrv.rules Installed virtualbox related RPMs are: # rpm -qa | grep virtualbox virtualbox-7.0.6-lp154.2.26.2.x86_64 virtualbox-kmp-default-7.0.6_k5.14.21_150400.24.41-lp154.2.26.2.x86_64 virtualbox-qt-7.0.6-lp154.2.26.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1198616] New: Emacs segfaults in xterm (or urxvt) without DISPLAY
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198616 Bug ID: 1198616 Summary: Emacs segfaults in xterm (or urxvt) without DISPLAY 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: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading to Tumbleweed 20220415 and emacs-28.1-393.10.x86_64, when I open xterm and unset DISPLAY, emacs almost always crashes. Even with -Q. Sometimes I can get something that looks like a potentially useful backtrace in gdb, sometimes not. The potentially useful one is: Thread 1 "emacs-gtk" received signal SIGSEGV, Segmentation fault. (gdb) bt #0 0x00000000004707a9 in () #1 0x00000000004748d3 in update_frame () #2 0x00000000004a0fd5 in () #3 0x00000000004976a9 in message3_nolog () #4 0x0000000000497978 in message3 () #5 0x00000000005df970 in Fmessage () #6 0x00000000005e3d81 in funcall_subr () #7 0x00000000005e2723 in Ffuncall () #8 0x0000000000629c70 in exec_byte_code () #9 0x00000000005e22e8 in () #10 0x00000000005e25bd in Ffuncall () #11 0x0000000000611308 in Fload () #12 0x00000000005e3e76 in funcall_subr () #13 0x00000000005e2723 in Ffuncall () #14 0x0000000000629c70 in exec_byte_code () #15 0x00000000005e22e8 in () #16 0x00000000005e7e31 in () #17 0x00000000005e8161 in eval_sub () #18 0x00000000006137af in () #19 0x000000000061600d in () #20 0x0000000000616371 in Feval_buffer () #21 0x00000000005e3e76 in funcall_subr () #22 0x00000000005e2723 in Ffuncall () #23 0x0000000000629c70 in exec_byte_code () #24 0x00000000005e22e8 in () #25 0x00000000005e25bd in Ffuncall () #26 0x0000000000611308 in Fload () #27 0x00000000005e3e76 in funcall_subr () #28 0x00000000005e2723 in Ffuncall () #29 0x0000000000629c70 in exec_byte_code () #30 0x00000000005e22e8 in () #31 0x00000000005e25bd in Ffuncall () #32 0x0000000000629c70 in exec_byte_code () #33 0x00000000005e22e8 in () #34 0x00000000005e25bd in Ffuncall () #35 0x0000000000629c70 in exec_byte_code () #36 0x00000000005e22e8 in () #37 0x00000000005e7e31 in () #38 0x00000000005e8161 in eval_sub () #39 0x000000000055f346 in () #40 0x00000000005e0cf7 in internal_condition_case () #41 0x000000000055f7b2 in () #42 0x00000000005e0c51 in internal_catch () #43 0x000000000055fb5b in () #44 0x000000000055fc5f in recursive_edit_1 () #45 0x000000000055fde3 in Frecursive_edit () #46 0x000000000046ae2c in main () (gdb) info threads Id Target Id Frame * 1 Thread 0x7fffec13b480 (LWP 18954) "emacs-gtk" 0x00000000004707a9 in ?? () 2 Thread 0x7fffeb347640 (LWP 18960) "gmain" 0x00007fffef35752f in __GI___poll (fds=0xb48020, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 (gdb) thread 2 [Switching to thread 2 (Thread 0x7fffeb347640 (LWP 18960))] #0 0x00007fffef35752f in __GI___poll (fds=0xb48020, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 29 return SYSCALL_CANCEL (poll, fds, nfds, timeout); (gdb) bt #0 0x00007fffef35752f in __GI___poll (fds=0xb48020, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007ffff6ef144e in () at /lib64/libglib-2.0.so.0 #2 0x00007ffff6ef156f in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x00007ffff6ef15c1 in () at /lib64/libglib-2.0.so.0 #4 0x00007ffff6f1bac5 in () at /lib64/libglib-2.0.so.0 #5 0x00007fffef2db2ba in start_thread (arg=<optimized out>) at pthread_create.c:442 #6 0x00007fffef365460 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Emacs seems to run fine in GNU screen (so this is my workaround) or in a virtual terminal. emacs-x11 and emacs-nox are also affected, except that both seem not crash under gdb (at least not now) and after that one successful start they also work in the same xterm window. But not in new ones. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1207674] New: VUL-0: CVE-2023-22486: ghc-cmark-gfm: cmark-gfm: quadratic complexity bug in handle_close_bracket may lead to a denial of service
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207674 Bug ID: 1207674 Summary: VUL-0: CVE-2023-22486: ghc-cmark-gfm: cmark-gfm: quadratic complexity bug in handle_close_bracket may lead to a denial of service Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/355235/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mimi.vx(a)gmail.com Reporter: thomas.leroy(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2023-22486 cmark-gfm is GitHub's fork of cmark, a CommonMark parsing and rendering library and program in C. Versions prior to 0.29.0.gfm.7 contain a polynomial time complexity issue in handle_close_bracket that may lead to unbounded resource exhaustion and subsequent denial of service. This vulnerability has been patched in 0.29.0.gfm.7. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-22486 https://github.com/github/cmark-gfm/security/advisories/GHSA-r572-jvj2-3m8p https://www.cve.org/CVERecord?id=CVE-2023-22486 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1208728] New: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208728 Bug ID: 1208728 Summary: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: victorfuga(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 6, my thinkpad x1 carbon will not enter s3 sleep even when set as the default sleep option. Checked a few distros and noted it was working using kernel 5.19 "LTS" in manjaro. Currently running Tumbleweed snapshot 20230226, sleep mode is set to "Linux" in the bios. Checked on lid close, sleep button in KDE, and Fn + 4 key combo. $ cat /sys/power/mem_sleep s2idle [deep] $ sudo journalctl | grep "PM: suspend" | tail -2 2�� 27 18:29:09 reisen kernel: PM: suspend entry (s2idle) 2�� 27 18:29:11 reisen kernel: PM: suspend exit -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1180882] New: perf does not build reproducibly
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1180882 Bug ID: 1180882 Summary: perf does not build reproducibly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1041090 Found By: Development Blocker: --- While working on reproducible builds for SLE and openSUSE, I found that our perf package differs across builds. /usr/bin/perf differs in ELF section .dynsym /usr/bin/perf differs in ELF section .rela.dyn because nftw in https://github.com/torvalds/linux/blob/v5.3/tools/perf/pmu-events/jevents.c… reads pmu-events/arch/x86/*/*.json in random filesystem readdir order -- You are receiving this mail because: You are on the CC list for the bug.

1 1