May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1217312] New: Google websites do not work in Firefox
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1217312 Bug ID: 1217312 Summary: Google websites do not work in Firefox Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: bart.vanassche+novell(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since more than a year, multiple Google websites, e.g. Google Search, Google Docs and Gmail, do not work well with the Firefox software included with openSUSE Tumbleweed. It often happens that loading one of these websites stalls. Logging in to a Google account doesn't work at all. I don't see this issue if I download Firefox binaries from the Mozilla website and load my existing profile (firefox/firefox -profileManager). Does this perhaps mean that there is a problem with changes made to the Firefox software that is available from openSUSE? Tumbleweed version: $ rpm -qf /etc/issue.net openSUSE-release-20231117-2596.1.x86_64 Firefox versions: $ rpm -q MozillaFirefox MozillaFirefox-119.0.1-1.1.x86_64 Binary downloaded from the Mozilla website: firefox-119.0.1.tar.bz2 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222170] New: build.opensuse.org returns 422 (Unprocessable Content), possibly due to UTF-8
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222170 Bug ID: 1222170 Summary: build.opensuse.org returns 422 (Unprocessable Content), possibly due to UTF-8 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: piotrekd(a)vivaldi.net QA Contact: adrian.schroeter(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hello, I registered a new (open)SUSE account. I can use it to log into build.opensuse, but after I do so, the website becomes unusable because trying to open it returns only the HTTP error 422 (Unprocessable Content) to the browser (no special page like the 404 one). I *guess* this may be caused by the non-ASCII (UTF-8) “ł” character that appears in my user name. The registration form at https://idp-portal.suse.com allowed me to use it, so I did. That site works just fine when I log in. BugZilla seems to work OK too. The openSUSE Open Build Service does not, however. Kind regards. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222752] New: ugrep: build results depend on CPU
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1222752 Bug ID: 1222752 Summary: ugrep: build results depend on CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: Andreas.Stieger(a)gmx.de Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1100677 Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our ugrep binaries depend on the build machine CPU again. It seems SR 1166721 reverted my previous SR 818786 related: https://github.com/Genivia/ugrep/pull/50 CPU march=native ; partial fix The buildroot diff shows +++ /home/abuild/rpmbuild/BUILD.unsorted/ugrep-5.1.4/Makefile @@ -327,9 +327,9 @@ SED = /usr/bin/sed SET_MAKE = SHELL = /usr/bin/bash -SIMD_AVX2_FLAGS = -mavx2 +SIMD_AVX2_FLAGS = SIMD_AVX512BW_FLAGS = -SIMD_FLAGS = -msse2 -DHAVE_AVX2 +SIMD_FLAGS = -msse2 -DHAVE_SSE2 There are multiple ways to solve that: - never use AVX2 (as before) - always use AVX2 - detect AVX2 at runtime instead of compile-time -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1216393] New: Electron/Chromium can't render h264 in webrtc
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1216393 Bug ID: 1216393 Summary: Electron/Chromium can't render h264 in webrtc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: bjorn.bidar(a)thaodan.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- * Description: When trying to stream WebRTC with h264 in Electron/Chromium the screen stays black even thou OpenH264 is correctly installed. * How to reproduce: 1. Open Chromium 2. Open https://mozilla.github.io/webrtc-landing/pc_test_no_h264.html 3. Click test ** Another option is to use: https://mozilla.github.io/webrtc-landing/pc_test.html 1. Tick require h264 2. Start the video, wait 3. The message now should be "No H264 found in the offer!!!" * Background and reason for the bug: openSUSE builds both Chromium and Electron in a way that h264 isn't compiled into both packages but loaded using the Openh264 provided by openSUSE but blessed by Cisco. However Chromium has to use some of the openh264 to build even thou it's not used during runtime. The gyp option `rtc_use_h264` has be set to true and third_party/openh264 has to be included in the tarball (already the case in the upstream third_party/openh264 tarball). This is due webrtc using openh264 headers in third_party/webrtc/modules/video_coding/codecs/h264/h264_encoder_impl.cc -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1218303] New: VUL-0: CVE-2023-6704: libavif,chromium,ungoogled-chromium: use after free in libavif
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1218303 Bug ID: 1218303 Summary: VUL-0: CVE-2023-6704: libavif,chromium,ungoogled-chromium: use after free in libavif Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: aaronpuchert(a)alice-dsl.net, andrea.mattiazzo(a)suse.com, Andreas.Stieger(a)gmx.de, gmbr3(a)opensuse.org, security-team(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It was reported that libavif before 1.0.3, and as bundled in Chromium, contained a use-after-free bug. colorProperties could be pointing to a dangling pointer if findAlphaItem() resizes the meta.items array. Also bundled in chromium, see bug 1218048 References: https://github.com/AOMediaCodec/libavif/pull/1808 https://github.com/AOMediaCodec/libavif/commit/b984f48be99b41405cb4a7d44380… https://github.com/AOMediaCodec/libavif/releases/tag/v1.0.3 https://bugs.chromium.org/p/chromium/issues/detail?id=1504792 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1220201] New: Firefox on Wayland - download dialog disappearing
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1220201 Bug ID: 1220201 Summary: Firefox on Wayland - download dialog disappearing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Using Firefox on Wayland the download dialog is disappearing after chosing "save file" and before selecting the download file and directory. One can see the "enter name ..." dialog for a second, then it vanishes. On the same machine this does not happen with Xorg. There is no error or warning in the journal, i.e. for a crash. Operating System: openSUSE Tumbleweed 20240220 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1223967] New: %suse_build_hwcaps_libs fails to generate -x86_64-v3 packages when shared library is an update-alternatives link
by bugzilla_noreply＠suse.com 29 Aug '24

29 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1223967 Bug ID: 1223967 Summary: %suse_build_hwcaps_libs fails to generate -x86_64-v3 packages when shared library is an update-alternatives link Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- ## Originally reported on GitHub: https://github.com/openSUSE/obs-build/issues/1001 This came up when trying to enable -v3 hwcaps enhanced libs for `lapack`. As it turns out, `lapack` uses update-alternatives to create a symlink `/usr/lib64/libblas.so.3` pointing to the real library `/usr/lib64/blas/libblas.so.3` via `update-alternatives` called during `post`. The file `/usr/lib64/libblas.so.3` does not exist a build-time, but created by update-alternatives during `post` install. It is also marked as `%ghost` in the package. Apparently `%{?suse_build_hwcaps_libs}` cannot handle this. It tries to copy the non-existent — at build time — `/usr/lib64/libblas.so.3` and fails catastrophically _after_ actually generating the hwaps libs. This is what I see in the log. Note the error: `mv: cannot stat '.cfiles/usr/lib64/liblapack.so.3': No such file or directory` which suggests it is trying to move a non-existent file which will be created during `post` install: > [ 218s] RPMLINT report: > [ 218s] =============== > [ 220s] ============================ rpmlint session starts ============================ > [ 220s] rpmlint: 2.5.0 > [ 220s] configuration: > [ 220s] /opt/testing/lib64/python3.11/rpmlint/configdefaults.toml > [ 220s] /opt/testing/share/rpmlint/cron-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/dbus-services.toml > [ 220s] /opt/testing/share/rpmlint/device-files-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/licenses.toml > [ 220s] /opt/testing/share/rpmlint/opensuse.toml > [ 220s] /opt/testing/share/rpmlint/pam-modules.toml > [ 220s] /opt/testing/share/rpmlint/permissions-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/pie-executables.toml > [ 220s] /opt/testing/share/rpmlint/polkit-rules-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/scoring.toml > [ 220s] /opt/testing/share/rpmlint/security.toml > [ 220s] /opt/testing/share/rpmlint/sudoers-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/sysctl-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/systemd-tmpfiles.toml > [ 220s] /opt/testing/share/rpmlint/users-groups.toml > [ 220s] /opt/testing/share/rpmlint/world-writable-whitelist.toml > [ 220s] /opt/testing/share/rpmlint/zypper-plugins.toml > [ 220s] rpmlintrc: > [ 220s] /home/abuild/rpmbuild/SOURCES/lapack.rpmlintrc > [ 220s] checks: 41, packages: 21 > [ 220s] > [ 220s] libblas3.x86_64: I: package-supports-update-alternatives > [ 220s] libcblas3.x86_64: I: package-supports-update-alternatives > [ 220s] liblapack3.x86_64: I: package-supports-update-alternatives > [ 220s] liblapacke3.x86_64: I: package-supports-update-alternatives > [ 220s] libblas3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] libcblas3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] liblapack3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] liblapacke3.x86_64_v3: I: package-supports-update-alternatives > [ 220s] Check time report (>1% & >0.1s): > [ 220s] Check Duration (in s) Fraction (in %) Checked files > [ 220s] ExtractRpm 0.3 30.3 > [ 220s] SignatureCheck 0.2 19.6 > [ 220s] BinariesCheck 0.2 19.2 > [ 220s] SharedLibraryPolicyCheck 0.2 16.2 > [ 220s] TOTAL 1.0 100.0 > [ 220s] > [ 220s] 21 packages and 0 specfiles checked; 0 errors, 0 warnings, 131 filtered, 0 badness; has taken 1.1 s > [ 220s] > [ 220s] ... cleaning ccache > [ 220s] setting SOURCE_DATE_EPOCH_MTIME to 1714856125 > [ 220s] 1 > [ 220s] ... saving ccache archive > [ 220s] ... creating baselibs > [ 220s] setting SOURCE_DATE_EPOCH_MTIME to 1714856125 > [ 220s] no targets for arch x86_64, skipping lapack-devel > [ 220s] no targets for arch x86_64, skipping liblapack3 > [ 220s] no targets for arch x86_64, skipping lapacke-devel > [ 220s] no targets for arch x86_64, skipping libblas3 > [ 220s] no targets for arch x86_64, skipping liblapacke3 > [ 220s] no targets for arch x86_64, skipping libcblas3 > [ 220s] no targets for arch x86_64, skipping cblas-devel > [ 220s] no targets for arch x86_64, skipping blas-devel > [ 220s] liblapack3(x86_64:x86-64-v3): writing specfile... > [ 220s] liblapack3(x86_64:x86-64-v3): running build... > [ 220s] rpmbuild failed: 256 > [ 220s] re-running in verbose mode: > [ 220s] using SOURCE_DATE_EPOCH with value 1714856124 as build time > [ 220s] Executing(%prep): /usr/bin/bash -e /var/tmp/rpm-tmp.r51odx > [ 220s] + umask 022 > [ 220s] + cd /home/abuild/rpmbuild/BUILD > [ 220s] + RPM_EC=0 > [ 220s] ++ jobs -p > [ 220s] + exit 0 > [ 220s] Executing(%build): /usr/bin/bash -e /var/tmp/rpm-tmp.dHOH58 > [ 220s] + umask 022 > [ 220s] + cd /home/abuild/rpmbuild/BUILD > [ 220s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] ++ dirname /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT > [ 220s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + RPM_EC=0 > [ 220s] ++ jobs -p > [ 220s] + exit 0 > [ 220s] Executing(%install): /usr/bin/bash -e /var/tmp/rpm-tmp.Aiq5Zt > [ 220s] + umask 022 > [ 220s] + cd /home/abuild/rpmbuild/BUILD > [ 220s] + /usr/bin/rm -rf /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT > [ 220s] + /usr/bin/mkdir /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + rm -rf /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + mkdir /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + cd /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + mkdir -p .cfiles > [ 220s] + pushd .cfiles > [ 220s] ~/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/.cfiles ~/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 220s] + cat > [ 220s] + rpm2cpio //home/abuild/rpmbuild/RPMS/x86_64_v3/liblapack3-3.12.0-94.1.x86_64_v3.rpm > [ 220s] + cpio -i -d -v -E .filelist > [ 220s] ./usr/lib64/lapack/liblapack.so.3 > [ 221s] ./usr/lib64/lapack/liblapack.so.3.12.0 > [ 221s] 15311 blocks > [ 221s] + popd > [ 221s] ~/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64 > [ 221s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack > [ 221s] + mv .cfiles/usr/lib64/lapack/liblapack.so.3 /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack/liblapack.so.3 > [ 221s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack > [ 221s] + mv .cfiles/usr/lib64/lapack/liblapack.so.3.12.0 /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/lapack/liblapack.so.3.12.0 > [ 221s] + mkdir -p /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3 > [ 221s] + mv .cfiles/usr/lib64/liblapack.so.3 /home/abuild/rpmbuild/BUILDROOT/lapack-3.12.0-94.1.x86_64/usr/lib64/glibc-hwcaps/x86-64-v3/liblapack.so.3 > [ 221s] mv: cannot stat '.cfiles/usr/lib64/liblapack.so.3': No such file or directory > [ 221s] error: Bad exit status from /var/tmp/rpm-tmp.Aiq5Zt (%install) > [ 221s] > [ 221s] RPM build errors: > [ 221s] Bad exit status from /var/tmp/rpm-tmp.Aiq5Zt (%install) > [ 221s] ### VM INTERACTION START ### > [ 221s] [ 217.139930][ T1] sysrq: Power Off > [ 221s] [ 217.141087][ T10] reboot: Power down > [ 221s] ### VM INTERACTION END ### > [ 221s] > [ 221s] i01-ch1d failed "build lapack.spec" at Mon May 6 11:51:16 UTC 2024. > [ 221s] FWIW, here is the baselibs.conf: > ... > > liblapack3 > -/usr/lib(64)?/liblapack.so.3 > requires "update-alternatives" > postin "ln -sf /etc/alternatives/liblapack.so.3_<targettype> /usr/%_lib/liblapack.so.3" > postin "/usr/sbin/update-alternatives --force --install /usr/%_lib/liblapack.so.3 liblapack.so.3_<targettype> /usr/%_lib/lapack/liblapack.so.3 50" > postun "/usr/sbin/update-alternatives --remove liblapack.so.3_<targettype> /usr/%_lib/lapack/liblapack.so.3" > > ... And attached is the full build log if it helps (from https://build.opensuse.org/package/show/home:badshah400:lapackv3/lapack) -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1220814] New: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?)
by bugzilla_noreply＠suse.com 28 Aug '24

28 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1220814 Bug ID: 1220814 Summary: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: michael.burge77(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873182 --> https://bugzilla.suse.com/attachment.cgi?id=873182&action=edit full journalctl of the third crash I have an old portable with a wonky dc power jack which tends to generate a few quick AC0<->BAT0 events in succession. Starting with kernel 6.7.6-1-default the system locks up. Log is full of ``` Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost plasmashell[2682]: plasma-pk-updates: acPluggedChanged onBattery: false -> true Mar 01 17:34:17 ost kernel: BUG: unable to handle page fault for address: 0000000000007b8a Mar 01 17:34:17 ost kernel: #PF: supervisor read access in kernel mode Mar 01 17:34:17 ost kernel: #PF: error_code(0x0000) - not-present page ``` until it locks up with ``` Mar 01 18:11:29 ost kernel: note: kworker/11:5[23457] exited with irqs disabled Mar 01 18:11:50 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:54 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:55 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:58 ost plasmashell[5912]: [5912:0301/181158.744595:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. Mar 01 18:12:05 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:12:06 ost kernel: BUG: workqueue lockup - pool cpus=11 node=0 flags=0x0 nice=0 stuck for 37s! ``` at which point only holding down the power button works. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1224046] New: [Kernel][Upgrade] After upgrade Leap 15.4 -> 15.5 system fails to boot - hangs on KDE
by bugzilla_noreply＠suse.com 27 Aug '24

27 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1224046 Bug ID: 1224046 Summary: [Kernel][Upgrade] After upgrade Leap 15.4 -> 15.5 system fails to boot - hangs on KDE Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: viktors.trubovics(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874762 --> https://bugzilla.suse.com/attachment.cgi?id=874762&action=edit Boot video with loglevel=7 After upgrade Leap 15.4 -> 15.5 system fails to boot - hangs on KDE It fails to load KDE on all 5.14.21-150500.x kernels but boots successfully on 5.14.21-150400.24.100 and 5.14.21-150400.24.97 kernels. See attached boot video. Used procedure for upgrade: https://en.opensuse.org/SDB:System_upgrade_to_Leap_15.5 Machine is alive so I can collect any additional information. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1219282] New: Distorted sound in some applications, apparently occurring under system heavier load
by bugzilla_noreply＠suse.com 27 Aug '24

27 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1219282 Bug ID: 1219282 Summary: Distorted sound in some applications, apparently occurring under system heavier load 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: bartoletti.stefano(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872253 --> https://bugzilla.suse.com/attachment.cgi?id=872253&action=edit sound devices I'm experiencing some annoying sound problems, that are occurring only during some circumstances (apparently under heavier system load, but I don't know if this is a factor), and appeared starting from about a month ago (end of December 2023). Before that, everything was working normally. I'm running a fully updated tumbleweed, and I can notice this problem mainly when running games under Wine. Basically, the game starts fine, and after a while (there is not a fixed time), the audio starts crackling/scratching. Sometimes this just distorts the sound output, sometimes it is so severe to mute any sound completely. - It does not happen with every application. At the moment, browsers, VLC, spotify, and so on play sound correctly. Games run under Wine (through flatpak) and some other Linux games (still flatpak) have this problem. When this happens, when I close an app that causes this problem, sometimes even other apps (said browsers, spotify, etc) have their sounds distorted, at least for a while. - I'm not sure about this, but I think that I noticed this problem more often when there is a heavier system load (especially disk I/O), but to be honest, after all this time trying to figure this out without results, it may be me drawing unrelated conclusions. - This problem occurs only with a specific audio device, that controls my laptop built-in speakers: an "AMD Family 17h/19h HD Audio". My system is also equipped with an "AMD Renoir Radeon High Definition Audio" device that controls audio from the HDMI port, which works correctly when I connect it to i.e. an external TV. Everything is also working correctly with Bluetooth headphones or wired headphones connected to the jack port. This problem is occurring with every possible configuration that I can't test: - Both with pipewire (my default engine, which was working correctly until a month ago) and pulseaudio - Both with my user account and with a brand new test account that I created just for testing this - By logging in both with Wayland and X11 (and even ICEWM) - With every Kernel that I was able to test right now (current 6.7.x, 6.6.x, 6.5.x), but only starting from the end of December (before that, no problems even with these versions) I'm very puzzled and mildly annoyed by my inability to find a solution. From what I can see, this seems to be unrelated to my specific user config and I am unable to understand what should I do. Every possible related issue that I found by googling is mainly related to not having sound at all, which is easily diagnosed, while in my case this occurs in ways that I am not able to correctly pinpoint and troubleshoot. If it is useful, I've opened a question on Superuser, but it has received much attention. Anyway, it's here https://superuser.com/q/1827353/170331 I'm adding some useful info as attachments, feel free to ask for more. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 17