August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228855] network manager sstp not work
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228855 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fabian(a)ritter-vogt.de |os.gnome.maintainers@gmail. | |com CC| |fvogt(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1187209] podman uses wrong uid when changing user with su
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1187209 https://bugzilla.suse.com/show_bug.cgi?id=1187209#c6 --- Comment #6 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- This is expected behavior in Podman. Taken from [1]: Podman expects a valid login session for the `rootless+cgroupv2` use-case. Podman execution is expected to fail if the login session is not present. In most cases, podman will figure out a solution on its own but if `XDG_RUNTIME_DIR` is pointing to a path that is not writable execution will most likely fail. Typical scenarios of such cases are seen when users are trying to use Podman with `su - <user> -c '<podman-command>'`, or `sudo -l` and badly configured systemd session. Execute Podman via systemd-run that will first start a systemd login session: > $ sudo systemd-run --machine=username@ --quiet --user --collect --pipe --wait podman run --rm docker.io/library/alpine echo hello Start an interactive shell in a systemd login session with the command machinectl and then run Podman: > $ sudo -i > # machinectl shell username@ > Connected to the local host. Press ^] three times within 1s to exit session. > $ podman run --rm docker.io/library/alpine echo hello Start a new systemd login session by logging in with ssh and then run Podman: > ssh <username>@localhost Before invoking Podman command create a valid login session for your rootless user: > loginctl enable-linger <username> [1]: https://github.com/containers/podman/blob/7e469996b19752e24c69c43c44919ca7b… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228855] network manager sstp not work
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228855 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |fabian(a)ritter-vogt.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228859] New: Can not update TPM 2.0 predictions with nvidia drivers installed
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228859 Bug ID: 1228859 Summary: Can not update TPM 2.0 predictions with nvidia drivers installed Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: vortex(a)z-ray.de QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello there this came to my attention during boo#1224773 and as it list a slightly different issue I felt like opening up a new bug for this one even though it might be some what related. After manually fixing the nvidia driver installation on Aeon RC3 as described in the other bug report: - Manually generating a new initrd file using tu initrd - Moving the initrd file to /boot/efi/opensuse-aeon/KERNEL_VERSION/ - Fixing the latest boot entry to point towards the new initrd The user will (obviously) promoted to in put the TPM recovery key on every boot. According to the Aeon wiki (https://en.opensuse.org/Portal:Aeon/Encryption#Remeasuring_Boot_Integrity) this should be fixable by simply running: > sudo sdbootutil update-predictions > > WARNING:esys:src/tss2-esys/api/Esys_PolicyOR.c:286:Esys_PolicyOR_Finish() Received TPM Error > ERROR:esys:src/tss2-esys/api/Esys_PolicyOR.c:100:Esys_PolicyOR() Esys Finish ErrorCode (0x000001c4) > Failed to add OR policy to TPM: tpm:parameter(1):value is out of range or is not correct for the context > Failed to submit super PCR policy: State not recoverable > Error creating the policy! > Please, provide the recovery PIN to register the new policy > NVIndex policy created But that doesn't work. Then I tried: > sudo sdbootutil --ask-pin update-predictions > > Recovery PIN: WARNING:esys:src/tss2-esys/api/Esys_NV_Write.c:310:Esys_NV_Write_Finish() Received TPM Error > ERROR:esys:src/tss2-esys/api/Esys_NV_Write.c:110:Esys_NV_Write() Esys Finish ErrorCode (0x0000099d) > Failed to write to NV index: State not recoverable > Error creating the policy! > Provided PIN incorrect or TPM2 locked after too many retries > NVIndex policy created I tested this multiple times yesterday and today and I am 90% confident I input my recovery key right. I mean I booted the system with it ^^" but as you can see still no luck to update the predictions for the TPM module either. At this point I am not quite sure if the issue will solve itself as soon as issue 1224773 is solved as I manually tampered with the system and the initrd to fix the driver installation. Kind regards, Imo. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1228808] grub error: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found.
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228808 https://bugzilla.suse.com/show_bug.cgi?id=1228808#c2 --- Comment #2 from Vinay Gahlout <vinaygahlout(a)google.com> --- >> Why is GRUB_SERIAL_COMMAND set as "None"? I have no idea. This config came with openSUSE image. Afaik, We have not altered anything in /etc/default/grub. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226031] apparmor stops working due to "aa-logprof ERROR: Can't parse mount rule mount "" -> "/","
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226031 https://bugzilla.suse.com/show_bug.cgi?id=1226031#c21 --- Comment #21 from David Disseldorp <ddiss(a)suse.com> --- (In reply to Martin Jedamzik from comment #20) > here you go ( using the reproducer from Christian ) > > leap156:~ # uname -r > 6.4.0-150600.1.g10a598f-default > leap156:~ # echo '/t { pivot_root "/tmp/" -> "/tmp/", }' | apparmor_parser > -r > Warning from stdin (line 1): apparmor_parser: cannot use or update cache, > disable, or force-complain via stdin > > Am I correct to assume that this is a success ? Yes, it appears that kernel policy unpacking was successful this time. Your test efforts are much appreciated! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226031] apparmor stops working due to "aa-logprof ERROR: Can't parse mount rule mount "" -> "/","
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1226031 https://bugzilla.suse.com/show_bug.cgi?id=1226031#c20 --- Comment #20 from Martin Jedamzik <martin.jedamzik(a)suse.com> --- here you go ( using the reproducer from Christian ) leap156:~ # uname -r 6.4.0-150600.1.g10a598f-default leap156:~ # echo '/t { pivot_root "/tmp/" -> "/tmp/", }' | apparmor_parser -r Warning from stdin (line 1): apparmor_parser: cannot use or update cache, disable, or force-complain via stdin Am I correct to assume that this is a success ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228864] perl-Bootloader can break systemd-boot installations dropping shim.efi
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

1 0

[Bug 1228864] perl-Bootloader can break systemd-boot installations dropping shim.efi
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228864 Alberto Planas Dominguez <aplanas(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|per-Bootloader can break |perl-Bootloader can break |systemd-boot installations |systemd-boot installations |dropping shim.efi |dropping shim.efi -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228864] per-Bootloader can break systemd-boot installations dropping shim.efi
by bugzilla_noreply＠suse.com 06 Aug '24

06 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228864 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |bootloader-maintainers@suse | |.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0