August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228175] New: ghc/haskell verification issues
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228175 Bug ID: 1228175 Summary: ghc/haskell verification issues Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: peter.simons(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- [working on reproducible builds for openSUSE] Since several weeks, I get verification issues again for binaries built by ghc, though this was working before. Local test-builds still produce bit-identical results, that match with my verification build, but not with the official build. https://rb.zq1.de/compare.factory/diffs/xmobar-strings-diff.txt shows some ordering issue of a list of .so files. Where/How is that created? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228820] sdbootutil needs support for showing NVIndex recovery key since systemd 256
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228820 https://bugzilla.suse.com/show_bug.cgi?id=1228820#c3 --- Comment #3 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Andrei Borzenkov from comment #2) > (In reply to Alberto Planas Dominguez from comment #1) > > I can add this, but since 2 months ago the LUKS2 recovery key is also used > > as the NVIndex policy PIN: > > > > OK, missed this. > > > > > https://en.opensuse.org/Portal:MicroOS/FDE#Re-enrollment > > sdbootutil update-predictions is using the current value of > %user:cryptenroll but it does not exist after reboot. Is one option of three: the keyring, the PIN envvar, and --ask-pin. They are in the linked doc ... In fact the example is PIN=... sdbootutil update-predictions > It can only exist > after running cryptenroll. So, when following the procedure described there > new random PIN will be created, Uhmm ... no. Is just the opposite. The key needs to be present before calling systemd-cryptenroll, that will be used. The PIN is not replaced. > so we are back on square one. Moreover, the > content of %user:cryptenroll key will not be recovery PIN (which was never > requested), it will be the content of user LUKS2 password. Sure, user may > enter LUKS recovery PIN here, but nothing tells it. It is used by sdbootutil to extract it from the keyring, and use it later here: https://github.com/openSUSE/sdbootutil/commit/35f3e34684b12e227792dacd60cae… > 10:~ # keyctl id '%user:cryptenroll' > 575532476 > 10:~ # keyctl pipe 575532476 > P@ssw0rd > 10:~ # > > But in this case it is too later anyway because sdbootutil > update-predictions was run before cryptenroll and so generated random PIN. That does not make much sense to me. The new PIN is generated when you remove the policy and the internal state of the TPM. Then the make-policy will create a new PIN, but this never happens in the linked code. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228824] libbotan 2 > 3 switch breaks dependencies?
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228824 https://bugzilla.suse.com/show_bug.cgi?id=1228824#c9 --- Comment #9 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to Andreas Stieger from comment #5) > Packages having Botan 2 as explicit build requirement: > rehex https://build.opensuse.org/request/show/1191453 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228826] New: On MicroOS "btrfs qgroup clear-stale" fails in snapper-cleanup.service
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228826 Bug ID: 1228826 Summary: On MicroOS "btrfs qgroup clear-stale" fails in snapper-cleanup.service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- 10:~ # cat /etc/os-release NAME="openSUSE MicroOS" # VERSION="20240801" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed microos sl-micro" VERSION_ID="20240801" 10:~ # systemctl status snapper-cleanup.service ○ snapper-cleanup.service - Daily Cleanup of Snapper Snapshots Loaded: loaded (/usr/lib/systemd/system/snapper-cleanup.service; static) Active: inactive (dead) since Sat 2024-08-03 18:39:03 MSK; 10min ago Duration: 3.615s Invocation: 79238e84e1b24ee59f75e47efa2c18a4 TriggeredBy: ● snapper-cleanup.timer Docs: man:snapper(8) man:snapper-configs(5) Process: 1390 ExecStart=/usr/lib/snapper/systemd-helper --cleanup (code=exited, status=0/S> Main PID: 1390 (code=exited, status=0/SUCCESS) CPU: 73ms Aug 03 18:38:59 10.0.2.15 systemd[1]: Started Daily Cleanup of Snapper Snapshots. Aug 03 18:39:00 10.0.2.15 systemd-helper[1390]: Running cleanup for 'root'. Aug 03 18:39:00 10.0.2.15 systemd-helper[1390]: Running number cleanup for 'root'. Aug 03 18:39:03 10.0.2.15 systemd-helper[1390]: Running timeline cleanup for 'root'. Aug 03 18:39:03 10.0.2.15 systemd-helper[1390]: Running empty-pre-post cleanup for 'root'. Aug 03 18:39:03 10.0.2.15 systemd-helper[1390]: Running 'btrfs qgroup clear-stale /'. Aug 03 18:39:03 10.0.2.15 systemd-helper[1390]: 'btrfs qgroup clear-stale /' failed. Aug 03 18:39:03 10.0.2.15 systemd[1]: snapper-cleanup.service: Deactivated successfully. 10:~ # `btrfs qgroup clear-stale` failed due to read-only root. From the strace: 1435 ioctl(3, BTRFS_IOC_QGROUP_CREATE, {create=0, qgroupid=277}) = -1 EROFS (Read-only file system) 1435 write(2, "ERROR: ", 7) = 7 1435 write(2, "failed to delete qgroup 0/277", 29) = 29 1435 write(2, "\n", 1) = 1 1435 write(1, "Delete stale qgroup 0/291\n", 26) = 26 Using writable subvolume on the same filesystem succeeds 10:~ # btrfs qgroup clear-stale /var Delete stale qgroup 0/258 Delete stale qgroup 0/265 Delete stale qgroup 0/266 Delete stale qgroup 0/267 Delete stale qgroup 0/268 Delete stale qgroup 0/269 Delete stale qgroup 0/270 Delete stale qgroup 0/271 Delete stale qgroup 0/272 Delete stale qgroup 0/273 Delete stale qgroup 0/274 Delete stale qgroup 0/275 Delete stale qgroup 0/276 Delete stale qgroup 0/277 Delete stale qgroup 0/291 10:~ # The snapper-cleanup.timer is enabled by default. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228824] libbotan 2 > 3 switch breaks dependencies?
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228824 https://bugzilla.suse.com/show_bug.cgi?id=1228824#c7 --- Comment #7 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- No, you are talking about different points in time here. Please wait a bit, the previously planned botan 2 transitional package will arrive shortly, so will a keepassxc built against botan 3 on Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228824] libbotan 2 > 3 switch breaks dependencies?
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228824 https://bugzilla.suse.com/show_bug.cgi?id=1228824#c5 --- Comment #5 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Packages having Botan 2 as explicit build requirement: biboumi keepassxc https://build.opensuse.org/request/show/1191430 rehex rnp https://build.opensuse.org/request/show/1191411 ueberzugpp https://build.opensuse.org/request/show/1191432 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224457] Kernel: Sound: AMD cpu with graphics + ASUS motherboard with ALC 887
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1224457 https://bugzilla.suse.com/show_bug.cgi?id=1224457#c68 --- Comment #68 from Takashi Iwai <tiwai(a)suse.com> --- Ah, it's a bad news for you, but it explains why all attempts fail so far. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228759] Partial systemd installation before the kernel gets installed
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228759 https://bugzilla.suse.com/show_bug.cgi?id=1228759#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- So neither kernel nor suse-module-tools needs an explicit Requires of udev. If so, Alberto's change in comment 14 should suffice. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228824] libbotan 2 > 3 switch breaks dependencies?
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228824 https://bugzilla.suse.com/show_bug.cgi?id=1228824#c4 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Also moving keepassxc to Botan 3: https://build.opensuse.org/request/show/1191430 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228659] Snapshot 20240730 - unbootable after transactional-update dup
by bugzilla_noreply＠suse.com 03 Aug '24

03 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228659 https://bugzilla.suse.com/show_bug.cgi?id=1228659#c37 --- Comment #37 from Andrei Borzenkov <arvidjaar(a)gmail.com> --- (In reply to Alberto Planas Dominguez from comment #32) > My current mental model > puts the issue in suse-module-tools and sdbootutil side, but I can be very > wrong here too. If you look at the log provided earlier (23/41) Installing: libinput-udev-1.26.0-1.1.x86_64 [.. /usr/bin/udevadm: error while loading shared libraries: libsystemd-shared-255.so: cannot open shared object file: No such file or directory done] which is unrelated to either kernel or sdbootutil or suse-module-tools. -- You are receiving this mail because: You are on the CC list for the bug.

1 0