June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1078825] salt-ssh failing with Leap-15.0 client
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1078825 http://bugzilla.suse.com/show_bug.cgi?id=1078825#c6 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED Flags|needinfo?(bwiedemann(a)suse.c | |om) | --- Comment #6 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- Works now with salt-2018.3.0-29.1 on 42.3 The UNIX timestamp in the old version decodes to 2017-11-27 so probably someone fixed it along the way. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078825] salt-ssh failing with Leap-15.0 client
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1078825 http://bugzilla.suse.com/show_bug.cgi?id=1078825#c5 Vítězslav Čížek <vcizek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann(a)suse.com Flags| |needinfo?(bwiedemann(a)suse.c | |om) --- Comment #5 from Vítězslav Čížek <vcizek(a)suse.com> --- I can no longer reproduce the bug. Is it still an issue? I see that the openssl initialization has been changed a bit in the upstream git. Firstly, libcrypto.OPENSSL_init_crypto() runs without parameters to use the default, so the LOAD_CONFIG and NO_LOAD_CONFIG options should no longer clash. And secondly, libcrypto.OPENSSL_init_crypto() is now even run only when OpenSSL version is lower than 1.1. So maybe a salt update fixed it? Could you please verify? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135751] [Staging] apparmor fails to build against swig 4.0
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1135751 http://bugzilla.suse.com/show_bug.cgi?id=1135751#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1135751) was mentioned in https://build.opensuse.org/request/show/707833 Factory / apparmor -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136927] [Build 20190528] System does not use same network names after update
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136927 http://bugzilla.suse.com/show_bug.cgi?id=1136927#c7 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dimstar@opensuse. | |org) | --- Comment #7 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Oliver Kurz from comment #6) > Maybe I can help. I doubt the iso of 20190527 is available anymore. It's > neither on openqa.opensuse.org nor could I find it on download.opensuse.org. > However, as the patch was reverted you can just use any published Snapshot > ISO as the reference, am I wrong? Ah indeed, tumbleweed has again dracut-044. Thanks Oliver. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120956] VUL-1: CVE-2018-20662: poppler: PDFDoc setup in PDFDoc.cc allows attackers to cause DOS because of a wrong return value from PDFDoc:setup
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1120956 http://bugzilla.suse.com/show_bug.cgi?id=1120956#c4 Alexandros Toptsoglou <atoptsoglou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #4 from Alexandros Toptsoglou <atoptsoglou(a)suse.com> --- The wrong patch for CVE-2018-20662 has been applied. As it is explained in comment 0 that patch creates regression and upstream did not use it. The correct patch is located at [1]. Please resubmit. [1] https://gitlab.freedesktop.org/mkasik/poppler/commit/7b4e372deeb716eb3fe3a5… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135751] New: [Staging] apparmor fails to build against swig 4.0
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1135751 Bug ID: 1135751 Summary: [Staging] apparmor fails to build against swig 4.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta(a)cboltz.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- See bug 1135746: swig is being updated to version 4.0 apparmor is one of the packages failing to build in this setup https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 780249] gtranslator crashes everytime I try to create translation memory from the files on my disk
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=780249 http://bugzilla.suse.com/show_bug.cgi?id=780249#c9 --- Comment #9 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (780249) was mentioned in https://build.opensuse.org/request/show/707812 Factory / gtranslator -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041213] GCC 7: gtranslator fails to build
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1041213 http://bugzilla.suse.com/show_bug.cgi?id=1041213#c2 --- Comment #2 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1041213) was mentioned in https://build.opensuse.org/request/show/707812 Factory / gtranslator -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136601] Installed grub (grubaa64.efi) is not signed - Yast-bootloader does not support SecureBoot on aarch64
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136601 http://bugzilla.suse.com/show_bug.cgi?id=1136601#c14 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #14 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Michael Chang from comment #13) > Please help to test on arm64. Thanks. I tested your grub2 package (using grub2-arm64-efi from Tumbleweed to keep the openSUSE key) with: grub2-install --suse-signed-grub and the installed 'grubaa64.efi' and 'grub.cfg' are working properly! Thanks a lot! :) I will update my PR for Yast bootloader and perl-Bootloader later today, or tomorrow. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136927] [Build 20190528] System does not use same network names after update
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136927 http://bugzilla.suse.com/show_bug.cgi?id=1136927#c6 --- Comment #6 from Oliver Kurz <okurz(a)suse.com> --- Maybe I can help. I doubt the iso of 20190527 is available anymore. It's neither on openqa.opensuse.org nor could I find it on download.opensuse.org. However, as the patch was reverted you can just use any published Snapshot ISO as the reference, am I wrong? -- You are receiving this mail because: You are on the CC list for the bug.

1 0