October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1231346] Virtualbox guest won't start but crashes with NS_ERROR_FAILURE (0X80004005)
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231346 https://bugzilla.suse.com/show_bug.cgi?id=1231346#c2 --- Comment #2 from Jan Engelhardt <jengelh(a)inai.de> --- https://forums.virtualbox.org/viewtopic.php?t=112370 Chances are whoever sees the error is running an outdated extension pack. The extpack ought to be upgraded alongside VirtualBox upgrades, i.e. you should not run extpack-6.x with vbox-7.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231346] Virtualbox guest won't start but crashes with NS_ERROR_FAILURE (0X80004005)
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231346 https://bugzilla.suse.com/show_bug.cgi?id=1231346#c1 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Jan Engelhardt <jengelh(a)inai.de> --- Cannot reproduce. libpthread.so is not supposed to be in /usr/lib/virtualbox. There is but one reason why VBoxSVC might search for a .so file in /usr/lib/virtualbox: There was no "libpthread.so" in any system path that matched the current architecture. But this is to be expected, too, because.. 1. libpthread.so is a hint file and for software development scenarios only. Its presence is *not guaranteed* on normal systems. *No program* should ever attempt to dlopen "libpthread.so", but *must* use "libpthread.so.0". 2. glibc>=2.34 (or thereabouts) has abolished the libpthread.so hint file altogether. (The same goes for libdl.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1230673] perl: y2038: 32-bit builds use 4-byte time_t
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1230673 https://bugzilla.suse.com/show_bug.cgi?id=1230673#c12 --- Comment #12 from Michael Schröder <mls(a)suse.com> --- Yes, that's also what ImageMagick does. I also checked net-snmp, they overwrite LD_RUN_PATH when doing the make call which is somewhat fragile. We should have some way to do that in our perl package like redhat has, but alas... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226676] Installation: kdump reports an error if systemd-boot has been selected for bootloader
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1226676 https://bugzilla.suse.com/show_bug.cgi?id=1226676#c23 --- Comment #23 from Alberto Planas Dominguez <aplanas(a)suse.com> --- Can the new update-bootloader be tested? This should be fixed after https://github.com/openSUSE/perl-bootloader/pull/173 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228864] New: per-Bootloader can break systemd-boot installations dropping shim.efi
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228864 Bug ID: 1228864 Summary: per-Bootloader can break systemd-boot installations dropping shim.efi Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: screening-team-bugs(a)suse.de Reporter: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When calling pbl.sh --install to install the bootloader in a systemd-boot it will drop the shim.efi, breaking secure boot and predictions in systemd-boot systems. Ideally in BLS systems it should call for now 'sdbootutil install' or 'sdbootutil update', as it will take care of keeping the shim.efi and renaming the bootloader as grub.efi, so secure boot is enabled in both systems -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1228862] New: When sdbootuil is used, transactional-update bootloader will address only the grub2 case
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1228862 Bug ID: 1228862 Summary: When sdbootuil is used, transactional-update bootloader will address only the grub2 case Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: lubos.kocman(a)suse.com Reporter: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When sdbootutil is used, the bootloader can be systemd-boot or grub2 with the BLS patches. `transactional-update bootloader` should be aware and avoid the changes in the grub configuration file, and the boot loader installation via pbl.sh --install. pbl.sh is not aware of sdbootutil for bootloader installation and will drop the shim.efi if systemd-boot is used -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1231346] Virtualbox guest won't start but crashes with NS_ERROR_FAILURE (0X80004005)
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231346 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |jengelh(a)inai.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231341] missing vbox module for current kernel-default
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231341 https://bugzilla.suse.com/show_bug.cgi?id=1231341#c4 --- Comment #4 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- You are right, my fault. There is an unsolvable: https://build.opensuse.org/package/show/Kernel:stable:Backport:KMP/virtualb… So the Repo might be out of sync. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231139] [SELinux] systemd-cryptsetup generator cannot read /etc/crypttab
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

https://bugzilla.suse.com/show_bug.cgi?id=1231139 https://bugzilla.suse.com/show_bug.cgi?id=1231139#c5 --- Comment #5 from Alberto Planas Dominguez <aplanas(a)suse.com> --- I am trying to get the pcrlock.json error but is taking some time. For now maybe makes more sense to focus on the generator error when accessing /etc/crypttab, as for this one I have the AVC -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1231139] [SELinux] systemd-cryptsetup generator cannot read /etc/crypttab
by bugzilla_noreply＠suse.com 07 Oct '24

07 Oct '24

1 0