June 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199885] [Build 20220523] plasma/Wayland glitches
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199885 https://bugzilla.suse.com/show_bug.cgi?id=1199885#c3 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #3 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks a lot! Accepted. Closing ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199052] amd iommu- warning after resume
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199052 https://bugzilla.suse.com/show_bug.cgi?id=1199052#c3 --- Comment #3 from Joerg Roedel <jroedel(a)suse.com> --- Upstream fix is: commit 42bb5aa043382f09bef2cc33b8431be867c70f8e Author: Joerg Roedel <jroedel(a)suse.de> Date: Fri May 20 12:22:14 2022 +0200 iommu/amd: Increase timeout waiting for GA log enablement -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199059] New: libqhull_r8_0.x86_64: E: binary-or-shlib-defines-rpath (Badness: 10000) /usr/lib64/libqhull_r.so.8.0.2 lib64
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199059 Bug ID: 1199059 Summary: libqhull_r8_0.x86_64: E: binary-or-shlib-defines-rpath (Badness: 10000) /usr/lib64/libqhull_r.so.8.0.2 lib64 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- RPATH points to 'lib64' folder, please fix it. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1195123] VUL-1: CVE-2021-45343: a NULL pointer dereference in libdxfrw in LibreCAD allows an attacker to crash the application via a crafted DXF document
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1195123 https://bugzilla.suse.com/show_bug.cgi?id=1195123#c4 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com Assignee|jslaby(a)suse.com |security-team(a)suse.de --- Comment #4 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #3) > (In reply to Carlos L�pez from comment #1) > > - openSUSE:Factory/librecad > > Already fixed long time ago: > https://build.opensuse.org/request/show/948961 This too: https://build.opensuse.org/request/show/955938 And SP4 was fixed rather recently: https://build.opensuse.org/request/show/980086 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195123] VUL-1: CVE-2021-45343: a NULL pointer dereference in libdxfrw in LibreCAD allows an attacker to crash the application via a crafted DXF document
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1195123 https://bugzilla.suse.com/show_bug.cgi?id=1195123#c3 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Carlos L�pez from comment #1) > - openSUSE:Factory/librecad Already fixed long time ago: https://build.opensuse.org/request/show/948961 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199186] New: VUL-1: CVE-2021-27419: klee-uclibc: uClibc-ng versions prior to 1.0.37 are vulnerable to integer wrap-around in functions malloc-simple
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199186 Bug ID: 1199186 Summary: VUL-1: CVE-2021-27419: klee-uclibc: uClibc-ng versions prior to 1.0.37 are vulnerable to integer wrap-around in functions malloc-simple Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/330633/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: jslaby(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2021-27419 uClibc-ng versions prior to 1.0.37 are vulnerable to integer wrap-around in functions malloc-simple. This improper memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-27419 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27419 https://downloads.uclibc-ng.org/releases/ https://www.cisa.gov/uscert/ics/advisories/icsa-21-119-04 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1199885] [Build 20220523] plasma/Wayland glitches
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199885 https://bugzilla.suse.com/show_bug.cgi?id=1199885#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |sndirsch(a)suse.com Component|KDE Workspace (Plasma) |X.Org Assignee|opensuse-kde-bugs@opensuse. |fvogt(a)suse.com |org | QA Contact|qa-bugs(a)suse.de |gfx-bugs(a)suse.de --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Fabian Vogt from comment #1) > 0522 contained a Mesa update, might be related. Yep, it's https://gitlab.freedesktop.org/mesa/mesa/-/issues/6552. Not just Plasma, but all swrast users on kms are affected. Fix submitted as https://build.opensuse.org/request/show/980303. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199909] NXP i.MX8MQ-EVK not able to recognize eMMC
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199909 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcheung(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200048] New: Display sometimes dies after waking up computer
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200048 Bug ID: 1200048 Summary: Display sometimes dies after waking up computer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: aaron.schweiger(a)gmail.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0 Build Identifier: After moving my mouse, instead of asking for a password, the display switches to text mode before dying. I use my NVIDIA for GPGPU, so I tried to install a minimal system: i+ | kernel-firmware-nvidia | package | 20220516-1.1 | noarch | Main Repository (OSS) i+ | nvidia-computeG06 | package | 515.43.04-10.2 | x86_64 | nVidia Graphics Drivers i+ | nvidia-gfxG06-kmp-default | package | 515.43.04_k5.17.7_1-10.5 | x86_64 | nVidia Graphics Drivers i+ | libdrm_nouveau2 | package | 2.4.110-1.2 | x86_64 | Main Repository (OSS) inxi -Gxxx Graphics: Device-1: NVIDIA TU102 [GeForce RTX 2080 Ti] vendor: eVga.com. driver: nvidia v: 515.43.04 bus-ID: 03:00.0 chip-ID: 10de:1e04 class-ID: 0300 Display: x11 server: X.Org 21.1.3 compositor: kwin_x11 driver: loaded: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: llvmpipe (LLVM 14.0.3 256 bits) v: 4.5 Mesa 22.1.0 direct render: Yes The system itself is a dual Xeon Dell 7910 with ECC memory. Here's an Oops that I suspect is the cause of the issue: May 30 20:57:18 localhost.localdomain kernel: PM: hibernation: hibernation exit May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device HDMI-0. May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices May 30 20:57:18 localhost.localdomain kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices May 30 20:57:18 localhost.localdomain kernel: BUG: kernel NULL pointer dereference, address: 0000000000000800 May 30 20:57:18 localhost.localdomain kernel: #PF: supervisor read access in kernel mode May 30 20:57:18 localhost.localdomain kernel: #PF: error_code(0x0000) - not-present page May 30 20:57:18 localhost.localdomain kernel: PGD 0 P4D 0 May 30 20:57:18 localhost.localdomain kernel: Oops: 0000 [#1] PREEMPT SMP PTI May 30 20:57:18 localhost.localdomain kernel: CPU: 58 PID: 15864 Comm: Xorg.bin Tainted: P S W OE 5.17.7-1-default #1 openSUSE Tumbleweed b4ba1fcd97f0731b1076a42506ea31afd2937a1c May 30 20:57:18 localhost.localdomain kernel: Hardware name: Dell Inc. Precision Tower 7910/0215PR, BIOS A34 10/19/2020 May 30 20:57:18 localhost.localdomain kernel: RIP: 0010:_nv002439kms+0x24/0x110 [nvidia_modeset] May 30 20:57:18 localhost.localdomain kernel: Code: 75 84 5b c3 66 90 89 f6 41 56 41 55 41 54 55 41 89 d5 48 69 ee c0 2f 00 00 53 48 8b 87 58 04 00 00 49 89 fc 48 89 cf 48 89 cb <4c> 8b b4 28 00 08 00 00 e8 2f ff ff ff 41 83 fd 03 0f 87 c5 00 00 May 30 20:57:18 localhost.localdomain kernel: RSP: 0018:ffff9a46a68236c0 EFLAGS: 00010206 May 30 20:57:18 localhost.localdomain kernel: RAX: 0000000000000000 RBX: ffff9a46a21cf608 RCX: ffff9a46a21cf608 May 30 20:57:18 localhost.localdomain kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9a46a21cf608 May 30 20:57:18 localhost.localdomain kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000004 May 30 20:57:18 localhost.localdomain kernel: R10: 0000000000000004 R11: ffffffffc3b62570 R12: ffff8dee86c05008 May 30 20:57:18 localhost.localdomain kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 May 30 20:57:18 localhost.localdomain kernel: FS: 00007fbcf8028940(0000) GS:ffff8e157f980000(0000) knlGS:0000000000000000 May 30 20:57:18 localhost.localdomain kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 30 20:57:18 localhost.localdomain kernel: CR2: 0000000000000800 CR3: 00000014519b4004 CR4: 00000000001706e0 May 30 20:57:18 localhost.localdomain kernel: Call Trace: May 30 20:57:18 localhost.localdomain kernel: <TASK> May 30 20:57:18 localhost.localdomain kernel: ? _nv002567kms+0x6c9/0x2cd0 [nvidia_modeset 0e35234a034c3728c2fa25d8a19b0c9b91201dbf] May 30 20:57:18 localhost.localdomain kernel: ? alloc_vmap_area+0x94/0x830 May 30 20:57:18 localhost.localdomain kernel: ? kmem_cache_alloc_node+0x1c0/0x370 May 30 20:57:18 localhost.localdomain kernel: ? prepare_alloc_pages.constprop.0+0x82/0x140 May 30 20:57:18 localhost.localdomain kernel: ? __alloc_pages_bulk+0x30e/0x690 May 30 20:57:18 localhost.localdomain kernel: ? vmap_small_pages_range_noflush+0x301/0x4b0 May 30 20:57:18 localhost.localdomain kernel: ? __vmalloc_node_range+0x38f/0x510 May 30 20:57:18 localhost.localdomain kernel: ? _nv000534kms+0x50/0x50 [nvidia_modeset 0e35234a034c3728c2fa25d8a19b0c9b91201dbf] May 30 20:57:18 localhost.localdomain kernel: ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset 0e35234a034c3728c2fa25d8a19b0c9b91201dbf] May 30 20:57:18 localhost.localdomain kernel: ? nvkms_ioctl_from_kapi+0x47/0x80 [nvidia_modeset 0e35234a034c3728c2fa25d8a19b0c9b91201dbf] May 30 20:57:18 localhost.localdomain kernel: ? _nv000019kms+0x691/0x7f0 [nvidia_modeset 0e35234a034c3728c2fa25d8a19b0c9b91201dbf] May 30 20:57:18 localhost.localdomain kernel: ? drm_connector_list_iter_next+0x81/0xb0 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? nv_drm_atomic_apply_modeset_config.isra.0+0x48d/0x540 [nvidia_drm 840cbbe698be756b715aead483c5859533ca8672] May 30 20:57:18 localhost.localdomain kernel: ? drm_atomic_check_only+0x5a7/0x9f0 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? drm_atomic_commit+0x13/0x60 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? drm_atomic_helper_set_config+0x6d/0xa0 [drm_kms_helper b3a822f6764fffddcd0766156054ee91056277a4] May 30 20:57:18 localhost.localdomain kernel: ? drm_mode_setcrtc+0x395/0x780 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? drm_mode_getcrtc+0x170/0x170 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? drm_ioctl_kernel+0xbe/0x160 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? drm_ioctl+0x21c/0x410 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? drm_mode_getcrtc+0x170/0x170 [drm eceed2d906d3f73f699f70947de57244439bee85] May 30 20:57:18 localhost.localdomain kernel: ? __x64_sys_ioctl+0x8d/0xc0 May 30 20:57:18 localhost.localdomain kernel: ? do_syscall_64+0x5b/0x80 May 30 20:57:18 localhost.localdomain kernel: ? do_syscall_64+0x67/0x80 May 30 20:57:18 localhost.localdomain kernel: ? exit_to_user_mode_prepare+0x194/0x230 May 30 20:57:18 localhost.localdomain kernel: ? syscall_exit_to_user_mode+0x18/0x40 May 30 20:57:18 localhost.localdomain kernel: ? do_syscall_64+0x67/0x80 May 30 20:57:18 localhost.localdomain kernel: ? exit_to_user_mode_prepare+0x194/0x230 May 30 20:57:18 localhost.localdomain kernel: ? syscall_exit_to_user_mode+0x18/0x40 May 30 20:57:18 localhost.localdomain kernel: ? do_syscall_64+0x67/0x80 May 30 20:57:18 localhost.localdomain kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xae May 30 20:57:18 localhost.localdomain kernel: </TASK> May 30 20:57:18 localhost.localdomain kernel: Modules linked in: af_packet intel_rapl_msr iTCO_wdt intel_pmc_bxt iTCO_vendor_support mei_wdt ucsi_ccg typec_ucsi typec roles dell_wmi sparse_keymap video dell_smm_hwmon nvidia_drm(POE) intel_rapl_common nvidia_modeset(POE) sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm dell_smbios dcdbas nvidia_uvm(POE) irqbypass intel_wmi_thunderbolt dell_wmi_descriptor wmi_bmof pcspkr igb snd_hda_codec_realtek i2c_i801 i2c_algo_bit i2c_smbus lpc_ich snd_hda_codec_generic dca ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg nvidia(POE) snd_intel_sdw_acpi joydev snd_hda_codec snd_hda_core snd_hwdep mei_me drm_kms_helper e1000e snd_pcm mei cec snd_timer rc_core snd syscopyarea sysfillrect sysimgblt i2c_nvidia_gpu fb_sys_fops soundcore nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat May 30 20:57:18 localhost.localdomain kernel: nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security nfnetlink rfkill ip6table_filter ip6_tables iptable_filter bpfilter dmi_sysfs squashfs loop tiny_power_button xfs drm fuse configfs ip_tables x_tables hid_generic usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel mxm_wmi aesni_intel xhci_pci crypto_simd xhci_pci_renesas cryptd xhci_hcd ehci_pci ehci_hcd mpt3sas usbcore sr_mod cdrom raid_class scsi_transport_sas wmi button btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr May 30 20:57:18 localhost.localdomain kernel: CR2: 0000000000000800 May 30 20:57:18 localhost.localdomain kernel: ---[ end trace 0000000000000000 ]--- May 30 20:57:18 localhost.localdomain kernel: RIP: 0010:_nv002439kms+0x24/0x110 [nvidia_modeset] May 30 20:57:18 localhost.localdomain kernel: Code: 75 84 5b c3 66 90 89 f6 41 56 41 55 41 54 55 41 89 d5 48 69 ee c0 2f 00 00 53 48 8b 87 58 04 00 00 49 89 fc 48 89 cf 48 89 cb <4c> 8b b4 28 00 08 00 00 e8 2f ff ff ff 41 83 fd 03 0f 87 c5 00 00 May 30 20:57:18 localhost.localdomain kernel: RSP: 0018:ffff9a46a68236c0 EFLAGS: 00010206 I use a cheap KVM to switch between computers. It seems likely the KVM is constantly disconnecting and reconnecting HDMI as I switch between computers and that is possibly related to the observed behavior. (As a possible work-around, I will try to use a DP-to-HDMI adapter.) Reproducible: Sometimes Steps to Reproduce: 1. Wait for computer to idle for a long time, 2. Use KVM to use other computer 2. Switch to computer via KVM 3. Move mouse to get out of lock screen --> crash happens -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1200077] openSUSE-Leap-15.4-GNOME-Live-x86_64-Build6.157-Media.iso does not boot
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1200077 https://bugzilla.suse.com/show_bug.cgi?id=1200077#c3 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Ulrich.Windl(a)rz.u | |ni-regensburg.de) --- Comment #3 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Ulrich Windl from comment #2) > I could boot the same stick on an older PC using an Intel CPU (6th gen). > However I noticed that not just the usual two boot entries (UEFI and legacy) > were displayed, but several legacy ones. That might be a bug in the PC's > BIOS, or maybe that's the issue that prevented boot on the Lenovo TP. It's possible that it can't decide whether to boot it as EFI, or legacy in USB, HDD or CDROM emulation mode... Do you have something like a "Boot from EFI file" option you can try? > I also noticed that during first boot a third partition was created on the > USB stick, adding an ext4 filesystem used as overlay filesystem. > Usual expectation of a live system is that it does not change the medium it > is booted from, at least not without asking for permission to do so, but > that might be a different issue. That's expected, that's the automatic persistence feature. -- You are receiving this mail because: You are on the CC list for the bug.

1 0