February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c7 --- Comment #7 from Jiri Slaby <jslaby(a)suse.com> --- And yet (sorry), brand new BIOSes might be buggy, so no BIOS update available (e.g. via fwupd)? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207655] amdgpu [RX 7900] causing system freeze
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207655 https://bugzilla.suse.com/show_bug.cgi?id=1207655#c7 --- Comment #7 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Stefan Dirsch from comment #6) > I've branched Mesa to build Mesa 23.0.0-rc4. Unfortunately this doesn't > include these fixes yet. I think it was branched before the patches got > merged. :-( > > https://build.opensuse.org/package/show/home:sndirsch:branches:X11:XOrg/Mesa Took me some time to get build working again, but looks good now. ------------------------------------------------------------------- Wed Feb 8 13:24:22 UTC 2023 - Stefan Dirsch <sndirsch(a)suse.com> - Update to version 23.0.0-rc4 - adjusted n_stop-iris-flicker.patch, u_dep_xcb.patch, u_fix-build-on-ppc64le.patch - re-enabled xmlconfig (/usr/share/drirc.d config snippets) - adjusted n_no-sse2-on-ix86-except-for-intel-drivers.patch to fix build on %ix86 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c6 --- Comment #6 from Jiri Slaby <jslaby(a)suse.com> --- Yeah and I also asked you about: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Doc… What last step (from [freezer, devices, ...]) does not expose the crash? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197542] New: zypper ps should show the interpreted program
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197542 Bug ID: 1197542 Summary: zypper ps should show the interpreted program Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: sionescu(a)cddr.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a program that runs in an interpreter has some of its files deleted, "zypper ps" shows the interpreter instead of the actual program. Showing the program that's being executed is more useful for deciding if the machine warrants a reboot. For example, after an update to Python 3.6, zypper ps shows: 5857 | ... | python3.6 (deleted) | | /usr/lib64/libpython3.6m.so.1.0 25325 | ... | python3.6 (deleted) | | /usr/lib64/libpython3.6m.so.1.0 25332 | ... | python3.6 (deleted) | | /usr/lib64/python3.6/lib-dynload/_heapq.cpython-36m-x86_64-linux-gnu.so While ps shows those 3 processes to be, in order: 5857 ... \_ /usr/bin/python3 /usr/bin/chrome-gnome-shell 25325 ... \_ /usr/bin/python3 /usr/bin/blueman-applet 25332 ... \_ /usr/bin/python3 /usr/bin/blueman-tray Even if there's no general solution for detecting interpreters, hard-coding the detection of the most common system-wide interpreters (Bash, Python, Ruby, Perl) would still be very useful. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c5 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #5 from Jiri Slaby <jslaby(a)suse.com> --- Just to sum up. no_console_suspend shows only a blinking cursor, right? Does pstore store anything to efi afterall? Do you have kdump set up? No crash generated in /var/crash/? (Note kdump is currently broken after each kernel update, see bug 1207114. You need to delete /boot/initrd-kdump and restart kdump service.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207988] [Build 20230206] Upgrade 15.3->TW : Audio volume set to 0%
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207988 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com Resolution|FIXED |INVALID -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207988] New: [Build 20230206] Upgrade 15.3->TW : Audio volume set to 0%
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207988 Bug ID: 1207988 Summary: [Build 20230206] Upgrade 15.3->TW : Audio volume set to 0% Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3102580/modules/amar ok/steps/23 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation This happens apparently only on 15.3 upgrades (net and DVD based): After upgrading to Tumbleweed, volume is set to 0% which results in amarok failing to play the audio (well, plays at 0% volume, which means we have no output validation) Rerunning the test on snapshot 0205 makes it fail there too - which implies something underlying must have broken openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-15.3-kde@64bit fails in [amarok](https://openqa.opensuse.org/tests/3102580/modules/amarok/steps/23) ## Test suite description ## Reproducible Fails since (at least) Build [20230206](https://openqa.opensuse.org/tests/3101758) ## Expected result Last good: [20230205](https://openqa.opensuse.org/tests/3095375) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207374 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Major -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207374 https://bugzilla.suse.com/show_bug.cgi?id=1207374#c9 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint(a)suse.com --- Comment #9 from Stefan Hundhammer <shundhammer(a)suse.com> --- Michal, thanks for notifying us about this. This probably sounded like a transparent thing to Lee Duncan, handled entirely within the open-iscsi package; but we need to so some things about that in YaST / the inst-sys as well: - make sure that /var/lib/iscsi/* is writable (on the RAM disk) in the inst-sys - When we copy the iscsi setup from the inst-sys to the target at the end of the installation (after installing all the RPMs), copy /var/lib/iscsi/ to /mnt/var/lib/iscsi/, not /etc/iscsi/ to /mnt/etc/iscsi. We'll have to check if more needs to be done. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207374] Cannot set up iscsi targets during installation
by bugzilla_noreply＠suse.com 08 Feb '23

08 Feb '23

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

1 0