July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201120] u-boot built on Leap does not include ATF
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201120 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1201204 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201145] New: TW 20220702: kstars does not start
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201145 Bug ID: 1201145 Summary: TW 20220702: kstars does not start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Mathias.Homann(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have TW 20220702 installed, kstars is not starting: mathias@mio:~> kstars kstars: symbol lookup error: kstars: undefined symbol: _ZN7SSolver10Parameters14convertFromMapE4QMapI7QString8QVariantE mathias@mio:~> tumbleweed status latest : 20220702 target : 20220702 installed: 20220702 mathias@mio:~> zypper se -si kstars Repository-Daten werden geladen... Installierte Pakete werden gelesen... S | Name | Type | Version | Arch | Repository ---+-------------+-------+-----------+--------+-------------------------- i+ | kstars | Paket | 3.5.9-1.2 | x86_64 | download.opensuse.org-oss i | kstars-lang | Paket | 3.5.9-1.2 | noarch | download.opensuse.org-oss mathias@mio:~> -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1201066] kernel upgrade fails with Failed to enroll new keys
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201066 https://bugzilla.suse.com/show_bug.cgi?id=1201066#c3 --- Comment #3 from Darragh O'Reilly <doreilly(a)suse.com> --- (In reply to Marcus Meissner from comment #2) > try perhaps: > > mokutil --import /etc/uefi/certs/1F673297.crt --root-pw --ignore-keyring localhost:~ # mokutil --import /etc/uefi/certs/1F673297.crt --root-pw --ignore-keyring Failed to enroll new keys localhost:~ # echo $? 255 localhost:~ # mokutil --test-key /etc/uefi/certs/1F673297.crt /etc/uefi/certs/1F673297.crt is already in the built-in trusted keyring localhost:~ # mokutil --sb-state SecureBoot disabled Platform is in Setup Mode -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201197] New: Virtual box fails to start: /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0'
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201197 Bug ID: 1201197 Summary: Virtual box fails to start: /usr/lib/virtualbox/VMMR0.r0: Unable to locate imported symbol 'SUPR0FpuBegin' for module 'VMMR0.r0' Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: martin.jacobs(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859996 --> http://bugzilla.opensuse.org/attachment.cgi?id=859996&action=edit Start of virtual box instance. I do see this error since upgrade to virtial box packages 6.1.34. File VMMR0.r0 belongs to package virtualbox-6.1.34-lp153.2.30.1.x86_64 All virtual box instances are affected. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1201120] u-boot built on Leap does not include ATF
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201120 http://bugzilla.opensuse.org/show_bug.cgi?id=1201120#c1 --- Comment #1 from Michal Suchanek <msuchanek(a)suse.com> --- ATF is required to boot Linux on rk3399 It is possibly required on other hardware as well but I do not have the hardware to test. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201198] New: /etc/sysconfig/irqbalance should be migrated to use IRQBALANCE_BANNED_CPULIST
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201198 Bug ID: 1201198 Summary: /etc/sysconfig/irqbalance should be migrated to use IRQBALANCE_BANNED_CPULIST Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: grasland(a)lal.in2p3.fr QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The IRQBALANCE_BANNED_CPUS environment variable is being deprecated (and for good reasons, that hexadecimal binary mask syntax was awful) in favor of a IRQBALANCE_BANNED_CPULIST environment variable that uses a more standard cpu list syntax (comma-separated numbers + dashes for ranges). As a consequence, YaST/sysconfig irqbalance configuration should stop using IRQBALANCE_BANNED_CPUS and migrate to IRQBALANCE_BANNED_CPULIST instead. Source : https://github.com/Irqbalance/irqbalance/blob/c1cbd89fa44bc8a5653fd23e88bcd… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201194] New: apulse: too many Provides symbols
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201194 Bug ID: 1201194 Summary: apulse: too many Provides symbols Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i586 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: sor.alexei(a)meowr.ru Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- # rpm -q --provides apulse.x86_64 apulse = 0.1.13-2.11 apulse(x86-64) = 0.1.13-2.11 config(apulse) = 0.1.13-2.11 # rpm -q --provides apulse-32bit.x86_64 apulse-32bit = 0.1.13-2.11 apulse-32bit(x86-32) = 0.1.13-2.11 libpulse-mainloop-glib.so.0 libpulse-mainloop-glib.so.0(PULSE_0) libpulse-simple.so.0 libpulse-simple.so.0(PULSE_0) libpulse.so.0 libpulse.so.0(PULSE_0) The .so files in apulse and apulse-32bit seem to be LD_PRELOAD-only modules for use with the /usr/bin/apulse wrapper. I think apulse-32bit should not have these provides, mirroring the case of apulse. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201066] kernel upgrade fails with Failed to enroll new keys
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201066 https://bugzilla.suse.com/show_bug.cgi?id=1201066#c2 --- Comment #2 from Marcus Meissner <meissner(a)suse.com> --- The shim task is only to block the old key via a deny list. The enrollment should work though, although I am not 100% sure that this works on Arm64. would be nice to run this mokutil stand alone. try perhaps: mokutil --import /etc/uefi/certs/1F673297.crt --root-pw --ignore-keyring -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201066] kernel upgrade fails with Failed to enroll new keys
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201066 https://bugzilla.suse.com/show_bug.cgi?id=1201066#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- Hmm, isn't shim updated together for the new cert? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200965] Intel Skylake: iris driver mistakenly been used (Dell Latitude 7480)
by bugzilla_noreply＠suse.com 04 Jul '22

04 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200965 https://bugzilla.suse.com/show_bug.cgi?id=1200965#c10 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #10 from Stefan Dirsch <sndirsch(a)suse.com> --- Closing as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0