February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1040589] bash/gcc/gzip/python differ between builds because of profiling
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1040589 http://bugzilla.suse.com/show_bug.cgi?id=1040589#c28 --- Comment #28 from Martin Liška <martin.liska(a)suse.com> --- We've got a team meeting and we discuss the topic quite thoroughly. There's an analysis why the mentioned packages have not reproducible builds: 1) GCC: it's using garbage collected memory and similar mechanisms that are dependent on memory layout (ASLR, heap allocation). That makes it complicated to achieve a reproducible builds. 2) Python: I haven't analyzed the package, but I would expect it's affected by similar problem. 3) gzip - looks stable to me right now 4) xz - likewise 5) sed - analyzed here: https://bugzilla.suse.com/show_bug.cgi?id=1040589#c9 6) hello - the package looks stable 7) bash: I did concat of gcov-dump of all gcda and gcno files (by adding --coverage): $ find /var/tmp/ -name '*.gcda' 2>/dev/null | sort | xargs -L1 gcov-dump -l > .. and using a simple script: https://github.com/marxin/script-misc/blob/master/gcov-diff.py $ ./gcov-diff.py /tmp/gcda1 /tmp/gcda2 /tmp/gcno1 | colordiff Difference for fn 1039863413 (fmtumax fmtulong.c:84) --- +++ @@ -1,6 +1,6 @@ 01a10000: 60:COUNTERS arcs 30 counts 0: 0 0 275415 91 0 0 0 0 - 8: 198528 76887 12 184735 0 0 0 0 + 8: 198528 76887 12 184812 0 0 0 0 16: 0 0 0 0 0 0 0 0 24: 0 0 0 0 0 91 01a30000: 8:COUNTERS interval 4 counts Difference for fn 1133735831 (mbschr mbschr.c:43) --- +++ @@ -1,5 +1,5 @@ 01a10000: 24:COUNTERS arcs 12 counts - 0: 1720761 1105721 1105721 669139 1665477 667538 667538 667533 - 8: 1035 6682747 668104 1987469 + 0: 1720761 1105721 1105721 669139 1665499 667538 667538 667533 + 8: 1035 6682747 668104 1987491 01af0000: 2:COUNTERS time_profiler 1 counts 0: 38 Difference for fn 1191969440 (timeval_to_cpu timeval.c:73) --- +++ @@ -1,6 +1,6 @@ 01a10000: 16:COUNTERS arcs 8 counts 0: 6 0 0 0 36 24 0 6 01a70000: 6:COUNTERS single 3 counts - 0: 9 4 6 + 0: 11 2 6 01af0000: 2:COUNTERS time_profiler 1 counts 0: 265 Difference for fn 58810953 (make_word_flags make_cmd.c:102) --- +++ @@ -1,5 +1,5 @@ 01a10000: 22:COUNTERS arcs 11 counts - %2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124446] PHP 7.3 preg_match(): JIT compilation failed: no more memory (need pcre.jit=0 by default in php.ini)
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124446 http://bugzilla.suse.com/show_bug.cgi?id=1124446#c1 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Petr Gajdos <pgajdos(a)suse.com> --- Workaround submitted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1091097] 9p kernel module(s) needed in kernel-default-base for kubic development environment
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1091097 http://bugzilla.suse.com/show_bug.cgi?id=1091097#c13 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek(a)suse.com Assignee|jslaby(a)suse.com |kernel-maintainers(a)forge.pr | |ovo.novell.com Flags|needinfo? |needinfo?(msuchanek(a)suse.co | |m) --- Comment #13 from Jiri Slaby <jslaby(a)suse.com> --- I'm not sure who should be assignee here. Perhaps Michal Suchanek's solution will fix this? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1116625] Systemd automount units fail after suspend/resume
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1116625 http://bugzilla.suse.com/show_bug.cgi?id=1116625#c33 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|systemd-maintainers(a)suse.de |os.gnome.maintainers@gmail. | |com --- Comment #33 from Franck Bui <fbui(a)suse.com> --- OK I'm re-assigning this bug to the NM maintainers since /etc/NetworkManager/dispatcher.d/nfs is part of NM. Thanks Neil for your help. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123245] After zypper dup from Leap:15.0 to Tumbleweed boot fails intermittently failed to find grub_efi_allocate_fixed
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1123245 http://bugzilla.opensuse.org/show_bug.cgi?id=1123245#c11 --- Comment #11 from Dave Plater <davejplater(a)gmail.com> --- (In reply to Neil Rickert from comment #10) > > This is confusing, because I do not see any "secure boot" entry in the > output that you show in comment #3 above. That would be Boot0002* judging by the order, Boot0000* is the default boot. > > It is also unclear what you mean by "secure boot is disabled". You can > disable secure-boot in your BIOS (or UEFI firmware). And that should not > have any effect on which boot entries are there. You can also disable in > Yast, which probably does affect your boot entries. Leap:42.3 installation originally enabled tpm and secure boot by default. When secure boot is enabled in yast the third bios boot entry appears. If I select it in the bios boot menu it boots. The default bios boot item is the problem one. > > I would suggest leaving secure boot enabled in Yast, but disabled in your > BIOS. That's what will probably work best for you. > > Your problem appears to be that you are using a stale boot entry with your > UEFI firmware, which no longer matches the installed grub2-efi. When you > use secure-boot (as set in Yast bootloader), then the code used for the boot > entry is self-contained and will usually work even when it does not match > the installed "grub2-efi". What I still don't understand is why Leap had no problems, I had to run a 4.17 kernel for the wifi, but Tumbleweed just can't get it right without intervention > > The more complete solution would be to update "grubx64.efi" in your EFI > partition, so that it is identical to "/boot/grub2/x86_64-efi/core.efi". > And since you have two EFI partitions, with a "grubx64.efi" in both > partitions, you should update both of those. And, to be clear, those files > will be in a directory with path "EFI/opensuse" (relative to the top of the > EFI partition). If the same filename is found in other directories, that's > probably from a different linux version. "Different linux version"? I've only openSUSE and windows 10. I can possibly fix my problem (If it survives kernel updates) by using Boot0002* as the default entry but that doesn't fix the bug. What exactly causes: "failed to find grub_efi_allocate_fixed"? Where can I find documentation on my boot process? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1123498] VUL-0: CVE-2019-6690: python-python-gnupg: improper input validation in gnupg.GPG.encrypt() and gnupg.GPG.decrypt()
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123498 http://bugzilla.suse.com/show_bug.cgi?id=1123498#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-SU-2019:0143-1: An update that fixes one vulnerability is now available. Category: security (important) Bug References: 1123498 CVE References: CVE-2019-6690 Sources used: openSUSE Leap 15.0 (src): python-python-gnupg-0.4.4-lp150.2.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 984158] kiwi docs missing parenthesis typo
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=984158 http://bugzilla.suse.com/show_bug.cgi?id=984158#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2019:0279-1: An update that has 18 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1003091,1008898,1009032,1029904,1036198,1039469,1047291,1059715,1066873,1071135,1075810,1075813,1095856,1108837,1116729,1118306,984158,997085 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 12-SP3 (src): kiwi-7.04.47-72.31.1 SUSE Linux Enterprise Server 12-SP3 (src): kiwi-7.04.47-72.31.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1047291] kiwi: duplicate binaries in openSUSE:Leap:42.3
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1047291 http://bugzilla.suse.com/show_bug.cgi?id=1047291#c26 --- Comment #26 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2019:0279-1: An update that has 18 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1003091,1008898,1009032,1029904,1036198,1039469,1047291,1059715,1066873,1071135,1075810,1075813,1095856,1108837,1116729,1118306,984158,997085 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 12-SP3 (src): kiwi-7.04.47-72.31.1 SUSE Linux Enterprise Server 12-SP3 (src): kiwi-7.04.47-72.31.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1039469] kiwi: Image built with 'oem-partition-install' can`t find partitions
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1039469 http://bugzilla.suse.com/show_bug.cgi?id=1039469#c12 --- Comment #12 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2019:0279-1: An update that has 18 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 1003091,1008898,1009032,1029904,1036198,1039469,1047291,1059715,1066873,1071135,1075810,1075813,1095856,1108837,1116729,1118306,984158,997085 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 12-SP3 (src): kiwi-7.04.47-72.31.1 SUSE Linux Enterprise Server 12-SP3 (src): kiwi-7.04.47-72.31.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124508] TW 20190205 Installer font much too small
by bugzilla_noreply＠novell.com 07 Feb '19

07 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1124508 http://bugzilla.opensuse.org/show_bug.cgi?id=1124508#c14 Stasiek Michalski <hellcp(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #14 from Stasiek Michalski <hellcp(a)mailbox.org> --- (In reply to Felix Miata from comment #13) > The computer figures out how many pixels are needed to produce appropriate > size instead of the designer choosing arbitrary px numbers that work for him > on his display but become illegible on high density displays. I really wanted to use em for stylesheets, but I can't do that, because of ``` However, Qt is limited to font sizes in pt and px and any other size must be in px, em or ex. ``` From: http://doc.qt.io/qt-5/stylesheet-reference.html#length That basically means that even if we change the fonts to use em, they will be out of size compared to everything else (checkboxes, logos, scrollbars, arrows for sliding widgets etc). Unfortunately the only way to keep that at least somewhat consistent is to use px measurements. That is entirely Qt's fault, css has long ago adapted to using em's for all the elements' sizing being possible. I will take a look at font sizes soon, Source Sans Pro is in fact smaller than previous Sans font we used for the interface, which is an issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0