April 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210182] New: python-social-auth-core fails to build in Leap 15.5
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210182 Bug ID: 1210182 Summary: python-social-auth-core fails to build in Leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello package python-social-auth-core currently fails to build in Leap 15.5 We would like to have it fixed prior to the RC build in April. See details at https://en.opensuse.org/openSUSE:Roadmap here's the build log https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 45s] -- Docs: https://docs.pytest.org/en/latest/warnings.html [ 45s] =========================== short test summary info ============================ [ 45s] ERROR social_core/tests/backends/test_azuread_b2c.py - AttributeError: 'str' ... [ 45s] ERROR social_core/tests/backends/test_keycloak.py - AttributeError: 'str' obj... [ 45s] !!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!! [ 45s] ================ 269 deselected, 7 warnings, 2 errors in 2.90s ================= [ 45s] error: Bad exit status from /var/tmp/rpm-tmp.biuK6A (%check) [ 45s] [ 45s] [ 45s] RPM build errors: [ 45s] Bad exit status from /var/tmp/rpm-tmp.biuK6A (%check) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1126900] New: health-checker: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system.
by bugzilla_noreply＠novell.com 06 Apr '23

06 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1126900 Bug ID: 1126900 Summary: health-checker: grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: iforster(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From a health-checker run: Clearing GRUB flag + grub2-editenv - set health_checker_flag=0 grub2-editenv: error: cannot open `/boot/grub2/grubenv': Read-only file system. Starting health check -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c19 --- Comment #19 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Takashi Iwai from comment #18) > Yeah, we should definitely check it (although there can be a fear of kABI > breakage...) I backported the series to users/pjakobsson/SLE15-SP5/bsc1206843 And building it at: home:patrikjakobsson:bsc1206843 Let's hope it doesn't break kabi too badly. > > Also I found 6.1.x stable gained lots of fixes for amdgpu, and we seem > missing them. I'll try to backport them, too. Great. Yes it looks like there is additional patches needed on top of that series. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c18 --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- Yeah, we should definitely check it (although there can be a fear of kABI breakage...) Also I found 6.1.x stable gained lots of fixes for amdgpu, and we seem missing them. I'll try to backport them, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194160] New: texlive-tex-gyre-fonts: Unknown Type 1 weight "BoldItalic"
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1194160 Bug ID: 1194160 Summary: texlive-tex-gyre-fonts: Unknown Type 1 weight "BoldItalic" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Upgrading from Leap 15.2 to 15.3 via "zypper dup" showed this error message: (4328/5706) Installing: texlive-tex-gyre-fonts-2017.134.2.004svn18651-5.18.noarch .....[done] Additional rpm output: Unknown Type 1 weight "BoldItalic" Couldn't determine weight for qcsbi.pfb -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1204746] New: texlive-scheme-medium missing english documentation for fancyhdr
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1204746 Bug ID: 1204746 Summary: texlive-scheme-medium missing english documentation for fancyhdr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: lukasstraub2(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When installing texlive-scheme-medium, it includes documentation, but for example for fancyhdr only the italian docs are included, not the english ones. i.e. only texlive-fancyhdr-it is installed, not texlive-fancyhdr-doc. I suspect this is not the only package that has this problem. I expect at least english documentation to be installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1206843] Lenovo T14s Gen3 AMD resume from sleep broken
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1206843 https://bugzilla.suse.com/show_bug.cgi?id=1206843#c17 Patrik Jakobsson <patrik.jakobsson(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(patrik.jakobsson@ | |suse.com) | --- Comment #17 from Patrik Jakobsson <patrik.jakobsson(a)suse.com> --- (In reply to Takashi Iwai from comment #11) > There seems still some issue with MST. > Now we received a Lenovo dock and I've tested T14s Gen 3 with the Lenovo > dock. > > Both S3 and S4 work fine as long as no dock is connected or the dock is kept > connected while suspend/resume (although we see some spurious kernel > WARNING). > > But when a dock is connected at S3/S4 and gets removed before the resume: > the machine can be resumed on the laptop screen, but the monitor on the dock > can't be enabled after re-plugging the dock. > > (Actually, the first replug doesn't detect the monitor at all. When you > replug twice, it'll probe the monitor, but the mode switching fails.) > > On 6.1.12 and 6.2.9 kernels, the situation is better, the monitor works > again after the second replug. > > Patrik, on which kernel version is the DRM code of our SP5 based? > I'm suspecting we're scratching the bug in the past upstream: > https://gitlab.freedesktop.org/drm/amd/-/issues/2171 This sounds familiar. I updated DRM to v6.0 but AMDGPU to v6.1. While doing so I had to exclude a series of DP-MST refactoring from Lyude Paul [1]. Perhaps this is a series that is needed? IIRC these patches also affected the extra DG2 patches I had to add to i915. [1] https://patchwork.freedesktop.org/series/104844/#rev5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208289] New: [distrobox] cannot enter a container
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1208289 Bug ID: 1208289 Summary: [distrobox] cannot enter a container Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Just run (distrobox is 1.4.2.1 from TW): $ distrobox create paperino $ distrobox enter paperino and in the podman logs I found this piece of wisdom: Resolving package dependencies... Problem: the to be installed util-linux-systemd-2.38.1-6.1.x86_64 requires 'which', but this requirement cannot be provided not installable providers: which-2.21-5.7.i586[repo-oss] which-2.21-5.7.x86_64[repo-oss] Solution 1: deinstallation of busybox-which-1.36.0-26.1.noarch Solution 2: do not install util-linux-systemd-2.38.1-6.1.x86_64 Solution 3: break util-linux-systemd-2.38.1-6.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c Error: An error occurred Obviously entering errored in ��Installing basic packages��. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1199871] Rootless podman logging broken by default
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1199871 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcepl(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210163] New: Kernel panic on boot with kernel 6.2.9-1
by bugzilla_noreply＠suse.com 06 Apr '23

06 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210163 Bug ID: 1210163 Summary: Kernel panic on boot with kernel 6.2.9-1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: rodney.baker(a)iinet.net.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading to the latest 20230402 snapshot I get a kernel panic at the start of the boot process when booting kernel 6.2.9-1-default. Bootloader kernel command line: idewait=10 plymouth.enable=0 splash quiet showopts nvidia-drm.modeset=1 elevator=cfq Crash details: Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,5) CPU:9 PID:1 Comm: Swapper/0 Not tainted 6.2.9-1-default #1 openSUSE Tumbleweed 72246ebc6bb73a9bec193bedaaaba1392d6fb332 Hardware name: System manufacturer System Product Name/PRIME X299-A, BIOS 3501 07/13/2021 Call Trace: <TASK> dump_stack_lvl+0x23/0x60 panic=0x346/0x350 mount_block_root=-x1f7/0x280 prepare_namespace=0xec/0x170 kernel_init_freeable= 0x411/0x450 ? __pfx_kernel_init=0x10/0x10 kernel_init=016/0x1c0 ret_from_fork=0x29/0x50 </TASK> Kernel Offset: 0x31e00000 from 0xffffffff81000000 (relocation range 0xffffffff80000000-0xffffffffbfffffff) Rebooting in 90 seconds.. The system is booting of a Samsung EVO 850 SATA SSD - there are no NVMe drives in the system. It boots fine with kernel 6.2.6-1-default. -- You are receiving this mail because: You are on the CC list for the bug.

1 3