December 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1156441] grub2-install does not setup env_block for btrfs
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1156441 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158631] New: VUL-0: CVE-2019-19333: libyang: stack-based buffer overflow in make_canonical when bits leaf type is used
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1158631 Bug ID: 1158631 Summary: VUL-0: CVE-2019-19333: libyang: stack-based buffer overflow in make_canonical when bits leaf type is used Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other URL: https://smash.suse.de/issue/248485/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: rfrohl(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1779573 libyang up to version 1 release 4 has a stack-based buffer overflow in function make_canonical() in parser.c, when dealing with "bits" types with a name longer than 511 bytes. An application that uses libyang to validate untrusted YANG files could be vulnerable to this flaw, which could be used by an attacker to cause a denial of service or possibly gain code execution. References: https://bugzilla.redhat.com/show_bug.cgi?id=1779573 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-19333 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1156515] grub2-mkconfig fails to build config for xen, because awk errors
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1156515 http://bugzilla.suse.com/show_bug.cgi?id=1156515#c2 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Michael Chang <mchang(a)suse.com> --- Thanks Adam for the bug report Olaf for the quick turnaround. let's move on to bsc#1157912 to help keeping the status in sync. *** This bug has been marked as a duplicate of bug 1157912 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158403] On Raspberry Pi 1B zypper dup from Tumbleweed 20190830 leaves a non-bootable system
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1158403 http://bugzilla.suse.com/show_bug.cgi?id=1158403#c8 --- Comment #8 from Michael Chang <mchang(a)suse.com> --- (In reply to Freek de Kruijf from comment #0) > I had a Tumbleweed system upgraded to 20190830 which I tried to upgrade to > 20191109. After the upgrade the system did not boot anymore. > I tried to install image > openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2019.10.25-Build1.29.raw, > but the system did not boot. A grub2 screen appeared on the console on the > serial line, but apparently it did not continue to load initrd. And have you tried other linux console output other than serial ? Likely the kernel would be using other console device and redirect to it. (If so, we can classify to config issue). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158403] On Raspberry Pi 1B zypper dup from Tumbleweed 20190830 leaves a non-bootable system
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1158403 http://bugzilla.suse.com/show_bug.cgi?id=1158403#c7 --- Comment #7 from Michael Chang <mchang(a)suse.com> --- (In reply to Alynx Zhou from comment #6) > The first screenshot looks like a grub2 issue, maybe grub2 bugowner can help > us, thanks! The first screenshot did show some problem, mostly likely in grub.cfg, but did not cease booting. As far as I know, some kiwi config seems to set $prefix wrongly at very beginning hence grub couldn't look up its modules, and shortly after the $prefix gets corrected everything start to work as expected. The real problem was in the last one after kernel/initrd got loaded. Have you tried update the uboot as the bug report suggested ? https://bugzilla.suse.com/show_bug.cgi?id=1145646 Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156515] grub2-mkconfig fails to build config for xen, because awk errors
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1156515 Jiri Srain <jsrain(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|jsrain(a)suse.com |mchang(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078466] systemd: duplicated entries in tmpfiles.d
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1078466 http://bugzilla.suse.com/show_bug.cgi?id=1078466#c39 --- Comment #39 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Franck Bui from comment #37) > (In reply to Ludwig Nussel from comment #5) > > [...] nevertheless if tmpfiles is used there should be only one place. > > I agree (eventually). > > It's much simpler if all tmpfiles are kept in one place like it was before > filesystem (silently) introduced fs-var.conf... "As it was before" proved that this will not work: the ownership/permissions used by tmpfiles did never matched the one from filesystem.rpm. Currently, the files are build from the same source, means filesystem.rpm and the fs-var.conf are always in sync. If you move that to aaa_base, who will sync them if somebody makes changes to filesystem.rpm? I'm afraid the result will be the same as we had before: conflicting informations between tmpfiles and filesystem.rpm. It is much simpler if tmpfiles are owned by the package who requires them, uses them, needs, them, ... and not decoupled somewhere else nobody will care. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158474] update of kernel package(s) takes LONG time (44 MINUTES!!!!) - module compression?
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1158474 http://bugzilla.opensuse.org/show_bug.cgi?id=1158474#c8 --- Comment #8 from robert spitzenpfeil <rs.opensuse(a)spitzenpfeil.org> --- I did, in a VM with 2 cores. >> time sudo /usr/sbin/depmod -F /boot/System.map-5.3.12-1-default -ae 5.3.12-1-default real 0m14.919s user 0m9.113s sys 0m0.831s Are you sure it's not your SSD being sick? If you fill them up above 70% (I've read) they supposedly get rather slow at writing, due to erase block sizes and so forth. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149792] openssl 1.1.1c causes build failures in other packages
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

1 0

[Bug 1158543] Broken dbus API aborts sddm if second greeter is not posssible over dbus due X server crash
by bugzilla_noreply＠novell.com 06 Dec '19

06 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1158543 http://bugzilla.suse.com/show_bug.cgi?id=1158543#c7 --- Comment #7 from Dr. Werner Fink <werner(a)suse.com> --- https://github.com/sddm/sddm/issues/1214 -- You are receiving this mail because: You are on the CC list for the bug.

1 0