December 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1234582] VUL-0: CVE-2024-45337: cloudflared: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234582 https://bugzilla.suse.com/show_bug.cgi?id=1234582#c2 --- Comment #2 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1234582) was mentioned in https://build.opensuse.org/request/show/1230993 Factory / cloudflared -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234582] VUL-0: CVE-2024-45337: cloudflared: golang.org/x/crypto/ssh: Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c66 --- Comment #66 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Guillermo Perez from comment #65) > but it would be nice if, for some next uodate, the echo > for the recovery key wouldn't be obscured sdbootutil print the recovery key in the terminal, together with the QR code. Or do you mean in some part of the Aeon installer? In any case your system can be recovered. It should work now with `sdbootutil enroll --method=tpm2` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1234405] devel:microos/libeconf: Bug libeconf 0.7.5 causes systemd/sddm/pam/libc crash and prevents login
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234405 https://bugzilla.suse.com/show_bug.cgi?id=1234405#c11 --- Comment #11 from pallas wept <pallaswept(a)proton.me> --- Just a quick note to let you know that I have tested the new version and it's working fine here, thank you! By the way, I was impressed that you added a test case for this. Very thorough work. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220088] New: Hibernate completes shuts machine off *then* machine automatically turns back on.
by bugzilla_noreply＠suse.com 14 Dec '24

14 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1220088 Bug ID: 1220088 Summary: Hibernate completes shuts machine off *then* machine automatically turns back on. 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: pj.opensuse(a)gmx.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, when hibernate is envoked from the Tumbleweed menu the hibernate feature seems to complete and shutoff the machine for 2 seconds...... Then the machine automatically powers back on. I enter the LUKS password and the machine continues to boot. I enter the user password at SDDM screen. After loading KDE I can then see that Hibernate has indeed worked. Largest issue is machine is cycling, (powering back on) after hibernation has been envoked. I have shut off all wake-on power options in the bios settings. The machine is kept very current with the latest updates. What are your thoughts on this? -Best Regards -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1228863] New: System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 Bug ID: 1228863 Summary: System asking for recovery key while booting a default mode encrypted Aeon system after automatic update Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: rbrown(a)suse.com Reporter: happymab.dev(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I booted the system after the automatic update on 04 Aug 2024, the system asked for the recovery key. I booted the system using the recovery key and tried the following to fix the issue: - sudo sdbootutil update-predictions - sudo sdbootutil --ask-pin update-predictions - Clear TPM in BIOS and run sudo sdbootutil --ask-pin update-predictions None of the above actions fixed the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1234471] laptop fails to suspend (sleep) due to issue with nvidia GPU driver
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1234471 https://bugzilla.suse.com/show_bug.cgi?id=1234471#c11 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Flags|needinfo?(toby(a)breckon.org) | Resolution|--- |DUPLICATE --- Comment #11 from Stefan Dirsch <sndirsch(a)suse.com> --- Thanks for feedback. Ok. Closing as dup. *** This bug has been marked as a duplicate of bug 1226116 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226116] nvidia-open-driver-G06 ... 550.90.07: Fails suspend/recover from powersaving with NVreg_PreserveVideoMemoryAllocations (needed for GNOME Wayland)
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1226116 https://bugzilla.suse.com/show_bug.cgi?id=1226116#c13 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |toby(a)breckon.org --- Comment #13 from Stefan Dirsch <sndirsch(a)suse.com> --- *** Bug 1234471 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c64 --- Comment #64 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Guillermo Perez from comment #63) > (In reply to Alberto Planas Dominguez from comment #62) > > (In reply to Guillermo Perez from comment #61) > > > > > ~> sdbootutil -v --ask-pin update-predictions > > > Error: Can't determine root subvolume > > > > Do you have a default snapshot? > > > > sudo snapper ls > > > > This should show a list of snapshots, and one of the should be marked with > > "*". If this is not the case, somehow you system lacks of default subvolume. > > No, I've got only the one reverted (marked with a - and the last one, marked > with +) No default snapshots. This is the main issue in your system. sdbootutil (actually snapper) cannot find the default snapshot, because you do no have one. You can mark a new one with btrfs or snapper (snapper modify --default). Your issue is not really related with sdbootutil afaict -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228863] System asking for recovery key while booting a default mode encrypted Aeon system after automatic update
by bugzilla_noreply＠suse.com 13 Dec '24

13 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228863 https://bugzilla.suse.com/show_bug.cgi?id=1228863#c63 --- Comment #63 from Guillermo Perez <guillermopf10(a)gmail.com> --- (In reply to Alberto Planas Dominguez from comment #62) > (In reply to Guillermo Perez from comment #61) > > > ~> sdbootutil -v --ask-pin update-predictions > > Error: Can't determine root subvolume > > Do you have a default snapshot? > > sudo snapper ls > > This should show a list of snapshots, and one of the should be marked with > "*". If this is not the case, somehow you system lacks of default subvolume. No, I've got only the one reverted (marked with a - and the last one, marked with +) No default snapshots. BTW, after following the steps in the wiki for completely re-enroll tpm2, it generated a new recovery key. Rebooting the PC asks for a key, the new one doesn't seems to work, but the old one does. After running again sudo systemd-cryptenroll now it only lists SLOT TYPE 2 recovery So it doesn't recognises tpm2. I'm starting to think maybe the only solution is a reinstall. -- You are receiving this mail because: You are on the CC list for the bug.

1 0