May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224789] New: VUL-0: CVE-2024-33900: keepassxc: recovery of cleartext credentials
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1224789 Bug ID: 1224789 Summary: VUL-0: CVE-2024-33900: keepassxc: recovery of cleartext credentials Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/406770/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mrueckert(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- KeePassXC 2.7.7 allows attackers to recover cleartext credentials. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-33900 https://www.cve.org/CVERecord?id=CVE-2024-33900 https://gist.github.com/Fastor01/30c6d89c842feb1865ec2cd2d3806838 https://keepassxc.org/blog/ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215701] New: VUL-0: CVE-2023-40581: yt-dlp: template expansion in `--exec` flag
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1215701 Bug ID: 1215701 Summary: VUL-0: CVE-2023-40581: yt-dlp: template expansion in `--exec` flag Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/379815/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: jengelh(a)inai.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: rfrohl(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- yt-dlp is a youtube-dl fork with additional features and fixes. yt-dlp allows the user to provide shell command lines to be executed at various stages in its download steps through the `--exec` flag. This flag allows output template expansion in its argument, so that metadata values may be used in the shell commands. The metadata fields can be combined with the `%q` conversion, which is intended to quote/escape these values so they can be safely passed to the shell. However, the escaping used for `cmd` (the shell used by Python's `subprocess` on Windows) does not properly escape special characters, which can allow for remote code execution if `--exec` is used directly with maliciously crafted remote data. This vulnerability only impacts `yt-dlp` on Windows, and the vulnerability is present regardless of whether `yt-dlp` is run from `cmd` or from `PowerShell`. Support for output template expansion in `--exec`, along with this vulnerable behavior, was added to `yt-dlp` in version 2021.04.11. yt-dlp version 2023.09.24 fixes this issue by properly escaping each special character. `\n` will be replaced by `\r` as no way of escaping it has been found. It is recommended to upgrade yt-dlp to version 2023.09.24 as soon as possible. Also, always be careful when using --exec, because while this specific vulnerability has been patched, using unvalidated input in shell commands is inherently dangerous. For Windows users who are not able to upgrade: 1. Avoid using any output template expansion in --exec other than {} (filepath). 2. If expansion in --exec is needed, verify the fields you are using do not contain ", | or &. 3. Instead of using --exec, write the info json and load the fields from it instead. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-40581 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222859] New: VUL-0: CVE-2024-32019: netdata: local privilege escalation and command execution via untrusted search path
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1222859 Bug ID: 1222859 Summary: VUL-0: CVE-2024-32019: netdata: local privilege escalation and command execution via untrusted search path Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/401694/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mia(a)0x0.st Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- Netdata is an open source observability tool. In affected versions the `ndsudo` tool shipped with affected versions of the Netdata Agent allows an attacker to run arbitrary programs with root permissions. The `ndsudo` tool is packaged as a `root`-owned executable with the SUID bit set. It only runs a restricted set of external commands, but its search paths are supplied by the `PATH` environment variable. This allows an attacker to control where `ndsudo` looks for these commands, which may be a path the attacker has write access to. This may lead to local privilege escalation. This vulnerability has been addressed in versions 1.45.3 and 1.45.2-169. Users are advised to upgrade. There are no known workarounds for this vulnerability. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-32019 https://www.cve.org/CVERecord?id=CVE-2024-32019 https://github.com/netdata/netdata/pull/17377 https://github.com/netdata/netdata/security/advisories/GHSA-pmhq-4cxq-wj93 https://bugzilla.redhat.com/show_bug.cgi?id=2274984 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214211] New: "Loading basic drivers" is printed twice on the screen when loading installation system
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1214211 Bug ID: 1214211 Summary: "Loading basic drivers" is printed twice on the screen when loading installation system 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: dheidler(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 868778 --> https://bugzilla.suse.com/attachment.cgi?id=868778&action=edit screenshot Something like this is printed: Loading basic drivers...Loading basic drivers ok Expected: Loading basic drivers... ok -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221918] New: VUL-0: CVE-2024-2824: jhead: heap-based buffer overflow in function PrintFormatNumber
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1221918 Bug ID: 1221918 Summary: VUL-0: CVE-2024-2824: jhead: heap-based buffer overflow in function PrintFormatNumber Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/398716/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: pgajdos(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- A vulnerability was found in Matthias-Wandel jhead 3.08 and classified as critical. This issue affects the function PrintFormatNumber of the file exif.c. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-257711. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-2824 https://www.cve.org/CVERecord?id=CVE-2024-2824 https://github.com/Matthias-Wandel/jhead/files/14613084/poc.zip https://github.com/Matthias-Wandel/jhead/issues/84 https://vuldb.com/?ctiid.257711 https://vuldb.com/?id.257711 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223446] New: zypper dup uninstalls > 100 base packages (guess: because of unknown repo signing key)
by bugzilla_noreply＠suse.com 04 Oct '24

04 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1223446 Bug ID: 1223446 Summary: zypper dup uninstalls > 100 base packages (guess: because of unknown repo signing key) 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: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874527 --> https://bugzilla.suse.com/attachment.cgi?id=874527&action=edit y2logs.tar.xz Environment: a s390x (zSystems) VM on the LinuxOne community cloud (https://linuxone.cloud.marist.edu) originally SLE 15 SP4, upgraded to Tumbleweed. To automate the Tumbleweed updates, I enabled os-update, which basically calls zypper dup -y --auto-agree-with-product-licenses This automated update worked on 2024-04-04. For some (so far unknown) reason, the automated zypper dup on 2024-04-26 uninstalled lots of packages, including quite some base packages (for example sudo, less, vim, file, shadow), and left the system in a half-broken state. At least ssh login and su still worked. After re-creating /etc/resolv.conf and reinstalling the removed packages, I could get some logs and fix the system. (I had a similar breakage on another VM some months ago, but back then, I didn't know the root password and therefore couldn't collect logs.) An interesting detail is that zypper asked me to trust a key today: # zypper ref Repository 'repo-openh264 (%{distver})' is up to date. New repository or package signing key received: Repository: repo-oss (%{distver}) Key Fingerprint: F00C 20EF 1E11 14C9 B5F6 9B22 76CA 4244 F6AB 3975 Key Name: openSUSE:Factory:zSystems OBS Project <openSUSE:Factory:zSystems@build.opensuse.org> Key Algorithm: RSA 2048 Key Created: Tue 02 Aug 2022 11:09:47 PM EDT Key Expires: Thu 10 Oct 2024 11:09:47 PM EDT Rpm Name: gpg-pubkey-f6ab3975-62e9e6fb That might already be a hint what caused the removal of the packages. If I zypper mr -d openSUSE:repo-oss zypper dup it proposes to delete 108 packages - and on a quick look, the list looks similar to what was removed automagically. My _guess_ is that the missing key had a similar result as disabling the repo. Still, even "zypper dup -y" should error out if a repo is signed with an unknown key, instead of silently disabling the repo and removing seemingly "orphaned" packages. I'll attach the y2logs so that you can check if my guess is correct ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1216797] New: SeaMonkey fails to build with rust >= 1.48
by bugzilla_noreply＠suse.com 03 Oct '24

03 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1216797 Bug ID: 1216797 Summary: SeaMonkey fails to build with rust >= 1.48 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- SeaMonkey was failing to build with rust >= 1.48 due to upstream bug <https://bugzilla.mozilla.org/show_bug.cgi?id=1860935>. To fix this issue, I have added a patch to the SeaMonkey 2.53.17.1 packages provided by the mozilla/seamonkey package on OBS: <https://build.opensuse.org/package/show/mozilla/seamonkey>. I am requesting that these changes be included in Leap 15.4 and 15.5. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216083] New: cockpit-ws: theme QA
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1216083 Bug ID: 1216083 Summary: cockpit-ws: theme QA Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Cockpit-bugs(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: Cockpit-bugs(a)suse.de, qa-bugs(a)suse.de Depends on: 1216082 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1216082 +++ We should add openQA test for basic theme and login -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1216082] New: cockpit-ws: theme missing
by bugzilla_noreply＠suse.com 01 Oct '24

01 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1216082 Bug ID: 1216082 Summary: cockpit-ws: theme missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Cockpit-bugs(a)suse.de Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The theme seems to not be loaded correcly. It looks very dark, like the default theme. See MicroOS 5.1 for correct theme. TW, 5.5 need fixes. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1219395] New: get-edid segfault
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1219395 Bug ID: 1219395 Summary: get-edid segfault Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: jiri.belka(a)suse.com QA Contact: packagehub-bugs(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 872339 --> https://bugzilla.suse.com/attachment.cgi?id=872339&action=edit getappcore output read-edid-3.0.2-bp155.3.9.x86_64 sles-release-15.5-150500.43.4.x86_64 avocado:~ # get-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Looks like no busses have an EDID. Sorry! Attempting to use the classical VBE interface Illegal instruction (core dumped) avocado:~ # coredumpctl list TIME PID UID GID SIG COREFILE EXE SIZE Wed 2024-01-31 08:07:15 CET 31656 0 0 SIGILL present /usr/bin/get-edid 27.3K Wed 2024-01-31 08:09:05 CET 31755 0 0 SIGILL present /usr/bin/get-edid 27.3K avocado:~ # systool -vc drm | grep -P 'Class Device path = .*drm/card' Class Device path = "/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0/card0-VGA-1" Class Device path = "/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0" Class Device path = "/sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0/card0-Virtual-1" avocado:~ # ls -1 /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0/card0*/edid /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0/card0-VGA-1/edid /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0/card0-Virtual-1/edid But, `edid' files do not provide any data, there is no monitor attached to it. ls -1 /sys/devices/pci0000:00/0000:00:1c.5/0000:02:00.0/0000:03:00.0/drm/card0/card0*/edid | xargs -L 1 od -A n -t x1 | wc -l 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1215663] New: # CONFIG_SCHED_AUTOGROUP is not set causes Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215663 Bug ID: 1215663 Summary: # CONFIG_SCHED_AUTOGROUP is not set causes Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice(). Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vvedomil(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I tried to play over Steam on OpenSUSE Tumbleweed and the terminal reported the following error: Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice(). Autogroup scheduling needs to be enabled during kernel compilation. I checked that on https://github.com/SUSE/kernel-source/blob/15b4ad8fb5f18870bb9e4011a2bb53cb… I can see # CONFIG_SCHED_AUTOGROUP is not set, that's the origin of the issue. So many distros enable that by default and I've never seen this issue with Steam on distros where is set CONFIG_SCHED_AUTOGROUP=y Examples: Arch Linux: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/main… CachyOS: https://github.com/CachyOS/linux-cachyos/blob/1d74c2037cd78f292fb6606708fa8… Could I ask to change that? Change config, build a kernel with CONFIG_SCHED_AUTOGROUP=y, and make the OpenSUSE kernel and the whole distro more friendly to gaming through Steam. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216851] New: kernel BUG at ../mm/slub.c:379!
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1216851 Bug ID: 1216851 Summary: kernel BUG at ../mm/slub.c:379! Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Observed today first time when doing day-to-day work with firefox on a laptop logged in as plain user. Potential dupe #1190482 [226385.604827] kernel BUG at ../mm/slub.c:379! [226385.604844] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI [226385.604853] CPU: 4 PID: 765 Comm: irq/176-iwlwifi Kdump: loaded Tainted: G N 5.14.21-150400.24.88-default #1 SLE15-SP4 bd2f624c6b628ccd74aec14e859f7b291002e62d [226385.604866] Hardware name: LENOVO 20W000ATGE/20W000ATGE, BIOS N34ET53W (1.53 ) 08/31/2022 [226385.604872] RIP: 0010:__slab_free+0x2ba/0x4b0 [226385.604884] Code: 85 8e 00 00 00 45 85 c9 0f 84 b6 00 00 00 48 81 c4 88 00 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d 49 8d 65 f0 41 5d c3 cc cc cc cc <0f> 0b 65 ff 05 fd 17 31 79 f0 49 0f ba 2c 24 00 0f 83 31 ff ff ff [226385.604894] RSP: 0018:ffffb92c80234aa0 EFLAGS: 00010246 [226385.604902] RAX: ffff9ad50daf4070 RBX: 000000008020001a RCX: ffff9ad50daf4000 [226385.604908] RDX: ffff9ad50daf4000 RSI: fffffaff0736bd00 RDI: ffff9ad49b881c00 [226385.604914] RBP: ffffb92c80234b50 R08: 0000000000000001 R09: ffffffff872564b3 [226385.604919] R10: ffff9ad4821d0840 R11: ffff9ad50daf4000 R12: fffffaff0736bd00 [226385.604924] R13: ffff9ad50daf4000 R14: ffff9ad49b881c00 R15: ffff9ad50daf4000 [226385.604930] FS: 0000000000000000(0000) GS:ffff9ad79f500000(0000) knlGS:0000000000000000 [226385.604937] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [226385.604942] CR2: 00007f4cc3e6c000 CR3: 0000000159c10006 CR4: 0000000000770ee0 [226385.604949] PKRU: 55555554 [226385.604953] Call Trace: [226385.604958] <IRQ> [226385.604966] ? iwl_mvm_tx_mpdu+0x204/0x580 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605002] ? kmem_cache_free+0x3c0/0x410 [226385.605011] ? kfree_skb_list+0x13/0x30 [226385.605021] ? kmem_cache_free+0x3c0/0x410 [226385.605029] kmem_cache_free+0x3c0/0x410 [226385.605037] kfree_skb_list+0x13/0x30 [226385.605045] ieee80211_report_used_skb+0xaf/0x490 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605098] ieee80211_tx_status_ext+0x510/0xb30 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605145] ieee80211_tx_status+0x7c/0xb0 [mac80211 27f3494b511335547355ff5927e7ac5c52c3181a] [226385.605192] iwl_mvm_tx_reclaim+0x376/0x3f0 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605224] iwl_mvm_rx_ba_notif+0x187/0x360 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605251] iwl_mvm_rx_common+0xe3/0x2e0 [iwlmvm 8cc7b51ab5d521e96ea680d180f15f69cb14c62f] [226385.605277] iwl_pcie_rx_handle+0x4db/0x8f0 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605309] iwl_pcie_napi_poll_msix+0x29/0xc0 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605335] __napi_poll+0x2a/0x180 [226385.605344] net_rx_action+0x24c/0x2a0 [226385.605352] __do_softirq+0xd2/0x2c0 [226385.605360] ? irq_forced_thread_fn+0x80/0x80 [226385.605371] do_softirq+0x71/0x80 [226385.605381] </IRQ> [226385.605385] <TASK> [226385.605389] __local_bh_enable_ip+0x64/0x70 [226385.605398] iwl_pcie_irq_rx_msix_handler+0xc2/0x120 [iwlwifi 1d7ba350faa5c4a5226540622d76fe15ddc58664] [226385.605425] irq_thread_fn+0x1e/0x60 [226385.605437] irq_thread+0xec/0x1a0 [226385.605446] ? wake_threads_waitq+0x30/0x30 [226385.605459] ? irq_thread_check_affinity+0xe0/0xe0 [226385.605468] kthread+0x154/0x180 [226385.605480] ? set_kthread_struct+0x50/0x50 [226385.605492] ret_from_fork+0x1f/0x30 [226385.605507] </TASK> [226385.605513] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast ccm rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT xt_tcpudp bridge stp llc cmac algif_hash algif_skcipher af_alg nf_nat_tftp nft_objref af_packet nf_conntrack_tftp 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 ebtable_nat ebtable_broute ip6table_nat ip6table_mangle mhi_net(N) ip6table_raw mhi_wwan_ctrl(N) ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle bnep iptable_raw iptable_security ip_set btusb nfnetlink btrtl btbcm btintel uvcvideo bluetooth videobuf2_vmalloc ebtable_filter videobuf2_memops videobuf2_v4l2 videobuf2_common ebtables videodev mc ecdh_generic crc16 ip6table_filter ip6_tables iptable_filter bpfilter dmi_sysfs snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_soc_dmic iTCO_wdt intel_pmc_bxt [226385.605600] nls_iso8859_1 iTCO_vendor_support mei_hdcp(N) mfd_core nls_cp437 intel_rapl_msr snd_hda_codec_hdmi vfat snd_hda_codec_realtek fat snd_hda_codec_generic intel_tcc_cooling(N) xfs snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp iwlmvm kvm_intel soundwire_bus snd_soc_core mac80211 kvm libarc4 snd_compress irqbypass snd_pcm_dmaengine joydev think_lmi(N) mhi_pci_generic(N) efi_pstore(N) pcspkr snd_hda_intel wmi_bmof firmware_attributes_class(N) ucsi_acpi mhi(N) typec_ucsi snd_intel_dspcfg typec snd_intel_sdw_acpi roles thermal iwlwifi snd_hda_codec thinkpad_acpi snd_hda_core ledtrig_audio cfg80211 snd_hwdep platform_profile ac int3403_thermal snd_pcm processor_thermal_device_pci_legacy(N) processor_thermal_device snd_timer i2c_i801 [226385.605696] processor_thermal_rfim processor_thermal_mbox processor_thermal_rapl mei_me e1000e intel_rapl_common snd intel_hid(N) int340x_thermal_zone sparse_keymap mei soundcore intel_pmc_core i2c_smbus rfkill acpi_tad(N) intel_soc_dts_iosf(N) int3400_thermal igen6_edac acpi_thermal_rel acpi_pad button fuse configfs ip_tables x_tables dm_crypt essiv authenc i915 crc32_pclmul i2c_algo_bit ttm ghash_clmulni_intel drm_kms_helper syscopyarea sysfillrect aesni_intel nvme xhci_pci xhci_pci_renesas xhci_hcd crypto_simd sysimgblt fb_sys_fops sdhci_pci cec rc_core cqhci cryptd sdhci drm mmc_core usbcore nvme_core serio_raw nvme_common t10_pi wmi battery video pinctrl_tigerlake btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq coretemp sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua scsi_mod msr efivarfs [226385.605820] Supported: No, Unsupported modules are loaded -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224799] New: missed libjack dependency of blender on Leap 15.6
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1224799 Bug ID: 1224799 Summary: missed libjack dependency of blender on Leap 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other 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: --- On Leap 15.6 lkocman@localhost:~/Documents/legobricks/geeko-brickz> sudo zypper in blender [sudo] password for root: Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... Resolving package dependencies... The following 50 NEW packages are going to be installed: audaspace audaspace-plugins blender blender-cycles-devel blender-lang libAlembic1_8 libaudaspace1_3 libaudaspace-c1_3 libaudaspace-py1_3 libavdevice58_13 libblosc1 libboost_atomic1_66_0 libboost_chrono1_66_0 libboost_date_time1_66_0 libboost_filesystem1_66_0 libboost_locale1_66_0 libboost_regex1_66_0 libboost_serialization1_66_0 libboost_wave1_66_0 libbuffer0_3 libclang-cpp15 libdcmtk18 libftoa0_3 libGeneratedSaxParser0_3 libGLEW2_2 libImath-2_2-23 libjemalloc2 libLLVM15 libMathMLSolver0_3 libOpenCOLLADABaseUtils0_3 libOpenCOLLADAFramework0_3 libOpenCOLLADASaxFrameworkLoader0_3 libOpenCOLLADAStreamWriter0_3 libOpenColorIO1 libopencv3_4 libOpenImageDenoise0 libOpenImageIO2_2 libopenvdb7_1 libosdCPU3_4_4 liboslcomp1_11 liboslexec1_11 liboslquery1_11 libpartio1 libpugixml1 libQt5OpenGL5 libspnav0 libtbb2 libtinyxml0 libUTF0_3 python3-numpy 50 new packages to install. Overall download size: 131.4 MiB. Already cached: 0 B. After the operation, additional 505.3 MiB will be used. Backend: classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): y Retrieving: blender-cycles-devel-2.82a-bp156.3.12.noarch (repo-oss (15.6)) (1/50), 509.3 KiB Retrieving: blender-cycles-devel-2.82a-bp156.3.12.noarch.rpm .................................................................................................................................[done (4.1 MiB/s)] Retrieving: libAlembic1_8-1.8.4-bp156.3.6.x86_64 (repo-oss (15.6)) (2/50), 474.6 KiB Retrieving: libAlembic1_8-1.8.4-bp156.3.6.x86_64.rpm .......................................................................................................................................[done (333.3 KiB/s)] Retrieving: libGLEW2_2-2.2.0-150400.1.8.x86_64 (repo-oss (15.6)) (3/50), 165.2 KiB Retrieving: libGLEW2_2-2.2.0-150400.1.8.x86_64.rpm .........................................................................................................................................[done (353.0 KiB/s)] Retrieving: libImath-2_2-23-2.2.1-150000.3.3.1.x86_64 (repo-oss (15.6)) (4/50), 30.9 KiB Retrieving: libImath-2_2-23-2.2.1-150000.3.3.1.x86_64.rpm ................................................................................................................................................[done] Retrieving: libLLVM15-15.0.7-150500.4.6.2.x86_64 (repo-oss (15.6)) (5/50), 21.9 MiB Retrieving: libLLVM15-15.0.7-150500.4.6.2.x86_64.rpm .........................................................................................................................................[done (9.8 MiB/s)] Retrieving: libMathMLSolver0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (6/50), 80.8 KiB Retrieving: libMathMLSolver0_3-1.6.68-bp156.3.8.x86_64.rpm ...............................................................................................................................................[done] Retrieving: libQt5OpenGL5-5.15.12+kde151-150600.1.5.x86_64 (repo-oss (15.6)) (7/50), 307.3 KiB Retrieving: libQt5OpenGL5-5.15.12+kde151-150600.1.5.x86_64.rpm .............................................................................................................................[done (286.1 KiB/s)] Retrieving: libUTF0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (8/50), 14.6 KiB Retrieving: libUTF0_3-1.6.68-bp156.3.8.x86_64.rpm ..........................................................................................................................................[done (139.0 KiB/s)] Retrieving: libaudaspace1_3-1.3.0-bp156.6.5.x86_64 (repo-oss (15.6)) (9/50), 959.5 KiB Retrieving: libaudaspace1_3-1.3.0-bp156.6.5.x86_64.rpm .......................................................................................................................................[done (5.9 MiB/s)] Retrieving: libblosc1-1.21.5-bp156.1.3.x86_64 (repo-oss (15.6)) (10/50), 70.7 KiB Retrieving: libblosc1-1.21.5-bp156.1.3.x86_64.rpm ........................................................................................................................................................[done] Retrieving: libboost_atomic1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (11/50), 21.7 KiB Retrieving: libboost_atomic1_66_0-1.66.0-12.3.1.x86_64.rpm ...............................................................................................................................................[done] Retrieving: libboost_chrono1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (12/50), 29.6 KiB Retrieving: libboost_chrono1_66_0-1.66.0-12.3.1.x86_64.rpm .................................................................................................................................[done (278.4 KiB/s)] Retrieving: libboost_date_time1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (13/50), 34.9 KiB Retrieving: libboost_date_time1_66_0-1.66.0-12.3.1.x86_64.rpm ...............................................................................................................................[done (90.6 KiB/s)] Retrieving: libboost_filesystem1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (14/50), 50.6 KiB Retrieving: libboost_filesystem1_66_0-1.66.0-12.3.1.x86_64.rpm .............................................................................................................................[done (358.2 KiB/s)] Retrieving: libboost_locale1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (15/50), 246.6 KiB Retrieving: libboost_locale1_66_0-1.66.0-12.3.1.x86_64.rpm .................................................................................................................................[done (436.9 KiB/s)] Retrieving: libboost_regex1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (16/50), 266.3 KiB Retrieving: libboost_regex1_66_0-1.66.0-12.3.1.x86_64.rpm ..................................................................................................................................[done (224.7 KiB/s)] Retrieving: libboost_serialization1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (17/50), 112.0 KiB Retrieving: libboost_serialization1_66_0-1.66.0-12.3.1.x86_64.rpm ........................................................................................................................................[done] Retrieving: libboost_wave1_66_0-1.66.0-12.3.1.x86_64 (repo-oss (15.6)) (18/50), 187.5 KiB Retrieving: libboost_wave1_66_0-1.66.0-12.3.1.x86_64.rpm ....................................................................................................................................[done (96.4 KiB/s)] Retrieving: libdcmtk18-3.6.8-bp156.3.2.x86_64 (repo-oss (15.6)) (19/50), 5.3 MiB Retrieving: libdcmtk18-3.6.8-bp156.3.2.x86_64.rpm ...........................................................................................................................................[done (10.9 MiB/s)] Retrieving: libftoa0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (20/50), 15.7 KiB Retrieving: libftoa0_3-1.6.68-bp156.3.8.x86_64.rpm .........................................................................................................................................[done (511.1 KiB/s)] Retrieving: libjemalloc2-5.0.1-1.25.x86_64 (repo-oss (15.6)) (21/50), 220.6 KiB Retrieving: libjemalloc2-5.0.1-1.25.x86_64.rpm ...............................................................................................................................................[done (3.8 MiB/s)] Retrieving: libpartio1-1.14.6-bp156.3.7.x86_64 (repo-oss (15.6)) (22/50), 120.4 KiB Retrieving: libpartio1-1.14.6-bp156.3.7.x86_64.rpm .........................................................................................................................................[done (336.0 KiB/s)] Retrieving: libpugixml1-1.13-bp156.2.4.x86_64 (repo-oss (15.6)) (23/50), 85.9 KiB Retrieving: libpugixml1-1.13-bp156.2.4.x86_64.rpm ........................................................................................................................................................[done] Retrieving: libspnav0-1.1-bp156.2.4.x86_64 (repo-oss (15.6)) (24/50), 30.5 KiB Retrieving: libspnav0-1.1-bp156.2.4.x86_64.rpm .............................................................................................................................................[done (336.9 KiB/s)] Retrieving: libtbb2-2019_20190605-150200.3.2.1.x86_64 (repo-oss (15.6)) (25/50), 93.9 KiB Retrieving: libtbb2-2019_20190605-150200.3.2.1.x86_64.rpm ................................................................................................................................................[done] Retrieving: libtinyxml0-2.6.2-150000.3.6.1.x86_64 (repo-oss (15.6)) (26/50), 49.2 KiB Retrieving: libtinyxml0-2.6.2-150000.3.6.1.x86_64.rpm ......................................................................................................................................[done (925.9 KiB/s)] Retrieving: python3-numpy-1.17.3-150400.28.37.x86_64 (repo-oss (15.6)) (27/50), 2.6 MiB Retrieving: python3-numpy-1.17.3-150400.28.37.x86_64.rpm ....................................................................................................................................[done (10.6 MiB/s)] Retrieving: libclang-cpp15-15.0.7-150500.4.6.2.x86_64 (repo-oss (15.6)) (28/50), 12.0 MiB Retrieving: libclang-cpp15-15.0.7-150500.4.6.2.x86_64.rpm ....................................................................................................................................[done (9.6 MiB/s)] Retrieving: libOpenCOLLADABaseUtils0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (29/50), 53.6 KiB Retrieving: libOpenCOLLADABaseUtils0_3-1.6.68-bp156.3.8.x86_64.rpm .........................................................................................................................[done (199.4 KiB/s)] Retrieving: libaudaspace-py1_3-1.3.0-bp156.6.5.x86_64 (repo-oss (15.6)) (30/50), 65.5 KiB Retrieving: libaudaspace-py1_3-1.3.0-bp156.6.5.x86_64.rpm ................................................................................................................................................[done] Retrieving: libaudaspace-c1_3-1.3.0-bp156.6.5.x86_64 (repo-oss (15.6)) (31/50), 58.8 KiB Retrieving: libaudaspace-c1_3-1.3.0-bp156.6.5.x86_64.rpm .................................................................................................................................................[done] Retrieving: audaspace-1.3.0-bp156.6.5.x86_64 (repo-oss (15.6)) (32/50), 56.7 KiB Retrieving: audaspace-1.3.0-bp156.6.5.x86_64.rpm ...........................................................................................................................................[done (527.1 KiB/s)] Retrieving: audaspace-plugins-1.3.0-bp156.6.5.x86_64 (repo-oss (15.6)) (33/50), 65.1 KiB Retrieving: audaspace-plugins-1.3.0-bp156.6.5.x86_64.rpm ...................................................................................................................................[done (860.9 KiB/s)] Retrieving: libbuffer0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (34/50), 19.9 KiB Retrieving: libbuffer0_3-1.6.68-bp156.3.8.x86_64.rpm .....................................................................................................................................................[done] Retrieving: libosdCPU3_4_4-3.4.4-bp156.3.4.x86_64 (repo-oss (15.6)) (35/50), 354.4 KiB Retrieving: libosdCPU3_4_4-3.4.4-bp156.3.4.x86_64.rpm ......................................................................................................................................[done (182.7 KiB/s)] Retrieving: libopenvdb7_1-7.1.0-bp156.3.4.x86_64 (repo-oss (15.6)) (36/50), 712.8 KiB Retrieving: libopenvdb7_1-7.1.0-bp156.3.4.x86_64.rpm .........................................................................................................................................[done (5.7 MiB/s)] Retrieving: libopencv3_4-3.4.16-150400.1.9.x86_64 (repo-oss (15.6)) (37/50), 6.5 MiB Retrieving: libopencv3_4-3.4.16-150400.1.9.x86_64.rpm ........................................................................................................................................[done (9.0 MiB/s)] Retrieving: libOpenImageDenoise0-1.1.0-bp156.3.6.x86_64 (repo-oss (15.6)) (38/50), 35.7 MiB Retrieving: libOpenImageDenoise0-1.1.0-bp156.3.6.x86_64.rpm ..................................................................................................................................[done (9.5 MiB/s)] Retrieving: libOpenColorIO1-1.1.1-bp156.3.7.x86_64 (repo-oss (15.6)) (39/50), 312.4 KiB Retrieving: libOpenColorIO1-1.1.1-bp156.3.7.x86_64.rpm .......................................................................................................................................[done (5.8 MiB/s)] Retrieving: libOpenCOLLADAFramework0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (40/50), 75.5 KiB Retrieving: libOpenCOLLADAFramework0_3-1.6.68-bp156.3.8.x86_64.rpm .......................................................................................................................................[done] Retrieving: libGeneratedSaxParser0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (41/50), 30.8 KiB Retrieving: libGeneratedSaxParser0_3-1.6.68-bp156.3.8.x86_64.rpm .........................................................................................................................................[done] Retrieving: libOpenCOLLADAStreamWriter0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (42/50), 127.4 KiB Retrieving: libOpenCOLLADAStreamWriter0_3-1.6.68-bp156.3.8.x86_64.rpm ........................................................................................................................[done (3.3 MiB/s)] Retrieving: libOpenImageIO2_2-2.2.17.0-bp156.5.3.x86_64 (repo-oss (15.6)) (43/50), 1.7 MiB Retrieving: libOpenImageIO2_2-2.2.17.0-bp156.5.3.x86_64.rpm ..................................................................................................................................[done (9.1 MiB/s)] Retrieving: libOpenCOLLADASaxFrameworkLoader0_3-1.6.68-bp156.3.8.x86_64 (repo-oss (15.6)) (44/50), 1.2 MiB Retrieving: libOpenCOLLADASaxFrameworkLoader0_3-1.6.68-bp156.3.8.x86_64.rpm ..................................................................................................................[done (9.2 MiB/s)] Retrieving: liboslquery1_11-1.11.17.0-bp156.3.2.x86_64 (repo-oss (15.6)) (45/50), 77.5 KiB Retrieving: liboslquery1_11-1.11.17.0-bp156.3.2.x86_64.rpm ...............................................................................................................................................[done] Retrieving: liboslexec1_11-1.11.17.0-bp156.3.2.x86_64 (repo-oss (15.6)) (46/50), 805.9 KiB Retrieving: liboslexec1_11-1.11.17.0-bp156.3.2.x86_64.rpm ....................................................................................................................................[done (1.6 MiB/s)] Retrieving: liboslcomp1_11-1.11.17.0-bp156.3.2.x86_64 (repo-oss (15.6)) (47/50), 198.2 KiB Retrieving: liboslcomp1_11-1.11.17.0-bp156.3.2.x86_64.rpm ................................................................................................................................................[done] Retrieving: libavdevice58_13-4.4.4-150600.18.pm.1.x86_64 (packman) (48/50), 122.9 KiB Retrieving: libavdevice58_13-4.4.4-150600.18.pm.1.x86_64.rpm .............................................................................................................................................[done] Retrieving: blender-2.82a-bp156.3.12.x86_64 (repo-oss (15.6)) (49/50), 33.2 MiB Retrieving: blender-2.82a-bp156.3.12.x86_64.rpm ..............................................................................................................................................[done (8.7 MiB/s)] Retrieving: blender-lang-2.82a-bp156.3.12.noarch (repo-oss (15.6)) (50/50), 4.3 MiB Retrieving: blender-lang-2.82a-bp156.3.12.noarch.rpm .........................................................................................................................................[done (8.5 MiB/s)] Checking for file conflicts: .............................................................................................................................................................................[done] ( 1/50) Installing: blender-cycles-devel-2.82a-bp156.3.12.noarch .........................................................................................................................................[done] ( 2/50) Installing: libAlembic1_8-1.8.4-bp156.3.6.x86_64 .................................................................................................................................................[done] ( 3/50) Installing: libGLEW2_2-2.2.0-150400.1.8.x86_64 ...................................................................................................................................................[done] ( 4/50) Installing: libImath-2_2-23-2.2.1-150000.3.3.1.x86_64 ............................................................................................................................................[done] ( 5/50) Installing: libLLVM15-15.0.7-150500.4.6.2.x86_64 .................................................................................................................................................[done] ( 6/50) Installing: libMathMLSolver0_3-1.6.68-bp156.3.8.x86_64 ...........................................................................................................................................[done] ( 7/50) Installing: libQt5OpenGL5-5.15.12+kde151-150600.1.5.x86_64 .......................................................................................................................................[done] ( 8/50) Installing: libUTF0_3-1.6.68-bp156.3.8.x86_64 ....................................................................................................................................................[done] ( 9/50) Installing: libaudaspace1_3-1.3.0-bp156.6.5.x86_64 ...............................................................................................................................................[done] (10/50) Installing: libblosc1-1.21.5-bp156.1.3.x86_64 ....................................................................................................................................................[done] (11/50) Installing: libboost_atomic1_66_0-1.66.0-12.3.1.x86_64 ...........................................................................................................................................[done] (12/50) Installing: libboost_chrono1_66_0-1.66.0-12.3.1.x86_64 ...........................................................................................................................................[done] (13/50) Installing: libboost_date_time1_66_0-1.66.0-12.3.1.x86_64 ........................................................................................................................................[done] (14/50) Installing: libboost_filesystem1_66_0-1.66.0-12.3.1.x86_64 .......................................................................................................................................[done] (15/50) Installing: libboost_locale1_66_0-1.66.0-12.3.1.x86_64 ...........................................................................................................................................[done] (16/50) Installing: libboost_regex1_66_0-1.66.0-12.3.1.x86_64 ............................................................................................................................................[done] (17/50) Installing: libboost_serialization1_66_0-1.66.0-12.3.1.x86_64 ....................................................................................................................................[done] (18/50) Installing: libboost_wave1_66_0-1.66.0-12.3.1.x86_64 .............................................................................................................................................[done] (19/50) Installing: libdcmtk18-3.6.8-bp156.3.2.x86_64 ....................................................................................................................................................[done] (20/50) Installing: libftoa0_3-1.6.68-bp156.3.8.x86_64 ...................................................................................................................................................[done] (21/50) Installing: libjemalloc2-5.0.1-1.25.x86_64 .......................................................................................................................................................[done] (22/50) Installing: libpartio1-1.14.6-bp156.3.7.x86_64 ...................................................................................................................................................[done] (23/50) Installing: libpugixml1-1.13-bp156.2.4.x86_64 ....................................................................................................................................................[done] (24/50) Installing: libspnav0-1.1-bp156.2.4.x86_64 .......................................................................................................................................................[done] (25/50) Installing: libtbb2-2019_20190605-150200.3.2.1.x86_64 ............................................................................................................................................[done] (26/50) Installing: libtinyxml0-2.6.2-150000.3.6.1.x86_64 ................................................................................................................................................[done] (27/50) Installing: python3-numpy-1.17.3-150400.28.37.x86_64 .............................................................................................................................................[done] (28/50) Installing: libclang-cpp15-15.0.7-150500.4.6.2.x86_64 ............................................................................................................................................[done] (29/50) Installing: libOpenCOLLADABaseUtils0_3-1.6.68-bp156.3.8.x86_64 ...................................................................................................................................[done] (30/50) Installing: libaudaspace-py1_3-1.3.0-bp156.6.5.x86_64 ............................................................................................................................................[done] (31/50) Installing: libaudaspace-c1_3-1.3.0-bp156.6.5.x86_64 .............................................................................................................................................[done] (32/50) Installing: audaspace-1.3.0-bp156.6.5.x86_64 .....................................................................................................................................................[done] (33/50) Installing: audaspace-plugins-1.3.0-bp156.6.5.x86_64 .............................................................................................................................................[done] (34/50) Installing: libbuffer0_3-1.6.68-bp156.3.8.x86_64 .................................................................................................................................................[done] (35/50) Installing: libosdCPU3_4_4-3.4.4-bp156.3.4.x86_64 ................................................................................................................................................[done] (36/50) Installing: libopenvdb7_1-7.1.0-bp156.3.4.x86_64 .................................................................................................................................................[done] (37/50) Installing: libopencv3_4-3.4.16-150400.1.9.x86_64 ................................................................................................................................................[done] (38/50) Installing: libOpenImageDenoise0-1.1.0-bp156.3.6.x86_64 ..........................................................................................................................................[done] (39/50) Installing: libOpenColorIO1-1.1.1-bp156.3.7.x86_64 ...............................................................................................................................................[done] (40/50) Installing: libOpenCOLLADAFramework0_3-1.6.68-bp156.3.8.x86_64 ...................................................................................................................................[done] (41/50) Installing: libGeneratedSaxParser0_3-1.6.68-bp156.3.8.x86_64 .....................................................................................................................................[done] (42/50) Installing: libOpenCOLLADAStreamWriter0_3-1.6.68-bp156.3.8.x86_64 ................................................................................................................................[done] (43/50) Installing: libOpenImageIO2_2-2.2.17.0-bp156.5.3.x86_64 ..........................................................................................................................................[done] (44/50) Installing: libOpenCOLLADASaxFrameworkLoader0_3-1.6.68-bp156.3.8.x86_64 ..........................................................................................................................[done] (45/50) Installing: liboslquery1_11-1.11.17.0-bp156.3.2.x86_64 ...........................................................................................................................................[done] (46/50) Installing: liboslexec1_11-1.11.17.0-bp156.3.2.x86_64 ............................................................................................................................................[done] (47/50) Installing: liboslcomp1_11-1.11.17.0-bp156.3.2.x86_64 ............................................................................................................................................[done] (48/50) Installing: libavdevice58_13-4.4.4-150600.18.pm.1.x86_64 .........................................................................................................................................[done] (49/50) Installing: blender-2.82a-bp156.3.12.x86_64 ......................................................................................................................................................[done] (50/50) Installing: blender-lang-2.82a-bp156.3.12.noarch .................................................................................................................................................[done] lkocman@localhost:~/Documents/legobricks/geeko-brickz> lkocman@localhost:~/Documents/legobricks/geeko-brickz> blender blender: error while loading shared libraries: libjack.so.0: cannot open shared object file: No such file or directory lkocman@localhost:~/Documents/legobricks/geeko-brickz> sudo zypper in libjack [sudo] password for root: Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... 'libjack' not found in package names. Trying capabilities. Resolving package dependencies... The following NEW package is going to be installed: libjack0 1 new package to install. Overall download size: 94.7 KiB. Already cached: 0 B. After the operation, additional 287.7 KiB will be used. Backend: classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): y Retrieving: libjack0-1.9.12-150000.3.3.1.x86_64 (repo-oss (15.6)) (1/1), 94.7 KiB Retrieving: libjack0-1.9.12-150000.3.3.1.x86_64.rpm ......................................................................................................................................................[done] Checking for file conflicts: .............................................................................................................................................................................[done] (1/1) Installing: libjack0-1.9.12-150000.3.3.1.x86_64 ....................................................................................................................................................[done] lkocman@localhost:~/Documents/legobricks/geeko-brickz> -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225159] New: OpenSUSE installation support for RZ/G3S and RZ/V2H
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225159 Bug ID: 1225159 Summary: OpenSUSE installation support for RZ/G3S and RZ/V2H 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: john.vincent.xa(a)bp.renesas.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, Please enable Renesas RZ/V2H & RZ/G3S SOM device support in openSUSE by updating the following configurations in "config/arm64/default" file CONFIG_ARCH_R9A09G057=y #RZ/V2H CONFIG_ARCH_R9A08G045=y #RZ/G3S Best Regards John -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223613] New: irqbalance: Cannot change IRQ 180 affinity: Read-only file system
by bugzilla_noreply＠suse.com 30 Sep '24

30 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1223613 Bug ID: 1223613 Summary: irqbalance: Cannot change IRQ 180 affinity: Read-only file system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: munix9(a)googlemail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Get this with version 1.9.4.0.git+f8b8cdd-1.1 $ systemctl status irqbalance ● irqbalance.service - irqbalance daemon Loaded: loaded (/usr/lib/systemd/system/irqbalance.service; enabled; preset: enabled) Active: active (running) since Wed 2024-05-01 09:32:25 CEST; 8h ago Docs: man:irqbalance(1) https://github.com/Irqbalance/irqbalance Main PID: 1324 (irqbalance) Tasks: 2 (limit: 4915) CPU: 4.343s CGroup: /system.slice/irqbalance.service └─1324 /usr/sbin/irqbalance ‐‐journal May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 180 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 180 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 181 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 181 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 120 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 120 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 121 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 121 affinity is now unmanaged May 01 09:32:36 bowman irqbalance[1324]: Cannot change IRQ 213 affinity: Read-only file system May 01 09:32:36 bowman irqbalance[1324]: IRQ 213 affinity is now unmanaged Solved this with a patch from fedora: https://src.fedoraproject.org/rpms/irqbalance/blob/main/f/0001-Drop-Protect… See also https://build.opensuse.org/package/show/home:munix9:test/irqbalance https://bugzilla.redhat.com/show_bug.cgi?id=2276314 https://src.fedoraproject.org/rpms/irqbalance/tree/main Maybe the patch https://src.fedoraproject.org/rpms/irqbalance/blob/main/f/0001-irqbalance-u… is also interesting. If desired, I can create a SR. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222914] New: Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop
by bugzilla_noreply＠suse.com 28 Sep '24

28 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222914 Bug ID: 1222914 Summary: Upgrade from kernel 5.14.21-150500.55.39-default to kernel 5.14.21-150500.55.44-default broke on my laptop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: marc(a)marcchamberlin.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When I tried to install the upgrade mentioned in the summary it breaks and hangs during the bootup process for the new system and badly hangs requiring me to power cycle my laptop. I have frozen and locked my laptop at vmlinuz-5.14.21-150500.55.39-default for now, but that means I can no longer install any kernel patches or upgrades. I am not sure of the cause of the hang up but have narrowed it down to probably ??? either an inability to properly query my network interfaces (it sometimes stalls out when trying to get an IP address from my DHCP server) for their identity and capabilities) or perhaps something is wrong with the nVidia drivers. I have a relatively new Dell laptop as described here - # inxi -CGMSnaz System: Kernel: 5.14.21-150500.55.39-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.39-default root=UUID=ce027c75-c647-4b4b-8c6a-e5fb48f41513 splash=silent preempt=full mitigations=auto quiet security=apparmor Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM Distro: openSUSE Leap 15.5 Machine: Type: Laptop System: Dell product: XPS 15 9530 v: N/A serial: <filter> Chassis: type: 10 serial: <filter> Mobo: Dell model: 0GY0F9 v: A00 serial: <filter> UEFI: Dell v: 1.7.0 date: 08/14/2023 CPU: Info: model: 13th Gen Intel Core i9-13900H socket: U3E1 bits: 64 type: MST AMCP arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+ process: Intel 7 (10nm) family: 6 model-id: 0xBA (186) stepping: 2 microcode: 0x411C Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB Speed (MHz): avg: 540 high: 682 min/max: 400/5200:5400:4100 base/boost: 4851/5400 scaling: driver: intel_pstate governor: powersave volts: 1.3 V ext-clock: 100 MHz cores: 1: 440 2: 473 3: 404 4: 587 5: 544 6: 680 7: 468 8: 682 9: 564 10: 662 11: 443 12: 583 13: 624 14: 459 15: 532 16: 489 17: 488 18: 553 19: 580 20: 546 bogomips: 119807 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: Not affected Type: l1tf status: Not affected Type: mds status: Not affected Type: meltdown status: Not affected Type: mmio_stale_data status: Not affected Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: i915 v: kernel ports: active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 0000:00:02.0 chip-ID: 8086:a7a0 class-ID: 0300 Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] vendor: Dell driver: N/A alternate: nouveau, nvidia_drm, nvidia non-free: N/A status: unknown device ID bus-ID: 0000:01:00.0 chip-ID: 10de:28a0 class-ID: 0302 Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 3-6:3 chip-ID: 0c45:6a22 class-ID: fe01 serial: <filter> Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.5 compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22") s-diag: 582mm (22.9") Monitor-1: eDP-1 model: Samsung 0x414d built: 2020 res: 1920x1080 hz: 60 dpi: 145 gamma: 1.2 size: 336x210mm (13.23x8.27") diag: 396mm (15.6") ratio: 16:10 modes: 3456x2160 API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Graphics (RPL-P) direct render: Yes Network: Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 0000:00:14.3 chip-ID: 8086:51f1 class-ID: 0280 IF: wlan0 state: up mac: <filter> Device-2: ASIX AX88179 Gigabit Ethernet type: USB driver: ax88179_178a bus-ID: 2-1.3.2:4 chip-ID: 0b95:1790 class-ID: ff00 serial: <filter> IF: eth0 state: down mac: <filter> Please refer to the thread on users(a)lists.opensuse.org titled "Yikes! Looks like an update has screwed up my laptop" to see a discussion I had with the user community about this issue, for some additional information. They advised me to submit this bug report. I will be happy to provide any additional information requested, and I will see if I can capture a boot log file and add it in a followup comment. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1221715] New: GCC 14: liblogging package fails
by bugzilla_noreply＠suse.com 27 Sep '24

27 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221715 Bug ID: 1221715 Summary: GCC 14: liblogging package fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: thomas.blume(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building liblogging with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: beepframe.c:170:1: error: return type defaults to ‘int’ [-Wimplicit-int] 170 | sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ beeplisten.c: In function ‘sbLstnInit’: beeplisten.c:1055:28: error: implicit declaration of function ‘sbSock_InitUXDOMSOCK’ [-Wimplicit-function-declaration] 1055 | if((iRet = sbSock_InitUXDOMSOCK(&(pThis->pSockUXDOMSOCKListening), pActualSockName, /*SOCK_DGRAM*/ SOCK_STREAM)) != SR_RET_OK) | ^~~~~~~~~~~~~~~~~~~~ Builds with: Index: liblogging-1.0.6/rfc3195/src/beepframe.c =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/beepframe.c +++ liblogging-1.0.6/rfc3195/src/beepframe.c @@ -167,6 +167,7 @@ srRetVal sbFramActualRecvFramCommonHdr(s * The channel object is updated, e.g. with a * new seqno. */ +int sbFramActualRecvFramCommonBody(sbFramObj* pThis,sbChanObj *pChan) { unsigned iToRcv; Index: liblogging-1.0.6/rfc3195/src/sockets.h =================================================================== --- liblogging-1.0.6.orig/rfc3195/src/sockets.h +++ liblogging-1.0.6/rfc3195/src/sockets.h @@ -340,4 +340,8 @@ srRetVal sbSockRecvFrom(sbSockObj *pThis # define SOCKET_ERROR -1 #endif +#if FEATURE_UNIX_DOMAIN_SOCKETS == 1 +srRetVal sbSock_InitUXDOMSOCK(sbSockObj **ppThis, char *pszSockName, int iSockType); +#endif + #endif See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225147] New: Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 26 Sep '24

26 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 Bug ID: 1225147 Summary: Kernel hard lockup under mild GPU load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: llyyr.public(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0 Build Identifier: Randomly get hard lockups with no errors or dmesg logs, can't ssh into the system either. Reproducible: Always Steps to Reproduce: 1. Record the screen with vaapi encoding on amdgpu Actual Results: Kernel hard lockup some time after 5-30 minutes Expected Results: System should be stable With i5-13600k and RX 6600 XT. I'm running sway and the screen recording tool doesn't matter as long as it's using vaapi encoding. The Mesa version also doesn't matter. This happens on Kernel versions 6.7 or newer, I just tried 6.9.1 and can reproduce it there as well. It does not happen on 6.6.x. I'm currently running 6.6.31-lts. I'd go ahead and bisect the kernel but I'm not sure how to build and install the kernel in a way that it appears in the grub menu. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218694] New: [k8s,kube-flannel] YAML File to set up Flannel Network Add-On is outdated
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1218694 Bug ID: 1218694 Summary: [k8s,kube-flannel] YAML File to set up Flannel Network Add-On is outdated Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- After successfully setting up k8s (using `kubeadm init`), the coredns pod remains in a 'Pending' state: NAMESPACE NAME READY STATUS RESTARTS AG kube-system coredns-86ccd44ff8-24h9w 0/1 Pending 0 12 kube-system coredns-86ccd44ff8-rz5vq 0/1 Pending 0 12 kube-system etcd-k8s-head 1/1 Running 1 12 kube-system kube-apiserver-k8s-head 1/1 Running 1 12 kube-system kube-controller-manager-k8s-head 1/1 Running 1 12 kube-system kube-proxy-qprnj 1/1 Running 0 12 kube-system kube-scheduler-k8s-head 1/1 Running 1 13 This is due to a not yet installed network plugin. When installing `kubeadm` thru 'patterns-kubernetes-kubeadm', the package 'flannel-k8s-yaml' is installed alongside which contains a yaml file to set up Flannel as network plugin. Running `kubectl apply -f /usr/share/k8s-yaml/flannel/kube-flannel.yaml` using the supplied file fails, however after: | clusterrole.rbac.authorization.k8s.io/flannel created | clusterrolebinding.rbac.authorization.k8s.io/flannel created | serviceaccount/flannel created | configmap/kube-flannel-cfg created | daemonset.apps/kube-flannel-ds created with the error: | error: resource mapping not found for name: "psp.flannel.unprivileged" namespace: "" from "/usr/share/k8s-yaml/flannel/kube-flannel.yaml": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1" ensure CRDs are installed first When using the yaml file from https://github.com/flannel-io/flannel/blob/master/Documentation/kube-flanne… (wget https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/k…) it works, however, the flannel pod is still cycling thru a CrashLoopBackOff - it fails with (from log): | E0110 11:46:48.988799 1 main.go:332] Error registering network: failed to acquire lease: node "k8s-head" pod cidr not assigned -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1220731] New: Wayland KDE error messages about pipewire when hover about taskbar
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220731 Bug ID: 1220731 Summary: Wayland KDE error messages about pipewire when hover about taskbar Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a server with a Nvidia quadro K4200 GPU with two monitors connected on port DVI and DP-1 of the GPU. When I hover on the taskbar with the mouse pointer I see tha tI have error message in journalctl Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:51 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb9320 fd:53 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:51 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:56 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325fb8330: unknown peer 0x560325fba2e0 fd:64 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:56 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:26 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:27 hpprol2 pipewire[5524]: mod.client-node: 0x560326073d20: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:27 hpprol2 pipewire[5524]: mod.client-node: 0x56032614fb30: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:28 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:28 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:28 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:29 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:29 hpprol2 pipewire[5524]: mod.client-node: 0x5603260ea5e0: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:29 hpprol2 pipewire[5524]: mod.client-node: 0x560325f7ee60: unknown peer 0x560325fb7250 fd:53 Mar 01 09:21:30 hpprol2 pipewire[5524]: mod.client-node: 0x5603260ea5e0: unknown peer 0x560325fb9320 fd:56 Mar 01 09:21:32 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325fb7250 fd:51 Mar 01 09:21:32 hpprol2 pipewire[5524]: mod.client-node: 0x560325e284a0: unknown peer 0x560325f6c7b0 fd:56 Mar 01 09:21:36 hpprol2 pipewire[5524]: mod.client-node: 0x560325e2e150: unknown peer 0x560325f6c7b0 fd:57 Mar 01 09:21:41 hpprol2 pipewire[5524]: mod.client-node: 0x560325f92610: unknown peer 0x560325f6c8a0 fd:56 Mar 01 09:21:42 hpprol2 pipewire[5524]: mod.client-node: 0x560325e1d000: unknown peer 0x560325fb7250 fd:57 Mar 01 09:21:43 hpprol2 pipewire[5524]: mod.client-node: 0x560325f5a340: unknown peer 0x560325fb7250 fd:57 Also from time to time the monitor on the DP-1 flash: the background is shortly displayed. This also occurs only during the hower on the taskbar. Regards Philippe -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217853] New: kscreenlocker is broken on wayland with nvidia drivers
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217853 Bug ID: 1217853 Summary: kscreenlocker is broken on wayland with nvidia drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: yacha(a)orangefox.tech QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I use openSUSE Tumbleweed, the problem I'm having is that every time my PC wakes up from sleep or hibernation it shows me a broken screen locked. "The screen locker is broken and unlocking is not possible anymore..." If I press Super + L being in the KDE wayland session, it does show me kscreenlock without breaking. Only occurs after waking up. I use proprietary nvidia drivers and wayland. Reproducible: Always Steps to Reproduce: 1. Launch a wayland session 2. Go into suspend state 3. Wake it up. Here's the journalctl output of the kscreenlocker: Dec 04 20:01:29 localhost.localdomain kscreenlocker_greet[7134]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: kf.kirigami: Failed to find a Kirigami platform plugin Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:auth): pam_kwallet5: pam_sm_authenticate Dec 04 20:01:30 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:auth): pam_kwallet5: we were already executed Dec 04 20:01:33 localhost.localdomain kscreenlocker_greet[7134]: pam_kwallet5(kde:setcred): pam_kwallet5: pam_sm_setcred Is there anything I can do to fix or debug it? Thanks before. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225213] New: no sound on speakers, headphones work
by bugzilla_noreply＠suse.com 25 Sep '24

25 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225213 Bug ID: 1225213 Summary: no sound on speakers, headphones work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- after yesterdays upgrade sound does not play on speakers, but works on headphones. tried to change volum on all devices but no luck. Plasma indicator shows sound playing but nothing is hearable. polrus  ~  inxi -A Audio: Device-1: Intel Comet Lake PCH cAVS driver: sof-audio-pci-intel-cnl API: ALSA v: k6.9.1-1-default status: kernel-api Server-1: PipeWire v: 1.0.6 status: active polrus  ~  dmesg |grep snd_hda [ 6.260721] [ T773] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 6.579988] [ T1408] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat snd_soc_rt715 snd_soc_rt1308_sdw snd_soc_rt711 snd_hda_codec_hdmi regmap_sdw snd_soc_dmic snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof iwlmvm(+) snd_sof_utils soundwire_generic_allocation soundwire_bus snd_soc_avs snd_soc_hda_codec mac80211 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi libarc4 snd_soc_core snd_compress snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec snd_hda_core intel_uncore_frequency spi_nor intel_uncore_frequency_common snd_hwdep hid_sensor_als iTCO_wdt iwlwifi intel_tcc_cooling mtd intel_pmc_bxt hid_sensor_trigger snd_pcm processor_thermal_device_pci_legacy iTCO_vendor_support dell_laptop hid_sensor_iio_common x86_pkg_temp_thermal ee1004 processor_thermal_device industrialio_triggered_buffer intel_powerclamp -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1221501] New: Missing posttls-finger in postfix though changes mention it
by bugzilla_noreply＠suse.com 24 Sep '24

24 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221501 Bug ID: 1221501 Summary: Missing posttls-finger in postfix though changes mention it 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: toganm(a)dinamizm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The change file of postfix 3.8.6 dated Mar 5 16:46:16 UTC 2024 has the following change. Cleanup: this fixes posttls-finger certificate match expectations for all TLS security levels, including warnings for levels that don't implement certificate matching. By Viktor Dukhovni. However posttls-finger is not available in the postfix package. Two questions arise 1. Why is posttls-finger not included? 2. If it is not included why bother to put the above entry to the changelog. Cut copy paste is meaningful only if what is pasted reflects the reality. I would rather see that posttls-finger is included in the package. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217257] New: qt6-webengine error: 'using StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set'
by bugzilla_noreply＠suse.com 24 Sep '24

24 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217257 Bug ID: 1217257 Summary: qt6-webengine error: 'using StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello qt6-webengine does not build on Leap 15.6. This should be fixed before Beta (Feb 2023). https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set' [ 7245s] 429 | source_.set(source.data(), source.size()); [ 7245s] | ^~~ [ 7245s] ./../../../../../src/3rdparty/chromium/extensions/browser/api/web_request/form_data_parser.cc: In member function 'virtual bool extensions::FormDataParserMultipart::SetSource(base::StringPiece)': [ 7245s] ./../../../../../src/3rdparty/chromium/extensions/browser/api/web_request/form_data_parser.cc:573:11: error: 'using StringPiece = class absl::string_view' {aka 'class absl::string_view'} has no member named 'set' [ 7245s] 573 | source_.set(source.data(), source.size()); [ 7245s] | ^~~ [ 7245s] At global scope: [ 7245s] cc1plus: note: unrecognized command-line option '-Wno-stringop-overread' may have been intended to silence earlier diagnostics [ 7248s] [24766/27742] CXX obj/extensions/browser/browser_sources/browser_sources_jumbo_10.o [ 7250s] [24767/27742] CXX obj/extensions/browser/browser_sources/browser_sources_jumbo_18.o [ 7254s] [24768/27742] CXX obj/extensions/browser/browser_sources/browser_sources_jumbo_9.o [ 7254s] ninja: build stopped: subcommand failed. [ 7254s] FAILED: src/core/RelWithDebInfo/x86_64/QtWebEngineCore.stamp src/core/RelWithDebInfo/x86_64/QtWebEngineCore [ 7254s] cd /home/abuild/rpmbuild/BUILD/qtwebengine-everywhere-src-6.4.2/build/src/core && /usr/bin/ninja -j4 -C /home/abuild/rpmbuild/BUILD/qtwebengine-everywhere-src-6.4.2/build/src/core/RelWithDebInfo/x86_64 QtWebEngineCore [ 7254s] ninja: build stopped: subcommand failed. [ 7254s] error: Bad exit status from /var/tmp/rpm-tmp.KR5dFa (%build) [ 7254s] -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1223533] New: cockpit: /nonexistent/libexec/cockpit-askpass
by bugzilla_noreply＠suse.com 24 Sep '24

24 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1223533 Bug ID: 1223533 Summary: cockpit: /nonexistent/libexec/cockpit-askpass Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other 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: --- Created attachment 874558 --> https://bugzilla.suse.com/attachment.cgi?id=874558&action=edit nonexistent/libexec/cockpit-askpass On freshly installed Leap 15.6 + cockpit If you login to localhost:9090 as a standard user and you try to enable the admin view by clicking on the cockpit homescreen button, then cockpit will raise following error Problem becoming administrator Sudo: unable to run /nonexistent/libexec/cockpit-askpass: No such file or directory sudo: no password was provided sudo: a password is required lkocman@localhost:~/Workspace/obs> sudo zypper in cockpit [sudo] password for root: Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Retrieving repository 'packman' metadata .....................................................................................................................................................[done] Building repository 'packman' cache ..........................................................................................................................................................[done] Loading repository data... Warning: Repository 'update-non-oss (15.6)' metadata expired since 2023-09-21 14:47:58 CEST. Warning: Repository metadata expired: Check if 'autorefresh' is turned on (zypper lr), otherwise manually refresh the repository (zypper ref). If this does not solve the issue, it could be that you are using a broken mirror or the server has actually discontinued to support the repository. Reading installed packages... Resolving package dependencies... The following 2 recommended packages were automatically selected: cockpit-networkmanager cockpit-storaged The following package is recommended, but will not be installed due to conflicts or dependency issues: cockpit-packagekit The following 2 packages are suggested, but will not be installed: cockpit-pcp cockpit-selinux The following 8 NEW packages are going to be installed: cockpit cockpit-bridge cockpit-networkmanager cockpit-storaged cockpit-system cockpit-ws libpwquality-tools libudisks2-0_lvm2 8 new packages to install. Overall download size: 7.1 MiB. Already cached: 0 B. After the operation, additional 8.3 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: cockpit-bridge-309-bp156.1.2.x86_64 (repo-oss (15.6)) (1/8), 471.8 KiB Retrieving: cockpit-bridge-309-bp156.1.2.x86_64.rpm .............................................................................................................................[done (10.9 KiB/s)] Retrieving: cockpit-ws-309-bp156.1.2.x86_64 (repo-oss (15.6)) (2/8), 1.7 MiB Retrieving: cockpit-ws-309-bp156.1.2.x86_64.rpm ..................................................................................................................................[done (8.4 MiB/s)] Retrieving: libpwquality-tools-1.4.5-150600.2.2.x86_64 (repo-oss (15.6)) (3/8), 19.4 KiB Retrieving: libpwquality-tools-1.4.5-150600.2.2.x86_64.rpm ...................................................................................................................................[done] Retrieving: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64 (repo-oss (15.6)) (4/8), 57.0 KiB Retrieving: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64.rpm .....................................................................................................................[done (93.5 KiB/s)] Retrieving: cockpit-system-309-bp156.1.2.noarch (repo-oss (15.6)) (5/8), 3.2 MiB Retrieving: cockpit-system-309-bp156.1.2.noarch.rpm ..............................................................................................................................[done (6.7 MiB/s)] Retrieving: cockpit-storaged-309-bp156.1.2.noarch (repo-oss (15.6)) (6/8), 850.0 KiB Retrieving: cockpit-storaged-309-bp156.1.2.noarch.rpm ............................................................................................................................[done (4.2 MiB/s)] Retrieving: cockpit-networkmanager-309-bp156.1.2.noarch (repo-oss (15.6)) (7/8), 827.8 KiB Retrieving: cockpit-networkmanager-309-bp156.1.2.noarch.rpm ......................................................................................................................[done (3.8 MiB/s)] Retrieving: cockpit-309-bp156.1.2.x86_64 (repo-oss (15.6)) (8/8), 45.5 KiB Retrieving: cockpit-309-bp156.1.2.x86_64.rpm .................................................................................................................................................[done] Checking for file conflicts: .................................................................................................................................................................[done] (1/8) Installing: cockpit-bridge-309-bp156.1.2.x86_64 ........................................................................................................................................[done] (2/8) Installing: cockpit-ws-309-bp156.1.2.x86_64 ............................................................................................................................................[done] (3/8) Installing: libpwquality-tools-1.4.5-150600.2.2.x86_64 .................................................................................................................................[done] (4/8) Installing: libudisks2-0_lvm2-2.9.2-150400.3.3.1.x86_64 ................................................................................................................................[done] (5/8) Installing: cockpit-system-309-bp156.1.2.noarch ........................................................................................................................................[done] (6/8) Installing: cockpit-storaged-309-bp156.1.2.noarch ......................................................................................................................................[done] (7/8) Installing: cockpit-networkmanager-309-bp156.1.2.noarch ................................................................................................................................[done] (8/8) Installing: cockpit-309-bp156.1.2.x86_64 ...............................................................................................................................................[done] lkocman@localhost:~/Workspace/obs> sudo systemctl enable --now cockpit.socket Created symlink /etc/systemd/system/sockets.target.wants/cockpit.socket → /usr/lib/systemd/system/cockpit.socket. lkocman@localhost:~/Workspace/obs> -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1225432] New: [Agama][Milestone8+] iSCSI Discovery Passwords are logged into y2log in plain text
by bugzilla_noreply＠suse.com 23 Sep '24

23 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225432 Bug ID: 1225432 Summary: [Agama][Milestone8+] iSCSI Discovery Passwords are logged into y2log in plain text 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: locilka(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875149 --> https://bugzilla.suse.com/attachment.cgi?id=875149&action=edit Snippet of the log When iSCSI Targets are being discovered in Agama, the iSCSI library logs all the details. Sadly, also including passwords. How to reproduce? Easily -> Start Agama Installer -> Go to Storage details -> Click Prepare devices by configuring advanced storage technologies -> Choose iSCSI -> Click Discover iSCSI targets -> Fill-up some users/passwords -> Click Confirm This will be most probably the same in YaST as well because it uses the same library. BTW, there are two entries for user/password, but you can see only the first one in the log. That's most probably because the second one would be used later, if the first one succeeds (not my case). Additionally, even the save_y2logs script does not remove the passwords. maybe because the string in the log this: {"name"=>"discovery.sendtargets.auth.password", "value"=>"and their password", "kind"=>"value", "type"=>1, "comment"=>""} -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1222338] New: curl 8.7.1 and libzypp cause curl error 92 on fetching updates
by bugzilla_noreply＠suse.com 23 Sep '24

23 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222338 Bug ID: 1222338 Summary: curl 8.7.1 and libzypp cause curl error 92 on fetching updates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I can no longer refresh some 3rd party repositories after the curl 8.7.1 upgrade in tumbleweed. curl 8.6.0 works fine. the errors point out a http/2 protocol error. here's the snippet from the log: 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Found bundle for host: 0x564be94f55c0 [can multiplex] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Re-using existing connection with host dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] OPENED stream for https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:method: GET] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:scheme: https] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:authority: dl.google.com] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [:path: /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [user-agent: ZYpp 17.31.15 (curl 8.7.1)] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [17] [accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > GET /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml HTTP/2 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Host: dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > User-Agent: ZYpp 17.31.15 (curl 8.7.1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Request completely sent off 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < HTTP/2 200 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-length: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL++] request.cc(headerfunction):653 0x564be956d140 Got Content-Length Header: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-security-policy: default-src 'none' 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < server: downloads 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-content-type-options: nosniff 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-frame-options: SAMEORIGIN 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-xss-protection: 0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < cache-control: public,max-age=0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < last-modified: Wed, 03 Apr 2024 16:46:55 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < date: Thu, 04 Apr 2024 17:44:16 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < etag: "26973aa" 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Invalid HTTP header field was received: frame type: 1, stream: 17, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * HTTP/2 stream 17 was not closed cleanly: PROTOCOL_ERROR (err 1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Connection #0 to host dl.google.com left intact 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] basicdownloader_p.cc(onRequestFinished):201 0x564be956d140 Downloading on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml failed with error Server returned a HTTP/2 strea m error. Curl error (92) Invalid HTTP header field was received: frame type: 1, stream: 17, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-core] PathInfo.cc(unlink):705 unlink /var/tmp/AP_0xzr4SK4/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] metalinkinfo_p.cc(transitionToFinished):36 Downloading on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml transition to final state. 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] final_p.cc(FinishedState):20 About to enter FinishedState for url https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] initial_p.cc(enter):20 Entering initial state 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] initial_p.cc(initiate):44 No zchunk data available but metalink requested, going to download metalink directly. 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] metalinkinfo_p.cc(DlMetaLinkInfoState):25 Downloading metalink/zsync on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] initial_p.cc(exit):22 Leaving initial state 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] metalinkinfo_p.cc(initializeRequest):51 Requesting Metadata info from server! 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-core] PathInfo.cc(chmod):1099 assert_file_mode 00600 /var/lib/YaST2/cookieschmod /var/lib/YaST2/cookies 00600 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL++] request.cc(aboutToStart):469 0x564be956d140 Setting activity timeout to: 180 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Found bundle for host: 0x564be94f55c0 [can multiplex] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Re-using existing connection with host dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] OPENED stream for https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:method: GET] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:scheme: https] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:authority: dl.google.com] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [:path: /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [user-agent: ZYpp 17.31.15 (curl 8.7.1)] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * [HTTP/2] [19] [accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > GET /linux/chrome/rpm/stable/x86_64/repodata/repomd.xml HTTP/2 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Host: dl.google.com 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > User-Agent: ZYpp 17.31.15 (curl 8.7.1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > Accept: */*, application/x-zsync, application/metalink+xml, application/metalink4+xml 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 > 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Request completely sent off 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < HTTP/2 200 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-length: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL++] request.cc(headerfunction):653 0x564be956d140 Got Content-Length Header: 1356 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < content-security-policy: default-src 'none' 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < server: downloads 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-content-type-options: nosniff 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-frame-options: SAMEORIGIN 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < x-xss-protection: 0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < cache-control: public,max-age=0 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < last-modified: Wed, 03 Apr 2024 16:46:55 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < date: Thu, 04 Apr 2024 17:44:16 GMT 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 < etag: "26973aa" 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Invalid HTTP header field was received: frame type: 1, stream: 19, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * HTTP/2 stream 19 was not closed cleanly: PROTOCOL_ERROR (err 1) 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-curl++] curlhelper.cc(log_curl):119 0x564be956d140 * Connection #0 to host dl.google.com left intact 2024-04-04 19:43:42 <1> magnolia(30993) [ZYPP_MEDIA_CURL] basicdownloader_p.cc(onRequestFinished):201 0x564be956d140 Downloading on https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml failed with error Server returned a HTTP/2 stream error. Curl error (92) Invalid HTTP header field was received: frame type: 1, stream: 19, name: [content-length], value: [1449] 2024-04-04 19:43:42 <1> magnolia(30993) [zypp-core] PathInfo.cc(unlink):705 unlink /var/tmp/AP_0xzr4SK4/repodata/repomd.xml -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1217690] New: libcamera: reproducible builds vs signatures
by bugzilla_noreply＠suse.com 21 Sep '24

21 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217690 Bug ID: 1217690 Summary: libcamera: reproducible builds vs signatures Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: rfrohl(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jengelh(a)inai.de Blocks: 1062303 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE+ALP, I found that our libcamera package varies in every build because during build it creates a random keypair, embeds the pubkey adds .so.sign files When I asked upstream about it long ago, it was said to prevent smuggling in of 3rd party modules that shall not receive the same level of permissions as modules that are shipped as part of the main codebase. Can we patch src/libcamera/ipa_module.cpp to not use .sign files or is there another way to get reproducible build results for libcamera? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222461] New: VUL-0: CVE-2024-22189: TRACKERBUG: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 20 Sep '24

20 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222461 Bug ID: 1222461 Summary: VUL-0: CVE-2024-22189: TRACKERBUG: quic-go: memory exhaustion attack against QUIC's connection ID mechanism Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/400376/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: camila.matos(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- 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 20

[Bug 1222470] New: VUL-0: CVE-2024-22189: coredns: quic-go: memory exhaustion attack against QUIC's connection ID mechanism
by bugzilla_noreply＠suse.com 20 Sep '24

20 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222470 Bug ID: 1222470 Summary: VUL-0: CVE-2024-22189: coredns: 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: andrea.manzini(a)suse.com Reporter: camila.matos(a)suse.com QA Contact: qa-bugs(a)suse.de CC: camila.matos(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 6

[Bug 1223176] New: VUL-0: CVE-2024-32475: envoy: abnormal termination when using auto_sni with authority header longer than 255 characters
by bugzilla_noreply＠suse.com 20 Sep '24

20 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1223176 Bug ID: 1223176 Summary: VUL-0: CVE-2024-32475: envoy: abnormal termination when using auto_sni with authority header longer than 255 characters Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/402625/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: wolfgang.engel(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: --- Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-32475 https://www.cve.org/CVERecord?id=CVE-2024-32475 https://github.com/envoyproxy/envoy/commit/b47fc6648d7c2dfe0093a601d44cb704… https://github.com/envoyproxy/envoy/security/advisories/GHSA-3mh5-6q8v-25wj https://bugzilla.redhat.com/show_bug.cgi?id=2276149 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1220501] New: Kernel panics on EEVDF
by bugzilla_noreply＠suse.com 20 Sep '24

20 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220501 Bug ID: 1220501 Summary: Kernel panics on EEVDF Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: l4rryc0n5014(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873070 --> https://bugzilla.suse.com/attachment.cgi?id=873070&action=edit Compressed copy of /var/log/journal, accessed from Windows with WinBTRFS My laptop has been kernel panicking quite frequently as of late. At first I thought it was because of the boot option `pcie_aspm=force acpi_backlight=native` but it wasn't. I dropped into recovery mode to check `journalctl` and I found the recent panics were due to: EEVDF scheduling fail, picking leftmost BUG: kernel NULL pointer dereference, address: 00000000000000a0 I saw a lot of `EEVDF scheduling fail` before the entries cuts off for the next boot session which was me ACPI shutting down the laptop each time it grinds to a halt. Sometimes, I saw two additional entries in the journal: #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page A quick search on the first two entries yielded <https://lkml.org/lkml/2024/2/19/678>. Not sure how to read the thing considering it's Linux kernel stuffs. I also thought it was due to data corruption or something on the `/` and `/home` but `btrfs check --force --check-data-csum` said both were healthy, and I reinstalled openSUSE back Feb 19 after zeroing the two partitions for good measure (due to mishaps that compromised data integrity). The only things that has anything to do with the kernel I installed were VBox, Docker, KVM and QEMU, and the NVIDIA driver with blacklisting `nouveau` using https://en.opensuse.org/SDB:NVIDIA_the_hard_way, the rest was from https://en.opensuse.org/SDB:NVIDIA_drivers for G06 with a bunch more G06 stuff installed. Included is a compressed file or /var/log/journal which should include my laptop model; but for safety measure, I am using an Acer Nitro 5 (AN515-46-R6QR) running AMD Ryzen 7 6800H with an NVIDIA 3060 Mobile, upgraded to 32GB of RAM from stock configuration of 16GB with an additional 2TB drive added to the spare M.2 slot. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1214406] New: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully
by bugzilla_noreply＠suse.com 19 Sep '24

19 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1214406 Bug ID: 1214406 Summary: [kubeadm1.27] Multiple Issues before `kubeadm init` runs successfully Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: priyanka.saggu(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- 1. The Kubernetes package on TW seems to require cri-o as runtime dependency, however, it requires containerd. Thus, - cri-o should not be installed as a dependency - containerd had to be installed enabled and started (containerd doesn't have an rccontainerd link) 2. kubelet.service does not start: It complains about the option `--container-runtime` not being known. This option is pulled in from /etc/sysconfig/kubelet. It needs to be deleted from this file. It is not clear who has created this file and which package owns it. The rpm database does not know it. Since it is pulled in by ..../systemd/system/kubelet.service.d/10-kubeadm.conf I suspect it comes from kubernetes1.27-kubeadem but it's hard to tell where it is created - at least not in a post-install script. It would be good if the file was '%ghost' in the %files section of the package it originates from. The same is true for the environment file /var/lib/kubelet/kubeadm-flags.env which is written by `kubeadm init`. 3. 'kubeadm init' checks if the kubelet service is enabled. 4. Moreover, it requires a reboot to start all dependent services and load all required kernel modules: - br_netfilter needs to be loaded - containerd needs to be started This was fine for kubic these packages were originally meant for as this had transactional updates and required a reboot. On a 'regular' system where this is not the case, these modules should probably be loaded and services be started from a 'postinstall' script. -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1225697] New: Problem video driver i915
by bugzilla_noreply＠suse.com 16 Sep '24

16 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225697 Bug ID: 1225697 Summary: Problem video driver i915 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: sidewinderx(a)libero.it QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: I have a problem that is not clear to me I guess with the Intel G33 i915 video drivers. Upgrading from 15.4 to 15.5 opensuse leap I have freezes while navigating through the system menus and mainly I can’t launch graphics programs for pcb creation which didn’t happen in previous versions. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1219528] New: go 1.22rc2 breaks mockery
by bugzilla_noreply＠suse.com 16 Sep '24

16 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1219528 Bug ID: 1219528 Summary: go 1.22rc2 breaks mockery Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- package: https://build.opensuse.org/package/show/home:darix:restic/mockery upstream issue: https://github.com/vektra/mockery/issues/752 stack trace in upstream issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221701] New: GCC 14: libquicktime package fails
by bugzilla_noreply＠suse.com 15 Sep '24

15 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221701 Bug ID: 1221701 Summary: GCC 14: libquicktime package fails 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: michal.jires(a)suse.com QA Contact: qa-bugs(a)suse.de CC: danilo.spinella(a)suse.com Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Building libquicktime with GCC 14 fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Due to: error: File not found: /home/abuild/rpmbuild/BUILDROOT/libquicktime-1.2.4+git20180804.fff99cd-5.5.x86_64/usr/lib64/libquicktime/lqt_lame.so ./libquicktime-1.2.4+git20180804.fff99cd/config.log: conftest.c:59:5: error: return type defaults to 'int' [-Wimplicit-int] ./libquicktime-1.2.4+git20180804.fff99cd/config.log: 59 | main() ./libquicktime-1.2.4+git20180804.fff99cd/config.log: | ^~~~ Builds with automatically generated: Index: libquicktime-1.2.4+git20180804.fff99cd/configure.ac =================================================================== --- libquicktime-1.2.4+git20180804.fff99cd.orig/configure.ac +++ libquicktime-1.2.4+git20180804.fff99cd/configure.ac @@ -282,6 +282,7 @@ have_lame="false" AC_TRY_RUN([ #include <lame/lame.h> #include <stdio.h> +int main() { int version_major; See the meta bug#1220571 for more info. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220524] New: Files in virtualbox shared folder (on the guest) show wrong timestamp
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220524 Bug ID: 1220524 Summary: Files in virtualbox shared folder (on the guest) show wrong timestamp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: suse.junky(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my openSUSE Tumbleweed system (bare metal) Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: X11 I use virtualbox # zypper se -si virtual* Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------------------+--------+------------------ i | virtualbox | package | 7.0.14-3.1 | x86_64 | (System Packages) i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (System Packages) i+ | virtualbox-qt | package | 7.0.14-3.1 | x86_64 | (System Packages) # One guest is an openSUSE Tumbleweed 20240225 system with # zypper se -si virtualbox* Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+---------------------+--------+------------------ i+ | virtualbox-guest-tools | package | 7.0.14-3.1 | x86_64 | (System Packages) i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (System Packages) # The host shares a directory (/mnt/Lokal/VM_share) with the guest. On the host system I have (in my home directory) a file > ls -la *.jpg -rw-r--r-- 1 A users 40749 Mar 3 2023 Opensuse_beer_label.jpg when I copy this file to the shared directory > cp -a Opensuse_beer_label.jpg /mnt/Lokal/VM_share/ everything looks fine (on the host) > ls -la /mnt/Lokal/VM_share/ total 64 drwxr-xr-x 3 A users 4096 Feb 27 09:51 . drwxr-xr-x 7 root root 4096 Jan 3 2022 .. -rw-r--r-- 1 A users 40749 Mar 3 2023 Opensuse_beer_label.jpg > but on the guest system I see in the shared folder > ls -la total 64 drwxrwx--- 1 root vboxsf 4096 Jan 1 1970 . dr-xr-xr-x 5 root root 4096 Feb 27 09:40 .. -rwxrwx--- 1 root vboxsf 40749 Feb 27 09:44 Opensuse_beer_label.jpg > The timestamps in the share of the VM don’t make sense to me. This happens to all files copied to the share. Even when I copy files in the guest to the share their timestamps are changed (in the share) to the current date . However when I look at those files on the host they do have the correct date; i.e. the date of the original file in the guest. On MS Windows 11 (bare metal) with virtualbox 7.0.14 and openSUSE Tumbleweed 20240225 as guest I see the same behaviour. Kubuntu (as guest) does not show this behaviour although it uses VBoxGuestAdditions_7.0.14 as well. I discussed this already here: https://forums.opensuse.org/t/files-in-the-virtualbox-share-show-wrong-time… and a third user could very this behaviour in its setup as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1217824] New: longterm kernel: figure out how to build KMPs
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1217824 Bug ID: 1217824 Summary: longterm kernel: figure out how to build KMPs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: rfrohl(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Target Milestone: --- Found By: --- Blocker: --- One of the major open questions, before introducing the longterm kernel to Factory, is how KPMs can be build. This issue is supposed to server as a reminder, that this likely blocks the addition to Factory until it is resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215463] New: VirtualBox shared folders no longer working in Tumbleweed 20230915
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215463 Bug ID: 1215463 Summary: VirtualBox shared folders no longer working in Tumbleweed 20230915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: nixuser(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent updates in the last two week or so have broken shared folders in VirtualBox. You can mount the shares, and "ls" the files, but any attempt to access a file results in "killed" as a response. If I launch Thunar in Xfce it locks up and must be killed. Video scaling is working, and copy/paste between the host and guest are also working. Issue exists for Tumbleweed guests with a Fedora or Win10 host. Other hosts not tested. Tumbleweed guest fully up to date 20230915. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1225142] New: Kernel oops in nfs
by bugzilla_noreply＠suse.com 13 Sep '24

13 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225142 Bug ID: 1225142 Summary: Kernel oops in nfs Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: msvec(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875055 --> https://bugzilla.suse.com/attachment.cgi?id=875055&action=edit Kernel oops log As I already mentioned in bug 1223640 I'm getting oops in NFS (see the attached log) It happens in both kernel-default-5.14.21-150500.55.59.1.x86_64 kernel-default-5.14.21-150500.55.62.2.x86_64 Until and including the previous one it's been fine: kernel-default-5.14.21-150500.55.52.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215976] New: Hawk fails to build in Factory
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1215976 Bug ID: 1215976 Summary: Hawk fails to build in Factory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After the update in the Factory, there has disappeared the useradd and groupadd commands. Adding the shadow package in the BuildRequires has fixed it. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220891] New: HAWK: Update sanity check for passwd existance
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220891 Bug ID: 1220891 Summary: HAWK: Update sanity check for passwd existance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The /etc/pam.d/passwd is optional in fact, for example there is none in the tumbleeweed. So let's relax the condition: if there is no /etc/pam.d/passwd, check if there is a passwd binary in /usr/bin of /usr/sbin. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1220890] New: Update validation for the newer versions of rails
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220890 Bug ID: 1220890 Summary: Update validation for the newer versions of rails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: aburlakov(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with Rails6.1 there has changed the validation. Namely, the ActiveModel::Errors has changed it's structure. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223862] New: Packages with explicit x86_v3 target fail to build
by bugzilla_noreply＠suse.com 12 Sep '24

12 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1223862 Bug ID: 1223862 Summary: Packages with explicit x86_v3 target fail to build Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs(a)suse.de Reporter: cgoll(a)suse.com QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Packages with optimized code for AVX2 (x86_v3) or AVX (x86_v4) need this code streams explicitly enabled during the build process (faiss or gpt4all) so its not possible to use the %{?suse_build_hwcaps_libs} macro. When doing this, the packages are built, but some final scripts fail cleaning up the build root fail with the error: ``` [ 51s] find: cannot delete '//.build.packages/RPMS/x86_64_v3': Directory not empty [ 51s] ``` A failed example can found under: https://build.opensuse.org/package/show/home:mslacken:ml/faiss_bug where the two codestream build for AVX2 and AVX512 fail to build. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213181] New: ddclient dose not work for cloudflare
by bugzilla_noreply＠suse.com 11 Sep '24

11 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1213181 Bug ID: 1213181 Summary: ddclient dose not work for cloudflare Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- openSUSE-HW:/home/hillwood # ddclient FATAL: Error loading the Perl module JSON::Any needed for cloudflare update. It's my config: # /etc/ddclient.conf daemon=300 # check every 300 seconds syslog=yes # log update msgs to syslog #mail=root # mail all msgs to root mail-failure=root # mail failed update msgs to root pid=/run/ddclient/ddclient.pid # record PID in file. ssl=yes protocol=cloudflare ttl=1 # use=web # web=checkip.dyndns.org usev6=if, if=br0 login=email password=API Key zone=hillwoodhome.net cloud.home.hillwoodhome.net ddclient 3.10.0 works fine with this config. We should provide an update for Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225660] New: python311-pip package installs in /usr/lib by default
by bugzilla_noreply＠suse.com 11 Sep '24

11 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225660 Bug ID: 1225660 Summary: python311-pip package installs in /usr/lib by default 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: daniel.garcia(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In tumbleweed installing a package with pip3 as root installs in the system path /usr/lib. It should install in /usr/local/lib instead. Possibly related to this patch: https://build.opensuse.org/projects/devel:languages:python:Factory/packages… -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1222499] New: runc v1.2.0~rc1 breaks distrobox (and maybe more)
by bugzilla_noreply＠suse.com 11 Sep '24

11 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1222499 Bug ID: 1222499 Summary: runc v1.2.0~rc1 breaks distrobox (and maybe more) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since runc was updated to v1.2.0~rc1 last week in TW, distrobox (and therefore podman), when forcing runc engine, is no longer able to start container rootless. Error is : Error: unable to start container "988cc7b326ef04596a3d14ccc41bbdb43c74a6420b5e476b5da00b4e381f0d6f": runc: runc create failed: unable to start container process: error during container init: error mounting "/" to rootfs at "/run/host": mount dst=/run/host, dstFd=/proc/thread-self/fd/8, flags=0x5020: operation not permitted: OCI permission denied" ~/.config/containers/containers.conf [containers] [engine] runtime="runc" -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1221644] New: pipewire-pulse stops working when monitor powers off/on again
by bugzilla_noreply＠suse.com 10 Sep '24

10 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1221644 Bug ID: 1221644 Summary: pipewire-pulse stops working when monitor powers off/on again Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: hendersj(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I've observed this for some time. I have a triple monitor setup, and two of the three monitors have multiple devices plugged into them. When I lock my screen, one of the monitors switches to the Chromecast input automatically once DPMS kicks off the monitor, and when I switch it back on, pipewire-pulse refuses to play sound until I kill it *and* restart the application that was trying to play sound. This affects both sound input and output - I had a situation earlier today where the monitor was tuned back on (to keep the Chromecast from keeping the screen on all night, I turn it off using ddcutil to turn it off), and after killing pipewire-pulse, I was able to hear a web-based video call, but I could not be heard until I restarted Chrome (ie, my voice input - I tried both a bluetooth headset and a USB headset - would let me hear the other person on the meeting but they could not hear me and I could not control my microphone at all). It seems that a change in audio device availability - even a device that's not in use at he time (I rarely use the speaker on the monitor in question) causes pipewire-pulse to freak out and stop working properly until it is killed and restarts. Not sure what information would be useful from logs - let me know, and I'll see what I can grab. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225267] New: openSUSE-release and sles-release can be removed and updated even with zypper lock applied
by bugzilla_noreply＠suse.com 09 Sep '24

09 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1225267 Bug ID: 1225267 Summary: openSUSE-release and sles-release can be removed and updated even with zypper lock applied 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: vanda.barata(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This issue is happening on both SLES 15 SP4 and openSUSE Leap 15.4, as well as Tumbleweed. Zypper is able to lock, and resolve the locks, for the `sles-release` package and the `openSUSE-release` package (on their OS respectively), but the packages can still be upgraded and removed. `zypper ll --solvables` shows the lock ------------------------------------------------------------------------- 7 | openSUSE-release | 3 | package | (any) | Keep installed : openSUSE-release-15.4-lp154.166.1.x86_64 (@System) Do not install : [2] openSUSE-release-15.4-lp154.166.1.x86_64 (repo-update) openSUSE-release-15.4-lp154.153.1.x86_64 (repo-oss) ------------------------------------------------------------------------- but when saving the testcase, it doesn't containt said lock, and it's possible to remove the package. If the product itself is locked (shipped by the release package), it can't be removed, as expected: ------------------------------------------------------------------------- hobbes:~ (0)# zypper al product:Leap Specified lock has been successfully added. hobbes:~ (0)# zypper in -- -openSUSE-release Problem: 1: conflicting requests Solution 1: Following actions will be done: remove lock to allow removal of product:Leap-15.4-1.x86_64 remove lock to allow removal of product:Leap-15.4-1.x86_64 Solution 2: do not ask to delete all solvables providing openSUSE-release.x86_64 = 15.4-lp154.166.1 ------------------------------------------------------------------------- It seems the product lock is applied to the -release package but not the other way around. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1220589] New: lto1 does not finish
by bugzilla_noreply＠suse.com 09 Sep '24

09 Sep '24

https://bugzilla.suse.com/show_bug.cgi?id=1220589 Bug ID: 1220589 Summary: lto1 does not finish Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In OBS it crashes, probably because of OOM: https://build.opensuse.org/package/live_build_log/home:michals/ladybird/ope… locally it links forever: 17574 399 20 0 26.796g 0.026t 2156 R 100.0 42.43 40:18.79 lto1-wpa -- You are receiving this mail because: You are on the CC list for the bug.

1 7