May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220190] New: AUDIT: drkonqi6
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1220190 Bug ID: 1220190 Summary: AUDIT: drkonqi6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- drkonqi is the crash handler for KDE applications. drkonqi6 will coexist in openSUSE for a while and needs to be reviewed: [ 93s] drkonqi6.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system.d/org.kde.drkonqi.conf (sha256 file digest default filter:233b3b98de2fc6b780c1eb9c3ab9b9f99b1949dfab951cababd7c5a717b8ee16 shell filter:233b3b98de2fc6b780c1eb9c3ab9b9f99b1949dfab951cababd7c5a717b8ee16 xml filter:3326c5271c6321c5b3a703d187443eef260d54aa7347bc8f05d9090a153a04bd) [ 93s] drkonqi6.x86_64: E: dbus-file-unauthorized (Badness: 10000) /usr/share/dbus-1/system-services/org.kde.drkonqi.service (sha256 file digest default filter:b99a6dc5943df0e641616dc4be3122fdd1d1b1c418df298c56008b50c5fb2b08 shell filter:b6f2a505903e2d8874d7da96a197944ab4a11f351f3db80ffeeec86d9eefd79a xml filter:<failed-to-calculate>) Package sources: https://build.opensuse.org/package/show/KDE:Frameworks/drkonqi6 -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1224285] New: 6.9 broke pidfd
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224285 Bug ID: 1224285 Summary: 6.9 broke pidfd 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… commit cb12fd8e0dabb9a1c8aef55a6a41e2c255fcdf4b Author: Christian Brauner <brauner(a)kernel.org> Date: Mon Feb 12 16:32:38 2024 +0100 pidfd: add pidfs Without the commit, lsof shows: systemd ... 59 [pidfd:899] With the commit: systemd ... 1187 pidfd For util-linux, its test fail with: > [ 125s] --- tests/expected/lsfd/column-name-pidfd 2024-05-06 07:20:54.655845940 +0000 > [ 125s] +++ tests/output/lsfd/column-name-pidfd 2024-05-15 01:04:15.406666666 +0000 > [ 125s] @@ -1,2 +1,2 @@ > [ 125s] -3 anon_inode:[pidfd] pid=1 comm= nspid=1 > [ 125s] +3 pidfd:[INODENUM] pidfd:[INODENUM] > [ 125s] pidfd:ASSOC,KNAME,NAME: 0 > [ 125s] lsfd: NAME and KNAME column: [02] pidfd ... FAILED (lsfd/column-name-pidfd) And: > [ 125s] --- tests/expected/lsfd/column-type-pidfd 2024-05-06 07:20:54.655845940 +0000 > [ 125s] +++ tests/output/lsfd/column-type-pidfd 2024-05-15 01:04:15.573333333 +0000 > [ 125s] @@ -1,2 +1,2 @@ > [ 125s] -3 UNKN pidfd > [ 125s] +3 REG REG > [ 125s] pidfd:ASSOC,STTYPE,TYPE: 0 > [ 125s] lsfd: TYPE and STTYPE column: [02] pidfd ... FAILED (lsfd/column-type-pidfd) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1223342] New: Security issus in FreeRDP
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223342 Bug ID: 1223342 Summary: Security issus in FreeRDP Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: ecsos(a)schirra.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- CVE-2024-32039 CVE-2024-32040 CVE-2024-32041 CVE-2024-32458 CVE-2024-32459 CVE-2024-32460 Request is here: https://build.opensuse.org/request/show/1170000 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1222978] New: [SELinux] gnome-control-center (users) unable to set AutoLogin
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222978 Bug ID: 1222978 Summary: [SELinux] gnome-control-center (users) unable to set AutoLogin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- GNOME Control Center has the ability to set autologin, as button in a users account, requiring Polkit escalation in order to be able to set it Polkit is doing it's thing fine..but SELinux blocks it :) Audit.log output below type=USER_ACCT msg=audit(1713364967.267:211): pid=23024 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix acct="ilmehtar" exe="/usr/libexec/polkit-1/polkit-agent-helper-1" hostname=? addr=? terminal=? res=success' type=AVC msg=audit(1713364970.590:212): avc: denied { write } for pid=1269 comm="accounts-daemon" name="sysconfig" dev="overlay" ino=283 scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=dir permissive=1 type=AVC msg=audit(1713364970.590:213): avc: denied { add_name } for pid=1269 comm="accounts-daemon" name="displaymanager.new.1025417169" scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=dir permissive=1 type=AVC msg=audit(1713364970.590:214): avc: denied { create } for pid=1269 comm="accounts-daemon" name="displaymanager.new.1025417169" scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1 type=AVC msg=audit(1713364970.593:215): avc: denied { write } for pid=1269 comm="accounts-daemon" path="/etc/sysconfig/displaymanager.new.1025417169" dev="overlay" ino=1179107 scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1 type=AVC msg=audit(1713364970.593:216): avc: denied { remove_name } for pid=1269 comm="accounts-daemon" name="displaymanager.new.1025417169" dev="overlay" ino=1179107 scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=dir permissive=1 type=AVC msg=audit(1713364970.593:217): avc: denied { rename } for pid=1269 comm="accounts-daemon" name="displaymanager.new.1025417169" dev="overlay" ino=1179107 scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1 type=AVC msg=audit(1713364970.593:218): avc: denied { unlink } for pid=1269 comm="accounts-daemon" name="displaymanager" dev="overlay" ino=31627 scontext=system_u:system_r:accountsd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1 Not the most severe issue in the world (I personally dislike the feature)..but I have users who are super passionate about it, so at least I can now say the issue is filed in the right place :) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1223145] New: [SELinux] AVC denial on tw + gnome startup relating to xdm_t
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223145 Bug ID: 1223145 Summary: [SELinux] AVC denial on tw + gnome startup relating to xdm_t Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Operating System: tumbleweed with gnome desktop SELinux policy version and repository: the one currently in security:SELinux containing the /var/run change (commit in factory branch: 7eb64de2191880e9d2207fa60c9605268d6fc8ce) The software (incl. version) that is affected by the SELinux issue and the error message: gnome 46 + wayland SELinux Audit log: ---- time->Fri Apr 19 13:58:55 2024 type=AVC msg=audit(1713527935.206:83): avc: denied { getattr } for pid=1019 comm="startproc" path=2F7573722F7362696E2F706C796D6F75746864202864656C6574656429 dev="rootfs" ino=2256 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:root_t:s0 tclass=file permissive=0 Any other important details: install tumbleweed with gnome desktop over regular installer enable selinux, add security:SELinux repo, install selinux-policy + selinux-policy targeted from repo, reboot, AVC happens on every boot low prio, does not break functionality on a quick look -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1225352] New: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting?
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225352 Bug ID: 1225352 Summary: [Build 13.199] openQA test fails in prepare_firstboot: RPi3 not booting? Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://openqa.opensuse.org/tests/4217406/modules/prep are_firstboot/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: --- The Leap 15.5 JeOS image fails to boot in openQA for some time now. Initially it looked to me like an issue with the test infra, but the TW and 15.6 images boot while 15.5 fails consistently. I tried to reproduce the issue locally and except for a slow boot due to no ethernet cable it worked. The package diff between last working and latest build shows changes in aaa_base, coreutils, kernel, less, protobuf, libsemanage, perl, rpm and yast. Could be a kernel issue? ## Observation openQA test in scenario opensuse-15.5-JeOS-for-RPi-aarch64-jeos@RPi3 fails in [prepare_firstboot](https://openqa.opensuse.org/tests/4217406/modules/prepar… ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [13.183](https://openqa.opensuse.org/tests/4120363) ## Expected result Last good: [13.182](https://openqa.opensuse.org/tests/4119085) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1225544] New: When on Battery Power, Installation Cannot Continue Even After Plugging in Laptop
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225544 Bug ID: 1225544 Summary: When on Battery Power, Installation Cannot Continue Even After Plugging in Laptop Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: sm(a)eisoft.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If I start a new Aeon installation with my laptop unplugged and running on battery power, the installer correctly tells me that I need to be plugged into power before proceeding. However, even after plugging my laptop into a power source the aforementioned message cannot be dismissed. Software: openSUSE Aeon RC2 Hardware: Lenovo Thinkpad X1 Carbon 6th Intel Core i7 16GB Memory 1.0TB HD Steps to Reproduce: Start a fresh installation of Aeon via bootable USB while laptop is not connected to power. A message will appear saying that the installation cannot continue while on battery power. Plug laptop into power. Message will not be dismissed and clicking "ok" will result in message reappearing over and over again. Workaround: Make sure laptop is plugged in before starting an Aeon installation. ¯\_(ツ)_/¯ -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1225709] New: tik mounts the wrong path onto usb sticks installations
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225709 Bug ID: 1225709 Summary: tik mounts the wrong path onto usb sticks installations Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: hotel-brot.0z(a)icloud.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: tik tries to mount ‘/usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0’ but the correct path to mount would be ‘/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0\:0’ it seems as if tik just stops indicating the path at \ Reproducible: Always Steps to Reproduce: try to install aeon onto a usb stick Actual Results: mount: /var/lib/tik/mig/mnt: special device /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 does not exist. dmesg(1) may have more information after failed mount system call. [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:17][LOG] [pkexec][32] /usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 /var/lib/tik/mig/mnt [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:17][ERROR] Command <tt>/usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:20][LOG] [zenity][0][] --error --text Command <tt>/usr/bin/mount -o compress=zstd:1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_60A44C3FAD9EE791C9291FA8-0 /var/lib/tik/mig/mnt</tt> FAILED [/usr/lib/tik/modules/pre/20-mig][20240531-08:43:20][LOG] [STOP][1] /usr/bin/tik Expected Results: Successful mounting -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1224457] New: Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 Bug ID: 1224457 Summary: Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887 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: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: andrwlms(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Installation of Leap 15.5 or Tumbleweed on a machine with an AMD APU on an ASUS Prime B550-Plus (uses Realtek ALC 887 for sound) results in no sound from the motherboard. This is discussed in a thread on openSuSE forums: English language, Hardware forum, "5700G+ALC887" thread title. This has been explored with aplay -l, inxi -Axx, dmesg | grep snd_hda, lsmod and modprobe. It is apparently a matter of detection of the motherboard sound "card" in the presence of the CPU's integrated sound "card". This is apparently a bug in the kernel, not openSuSE, since installation of Linux Mint on the same hardware causes exactly the same problem, including identical output from aplay -l, inxi -Axx and dmesg | grep snd_hda. -- You are receiving this mail because: You are on the CC list for the bug.

1 47

[Bug 1222019] New: krdc can not connect to VNC hosts in plasma 6
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222019 Bug ID: 1222019 Summary: krdc can not connect to VNC hosts in plasma 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: noreply.section+dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading to Plasma 6, krdc can not connect to VNC hosts anymore. When trying to connect, krdc goes straight to a blue screen. After that, if trying to disconnect, the program freezes and the only way out is to kill the application. The behavior is the same regardless of what string is typed in the address field: i.e. the lock must happen quite early in the program. This still happens in tw 20240325 with krdc 24.02.1. A workaround so far is to use an alternative VNC viewer, such as tigervnc. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223909] New: Package vlc fails to build with gcc 14 because of assignments from incompatible pointer types
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223909 Bug ID: 1223909 Summary: Package vlc fails to build with gcc 14 because of assignments from incompatible pointer types Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- Vlc fails when built with GCC 14 because of use incompatible pointer types, which used to be warnings in previous versions of GCC but are errors by default in GCC 14: https://build.opensuse.org/package/live_build_log/home:rguenther:plgrnd/vlc… The bug seems to have been reported upstream as https://code.videolan.org/videolan/vlc/-/issues/28441 and to Gentoo as https://bugs.gentoo.org/919068. but there is also yet unresolved) Gentoo issue https://bugs.gentoo.org/919296 so the particular error might not be the only one. For more information on porting to gcc 14, see https://gcc.gnu.org/gcc-14/porting_to.html -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1215337] New: python-onnx does not build s390x
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215337 Bug ID: 1215337 Summary: python-onnx does not build s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: ada.lovelace(a)gmx.de, ihno(a)suse.com Target Milestone: --- Found By: --- Blocker: --- python-onnx does not build on openSUSE:Factory:zSystems for quite some time: osc buildhistory openSUSE:Factory:zSystems python-onnx standard s390x TIME SRCMD5 VER-REL.BUILD# REV DURATION 2019-11-26 15:59:51 c7251471230f79907f69762d42f620a6 1.6.0-1.1 1 414 2019-12-24 10:29:50 c7251471230f79907f69762d42f620a6 1.6.0-1.2 1 821 2020-01-07 20:22:00 c7251471230f79907f69762d42f620a6 1.6.0-1.3 1 138 2020-01-08 17:02:51 0147179dbf202fdba63d0887ccf75400 1.6.0-2.1 2 192 2020-01-11 08:08:49 0147179dbf202fdba63d0887ccf75400 1.6.0-2.2 2 137 2020-01-21 18:59:45 0147179dbf202fdba63d0887ccf75400 1.6.0-2.3 2 135 2020-02-05 07:12:05 0147179dbf202fdba63d0887ccf75400 1.6.0-2.4 2 668 2020-02-07 20:58:34 0147179dbf202fdba63d0887ccf75400 1.6.0-2.5 2 178 2020-02-16 16:40:23 0147179dbf202fdba63d0887ccf75400 1.6.0-2.6 2 280 2020-02-18 13:51:04 0147179dbf202fdba63d0887ccf75400 1.6.0-2.7 2 227 2020-02-19 17:01:33 0147179dbf202fdba63d0887ccf75400 1.6.0-2.8 2 264 This package is needed in order to prepare a container for onnx-mlir which is the platform that also supports IBM Telum processors on Mainframe. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1219545] New: sound hangs after zypper update; unable to play any sound
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1219545 Bug ID: 1219545 Summary: sound hangs after zypper update; unable to play any sound 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: Sound Assignee: tiwai(a)suse.com Reporter: batpul(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Sound used to work fine until yesterday Feb 3 zypper update. Today after boot the sound configuration was non-existent. After yast2 sound Quick configuration the test sound produces no output. Set all volume controls to max. No improvement. Reboot doesn't help. Repeatedly deleting and recreating the sound configuration with yast2 in various ways doesn't help. When an application like aplay, audacious tries to play a sound it hangs. yast2 sound configuration info. 100 Series/C230 Series Chipset Family HD Audio Controller Configured as sound card number 0 Driver snd-hda-intel PulseAudio is enabled. aplay just hangs until it timeouts: $ ll /usr/share/sounds/purple/alert.wav -rw-r--r-- 1 root root 23314 May 9 2022 /usr/share/sounds/purple/alert.wav $ aplay /usr/share/sounds/purple/alert.wav Playing WAVE '/usr/share/sounds/purple/alert.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono ALSA lib pcm_pulse.c:758:(pulse_prepare) PulseAudio: Unable to create stream: Timeout aplay: set_params:1416: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 16 CHANNELS: 1 RATE: 22050 PERIOD_TIME: 125000 PERIOD_SIZE: (2756 2757) PERIOD_BYTES: (5512 5513) PERIODS: 4 BUFFER_TIME: 500000 BUFFER_SIZE: 11025 BUFFER_BYTES: 22050 TICK_TIME: [0 0] -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1225286] New: noveau don't work after kernel update 6.9
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225286 Bug ID: 1225286 Summary: noveau don't work after kernel update 6.9 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: kl-tech(a)posteo.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875102 --> https://bugzilla.suse.com/attachment.cgi?id=875102&action=edit the problem on a photo Desktop KDE/GNOME Running sudo zypper dup caused a kernel update. Even after several restarts, the second AOC monitor on the Lenovo w520 continued to work. After going into energy saving mode a few times, the external display in question ran with a resolution of 4:9. After a restart, the display in the KDE login screen (is that SDDM?) gave an error message that it could not control the second monitor. In KDE it continued to work with the wrong resolution and could not be changed in the settings and was only displayed as VGA-1. After starting via grub(UEFI) it was possible to record the following error message with Google lens (unfortunately only parts of the message are preserved): 3.7901601[ T398) 0000:01:00.0: DRM: [DRM/00000001:kmsOutp] [LOAD_DET load:07 (ret:7) 3.802496][ TOS 0000:01:00.0: DRM: [DRM/00000001:kmsOutp] [LOAD_DET load:07 (ret:7) 0000:01:00.0: DRM: [DRM/00000001:kmsOutp] [LOAD_DET [ 3.854827][ T85 load:07 (ret:7) cau 0000:01:00.0: DRM: [DRM/00000001:kmsOutp] [LOAD_DET [ 3.888158][ T851 load:07 (ret:7) [ 3.921490][ T851 new 0000:01:08.0: DRM: [DRM/00000001:kmsOutp] [LOAD_DET load:07 (ret:7) The boot log showed no abnormalities. After resetting to a version about a week old, the system worked as expected: List of snapshots and updates: ---------------------------------------------------------------------------- -Snapshot that worked -didn't work (when resetting, but before the update) -didn't work (when resetting, but before the update) -The update -Sleep mode several times -didn't work ------------------------------------------------------- After resetting, everything worked until the next update. It should be mentioned that the monitor was turned off several times while it was connected, but it still works, so it's not a hardware defect. With other distros from the life USB stick, everything worked as expected. Once it's running, openuse tumbleweed is one of the most practical distributions. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222505] New: ckermit: cannot create lock file in /var/lock
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222505 Bug ID: 1222505 Summary: ckermit: cannot create lock file in /var/lock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ceggers(a)arri.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Kermit needs to create a lock file for the used serial port (e.g. /dev/ttyUSB0) under /var/lock (symlink to /run/lock). Until Leap 15.5, that directory was owned by group "lock", so it was sufficient to add the current user to the "lock" group. But now the directory is owned by group "root", so using the "lock" group is not sufficient anymore. Reproducible: Always Steps to Reproduce: 1. Add current user to "dialout" group (and create re-login after that). 2. Ensure that step 1. was successful (e.g. by using the "id" command). 3. kermit -l /dev/ttyUSB0 Actual Results: Kermit gives an error "can't open device". Using "set line /dev/ttyUSB0" in kermit's interactive mode gives a more precise error message: "Sorry, write access to UUCP lockfile directory denied." Expected Results: kermit should have created the lock file and open /dev/ttyUSB0 A workaround is to change the group of /run/lock to "dialout" (and to add the current user to this group). But this change is lost after every reboot. Possibly related to https://bugzilla.opensuse.org/show_bug.cgi?id=624290 ("ckermit from contrib repository does not use lockdev, so cannot write to /var/lock"). The packet installed is: $ rpm -q ckermit --info Name : ckermit Version : 9.0.302 Release : 150000.3.3.1 Architecture: x86_64 Install Date: Mo 08 Apr 2024 09:44:42 CEST Group : Hardware/Modem Size : 2621762 License : BSD-3-Clause Signature : RSA/SHA256, Fr 01 Apr 2022 13:39:36 CEST, Key ID 70af9e8139db7c82 Source RPM : ckermit-9.0.302-150000.3.3.1.src.rpm Build Date : Fr 01 Apr 2022 13:39:14 CEST Build Host : goat10 Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC <https://www.suse.com/> URL : http://www.kermitproject.org/ Summary : A Combined Serial and Network Communication Software Package Description : C-Kermit is a combined serial and network communication software package offering a consistent, medium-independent, and cross-platform approach to connection establishment, terminal sessions, file transfer, character-set translation, and automation of communication tasks. Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1214353] New: mhi: Enabling broadband connecting not working
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1214353 Bug ID: 1214353 Summary: mhi: Enabling broadband connecting not working 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: Network Assignee: screening-team-bugs(a)suse.de Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868851 --> https://bugzilla.suse.com/attachment.cgi?id=868851&action=edit hwinfo.txt When trying to use broadband connecting with network manager, I can not get beyond entering SIM code - starting connection does not work System Slot: #36 Designation: "M.2 WWAN Connector (J3702)" Type: 0xa6 (Other) Bus Width: 0x08 (Other) Status: 0x03 (Available) Length: 0x04 (Long) Slot ID: 4 Characteristics: 0x0704 (3.3 V, PME#, Hot-Plug) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222854] New: https subversion checkout fails
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222854 Bug ID: 1222854 Summary: https subversion checkout fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jonathan.brady(a)denbridgemarine.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Fresh install of current beta, with just "subversion" package added. At the time of writing that is subversion-1.14.1-150400.3.8. Trying to checkout any https url fails. For example "svn co https://opensuse.org" (yes, I know there is no repository there, there doesn't need to be), the command never returns. tcpdump shows lots of activity on port 443, but the TLS connection never establishes. Other programs (w3m for example are able to establish TLS connection without problem). My expected result with that URL, would be: Redirecting to URL 'https://www.opensuse.org': svn: E170013: Unable to connect to a repository at URL 'https://www.opensuse.org' svn: E175003: The server at 'https://www.opensuse.org' does not support the HTTP/DAV protocol -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1215172] New: VUL-0: croc: multiple security issues in croc
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215172 Bug ID: 1215172 Summary: VUL-0: croc: multiple security issues in croc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: jsmithfpv(a)gmail.com Reporter: matthias.gerstner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have reviewed the Croc codebase during the past month and have found a series of security issues, mostly in the area of a receiver of files which can be harmed by a malicious sender. There are now public GitHub issues about the most pressing issues: - possible creation of files in dangerous path location: https://github.com/schollz/croc/issues/593 - Interactive File Overwrite Prompt can be Circumvented by Sending ZIP file: https://github.com/schollz/croc/issues/594 - Escape Sequences in Filenames are not Filtered: https://github.com/schollz/croc/issues/595 - Use of Parts of the Shared Secret as Room Name: https://github.com/schollz/croc/issues/596 - Unencrypted "ips?" Message Leaks Information from the Sender Side: https://github.com/schollz/croc/issues/597 - Shared Secret Passed on Command Line Possibly Leaks to other Local Users: https://github.com/schollz/croc/issues/598 Nothing of this is currently fixed and it sounds like they also won't be fixed for a longer time, because the upstream author is lacking time to take care of this. As maintainers of croc you may be able to help out upstream to fix these issues or you may consider dropping this package from openSUSE until it becomes better. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1225317] New: AUDIT-0: systemd: Please review the new DBUS /polkit stuff brought by v256
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1225317 Bug ID: 1225317 Summary: AUDIT-0: systemd: Please review the new DBUS /polkit stuff brought by v256 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, The next major version of system (v256) will come with a host of new features and thus a bunch of methods/actions to review. Could you please review them ? I created the following project that will be used as the devel project for v256: https://build.opensuse.org/package/live_build_log/home:fbui:systemd:v256/sy… You should find the build logs there where the list of methods/actions to review is detailed. Please note that the integration is still WIP hence most of the new stuff has been temporarily packaged in the systemd-experimental subpackage. But some of them will be moved in different subpackages once the integration will be finished. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

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

17 Jun '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 8

[Bug 1222595] New: find-debuginfo.sh crash when build with kanidm
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222595 Bug ID: 1222595 Summary: find-debuginfo.sh crash when build with kanidm 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: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- find-debuginfo.sh crash when building with kanidm, the full build log openSUSE:Backports:SLE-15-SP6 staging[1] [ 1201s] + /usr/lib/rpm/find-debuginfo.sh -j4 --build-id-seed 1.1.0~rc16~git4.d407844-bp156.2.1 --unique-debug-suffix -1.1.0~rc16~git4.d407844-bp156.2.1.x86_64 --unique-debug-src-base kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 -S debugsourcefiles.list /home/abuild/rpmbuild/BUILD/kanidm-1.1.0~rc16~git4.d407844 [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/bin/kanidm [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/lib64/security/pam_kanidm.so [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/lib64/libnss_kanidm.so.2 [ 1201s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/kanidm-1.1.0~rc16~git4.d407844-bp156.2.1.x86_64/usr/sbin/kanidm-ipa-sync [ 1201s] Cannot handle 8-byte build ID [ 1201s] Cannot handle 8-byte build ID [ 1203s] Cannot handle 8-byte build ID [ 1203s] Cannot handle 8-byte build ID [ 1203s] /usr/lib/rpm/find-debuginfo.sh: line 521: /tmp/find-debuginfo.avVGqk/res.*: No such file or directory [1] https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215622] New: iscsiuio - Couldn't mmap registers: Invalid argument
by bugzilla_noreply＠suse.com 17 Jun '24

17 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215622 Bug ID: 1215622 Summary: iscsiuio - Couldn't mmap registers: Invalid argument Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When trying to set up an iscsi initiator (in yast) using a bnx2 offload engine, I wasn't getting very far, see bug#1215621. I kept getting this error: iscsiadm: Could not set host net params (err 29) I ran iscsiuio with debug level 4 and noticed the following error msg: Couldn't mmap registers: Invalid argument After some research, I rebooted the machine with "iomem=relaxed" - now it works: anton:~ # iscsiadm -m discovery -P 1 -t st -I eth4-bnx2i -p 10.42.8.10:3260 iscsiadm: Could not set host net params (err 29) iscsiadm: Connection to discovery portal 10.42.8.10 failed: operation failed but retry may succeed Target: iqn.2023-09.local.rz2:opensuse-mirror Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i Target: iqn.2023-09.local.rz2:webspace Portal: 10.42.8.10:3260,1 Iface Name: eth4-bnx2i -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1221183] New: Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221183 Bug ID: 1221183 Summary: Upgrade problems with clang-cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: franz.sirl-obs(a)lauterbach.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, during a "zypper --releasever=15.6 dup" upgrade from a fully up-to-date 15.5 installation I got the following messages: Checking for file conflicts: ...................................................................................................................................................................[error] Detected 4 file conflicts: File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from install of clang13-13.0.1-bp156.7.42.x86_64 (Main Repository) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang11-11.0.1-150300.3.6.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang15-15.0.7-150500.4.4.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang7-7.0.1-150100.3.22.2.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes Even though this is mostly harmless, it disturbs the upgrade experience and probably can be easily fixed by backporting the clang-cpp/update-alternatives change from clang17 to the other clang versions that are part of Leap. regards, Franz -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222269] New: LLVM run OOM while building typst for armv6/7 with 24G of RAM
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1222269 Bug ID: 1222269 Summary: LLVM run OOM while building typst for armv6/7 with 24G of RAM Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- LLVM run OOM while building typst for armv6/7 with 24G of RAM while aarch64 requires 11.8G of RAM ********** [ 173s] Compiling typst-ide v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/crates/typst-ide) [ 429s] Compiling typst-fuzz v0.11.0 (/home/abuild/rpmbuild/BUILD/typst-0.11.0/tests/fuzz) [ 658s] LLVM ERROR: out of memory [ 658s] Allocation failed [ 658s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 658s] called `Option::unwrap()` on a `None` value [ 658s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 658s] error: could not compile `typst-docs` (bin "typst-docs") [ 658s] warning: build failed, waiting for other jobs to finish... [ 663s] LLVM ERROR: out of memory [ 663s] Allocation failed [ 664s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 664s] called `Option::unwrap()` on a `None` value [ 664s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 664s] error: could not compile `typst-fuzz` (bin "compile") [ 694s] LLVM ERROR: out of memory [ 694s] Allocation failed [ 694s] thread 'main' panicked at cargo-auditable/src/rustc_wrapper.rs:101:39: [ 694s] called `Option::unwrap()` on a `None` value [ 694s] note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace [ 694s] error: could not compile `typst-cli` (bin "typst") [ 694s] error: Bad exit status from /var/tmp/rpm-tmp.R2PFPX (%build) ********** See: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:ARM/typs… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224003] New: after snapshot 20240424 core dump for named with samba-ad-dc
by bugzilla_noreply＠suse.com 16 Jun '24

16 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1224003 Bug ID: 1224003 Summary: after snapshot 20240424 core dump for named with samba-ad-dc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874735 --> https://bugzilla.suse.com/attachment.cgi?id=874735&action=edit Coredump of named with samba-ad-dc I have a raspberry with samba-ad-dc and named. After snapshot 20240424 named doesn't start and I have a core dump for named; If I comment the instructions for samba-ad-dc in /etc/named.conf I can start named. the two instructions commented in named.confare include "/var/lib/samba/bind-dns/named.conf"; tkey-gssapi-keytab "/var/lib/samba/bind-dns/dns.keytab"; Samba-ad-dc is running rasp:/etc # systemctl status samba-ad-dc ● samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/usr/lib/systemd/system/samba-ad-dc.service; enabled; preset: disabled) Active: active (running) since Wed 2024-04-03 09:04:17 CEST; 1 month 3 days ago Docs: man:samba(8) man:samba(7) man:smb.conf(5) Process: 1256 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 1318 (samba) Status: "samba: ready to serve connections..." Tasks: 51 (limit: 4471) CPU: 9min 54.827s CGroup: /system.slice/samba-ad-dc.service etc.... I attach the coredump Many thanks in advance -- You are receiving this mail because: You are on the CC list for the bug.

1 3