October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221849] New: grub2 bash-completion failed with '_split_longopt: command not found'
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221849 Bug ID: 1221849 Summary: grub2 bash-completion failed with '_split_longopt: command not found' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading bash-completion to 2.12, grub2 bash-completion scripts stopped to work and showed the error: _split_longopt: command not found. It's because bash-completion 2.12 renamed '_split_longopt' as '_comp__split_longopt', and bash-completion upstream(*) stated that '_split_longopt' is a private API so it should not be used directly. Instead, the script should use '_init_completion -s' or the newer '_comp_initialize -s' to initialize 'cur', 'prev', and 'split'. (*) https://github.com/scop/bash-completion/issues/1135 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231789] New: Docker image opensuse/leap:15.6 for linux/arm is actually Leap 15.5
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231789 Bug ID: 1231789 Summary: Docker image opensuse/leap:15.6 for linux/arm is actually Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: armv7 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: opensuse(a)karuhtz.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The official Docker image `opensuse/leap:15.6` for `linux/arm` architecture (https://hub.docker.com/layers/opensuse/leap/15.6/images/sha256-1f4a999dce16…) seems to actually be a Leap 15.5 image: * /etc/os-release says VERSION="15.5" * `zypper lr -u` lists repos with 15.5 URIs Reproduce with: > docker run --rm --platform=linux/arm opensuse/leap:15.6 cat /etc/os-release NAME="openSUSE Leap" VERSION="15.5" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.5" PRETTY_NAME="openSUSE Leap 15.5" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.5" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" Expected: I would expect an image tagged with `15.6` to actually contain a 15.6 release. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232454] New: VUL-0: CVE-2024-50624: kmail-account-wizard: plaintext HTTP used for URLs when retrieving configuration files
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232454 Bug ID: 1232454 Summary: VUL-0: CVE-2024-50624: kmail-account-wizard: plaintext HTTP used for URLs when retrieving configuration files Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/425830/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: christophe(a)krop.fr 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: --- ispdbservice.cpp in KDE Kmail before 6.2.0 allows man-in-the-middle attackers to trigger use of an attacker-controlled mail server because cleartext HTTP is used for a URL such as http://autoconfig.example.com or http://example.com/.well-known/autoconfig for retrieving the configuration. This is related to kmail-account-wizard. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-50624 https://www.cve.org/CVERecord?id=CVE-2024-50624 https://bugs.kde.org/show_bug.cgi?id=487882 https://invent.kde.org/pim/kmail-account-wizard/-/commit/9784f5ab41c3aff435… https://invent.kde.org/pim/kmail/-/tags https://kde.org/announcements/megarelease/6/ -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1232046] New: PC Freezes When Coming Out of Sleep
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232046 Bug ID: 1232046 Summary: PC Freezes When Coming Out of Sleep Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: adamska156(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: openSUSE Tumbleweed 20241018 KDE Plasma Version: 6.2.1 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor Memory: 31.0 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7D78 System Version: 1.0 When PC comes out of sleep, as soon as the kscreenlocker pops up the entire system freezes and becomes unresponsive. I'm unsure how to trace this issue. I've looked through logs and don't see anything but I don't know what to look for. This issue has been occuring for 2 or 3 weeks. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1232648] New: [tw][selinux][wireguard] serial-getty@hvc0.service: Deactivated after wireguard tests and caused openQA test fail
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232648 Bug ID: 1232648 Summary: [tw][selinux][wireguard] serial-getty(a)hvc0.service: Deactivated after wireguard tests and caused openQA test fail Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: x86-64 URL: https://openqa.opensuse.org/tests/4606619/modules/wire guard/steps/133 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Description The issue is a bit strange, it can only be seen with tw with selinux enabled by default. the serial terminal login session gets dis-connect after wireguard tests. but I can't find a manual reproducing step so far. I can see below messages even from test code, no logout operation is there: > Oct 30 22:48:27 client login[958]: pam_systemd(login:session): New sd-bus connection (system-bus-pam-systemd-958) opened. > Oct 30 22:48:27 client login[958]: pam_unix(login:session): session closed for user root > Oct 30 22:48:27 client systemd-logind[817]: Session 1 logged out. Waiting for processes to exit. > Oct 30 22:48:27 client systemd[1]: serial-getty(a)hvc0.service: Deactivated successfully. > Oct 30 22:48:27 client systemd[1]: run-credentials-serial\x2dgetty\x40hvc0.service.mount: Deactivated successfully. And I can see the serial terminal is logged out: > Welcome to openSUSE Tumbleweed 20241027 - Kernel 6.11.5-1-default (hvc0). > > ens4: 10.0.2.102 fe80::5054:ff:fe12:40f > wg1: 192.168.2.2 > > > client login: [openQA jobs are failed here since the expected return codes are missing] The issue is not seen with apparmor enabled by default. https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor… Workaround: switch to root-console after the tests to complete the job My questions: 1. Does selinux force reset the hvc0? 2. Why the issues are seen after some network changes to system? Please see attached logs for more detail information aslo https://progress.opensuse.org/issues/168589 records ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-wireguard@64bit fails in [wireguard](https://openqa.opensuse.org/tests/4606619/modules/wireguard/step… ## Test suite description Multimachine Wireguard client test. Maintainers: pdostal(a)suse.cz, pvorel(a)suse.cz ## Reproducible Fails since (at least) Build [rfan1028](https://openqa.opensuse.org/tests/4600433) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1231756] New: xe driver unexpectedly does not support Arc A750 (56a1)
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231756 Bug ID: 1231756 Summary: xe driver unexpectedly does not support Arc A750 (56a1) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jcheung(a)suse.com, marc.ruehrschneck(a)suse.com, mbrugger(a)suse.com, patrik.jakobsson(a)suse.com Target Milestone: --- Found By: --- Blocker: --- According to Intel's https://dgpu-docs.intel.com/devices/hardware-table.html the 8086:56A1 Arc A750 dGPU should be enabled since 6.2 and not need force_probe. However, in Tumbleweed aarch64 with 6.11.3 kernel I got: [ 12.232648] [ T661] xe 000d:03:00.0: Your graphics device 56a1 is not officially supported by xe driver in this kernel version. To force Xe probe, use xe.force_probe='56a1' and i915.force_probe='!56a1' module parameters or CONFIG_DRM_XE_FORCE_PROBE='56a1' and CONFIG_DRM_I915_FORCE_PROBE='!56a1' configuration options. and when following those instructions, [ 11.765712][ T577] Setting dangerous option force_probe - tainting kernel [ 11.772912][ T577] xe 000d:03:00.0: Adding to iommu group 18 ... [ 11.968981][ T660] xe 000d:03:00.0: enabling device (0000 -> 0002) ... [ 11.990262][ T660] xe 000d:03:00.0: [drm] Found DG2/G10 (device ID 56a1) display version 13.00 ... [ 12.062198][ T660] xe 000d:03:00.0: [drm] Using GuC firmware from i915/dg2_guc_70.bin version 70.29.2 ... [ 12.100456][ T660] xe 000d:03:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none ... [ 12.100456][ T660] xe 000d:03:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none [ 12.102321][ T705] BTRFS info (device nvme0n1p2): using free-space-tree [ 12.111966][ T660] Unable to handle kernel paging request at virtual address ffffffffc08003cc [ 12.127252][ T660] Mem abort info: [ 12.130732][ T660] ESR = 0x0000000096000006 [ 12.135168][ T660] EC = 0x25: DABT (current EL), IL = 32 bits [ 12.141167][ T660] SET = 0, FnV = 0 [ 12.144909][ T660] EA = 0, S1PTW = 0 [ 12.148739][ T660] FSC = 0x06: level 2 translation fault [ 12.154304][ T660] Data abort info: [ 12.157872][ T660] ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000 [ 12.164045][ T660] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 12.169783][ T660] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 12.175782][ T660] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000080d66e08000 [ 12.183173][ T660] [ffffffffc08003cc] pgd=0000080d67c78003, p4d=0000080d67c78003, pud=0000080d67c79003, pmd=0000000000000000 [ 12.194477][ T660] Internal error: Oops: 0000000096000006 [#1] SMP [ 12.200733][ T660] Modules linked in: xe(+) drm_ttm_helper ttm i2c_algo_bit aes_ce_blk gpu_sched aes_ce_cipher drm_buddy crct10dif_ce polyval_ce video polyval_generic drm_suballoc_helper xhci_pci drm_gpuvm ghash_ce xhci_pci_renesas drm_exec xhci_hcd gf128mul sm4 drm_display_helper nvme sha2_ce sha256_arm64 usbcore nvme_core cec sha1_ce sbsa_gwdt rc_core nvme_auth usb_common xgene_hwmon gpio_dwapb btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq ip6_tables x_tables br_netfilter bridge stp llc efivarfs [ 12.245579][ T660] CPU: 0 UID: 0 PID: 660 Comm: kworker/0:2 Tainted: G U 6.11.3-1-default #1 openSUSE Tumbleweed 1400000003000000474e5500fd56bd985baac2f4 [ 12.260779][ T660] Tainted: [U]=USER [ 12.264429][ T660] Hardware name: ADLINK Ampere Altra Developer Platform/Ampere Altra Developer Platform, BIOS TianoCore 2.04.100.11 (SYS: 2.06.20220308) 10/05/2 [ 12.278930][ T660] Workqueue: events work_for_cpu_fn [ 12.283975][ T660] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 12.291620][ T660] pc : logic_inb+0xc0/0x108 [ 12.295968][ T660] lr : intel_vga_reset_io_mem+0x38/0x68 [xe] [ 12.302000][ T660] sp : ffff800083c7ba90 [ 12.305997][ T660] x29: ffff800083c7ba90 x28: ffffc97776d89408 x27: 0000000000000001 [ 12.313817][ T660] x26: ffff07ff955c4000 x25: ffff07ff8322f0c8 x24: ffffc97776dc0d70 [ 12.321636][ T660] x23: ffff07ff955c5760 x22: 0000000000045404 x21: 0000000000000000 [ 12.329455][ T660] x20: 00000000000003cc x19: ffff07ff8322f000 x18: ffffffffffffffff [ 12.337274][ T660] x17: 2c6d656d2b6f693d x16: ffffc977a1414a68 x15: 6c6f203a6465676e [ 12.345092][ T660] x14: 616863207365646f x13: 205d303636542020 x12: 5b5d363534303031 [ 12.352911][ T660] x11: 65646f6365642c6d x10: 656d2b6f693d7365 x9 : ffffc977a0d26250 [ 12.360730][ T660] x8 : 3a62726161677620 x7 : 205b5d3635343030 x6 : 00000000000000ff [ 12.368549][ T660] x5 : 0000000000000000 x4 : 000000000000000a x3 : 0000000000000000 [ 12.376368][ T660] x2 : 0000000000000000 x1 : 0000000000ffbffe x0 : ffffffffc08003cc [ 12.384187][ T660] Call trace: [ 12.387316][ T660] logic_inb+0xc0/0x108 [ 12.391315][ T660] intel_vga_reset_io_mem+0x38/0x68 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.400545][ T660] hsw_power_well_enable+0x150/0x1d0 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.409854][ T660] intel_power_well_enable+0x74/0xa0 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.419156][ T660] intel_power_well_get+0x2c/0x40 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.428193][ T660] __intel_display_power_get_domain.part.0+0x78/0xc8 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.438876][ T660] intel_power_domains_init_hw+0x8c/0x300 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.448602][ T660] intel_display_driver_probe_noirq+0xa0/0x1f8 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.458761][ T660] xe_display_init_noirq+0x68/0xc8 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.467876][ T660] xe_device_probe+0x2c0/0x590 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.476647][ T660] xe_pci_probe+0x634/0x9b0 [xe 1400000003000000474e5500a641a49136d814c9] [ 12.485151][ T660] local_pci_probe+0x48/0xc0 [ 12.489587][ T660] work_for_cpu_fn+0x24/0x40 [ 12.494019][ T660] process_one_work+0x174/0x418 [ 12.498713][ T660] worker_thread+0x2d4/0x3f8 [ 12.503146][ T660] kthread+0x118/0x130 [ 12.507058][ T660] ret_from_fork+0x10/0x20 [ 12.511318][ T660] Code: d65f03c0 929fffe0 f2b81000 8b000280 (39400000) [ 12.518094][ T660] ---[ end trace 0000000000000000 ]--- Note: the i915 driver does not appear to be available on aarch64, only xe. Is the Intel documentation wrong? Anything to check other than waiting for 6.12 packages to re-test? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1230637] New: Wrong colors with Mesa 24.2.2
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230637 Bug ID: 1230637 Summary: Wrong colors with Mesa 24.2.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: sndirsch(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After fixing broken rendering with Mesa 24.1.4 (boo#1228164) an update to Mesa 24.2.2 (where the fix was dropped again since it no longer applied) broke colors: Examples in openQA during installation with YaST https://openqa.opensuse.org/tests/4484038#step/welcome/7 https://openqa.opensuse.org/tests/4485651#step/partitioning_finish/2 -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1221865] New: Allow Pipewire to operate under the superuser account.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1221865 Bug ID: 1221865 Summary: Allow Pipewire to operate under the superuser account. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All URL: https://gitlab.freedesktop.org/pipewire/pipewire/-/iss ues/2244#note_2336608 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Community User Blocker: No Provide a SystemD override file, as https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2244#note_2336608 explains, to allow the superuser account to use Pipewire when authenticated. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215639] New: Provide the user with a choice of where they want their SWAP partition to be.
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215639 Bug ID: 1215639 Summary: Provide the user with a choice of where they want their SWAP partition to be. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- When installing OpenSUSE with multiple internal drives, per https://forums.opensuse.org/t/how-to-transfer-swap-partition-to-os-drive-fr…, the OSTW installer places the SWAP partition on a (seemingly random) secondary internal drive. I don't want this - if I don't select the other drives when asked, it shouldn't touch them (I realize the quoted post states I did, but it refers to a previous installation; I've tested both). Consequently, either don't put the SWAP partiton on another drive unless multiple have been selected (this is the reason for this issue's designation as a bug rather than an enhancement) or allow the user to choose separately where the SWAP partition should be without needing to use the expert partitioner. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1213784] New: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com
by bugzilla_noreply＠suse.com 06 Nov '24

06 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213784 Bug ID: 1213784 Summary: bugzilla.opensuse.org e-mails direct to bugzilla.suse,com Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Target Milestone: --- Found By: --- Blocker: --- When I file a report at opensuse.bugzilla.org and receive a message via e-mail about it, all links in the post direct me to bguzilla.suse.com instead. This is quite the hassle when dealing with frequent notifications on multiple tickets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3