October 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1215337] python-onnx does not build s390x
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215337 https://bugzilla.suse.com/show_bug.cgi?id=1215337#c3 --- Comment #3 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Hi Berthold, I can forward this bug report only with the build/error log. Can you attach it, please? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208766] Kernel 6.2.1 does not suspend/hibernate anymore for AMD Ryzen 7 Pro
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1208766 https://bugzilla.suse.com/show_bug.cgi?id=1208766#c17 --- Comment #17 from Frank Krüger <fkrueger(a)mailbox.org> --- (In reply to Joey Lee from comment #12) > (In reply to Joey Lee from comment #3) > > After the Tumbleweed kernel be locked down, the only way for using > > hibernation is disabled EFI secure boot. User can use UEFI firmware UI to > > disable secure boot, or using mokutil to disable validation from shim layer: > > > > mokutil --disable-validation > > > > > > On the other hand, upstream is working on a solution with TPM2: > > > > [PATCH v5 00/11] Encrypted Hibernation > > https://lkml.org/lkml/2022/11/11/1229 > > Evan's patch set is developed to v5. Then he got suggestions about the > security of PCR23. His idea is following: > > [PATCH v5 01/11] tpm: Add support for in-kernel resetting of PCRs Evan Green > https://lore.kernel.org/lkml/20221111151451.v5.7. > Ifff11e11797a1bde0297577ecb2f7ebb3f9e2b04@changeid/T/ > #m77aa6045cae41786c7d831ca7a99f519961e1891 Is there a solution within sight regarding hibernation with the lockdown kernel, when secure boot is enabled? Thx. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215826] New: kernel-default-6.5.4 won't boot; can't activate swap
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215826 Bug ID: 1215826 Summary: kernel-default-6.5.4 won't boot; can't activate swap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869836 --> https://bugzilla.suse.com/attachment.cgi?id=869836&action=edit Output of hwinfo (with 6.4.12) I upgraded from Tumbleweed 20230908 to 20230921, which included an upgrade from kernel-default-6.4.12 to kernel-default-6.5.4. The new kernel has problems booting or resuming from suspend. In particular, when booting, about half the time the kernel is unable to activate the swap device. The last message printed to the console is "a start job is running for /dev/sda2" (the device in question being my swap partition) and a timer that counts up. I've let it run for as long as 10 hours but it never finishes. Resuming from suspend also doesn't work. In this case the computer simply locks up or powers off. (I haven't tested hibernate.) I had a similar problem (only with resuming from suspend, not with activating swap space) with kernel-default-5.19.1; not sure if this is related. See Bug 1202571. Downgrading to the 6.4.12 kernel works around the issue. I am attaching the output of hwinfo (using the 6.4.12 kernel). -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215826] kernel-default-6.5.4 won't boot; can't activate swap
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215826 https://bugzilla.suse.com/show_bug.cgi?id=1215826#c2 --- Comment #2 from Tristan Miller <psychonaut(a)nothingisreal.com> --- (In reply to Felix Miata from comment #1) > Something to try: Remove resume=/dev/sda2 from /etc/default/grub and > /boot/grub2/grub.cfg entirely, or replacing it with resume=UUID=<swapUUID> > or resume=LABEL=<swapLABEL> (using the actual UUID or LABEL from lsblk -f or > blkid). To test whether this is the right track, strike the E key at the > Grub menu and change resume=/dev/sda2 to noresume before proceeding with > boot. Noresume means what it spells, but it should boot straight away if I'm > right. Yes, using noresume or resume=UUID=<swapUUID> seems to solve the problem. I noticed when looking up the UUID of the swap device that it was always /dev/sdb2 when booting from the 6.4.12 kernel, whereas when booting from the 6.5.4 kernel it was sometimes /dev/sda2 and sometimes /dev/sdb2. So I think the real problem here is that the 6.5.4 kernel doesn't assign device names in the same consistent manner than 6.4.12 did, so you can't rely on these names in the bootloader. I think that nowadays a fresh install of Tumbleweed will always use the device's UUID, but my system was first installed back in 2014 and so was still using the old /dev/sdXY-style identifiers. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215845] displaymanager.service does not restart on failure
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215845 https://bugzilla.suse.com/show_bug.cgi?id=1215845#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS CC| |seife(a)novell.slipkontur.de Flags| |needinfo?(seife(a)novell.slip | |kontur.de) --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. Killing it once should not terminate the display manager. Could you please check this behaviour with a displaymanager like xdm or gdm? I know that these are adjusted to terminate themselves if X crashes 3 times in a row in a short amount of time. So you have a chance to get into the system on Linux console. But not after killing X once ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215774] New: during installation of pitivi you run into librosa requirements which cannot be fullfilled because a dependency is missing
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215774 Bug ID: 1215774 Summary: during installation of pitivi you run into librosa requirements which cannot be fullfilled because a dependency is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: stakanov(a)disroot.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Problem: nothing provides '(python311-pooch >= 1.0 with python311-pooch < > 1.7)' needed by the to be installed python311-librosa-0.10.1-1.4.noarch > Solution 1: do not install pitivi-2023.03-1.3.x86_64 > Solution 2: break python311-librosa-0.10.1-1.4.noarch by ignoring some of its > dependencies the issue for me is minor and mainly due to the fact that I do not know if the functionality would be afflicted if I ignore. But other users may appreciate if this will be fixed (apparently the reason explained by a user (arvidjaar(a)gmail.com) is that "librosa failed to build against current pooch". So maybe this will be corrected automatically during future updates.) Feel free to indicate one solution of the above (one or two), so that other users may find it and know what to do and how to proceed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1211546] Nautilus Preview Sushi not working/showing out of the Box on fresh TW install
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1211546 https://bugzilla.suse.com/show_bug.cgi?id=1211546#c7 Bjørn Lie <bjorn.lie(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #7 from Bjørn Lie <bjorn.lie(a)gmail.com> --- This is resolved, so closing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215741] New: Warning/error message "Transport endpoint is not connected" in journald after cron job run by root
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215741 Bug ID: 1215741 Summary: Warning/error message "Transport endpoint is not connected" in journald after cron job run by root Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: claude.diderich(a)sigmadream.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a cron job owned by root finishes, a warning + failure message is logged to the journal file: Sep 27 00:15:12 jasper systemd[1]: user-runtime-dir(a)0.service: Failed with result 'exit-code'. Sep 27 00:15:12 jasper systemd[1]: user-runtime-dir(a)0.service: Control process exited, code=exited, status=1/FAILURE Sep 27 00:15:12 jasper systemd-user-runtime-dir[40960]: Failed to remove runtime directory /run/user/0 (after unmounting): Transport endpoint is not connected Sep 27 00:15:01 jasper CRON[40871]: pam_unix(crond:session): session closed for user root Sep 27 00:15:01 jasper CRON[40871]: (root) CMDEND (/usr/lib/cron/run-crons >/dev/null 2>&1) Sep 27 00:15:01 jasper CRON[40912]: (root) CMD (/usr/lib/cron/run-crons >/dev/null 2>&1) The cron job is executed correctly. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1215436] Unable to boot kernels 6.5.2 or 6.5.3 unless acpi=noirq specified
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215436 https://bugzilla.suse.com/show_bug.cgi?id=1215436#c35 --- Comment #35 from Stuart Rogers <stuart(a)stella-maris.org.uk> --- My issue is that any kernel after 6.4.12 fails unless I blacklist firewire. Now at some point in kernel 6.5.x a fix was applied which stopped this working. So I need help to determine what the change was and what in that change was causing it to fail so completely that the system rebooted. If I can get some assistance to get that far and it turns out to be an issue with my hardware/BIOS I can take it up with MSI who make my motherboard. I stress that up to and including 6.4.12 I had no issues with it at all. I do not have the information or experience to move this further bisecting the kernel without some help from someone with the relevant knowledge of the fixes etc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215849] New: ghostwriter fails to start
by bugzilla_noreply＠suse.com 01 Oct '23

01 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215849 Bug ID: 1215849 Summary: ghostwriter fails to start 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- > $ ghostwriter SOMEFILE.md > QFontDatabase: Must construct a QGuiApplication before accessing QFontDatabase > [1] 8613 IOT instruction (core dumped) ghostwriter SOMEFILE.md I know that ghostwriter is broken now for some time (weeks), it was just today that I looked into what is broken. -- You are receiving this mail because: You are on the CC list for the bug.

1 0