July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225633] New: Migration from MicroOS Desktop to Aeon failed on none EFI system
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225633 Bug ID: 1225633 Summary: Migration from MicroOS Desktop to Aeon failed on none EFI system Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875210 --> https://bugzilla.suse.com/attachment.cgi?id=875210&action=edit tik install log file Hey there, was about to migrate one of my MicroOS Desktop installs to Aeon using the Aeon installer image. After it had backed up the old home, installing the new system and moving the home directory back it failed with the error message: "Command /usr/sbin/efibootmgr -o FAILED" I am aware that Aeon does not support none EFI systems. Might it be possible to do a EFI check before installing everything and tell the user? The full log does confirm that EFI is not enabled. It was just my idiocy that I forgot to enable EFI on my old Laptop beforehand. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1223455] New: Power mode does not enter power saver
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223455 Bug ID: 1223455 Summary: Power mode does not enter power saver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: pocketfullofmarbles(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When the battery drops to 20% power-profiles-daemon should automatically enter the powersave mode but this expected behavior does not happen on tumbleweed (gnome), also tested in opensuse tumbleweed live image(gnome) encountered the same problem. Otherwise the gnome power profiles wtih power-profiles-daemon work as expected. My laptops hardware probes if it helps: https://linux-hardware.org/?computer=c3ac730fb235 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227436] openQA did not catch regression https://github.com/openSUSE/snapper/issues/918
by bugzilla_noreply＠suse.com 08 Jul '24

08 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227436 https://bugzilla.suse.com/show_bug.cgi?id=1227436#c1 Karl Mistelberger <karl.mistelberger(a)nefkom.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl.mistelberger(a)nefkom.ne | |t --- Comment #1 from Karl Mistelberger <karl.mistelberger(a)nefkom.net> --- snapper stopped creating pre/post snapshots and dumps core: erlangen:~ # journalctl -b -p3 Jul 08 05:32:09 erlangen systemd-coredump[4538]: [🡕] Process 4536 (snapper-zypp-pl) of user 0 dumped core. Stack trace of thread 4536: #0 0x00007fc52d2949dc __pthread_kill_implementation (libc.so.6 + 0x949dc) #1 0x00007fc52d241176 raise (libc.so.6 + 0x41176) #2 0x00007fc52d228917 abort (libc.so.6 + 0x28917) #3 0x00007fc52d6adc4d n/a (libstdc++.so.6 + 0xadc4d) #4 0x00007fc52d6bf2ec n/a (libstdc++.so.6 + 0xbf2ec) #5 0x00007fc52d6ad7f5 _ZSt9terminatev (libstdc++.so.6 + 0xad7f5) #6 0x00007fc52d6bf578 __cxa_throw (libstdc++.so.6 + 0xbf578) #7 0x000055d955b6b249 n/a (snapper-zypp-plugin + 0x14249) #8 0x000055d955b69535 n/a (snapper-zypp-plugin + 0x12535) #9 0x00007fc52d22a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #10 0x00007fc52d22a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #11 0x000055d955b6b3c5 n/a (snapper-zypp-plugin + 0x143c5) ELF object binary architecture: AMD x86-64 Jul 08 05:32:09 erlangen systemd-coredump[4547]: [🡕] Process 4545 (boot-plugin) of user 0 dumped core. Stack trace of thread 4545: #0 0x00007faa94c949dc __pthread_kill_implementation (libc.so.6 + 0x949dc) #1 0x00007faa94c41176 raise (libc.so.6 + 0x41176) #2 0x00007faa94c28917 abort (libc.so.6 + 0x28917) #3 0x00007faa950adc4d n/a (libstdc++.so.6 + 0xadc4d) #4 0x00007faa950bf2ec n/a (libstdc++.so.6 + 0xbf2ec) #5 0x00007faa950ad7f5 _ZSt9terminatev (libstdc++.so.6 + 0xad7f5) #6 0x00007faa950bf578 __cxa_throw (libstdc++.so.6 + 0xbf578) #7 0x0000559a0366e697 n/a (boot-plugin + 0xc697) #8 0x0000559a0366cf67 n/a (boot-plugin + 0xaf67) #9 0x00007faa94c2a1f0 __libc_start_call_main (libc.so.6 + 0x2a1f0) #10 0x00007faa94c2a2b9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a2b9) #11 0x0000559a0366e725 n/a (boot-plugin + 0xc725) ELF object binary architecture: AMD x86-64 erlangen:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227480] New: Can't use ignition.config.url due to unknown Certificate Authority
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227480 Bug ID: 1227480 Summary: Can't use ignition.config.url due to unknown Certificate Authority Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: bcmjmrth(a)seip.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Build Identifier: No matter what ignition.config.url with https I enter i get this error. Reproducible: Always Steps to Reproduce: 1. Boot MicroOS QEMU image 2. In grub edit boot entry and add "ignition.config.url=https://anything.com" as kernel parameter 3. Enter emergency shell and run journalctl to see it's due to an unknown certifcate Actual Results: "failed to acquire config: unable to fetch ressource in time" Expected Results: Config loads as you would expect -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225784] clang: Please subpackage compiler-rt libraries
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225784 https://bugzilla.suse.com/show_bug.cgi?id=1225784#c6 --- Comment #6 from Daan De Meyer <daan.j.demeyer(a)gmail.com> --- > Why would one need them in a separate package? They shouldn't be needed at runtime, but only when building software, and I think they can only be used with Clang and not GCC. It should be noted that while compiler-rt is a separate subproject upstream, it's also upstream's choice to install it in %{_libdir}/clang. Both are fine with me, I don't mind too much where the static libraries live, as long as the shared libraries are subpackaged. > Instead of $(clang --print-file-name="")lib/linux, better use $(clang -print-runtime-dir). Thank you for the suggestion, I will give that a try. > But it's not so nice that this has to be done manually, or that we need an RPATH at all. The only issue with adding SO numbers is that this is discouraged by our packaging guidelines, so I might just leave them in their directory for now. But this is also kind of against the guidelines, as these are not private libraries, but meant to be used by other applications. So they should probably live in %{_libdir}. Frankly if you did this it would just make my life harder. Every other distro ships these libraries in the private directory so I'd just have to add yet more special casing to deal with openSUSE doing it differently. If you really want to go this route I would suggest discussing this with all the other distribution clang maintainers so this move can be done across distros instead of only in openSUSE. Given the amount of work that would entail, I suggest just following the other distributions here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226823] bluetooth earphones fail
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226823 https://bugzilla.suse.com/show_bug.cgi?id=1226823#c15 Dmitry Markov <werwolf131313(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Flags|needinfo?(werwolf131313@gma | |il.com) | Resolution|--- |FIXED --- Comment #15 from Dmitry Markov <werwolf131313(a)gmail.com> --- (In reply to Antonio Larrosa from comment #14) > Thanks for the confirmation. Dmitry Markov, can you confirm that the update > to wireplumber 0.5.5 fixes the issue for you too? I confirm, I made several test calls, everything works fine -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209053] openssl 3 should fail on certain hash algorithms on FIPS
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1209053 https://bugzilla.suse.com/show_bug.cgi?id=1209053#c15 --- Comment #15 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- In bsc#1209037, the test failed because it checks for any of these strings: /disabled for fips|disabled for FIPS|unknown option|Unknown digest|dgst: Unrecognized flag/ These strings were used in the past openssl versions but I think capturing the error output directly from openssl would be the best option as suggested by Marcus, probably add :unsupported:. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227462] Stressapptest (Package): Process Error: Sat::Initialize() failed
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227462 https://bugzilla.suse.com/show_bug.cgi?id=1227462#c1 --- Comment #1 from Michal Suchanek <msuchanek(a)suse.com> --- (In reply to Bernhard JoRo from comment #0) > 2024/07/04-14:42:44(CEST) Log: Command line option '-A' bypasses this error. Fedora is using an older version. If you can run theirs this is likely an upstream regression. Please report the issue upstream if you do not like the provided workaround. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209053] openssl 3 should fail on certain hash algorithms on FIPS
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1209053 https://bugzilla.suse.com/show_bug.cgi?id=1209053#c14 Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #14 from Pedro Monreal Gonzalez <pmonrealgonzalez(a)suse.com> --- One more note, SHA-1 can still be used in FIPS mode but SHA-1 is not allowed anymore in FIPS 186-5 signature verification operations. So, we will force disable SHA-1 signature verification in the fips provider.. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227469] New: lm_sensors out of date, please update to 3.6.0
by bugzilla_noreply＠suse.com 07 Jul '24

07 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227469 Bug ID: 1227469 Summary: lm_sensors out of date, please update to 3.6.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- My recent computer is not properly supported since it has an nct6798 temperature sensor, which is supported by 3.6.0. 3.6.0 has been out for over five years, so it seems about time to upgrade lm_sensors from 3.5.0 to 3.6.0. I get constant warnings due to this. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 2