April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222233] New: Segmentation fault in kwin_wayland
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222233 Bug ID: 1222233 Summary: Segmentation fault in kwin_wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873996 --> https://bugzilla.suse.com/attachment.cgi?id=873996&action=edit journal log of the crash During normal desktop usage suddenly my desktop reset itself. The journal revealed a SIGSEGV in kwin_wayland: > Apr 02 13:57:26 racetrack-7290 kernel: traps: kwin_wayland[3284] general protection fault ip:7f448470c615 sp:7ffc5e0b7290 error:0 in screencast.so[7f4484700000+14000] > Apr 02 13:57:26 racetrack-7290 systemd[1]: Started Process Core Dump (PID 11805/UID 0). > Apr 02 13:57:26 racetrack-7290 systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling. > Apr 02 13:57:27 racetrack-7290 systemd-coredump[11808]: [🡕] Process 3284 (kwin_wayland) of user 1000 dumped core. > > Stack trace of thread 3284: > #0 0x00007f448470c615 _ZN4KWin16ScreenCastStream17onStreamAddBufferEP9pw_buffer (screencast.so + 0x16615) > #1 0x00007f447ffa2c6b n/a (libpipewire-0.3.so.0 + 0x87c6b) > #2 0x00007f447ff9a9eb pw_impl_port_use_buffers (libpipewire-0.3.so.0 + 0x7f9eb) > #3 0x00007f447feeadb5 n/a (libpipewire-module-client-node.so + 0x11db5) > #4 0x00007f447fef9e27 n/a (libpipewire-module-client-node.so + 0x20e27) > #5 0x00007f44840517d0 n/a (libpipewire-module-protocol-native.so + 0x157d0) > #6 0x00007f4484051f90 n/a (libpipewire-module-protocol-native.so + 0x15f90) > #7 0x00007f44840937e6 n/a (libspa-support.so + 0x87e6) > #8 0x00007f4484705aa9 n/a (screencast.so + 0xfaa9) > #9 0x00007f4489fdaa83 n/a (libQt6Core.so.6 + 0x1daa83) > #10 0x00007f4489fe27af _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt6Core.so.6 + 0x1e27af) > #11 0x00007f4489fe2ffe _ZN15QSocketNotifier5eventEP6QEvent (libQt6Core.so.6 + 0x1e2ffe) > #12 0x00007f448b1c1a7e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1c1a7e) > #13 0x00007f4489f87998 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x187998) > #14 0x00007f448a0df36c _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt6Core.so.6 + 0x2df36c) > #15 0x00007f448a0dfe37 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x2dfe37) > #16 0x00007f448ac0646d _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x60646d) > #17 0x00007f4489f921ab _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x1921ab) > #18 0x00007f4489f8bde6 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x18bde6) > #19 0x0000558b21d4385a n/a (kwin_wayland + 0x5885a) > #20 0x00007f448962a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) > #21 0x00007f448962a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) > #22 0x0000558b21d496d5 n/a (kwin_wayland + 0x5e6d5) I'm attaching the full journal here. I also have the coredump but am reluctant to post it here, because the desktop session might contain sensitive data. I'm on Tumbleweed 20240329 and have no idea what could have triggered this issue or how to reproduce it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222014] New: Radeon video driver fails on the last 2 kernels after last night's update
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222014 Bug ID: 1222014 Summary: Radeon video driver fails on the last 2 kernels after last night's update 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: rskunath(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873827 --> https://bugzilla.suse.com/attachment.cgi?id=873827&action=edit Terminal error output snips This happens on the current and last kernel and was working fine until I applied the updates of last night. The system is an AMD FX-8350 CPU and a Radeon RX 580 AMD GPU. This is Tumbleweed and none of the Chrome or Chromium browsers will open. Chrome terminal snips of the errors are in the attachment. Please let me know if I can do anything to help isolate this. This is on KDE Plasma 6 and KDE X11. Errors are the same on the last 2 kernels. Both kernels were working, the current kernel worked last night. The DE comes up and works apparently normally in Wayland and X11 both. Thanks in advance, Rick Kunath -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1133809] Enable bit-reproducible packages
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1133809 Bug 1133809 depends on bug 1148824, which changed state. Bug 1148824 Summary: Issues with %clamp_mtime_to_source_date_epoch https://bugzilla.suse.com/show_bug.cgi?id=1148824 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1148824] Issues with %clamp_mtime_to_source_date_epoch
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1148824 https://bugzilla.suse.com/show_bug.cgi?id=1148824#c24 Jan Zerebecki <jzerebecki(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|IN_PROGRESS |RESOLVED --- Comment #24 from Jan Zerebecki <jzerebecki(a)suse.com> --- Yes, it is fixed in Tumbleweed. Though we still need to upstream the rpm changes, adapt to them, then submit the changes and enable this in ALP, so it will also be in Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222196] New: libisoburn1: udevadm hwdb is deprecated. Use systemd-hwdb instead.
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222196 Bug ID: 1222196 Summary: libisoburn1: udevadm hwdb is deprecated. Use systemd-hwdb instead. 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: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Running `zypper dup` on Tumbleweed I noticed the following message related to libisoburn1: ( 624/2166) Installing: libisoburn1-1.5.6-1.3.x86_64 .........[done] udevadm hwdb is deprecated. Use systemd-hwdb instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222081] Jamulus crashes since some time (no package update)
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222081 https://bugzilla.suse.com/show_bug.cgi?id=1222081#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- Thanks. It looks like the code path via JACK callback. Can it be some inconsistency with opus? You can try downgrading the pipewire packages from OBS TW history repo http://download.opensuse.org/history/ If this works, it's concluded as a regression there. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222172] emacsclient -n -c fails to start when emacs daemon is started early
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222172 https://bugzilla.suse.com/show_bug.cgi?id=1222172#c3 --- Comment #3 from Dr. Werner Fink <werner(a)suse.com> --- https://www.emacswiki.org/emacs/EmacsAsDaemon -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1221734] New: RTL8723BE cannot initialize mac after suspend or loss of AP
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221734 Bug ID: 1221734 Summary: RTL8723BE cannot initialize mac after suspend or loss of AP 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:Drivers Assignee: kernel-bugs(a)suse.de Reporter: owinebar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am using Leap 15.5 on an old ASUS laptop, model R541U. The wifi was working fine when I initially installed Leap 15.4 as the sole OS around April 2023. The wifi started acting flaky in September 2023, but I didn't pay much attention because it has been working. I finally took the time to try to get it working again. I set the power save parameters off, the debug_mask to 0xFFFFFFFFFFFFFFFF, and the debug_level to 5. I also set NetworkManager to use a permanent MAC address for wlan0 because there the error seemed to be associated with a message "Init MAC" failed. The device still fails in 2 situations, and reports the "Init MAC" error. The first is after suspending the laptop. Presumably the power save from the suspend is not dependent on the driver power save parameters, so it attempts and fails to reinitialize the wlan0 device. With debug level at 5, I see rtlwifi report "init MAC Fail as power on failure", the the "Init MAC failed" message from rtl8723be, then the message "Failed to config hardware!" from rtlwifi. The other failure arises when the connection to the AP is lost for 10s (at least that's what it reports) after rebooting with no intervening suspend. In the latter case, there are a lot of messages "Waiting for FW read clear HMEBox(0)!!! 0x130 = ff". The "Init MAC failed" message first appears in my messages file dated 2023-09-11. The previous rolled messages file is dated 2023-09-08. Looking at the zypp/history log, I evidently updated the kernel from 5.14.21-150400.24.74 to 5.14.21-150400.24.81, somewhere around August 31 or September 6 of 2023. I only updated the distribution on the laptop to 15.5 recently. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1193599] intel_dp_detect [i915]] *ERROR* LSPCON init failed on port D
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1193599 https://bugzilla.suse.com/show_bug.cgi?id=1193599#c43 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(opendreas(a)gmail.c | |om) --- Comment #43 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Andreas from comment #40) > The following message contains patches from the Intel developer. > https://patchwork.freedesktop.org/series/125157/ The patches aren't included in the upstream (yet?). I'm building a test kernel for SLE15-SP6 in OBS home:tiwai:bsc1193599-sp6 repo. The package will appear later at http://download.opensuse.org/repositories/home:/tiwai:/bsc1193599-sp6/pool/ Please give it a try later. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222156] radeon: After an upgrade the graphical interface no longer works
by bugzilla_noreply＠suse.com 02 Apr '24

02 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222156 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? -- You are receiving this mail because: You are on the CC list for the bug.

1 0