May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215645] New: Flatpak uses broken Adwaita theme in KDE Plasma with huge cursor
by bugzilla_noreply＠suse.com 19 Jun '24

19 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1215645 Bug ID: 1215645 Summary: Flatpak uses broken Adwaita theme in KDE Plasma with huge cursor 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: rx2l5t+4zshakz4lenfc(a)sharklasers.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Open Firefox, Thunderbird or any GTK4 app in Plasma and they will appear with a GNOME theme, with a huge Adwaita cursor. This seems to be caused by the most recent Flatpak and/or xdg-desktop updates. Apparently doesn't happen on X11, only on the Wayland session. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1223305] New: [Regression] Bluetooth audio devices reset/disconnected/audio profile changed(??) when wine/proton applications initialize sound
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1223305 Bug ID: 1223305 Summary: [Regression] Bluetooth audio devices reset/disconnected/audio profile changed(??) when wine/proton applications initialize sound 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: el(a)horse64.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm sadly having what seems to be a regression possibly related to Plasma 5 to 6. Now often when wine or proton applications initialize audio , e.g. when I startup EA App inside Steam at launch, or something like REAPER's windows version ( https://reaper.fm/ the trial is free and unrestricted) at any time I press "play", the following happens: 1. Audio drops out completely for a split second. 2. A visible notification is shown like my bluetooth device just freshly connected 3. Audio profile is degraded to something horrible, it sounds like the worst quality headset telephony codec. 4. Sometimes a second later it resets back to what bluetooth profile I had before, usually high-quality playback only "AAC". But sometimes it also just doesn't. This can be checked in plasma's audio device panel, where it will show the telephony codec "Headset Unit ... mSBC" profile in case it didn't reset properly. This also happens when another application is already playing audio in parallel, which sadly makes this disruptive. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1213606] New: mksusecd: fix --instsys option
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1213606 Bug ID: 1213606 Summary: mksusecd: fix --instsys option 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: snwint(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- mksusecd allows modifying the installation system using the --instsys option. This does not work correctly (existing files are not replaced). Also, ALP and Fedora use a Live media layout, which is not supported at all. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1218706] New: mksusecd: allow for zstd (and xz) compression in repo metadata
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1218706 Bug ID: 1218706 Summary: mksusecd: allow for zstd (and xz) compression in repo metadata Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: snwint(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently, Tumbleweed started using zstd in its repo metadata. For example, /repodata/<SHA256>-primary.xml.zst. Asjust mksusecd to support zstd (and xz, just in case). -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1214789] New: Drop the raw / uncompressed kernel-firmware package
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1214789 Bug ID: 1214789 Summary: Drop the raw / uncompressed kernel-firmware package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Currently, kernel-firmware repo provides two different ways of packaging: one is the kernel-firmware.rpm that contains all firmware files in raw and uncompressed format, and another is the split of several subpackages with compressed files which are gathered by kernel-firmwre-all.rpm meta package. The former, kernel-firmware.rpm is still provided only for the legacy use cases (the old SLE), and kernel-firmware-all.rpm already has "Provides: kernel-firmware" as the better (much smaller) replacement. Now, we'd like to drop the old big kernel-firmware.rpm finally. But this needs fixing the dependencies in some package or images. As far as I see, the only package that has an explicit use of the uncompressed files is installation-images. This needs the changes to adapt kernel-firmwre-all and handling of compressed files. Also, KIWI images may have requires of kernel-firmware, and that might be a bigger problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1221568] New: VUL-0: CVE-2024-22513: python-djangorestframework-simplejwt: information disclosure via inactive user
by bugzilla_noreply＠suse.com 18 Jun '24

18 Jun '24

https://bugzilla.suse.com/show_bug.cgi?id=1221568 Bug ID: 1221568 Summary: VUL-0: CVE-2024-22513: python-djangorestframework-simplejwt: information disclosure via inactive user Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/393624/ OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: mmachova(a)suse.com Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: carlos.lopez(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- djangorestframework-simplejwt version 5.3.1 and before is vulnerable to information disclosure. A user can access web application resources even after their account has been disabled due to missing user validation checks via the for_user method. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-22513 https://www.zerodayinitiative.com/advisories/ZDI-24-101/ https://www.cve.org/CVERecord?id=CVE-2024-22513 https://github.com/dmdhrumilmistry/CVEs/tree/main/CVE-2024-22513 https://bugzilla.redhat.com/show_bug.cgi?id=2269822 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[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 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 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