January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213043] New: windows:mingw:win{32|64}/mingw{32|64}-cross-cmake: no version support for generated mingw32(cmake:xxx) provides
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213043 Bug ID: 1213043 Summary: windows:mingw:win{32|64}/mingw{32|64}-cross-cmake: no version support for generated mingw32(cmake:xxx) provides Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- Qt6 packages often uses dependencies to cmake package including a version as shown below: %package devel Summary: Qt 6 base development meta package Requires: qt6-base-common-devel Requires: cmake(Qt6Concurrent) = %{real_version} Requires: cmake(Qt6Core) = %{real_version} Requires: cmake(Qt6DBus) = %{real_version} Requires: cmake(Qt6Gui) = %{real_version} Requires: cmake(Qt6Network) = %{real_version} Requires: cmake(Qt6OpenGL) = %{real_version} Requires: cmake(Qt6OpenGLWidgets) = %{real_version} Requires: cmake(Qt6PrintSupport) = %{real_version} Requires: cmake(Qt6Sql) = %{real_version} Requires: cmake(Qt6Test) = %{real_version} Requires: cmake(Qt6Widgets) = %{real_version} Requires: cmake(Qt6Xml) = %{real_version} BuildArch: noarch https://build.opensuse.org/package/view_file/KDE:Qt6/qt6-base/qt6-base.spec… Cmake-related provides generated by the named package do not currently support versions. This means that when porting Qt6 packages to MinGW, the versions would have to be removed manually or via script. It would therefore be helpful if a version were available for these generated "Provides". -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213028] New: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213028 Bug ID: 1213028 Summary: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- On building mingw32-qt6-imageformat for MinGW it turned out that the mentioned package does not have pkgconfig support ~/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats> osc build openSUSE_Leap_15.5 -j12 Building mingw32-qt6-imageformats.spec for openSUSE_Leap_15.5/x86_64 Getting buildconfig from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildconfig-openSUSE_Leap_15.5-x86_64 Getting buildinfo from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildinfo-openSUSE_Leap_15.5-x86_64.xml buildinfo is broken... it says: unresolvable: nothing provides mingw32(pkg:libmng) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215574] New: sshfs-3.7.4 hangs processes with Status "D"
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215574 Bug ID: 1215574 Summary: sshfs-3.7.4 hangs processes with Status "D" Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: E.Kuemmerle(a)fz-juelich.de QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I use sshfs to mount my home directory. This works fine since many years, including the version 3.7.3 of sshfs. After installing version 3.7.4 from https://download.opensuse.org/repositories/filesystems/15.5, simple file accesses still work, but when I try to login graphically, the login hangs because many processes hang with status "D": #ps -efl F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD ... 0 D myuser 9334 9218 0 80 0 - 62739 filena 13:53 ? 00:00:00 /usr/lib/xdg-permission-store 0 D myuser 9377 9218 0 80 0 - 158487 d_allo 13:53 ? 00:00:00 /usr/bin/ksmserver 0 D myuser 9379 9218 0 80 0 - 314812 d_allo 13:53 ? 00:00:00 /usr/bin/kded5 0 D myuser 9407 9218 0 80 0 - 186461 d_allo 13:53 ? 00:00:00 /usr/bin/plasmashell --no-respawn 0 D myuser 9506 9218 0 80 0 - 199330 d_allo 13:53 ? 00:00:00 /usr/lib/evolution-data-server/evolution-data-server/evolution-alarm-notify 0 D myuser 9515 9511 0 80 0 - 37989 d_allo 13:53 ? 00:00:00 oyranos-monitor -s --daemon 0 D myuser 9529 9218 0 80 0 - 156587 d_allo 13:53 ? 00:00:00 /usr/bin/kaccess 0 D myuser 9566 9377 0 80 0 - 161680 d_allo 13:53 ? 00:00:00 /usr/bin/kwin_x11 -session 1094a77331000144844708300000033840001_1448447132_823255 0 D myuser 9732 9218 0 80 0 - 11101 walk_c 13:58 ? 00:00:00 systemd-tmpfiles --user --clean The sshfs process does not die but file access to the sshfs filesystem is then no longer possible. I suppose the high access load causes the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1217409] New: memtest86+ v5 does not work on UEFI
by bugzilla_noreply＠suse.com 06 Mar '24

06 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217409 Bug ID: 1217409 Summary: memtest86+ v5 does not work on UEFI Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- memtest86+e is inherited from SLE-15:GA and wasn't touched ever since the original release. Interestingly it was not shipped in any SUSE product. Package is inherited to Leap 15.6 where users noticed that UEFI is supported only in v6 and above. Could we please update it to v6+? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219406] New: [BUG] kernel NULL pointer dereference with Linux 6.7.1-2-default
by bugzilla_noreply＠suse.com 06 Mar '24

06 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219406 Bug ID: 1219406 Summary: [BUG] kernel NULL pointer dereference with Linux 6.7.1-2-default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: kostas.peletidis(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just saw this bug on my work laptop. The desktop froze and only the mouse pointer was responsive. I connected to the laptop from another machine and noticed that Xorg was a zombie process. I also saw the following kernel messages: [ 8550.326847] pcieport 0000:00:08.1: PME: Spurious native interrupt! [13172.962208] BUG: kernel NULL pointer dereference, address: 0000000000000000 [13172.962228] #PF: supervisor read access in kernel mode [13172.962235] #PF: error_code(0x0000) - not-present page [13172.962243] PGD 0 P4D 0 [13172.962255] Oops: 0000 [#1] PREEMPT SMP NOPTI [13172.962266] CPU: 11 PID: 2019 Comm: Xorg.bin Not tainted 6.7.1-2-default #1 openSUSE Tumbleweed d50116cfdb1b14a701e904c894d8f1c040bf1146 [13172.962281] Hardware name: LENOVO 20XGS0V508/20XGS0V508, BIOS R1NET47W (1.17) 12/21/2021 [13172.962289] RIP: 0010:drm_mode_rmfb+0xb6/0x1c0 [13172.962308] Code: 00 00 4c 89 ef e8 7a 0e 3e 00 48 8b 83 98 00 00 00 48 2d 98 00 00 00 48 39 c3 0f 84 eb 00 00 00 31 d2 b9 01 00 00 00 4c 39 e0 <48> 8b 80 98 00 00 00 0f 44 d1 48 2d 98 00 00 00 48 39 c3 75 e8 85 [13172.962317] RSP: 0018:ffffa86fc2bbfc80 EFLAGS: 00010202 [13172.962327] RAX: ffffffffffffff68 RBX: ffff941bc60f1800 RCX: 0000000000000001 [13172.962334] RDX: 0000000000000001 RSI: ffff941bc2004920 RDI: ffff941bc60f18a8 [13172.962341] RBP: ffff941e7352b318 R08: ffff941bc2004b18 R09: ffff941c88c80200 [13172.962347] R10: 0000000000000000 R11: 0000000000000000 R12: ffff941e7352b300 [13172.962354] R13: ffff941bc60f18a8 R14: ffffa86fc2bbfd68 R15: 0000000000000004 [13172.962361] FS: 00007faa06805980(0000) GS:ffff941e9ef80000(0000) knlGS:0000000000000000 [13172.962368] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [13172.962374] CR2: 0000000000000000 CR3: 00000001045ce000 CR4: 0000000000750ef0 [13172.962379] PKRU: 55555554 [13172.962384] Call Trace: [13172.962390] <TASK> [13172.962403] ? __die+0x23/0x70 [13172.962423] ? page_fault_oops+0x14d/0x490 [13172.962434] ? ttwu_queue_wakelist+0xef/0x110 [13172.962446] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.962468] ? exc_page_fault+0x71/0x160 [13172.962480] ? asm_exc_page_fault+0x26/0x30 [13172.962495] ? drm_mode_rmfb+0xb6/0x1c0 [13172.962508] ? __pfx_drm_mode_rmfb_ioctl+0x10/0x10 [13172.962516] drm_ioctl_kernel+0xce/0x170 [13172.962525] ? __pfx_drm_mode_page_flip_ioctl+0x10/0x10 [13172.962543] drm_ioctl+0x256/0x490 [13172.962552] ? __pfx_drm_mode_rmfb_ioctl+0x10/0x10 [13172.962561] ? __pfx_drm_mode_page_flip_ioctl+0x10/0x10 [13172.962580] amdgpu_drm_ioctl+0x4e/0x90 [amdgpu c19de16ba0fd72478b307639f09a9c13c52c8d28] [13172.963085] __x64_sys_ioctl+0x97/0xd0 [13172.963098] do_syscall_64+0x64/0xe0 [13172.963108] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963116] ? syscall_exit_to_user_mode+0x2b/0x40 [13172.963122] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963129] ? do_syscall_64+0x70/0xe0 [13172.963137] ? switch_fpu_return+0x50/0xe0 [13172.963147] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963154] ? exit_to_user_mode_prepare+0x142/0x1f0 [13172.963165] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963172] ? syscall_exit_to_user_mode+0x2b/0x40 [13172.963178] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963185] ? do_syscall_64+0x70/0xe0 [13172.963192] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963199] ? do_syscall_64+0x70/0xe0 [13172.963206] ? syscall_exit_to_user_mode+0x2b/0x40 [13172.963212] ? srso_alias_return_thunk+0x5/0xfbef5 [13172.963219] ? do_syscall_64+0x70/0xe0 [13172.963227] ? __irq_exit_rcu+0x3b/0xb0 [13172.963242] entry_SYSCALL_64_after_hwframe+0x6e/0x76 [13172.963254] RIP: 0033:0x7faa067139ef [13172.963332] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [13172.963338] RSP: 002b:00007fff5e104280 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [13172.963346] RAX: ffffffffffffffda RBX: 00005608e31df550 RCX: 00007faa067139ef [13172.963351] RDX: 00007fff5e10431c RSI: 00000000c00464af RDI: 000000000000000e [13172.963355] RBP: 00007fff5e10431c R08: 00000005608e3575 R09: 0000000000000007 [13172.963360] R10: 00005608e35751a0 R11: 0000000000000246 R12: 00000000c00464af [13172.963364] R13: 000000000000000e R14: 00005608e12f3ff0 R15: 0000000000000040 [13172.963377] </TASK> [13172.963381] Modules linked in: tun rfcomm nf_conntrack_netbios_ns nf_conntrack_broadcast ccm af_packet 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_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink qrtr cmac algif_hash algif_skcipher af_alg bnep msr binfmt_misc snd_acp_legacy_mach snd_acp_mach snd_soc_nau8821 nls_iso8859_1 snd_soc_dmic snd_acp3x_pdm_dma snd_acp3x_rn snd_sof_amd_acp63 nls_cp437 snd_sof_amd_vangogh snd_sof_amd_rembrandt snd_sof_amd_renoir vfat snd_sof_amd_acp fat snd_ctl_led snd_sof_pci snd_sof_xtensa_dsp snd_hda_codec_realtek mt7921e snd_sof mt7921_common snd_hda_codec_generic btusb mt792x_lib snd_sof_utils btrtl mt76_connac_lib snd_hda_codec_hdmi btintel uvcvideo snd_soc_core intel_rapl_msr btbcm intel_rapl_common mt76 videobuf2_vmalloc btmtk snd_compress uvc snd_pcm_dmaengine snd_hda_intel videobuf2_memops edac_mce_amd bluetooth videobuf2_v4l2 snd_pci_ps snd_intel_dspcfg snd_intel_sdw_acpi [13172.963548] snd_rpl_pci_acp6x mac80211 videodev r8169 snd_acp_pci libarc4 thinkpad_acpi kvm_amd snd_acp_legacy_common snd_hda_codec snd_pci_acp6x videobuf2_common snd_pci_acp5x snd_hda_core realtek ecdh_generic mc ledtrig_audio snd_hwdep kvm mdio_devres cfg80211 snd_rn_pci_acp3x snd_pcm think_lmi platform_profile snd_acp_config irqbypass firmware_attributes_class snd_timer snd_soc_acpi wmi_bmof tiny_power_button efi_pstore libphy rfkill k10temp snd_pci_acp3x i2c_piix4 snd thermal soundcore ac joydev button nvme_fabrics fuse configfs dmi_sysfs ip_tables x_tables usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 amdxcp i2c_algo_bit drm_ttm_helper ttm drm_exec gpu_sched nvme drm_suballoc_helper xhci_pci drm_buddy xhci_pci_renesas ucsi_acpi hid_multitouch drm_display_helper nvme_core xhci_hcd aesni_intel cec typec_ucsi video hid_generic nvme_auth crypto_simd cryptd usbcore ccp roles rc_core t10_pi typec sp5100_tco battery [13172.963741] i2c_hid_acpi wmi i2c_hid serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq br_netfilter bridge stp llc efivarfs [13172.963781] CR2: 0000000000000000 [13172.963787] ---[ end trace 0000000000000000 ]--- [13172.963792] RIP: 0010:drm_mode_rmfb+0xb6/0x1c0 [13172.963801] Code: 00 00 4c 89 ef e8 7a 0e 3e 00 48 8b 83 98 00 00 00 48 2d 98 00 00 00 48 39 c3 0f 84 eb 00 00 00 31 d2 b9 01 00 00 00 4c 39 e0 <48> 8b 80 98 00 00 00 0f 44 d1 48 2d 98 00 00 00 48 39 c3 75 e8 85 [13172.963807] RSP: 0018:ffffa86fc2bbfc80 EFLAGS: 00010202 [13172.963813] RAX: ffffffffffffff68 RBX: ffff941bc60f1800 RCX: 0000000000000001 [13172.963818] RDX: 0000000000000001 RSI: ffff941bc2004920 RDI: ffff941bc60f18a8 [13172.963822] RBP: ffff941e7352b318 R08: ffff941bc2004b18 R09: ffff941c88c80200 [13172.963827] R10: 0000000000000000 R11: 0000000000000000 R12: ffff941e7352b300 [13172.963831] R13: ffff941bc60f18a8 R14: ffffa86fc2bbfd68 R15: 0000000000000004 [13172.963836] FS: 00007faa06805980(0000) GS:ffff941e9ef80000(0000) knlGS:0000000000000000 [13172.963841] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [13172.963846] CR2: 0000000000000000 CR3: 00000001045ce000 CR4: 0000000000750ef0 [13172.963851] PKRU: 55555554 [13172.963856] note: Xorg.bin[2019] exited with irqs disabled -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219198] New: pesign installation error
by bugzilla_noreply＠suse.com 05 Mar '24

05 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1219198 Bug ID: 1219198 Summary: pesign installation error 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: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I recently did a Leap 15.5 installation and saw the following error message in /var/log/zypp/history: # 2024-01-24 08:05:18 pesign-0.112-150000.4.18.1.x86_64.rpm installed ok # Additional rpm output: # warning: user pesign does not exist - using root # warning: group pesign does not exist - using root # warning: user pesign does not exist - using root # warning: group pesign does not exist - using root # 2024-01-24 08:05:18|install|pesign|0.112-150000.4.18.1|x86_64||repo-sle-update|70a227a2a14cd808569e4f7932409fc46f2c486081b8a0b618d2eb3503169db7| The error is due to the fact that the pesign user/group does not exist when the pesign package get installed. This is due to a bug introduced with pesign 0.112-150000.4.18.1. In such version of the package the pre scriptlet that in the previous version was executed when pesign was installed it is now executed when the package pesign-systemd is installed causing the error. The spec file should be fixed in this way: -%pre systemd +%pre getent group pesign >/dev/null || groupadd -r pesign getent passwd pesign >/dev/null || useradd -r -g pesign -d %{_localstatedir}/lib/pesign -s /bin/false -c "PE-COFF signing daemon" pesign + +%pre systemd %service_add_pre pesign.service -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1216071] New: Installation didn't have sof-firmware package
by bugzilla_noreply＠suse.com 05 Mar '24

05 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1216071 Bug ID: 1216071 Summary: Installation didn't have sof-firmware package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: federico(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- With the 20231006 snapshot of Tumbleweed, I got no sound. It seems that the installation procedure forgot to install the sof-firmware package. From the log: Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Oct 09 16:39:10 localhost kernel: usbcore: registered new interface driver uvcvideo Oct 09 16:39:10 localhost kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card0/input22 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: use msi interrupt mode Oct 09 16:39:10 localhost systemd[1]: Finished Load/Save Screen Backlight Brightness of backlight:intel_backlight. Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: hda codecs found, mask 5 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: DMICs detected in NHLT tables: 2 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: Direct firmware load for intel/sof/sof-adl-s.ri failed with error -2 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof firmware file is missing, you might need to Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: download it from https://github.com/thesofproject/sof-bin/ Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: failed to load DSP firmware -2 Oct 09 16:39:10 localhost kernel: sof-audio-pci-intel-tgl 0000:00:1f.3: error: sof_probe_work failed err: -2 Do you need a full journal, or some other data? -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1217005] New: VUL-0: CVE-2023-39913: Apache UIMA Java SDK: Deserialization of Untrusted Data, Improper Input Validation vulnerability
by bugzilla_noreply＠suse.com 05 Mar '24

05 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217005 Bug ID: 1217005 Summary: VUL-0: CVE-2023-39913: Apache UIMA Java SDK: Deserialization of Untrusted Data, Improper Input Validation vulnerability Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/384337/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: fstrba(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: stoyan.manolov(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Deserialization of Untrusted Data, Improper Input Validation vulnerability in Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK, Apache UIMA Java SDK.This issue affects Apache UIMA Java SDK: before 3.5.0. Users are recommended to upgrade to version 3.5.0, which fixes the issue. There are several locations in the code where serialized Java objects are deserialized without verifying the data. This affects in particular: * the deserialization of a Java-serialized CAS, but also other binary CAS formats that include TSI information using the CasIOUtils class; * the CAS Editor Eclipse plugin which uses the the CasIOUtils class to load data; * the deserialization of a Java-serialized CAS of the Vinci Analysis Engine service which can receive using Java-serialized CAS objects over network connections; * the CasAnnotationViewerApplet and the CasTreeViewerApplet; * the checkpointing feature of the CPE module. Note that the UIMA framework by default does not start any remotely accessible services (i.e. Vinci) that would be vulnerable to this issue. A user or developer would need to make an active choice to start such a service. However, users or developers may use the CasIOUtils in their own applications and services to parse serialized CAS data. They are affected by this issue unless they ensure that the data passed to CasIOUtils is not a serialized Java object. When using Vinci or using CasIOUtils in own services/applications, the unrestricted deserialization of Java-serialized CAS files may allow arbitrary (remote) code execution. As a remedy, it is possible to set up a global or context-specific ObjectInputFilter (cf. https://openjdk.org/jeps/290 and https://openjdk.org/jeps/415 ) if running UIMA on a Java version that supports it. Note that Java 1.8 does not support the ObjectInputFilter, so there is no remedy when running on this out-of-support platform. An upgrade to a recent Java version is strongly recommended if you need to secure an UIMA version that is affected by this issue. To mitigate the issue on a Java 9+ platform, you can configure a filter pattern through the "jdk.serialFilter" system property using a semicolon as a separator: To allow deserializing Java-serialized binary CASes, add the classes: * org.apache.uima.cas.impl.CASCompleteSerializer * org.apache.uima.cas.impl.CASMgrSerializer * org.apache.uima.cas.impl.CASSerializer * java.lang.String To allow deserializing CPE Checkpoint data, add the following classes (and any custom classes your application uses to store its checkpoints): * org.apache.uima.collection.impl.cpm.CheckpointData * org.apache.uima.util.ProcessTrace * org.apache.uima.util.impl.ProcessTrace_impl * org.apache.uima.collection.base_cpm.SynchPoint Make sure to use "!*" as the final component to the filter pattern to disallow deserialization of any classes not listed in the pattern. Apache UIMA 3.5.0 uses tightly scoped ObjectInputFilters when reading Java-serialized data depending on the type of data being expected. Configuring a global filter is not necessary with this version. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39913 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217416] New: MicroOS upgrade failed and screwed up nodes by deleting the root filesystem completely
by bugzilla_noreply＠suse.com 04 Mar '24

04 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1217416 Bug ID: 1217416 Summary: MicroOS upgrade failed and screwed up nodes by deleting the root filesystem completely Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: jreder(a)dimedis.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: We run K8s clusters using MicroOS for the nodes. K8s is provisioned with Terraform on Hetzner cloud platform using kube-hetzner Terraform module. Clusters ran fine for about six months with automatic upgrades and rebooting controlled using Kured. On November 16th the automatic upgrade failed on all nodes. On reboot after transactional-update ran: - /.snapshots is not mounted and empty - health-checker fails due to this - kubelet does not start - later transactional-update runs - it performs an "unused snapshot cleanup" and removes **all snapshots** from the filesystem - on next reboot the node is dead - no root filesystem present anymore This is the corresponding log output from transactional-update after the first boot: Nov 19 00:34:02 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: Creating a new grub2 config Nov 19 00:34:02 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: 2023-11-19 00:34:02 tukit 4.4.0 started Nov 19 00:34:02 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: 2023-11-19 00:34:02 Options: call 52 bash -c /usr/sbin/grub2-mkconfig > /boot/grub2/grub.cfg Nov 19 00:34:03 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: /var/lib/kubelet/pods not reset as customized by admin to unconfined_u:object_r:container_file_t:s0 Nov 19 00:34:03 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: /var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots not reset as customized by admin to unconfined_u:object_r:cont> Nov 19 00:34:03 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: 2023-11-19 00:34:03 Executing `bash -c /usr/sbin/grub2-mkconfig > /boot/grub2/grub.cfg`: Nov 19 00:34:03 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Generating grub configuration file ... Nov 19 00:34:03 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Found theme: /boot/grub2/themes/openSUSE/theme.txt Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Found linux image: /boot/vmlinuz-6.6.1-1-default Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Found initrd image: /boot/initrd-6.6.1-1-default Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Warning: os-prober will not be executed to detect other bootable partitions. Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Systems on them will not be added to the GRUB boot configuration. Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Check GRUB_DISABLE_OS_PROBER documentation entry. Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: Adding boot menu entry for UEFI Firmware Settings ... Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: done Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: 2023-11-19 00:34:04 Application returned with exit status 0. Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30290]: 2023-11-19 00:34:04 Transaction completed. Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30938]: 2023-11-19 00:34:04 tukit 4.4.0 started Nov 19 00:34:04 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30938]: 2023-11-19 00:34:04 Options: close 52 Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30938]: /var/lib/kubelet/pods not reset as customized by admin to unconfined_u:object_r:container_file_t:s0 Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30938]: /var/lib/rancher/k3s/agent/containerd/io.containerd.snapshotter.v1.overlayfs/snapshots not reset as customized by admin to unconfined_u:object_r:cont> Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30938]: 2023-11-19 00:34:05 New default snapshot is #52 (/.snapshots/52/snapshot). Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[30938]: 2023-11-19 00:34:05 Transaction completed. Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: Warning: The following files were changed in the snapshot, but are shadowed by Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: other mounts and will not be visible to the system: Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: /.snapshots/52/snapshot/var/lib/dbus/machine-id Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: WARNING: This snapshot has been created from a different base (47) Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: than the previous default snapshot (51) and does not Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: contain the changes from the latter. Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: New default snapshot is #52 (/.snapshots/52/snapshot). Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[18583]: transactional-update finished Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[31158]: 2023-11-19 00:34:05 tukit 4.4.0 started Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[31158]: 2023-11-19 00:34:05 Options: reboot kured Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[31158]: 2023-11-19 00:34:05 Triggering reboot using kured Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt transactional-update[31158]: 2023-11-19 00:34:05 Transaction completed. Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: transactional-update.service: Deactivated successfully. Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: Finished Update the system. Nov 19 00:34:05 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: transactional-update.service: Consumed 1min 15.285s CPU time. -- Boot 1a23c0e12e33484c99064b5dcc589168 -- Nov 20 00:07:10 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: Starting Update the system... Nov 20 00:07:10 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Checking for newer version. Nov 20 00:07:11 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: transactional-update 4.4.0 started Nov 20 00:07:11 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Options: cleanup dup reboot Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Separate /var detected. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Adding cleanup algorithm to snapshot #47 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19832]: Snapshot '47' not found. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19760]: ERROR: cannot set cleanup algorithm for snapshot #47 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Adding "important=yes" to snapshot #47 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19838]: Snapshot '47' not found. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19760]: ERROR: cannot set "important=yes for snapshot" #47 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Mark unused snapshot #51 for deletion Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19847]: Snapshot '51' not found. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19760]: ERROR: cannot set cleanup algorithm for snapshot #51 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/1 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/12 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/15 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/2 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/3 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/4 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/41 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/47 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/48 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/49 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/5 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/50 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/51 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/52 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/6 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/7 Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: Deleting unused overlay /var/lib/overlay/work-etc Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: 2023-11-20 00:07:12 tukit 4.4.0 started Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: 2023-11-20 00:07:12 Options: -c52 open Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: ERROR: Base snapshot '52' does not exist. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt transactional-update[19758]: transactional-update finished Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: transactional-update.service: Main process exited, code=exited, status=1/FAILURE Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: transactional-update.service: Failed with result 'exit-code'. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: Failed to start Update the system. Nov 20 00:07:12 k8stest1-wk-fsn1-cpx31-xgt systemd[1]: transactional-update.service: Consumed 1.375s CPU time. This happened: - at the same time on two different nodes in two different clusters - as soon as we reboot another node on which a transactional-update ran after 16th November 2023 So it looks this is not specific to - K8s - the nodes / network / anything in the infrastructure Reproducible: Always Steps to Reproduce: Sorry, can't provide information here since all this is automatically controlled by the system itself. Actual Results: After reboot of an updated node it doesn't start any workloads. It looks that it removes all snapshots from the system. On next boot there is no root filesystem anymore. The node is dead. Expected Results: Node is alive after transactional-update, even after several reboots. transactional-update should not do anything if the /.snapshots folder is empty! It should not delete all snapshots! I started a discussion for this case in the forum of the kube-hetzner project: https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/discussions/1… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215602] New: WARNING at drivers/acpi/platform_profile.c:74 platform_profile_show+0xa6/0xd0
by bugzilla_noreply＠suse.com 04 Mar '24

04 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215602 Bug ID: 1215602 Summary: WARNING at drivers/acpi/platform_profile.c:74 platform_profile_show+0xa6/0xd0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: jslaby(a)suse.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Happens for quite some time. > WARNING: CPU: 9 PID: 936 at drivers/acpi/platform_profile.c:74 platform_profile_show+0xa6/0xd0 [platform_profile] > Modules linked in: usblp rpcsec_gss_krb5 ... > CPU: 9 PID: 936 Comm: power-profiles- Kdump: loaded Tainted: G W 6.5.0-3.gf17167b-default #1 openSUSE Tumbleweed (u> > Hardware name: LENOVO 21CRS0K83K/21CRS0K83K, BIOS R22ET60W (1.30 ) 02/09/2023 > RIP: 0010:platform_profile_show+0xa6/0xd0 [platform_profile] > Code: c6 b0 90 b4 c0 48 89 ef e8 07 aa 37 ca 48 98 48 8b 54 24 08 65 48 2b 14 25 28 00 00 00 75 2b 48 83 c4 10 5b 5d e9 5a c1 b9 ca> > RSP: 0018:ffffb8e8c2f57d50 EFLAGS: 00010216 > RAX: 000000000eaefaf0 RBX: 0000000000000000 RCX: ffffffffc0b47060 > RDX: 0000000000000000 RSI: ffffb8e8c2f57d54 RDI: ffffffffc0b470a0 > RBP: ffff9af8144b8000 R08: ffff9afc5f173180 R09: ffff9af540eade00 > R10: 000000010696c009 R11: 000000000003f680 R12: ffffb8e8c2f57e10 > R13: ffffb8e8c2f57de8 R14: 0000000000000001 R15: ffffb8e8c2f57e80 > FS: 00007f91830698c0(0000) GS:ffff9afc5ee80000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 00007ffa73d181e8 CR3: 0000000103226000 CR4: 0000000000750ee0 > PKRU: 55555554 > Call Trace: > <TASK> > sysfs_kf_seq_show+0xab/0x100 > seq_read_iter+0x123/0x480 > vfs_read+0x1b8/0x300 Here: if (WARN_ON((profile < 0) || (profile >= ARRAY_SIZE(profile_names)))) { Added a printk to dump profile and cur_profile->profile_get (I assume dytc_profile_get()). -- You are receiving this mail because: You are on the CC list for the bug.

1 4