January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1180514] New: Postfix fails to send with default settings on WSL release
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180514 Bug ID: 1180514 Summary: Postfix fails to send with default settings on WSL release Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: WSL Assignee: sle-ms(a)suse.de Reporter: julianbane(a)compuserve.com QA Contact: qa-c(a)suse.de Found By: --- Blocker: --- On a fresh install of WSL openSUSE Leap 5.2 postfix fauils to send mail. The distribution comes with no .db files in /etc/postfix. Line 784 of /etc/postfix/main.cf reads: relay_domains = $mydestination, hash:/etc/postfix/relay As such it's expecting a 'relay.db' file in /etc/postfix that does not exist and postfix fails to send mails (tested with a simple 'echo "Hello World" | mail -s "Test" julianbane(a)compuserve.com' command). Either the .db file(s) need creating or simply comment out line 784 (personally I hink this is the better solution and worked for me). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180215] VUL-0: CVE-2020-28052: bouncycastle: OpenBSDBCrypt.checkPassword utility method compared incorrect data when checking the password
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180215 https://bugzilla.suse.com/show_bug.cgi?id=1180215#c3 Johannes Segitz <jsegitz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Johannes Segitz <jsegitz(a)suse.com> --- thank you -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180494] Boot on current installation and new installation fails
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180494 https://bugzilla.suse.com/show_bug.cgi?id=1180494#c1 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com Assignee|yast2-maintainers(a)suse.de |dracut-maintainers(a)suse.de --- Comment #1 from Josef Reidinger <jreidinger(a)suse.com> --- reassigning to dracut maintainers -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180348] shortcut key failed when trying to edit the grub2 boot menu
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180348 https://bugzilla.suse.com/show_bug.cgi?id=1180348#c8 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #8 from Michael Chang <mchang(a)suse.com> --- OK. Let's close as "resolved wontfix" because this is really firmware related to me. Feel free to reopen if you find time to test a debug build. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137373] Systemd mount and unmount partition during boot
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1137373 http://bugzilla.opensuse.org/show_bug.cgi?id=1137373#c48 --- Comment #48 from Bj�rn Voigt <bjoernv(a)arcor.de> --- (In reply to Philipp Reichmuth from comment #47) > For the record, since the upgrade to TW 20210101 after doing a zypper dup > before reboot, upon rebooting /opt is gone. I have found, that this issue does not always occur after "zypper dup". The question is, which Zypper dependent scripts trigger the issue. It would be also interesting to know, which kinds of /etc/fstab entries are affected. On my system all kinds of none-root entries (ext4 partitions, bind mounts) are unmounted sometimes on boot. May be, also very small and simple /etc/fstab lists with some ext4 can be affected. But if small and simple /etc/fstab lists are affected, it is unclear why not much more users are affected by this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180493] MultiOS Flatpak Installation
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180493 https://bugzilla.suse.com/show_bug.cgi?id=1180493#c1 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com, | |jreidinger(a)suse.com, | |slawek(a)lach.art.pl Flags| |needinfo?(ancor(a)suse.com), | |needinfo?(slawek(a)lach.art.p | |l) --- Comment #1 from Josef Reidinger <jreidinger(a)suse.com> --- ancor - opinions? Slawomir - is somewhere documentation about that kind of partition? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1116625] NetworkManager stops automount units when system is being suspended but doesn't reactivate them after resuming
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1116625 https://bugzilla.suse.com/show_bug.cgi?id=1116625#c46 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #46 from Jiri Slaby <jslaby(a)suse.com> --- I think the bug still persists. Last time I saw this with NetworkManager-1.28.0-1.1.x86_64 installed on 12/18. I edited /etc/NetworkManager/dispatcher.d/nfs on 12/21: > # Only unmount it when the type is nfs or nfs4 > if [ "$FS_TYPE" == "nfs" -o "$FS_TYPE" == "nfs4xx" ]; then The condition is inverted (by !), I think: '/x-systemd.automount/!d' -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180306] Tumbleweed 20201221 breaks "csh"
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180306 https://bugzilla.suse.com/show_bug.cgi?id=1180306#c1 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED See Also| |https://sourceware.org/bugz | |illa/show_bug.cgi?id=27146 --- Comment #1 from Martin Li��ka <martin.liska(a)suse.com> --- Thank you for the report, I forwarded that to upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=27146 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180413] diffutils not installed in in the main info directory
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180413 https://bugzilla.suse.com/show_bug.cgi?id=1180413#c2 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jslaby(a)suse.com --- Comment #2 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Christopher Yeleighton from comment #1) > Workaround: { install-info /usr/share/info/diffutils* /usr/share/info/dir; } 1) what do we do if info package is not installed? 2) do we want a (rpmlint) check for all packages? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180503] New: "osc build" don't ignore the line which was commented out
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180503 Bug ID: 1180503 Summary: "osc build" don't ignore the line which was commented out Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: junguo.wang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844784 --> http://bugzilla.opensuse.org/attachment.cgi?id=844784&action=edit build.log file and rpm spec file I got a issue when I tried to build a package with "osc build", it is that "osc build" don't ignore the line which was commented out, for example: this is the section of the rpm spec file: """ %prep ## %setup -q -n mda.lv2-%{version} %autosetup -p1 """ and I got the output from "osc build": """ [ 14s] RPMLINT report: [ 14s] =============== [ 15s] mda-lv2.src:43: W: macro-in-comment %setup [ 15s] mda-lv2.src:43: W: macro-in-comment %{version} [ 15s] There is a unescaped macro after a shell style comment in the specfile. Macros [ 15s] are expanded everywhere, so check if it can cause a problem in this case and [ 15s] escape the macro with another leading % if appropriate. [ 15s] [ 15s] 2 packages and 0 specfiles checked; 0 errors, 2 warnings. """ if I deleted the line "## %setup -q -n mda.lv2-%{version}" from the rpm spec file, the warnings will be ZERO rather that 2, so it seems that the commented-out line was NOT ignored by "osc build", is it normal ? I will upload the build log and the rpm spec file in next comments. -- You are receiving this mail because: You are on the CC list for the bug.

1 0