January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1178080] systemd-resolved linked against gnutls
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1178080 https://bugzilla.suse.com/show_bug.cgi?id=1178080#c2 --- Comment #2 from Ludwig Nussel <lnussel(a)suse.com> --- There's efforts to move systemd fully to openssl: https://github.com/systemd/systemd/pull/14743 Also, it's TW and we don't use resolved by default anyways. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175826] suitesparse s390x build failure "Illegal instruction" on s390p21 workers
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1175826 Sarah Julia Kriesch <sarah.kriesch(a)ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sarah.kriesch(a)ibm.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173718] VUL-1: libmicrohttpd: buffer overflow issue in URL parser
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1173718 https://bugzilla.suse.com/show_bug.cgi?id=1173718#c10 --- Comment #10 from Ladislav Slez�k <lslezak(a)suse.com> --- Fixed in libyui-rest-api-0.5.12 https://github.com/libyui/libyui-rest-api/pull/20 https://build.opensuse.org/request/show/860393 Details: The code already handled the new libmicrohttpd correctly (as written in comment #7) but there was a missing #include so the MHD_VERSION macro was not evaluated properly... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180487] chromium crash: FATAL:string_piece.h(328)] Check failed: pos <= size() (18446744073709551615 vs. 36)
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180487 https://bugzilla.suse.com/show_bug.cgi?id=1180487#c5 --- Comment #5 from Callum Farmer <gmbr3(a)opensuse.org> --- https://bugs.chromium.org/p/chromium/issues/detail?id=1162821#c6 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180550] New: LibreOffice: About dialog logo is broken
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180550 Bug ID: 1180550 Summary: LibreOffice: About dialog logo is broken Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: tchvatal(a)suse.com Reporter: maurizio.galli(a)gmail.com QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844829 --> http://bugzilla.opensuse.org/attachment.cgi?id=844829&action=edit About Dialog As per screenshot attached the about dialog image/logo is not centered. Personally I would prefer dropping the branding-openSUSE package altogether and only use upstream. However if the openSUSE branding is important to keep, it would be great to see it fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1180501] frequent sshd coredumps
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180501 https://bugzilla.suse.com/show_bug.cgi?id=1180501#c4 --- Comment #4 from Olaf Hering <ohering(a)suse.com> --- (In reply to patrick shanahan from comment #2) > ssh -V This is useless. ssh -v host_with_broken_sshd -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180195] New: emergency console: not installed plymouth results in inappropriate error message obfuscating genuine errors reported by journalctl -xb
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180195 Bug ID: 1180195 Summary: emergency console: not installed plymouth results in inappropriate error message obfuscating genuine errors reported by journalctl -xb Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Original summary: emergency console: not installed plymouth results in inappropriate error message obfuscating genuine errors reported by journalctl -xb Emergency session log ought not be obfuscating genuine errors by reporting error in an optional service that is purposely not installed. The following is the final message in the journal after a required filesystem failed to mount: "Subject: Process /usr/bin/plymouth could not be executed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel The process /usr/bin/plymouth could not be executed and failed. The error number returned by this process is ERRNO." Yet, there are, and never were, any plymou* rpms installed. Observed in TW 20201215. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1180195] emergency console: not installed plymouth results in inappropriate error message obfuscating genuine errors reported by journalctl -xb
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180195 https://bugzilla.suse.com/show_bug.cgi?id=1180195#c1 --- Comment #1 from Cliff Zhao <qzhao(a)suse.com> --- So I guess the full steps are: you installed TW 20201215 to your computer; then you removed all plymouth* packages; after reboot, you saw a errors in the journalctl output. then why you failing into the Emergency console? You just intend to goto the here? or you did nothing but uninstall plymouth* packages then you only can go to Emergency console? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179625] After latest updates the plymouth startup screen drops to "matrix style"
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179625 https://bugzilla.suse.com/show_bug.cgi?id=1179625#c1 --- Comment #1 from Cliff Zhao <qzhao(a)suse.com> --- Hi Stakanov: The recent update of plymouth should work together with the updated plymouth-branding-openSUSE package. Make sure you installed the latest edition of them both. Then, use ~> sudo plymouth-set-default-theme --rebuild-initrd bgrt to reset the theme. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180501] frequent sshd coredumps
by bugzilla_noreply＠suse.com 05 Jan '21

05 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180501 https://bugzilla.suse.com/show_bug.cgi?id=1180501#c3 Hans Petter Jansson <hpj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(paka(a)opensuse.org | |) --- Comment #3 from Hans Petter Jansson <hpj(a)suse.com> --- Thanks for the core dump. This seems to be happening in a few locations, but I haven't been able to repro it here yet, not even with valgrind. The dump makes it looks like a sshcipher_ctx struct has been partially overwritten with garbage. In cipher_free() it crashes on this line: > if ((cc->cipher->flags & CFLAG_CHACHAPOLY) != 0) { ...because cc->cipher points to a bad location (but it's not NULL). Questions: 1) Do you know more precisely when this started happening? I'm suspecting patches added to openssh or openssl this autumn. 2) Could you run sshd like this (as root): /usr/sbin/sshd -Dddd -p 2048 Then from a different shell session, connect to it like this: ssh localhost -p 2048 ...and trigger the crash, then attach the sshd debug output here? -- You are receiving this mail because: You are on the CC list for the bug.

1 0