May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1107765] New: SpamAssassin Net::DNS : Patching required
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1107765 Bug ID: 1107765 Summary: SpamAssassin Net::DNS : Patching required Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: b631093f-779b-4d67-9ffe-5f6d5b1d3f8a(a)protonmail.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SpamAssassin 3.4.1 has an important bug (https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7223) that needs to be patched if the release of the Net::DNS Perl package installed on your system is 1.01 or larger. Leap15 is affected: SpamAssassin Server version 3.4.1 > perl -MNet::DNS -le 'print $Net::DNS::VERSION' 1.14 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1068469] New: package spamassassin contains obsolete file README.SuSE
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1068469 Bug ID: 1068469 Summary: package spamassassin contains obsolete file README.SuSE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, Following a conversation in <https://lists.opensuse.org/opensuse-factory/2017-11/msg00346.html> about «Bulk renaming of "README.SuSE"», it was suggested to search for README.SuSE files in the distribution, find if the contents are valid or obsolete, and then suggest action to the package maintainer in a corresponding bugzilla. The package spamassassin-3.4.1-54.2.x86_64.rpmcontains an obsolete README.SuSE, as it applies to a Sys V init system, so in my opinion it should be simply removed. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1118678] New: devel:languages:perl/spamassassin: Bug in Spec: Source:1 is not in bz2 Format
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1118678 Bug ID: 1118678 Summary: devel:languages:perl/spamassassin: Bug in Spec: Source:1 is not in bz2 Format Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request Assignee: varkoly(a)suse.com Reporter: mgoppold(a)web.de QA Contact: adrian(a)suse.com CC: coolo(a)suse.com Found By: --- Blocker: --- Source1: .../Mail-SpamAssassin-rules-%{version}.r%{rules_revision}.tgz and later in %install: ... pushd %{buildroot}/usr/share/spamassassin && tar -xjf %{S:1} && popd ... Fix it with: tar -xzf %{S:1} -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1004453] New: [mga] no Xorg with Matrox gfxcard when valid vga= mode included on kernel cmdline to produce desirable vttys
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 Bug ID: 1004453 Summary: [mga] no Xorg with Matrox gfxcard when valid vga= mode included on kernel cmdline to produce desirable vttys Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com CC: eich(a)suse.com Found By: --- Blocker: --- Created attachment 697145 --> http://bugzilla.opensuse.org/attachment.cgi?id=697145&action=edit Xorg.0.log from i586 TW host a-865 Mailing list thread starter: https://lists.opensuse.org/opensuse/2016-08/msg00322.html (same with kernels 4.7.x as with kernel 4.6.4) : # Xorg.0.log excerpts X.Org X Server 1.18.4 [ 57.691] Current Operating System: Linux a-865 4.7.4-1-default #1 SMP Thu Sep 15 09:03:59 UTC 2016 (6a5bbb1) i686 [ 57.691] Kernel command line: root=LABEL=os133SS25 ipv6.disable=1 net.ifnames=0 noresume splash=0 vga=791 video=1024x768@60 3 [ 58.342] (EE) open /dev/dri/card0: No such file or directory [ 58.382] (EE) MGA(0): Unable to map Framebuffer F0000000 2000000. Invalid argument (22) [ 58.382] (EE) MGA(0): Unable to detect video RAM. [ 58.382] (EE) Screen(s) found, but none have a usable configuration. [ 58.383] (EE) [ 58.383] (EE) no screens found(EE)... I didn't update this installation for many months, which explains large gap between installed kernels. Xorg and vttys work as expected with kernel-pae 4.2.3 and vga=791 on cmdline, but vga= needs to be omitted with the newer kernels for Xorg to start. Omitting vga= from cmdline results in far too few columns and rows on the vttys. I looked on bugs.freedesktop.org but found nothing like this. I tried a fresh zypper up, but kernel-default 4.7.6 with vga=788 proved no better, as did kernel-vanilla. Also didn't help adding to xorg.conf device section either VideoRam 16384 and/or Option "OldDmaInit" "On". # zypper se -si | egrep 'x11-serv|mga|kernel' il | kernel-default | package | 4.7.4-1.1 | i586 | (System Packages) il | kernel-default | package | 4.6.4-2.2 | i586 | (System Packages) il | kernel-default | package | 4.7.6-1.1 | i586 | OSS i | kernel-firmware | package | 20160913-1.1 | noarch | OSS il | kernel-pae | package | 4.2.3-1.4 | i686 | (System Packages) i | kernel-vanilla | package | 4.7.6-1.1 | i686 | OSS i | nfs-kernel-server | package | 1.3.4-2.2 | i586 | OSS i | xf86-video-mga | package | 1.6.4-2.2 | i586 | OSS i | xorg-x11-server | package | 7.6_1.18.4-1.2 | i586 | OSS # lspci | grep VGA 01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Millennium G550 (rev 01) -- You are receiving this mail because: You are on the CC list for the bug.

2 55

[Bug 911401] New: Wrong yast language when multiple languages specified in LANGUAGE env variable
by bugzilla_noreply＠novell.com 29 Mar '21

29 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=911401 Bug ID: 911401 Summary: Wrong yast language when multiple languages specified in LANGUAGE env variable Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: PVince81(a)yahoo.fr QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Steps to reproduce: 1. Make sure that neither LANG nor any LC_* variables are set 2. Run: export LANGUAGE="en_US:de:fr" (or set this language order in KDE's language settings) 3. Run: kdesu yast2 Expected result: Since English is the first language, Yast2 should be in English. Actual result: Yast2 is in German! More info: If you do: - export LANGUAGE="en_US" - kdesu yast2 Yast2 will be in English. It seems zypper is also affected partially. When LANGUAGE="en_US:de:fr" then zypper is in English, but the confirmation prompt is in German: Overall download size: 682.1 MiB. Already cached: 0 B After the operation, additional 753.3 MiB will be used. Fortfahren? [j/n/? zeigt alle Optionen] (j): Could be a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=843573 but that one didn't have any details. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1028018] New: Updating postfix gives chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory
by bugzilla_noreply＠novell.com 29 Mar '21

29 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1028018 Bug ID: 1028018 Summary: Updating postfix gives chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just `zypper dup`-ed a Tumbleweed installation and got the following: Installing: postfix-3.1.4-3.1.x86_64 ........[done] Additional rpm output: Executing upgrade-configuration. chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory Updating /etc/sysconfig/postfix ... Updating /etc/sysconfig/mail ... Looking into /usr/lib/postfix indeed this file does not exist after the upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1112500] New: logwatch is out of sync with logrotate
by bugzilla_noreply＠novell.com 26 Mar '21

26 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1112500 Bug ID: 1112500 Summary: logwatch is out of sync with logrotate Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: adaugherity(a)tamu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In previous versions of openSUSE (up through Leap 42.2/SLE12SP2), both logwatch and logrotate were run via scripts in the /etc/cron.daily directory; logwatch was always run first because its symlink is named "0logwatch". This changed in 42.3/SP3 (and continues in 15) when logrotate was changed to use a systemd timer instead of cron.daily. Now it is possible for logrotate to run before logwatch, and if a log file is rotated, logwatch reports on just the few log entries in the new log file (which may be entirely skipped, depending on the range and archive settings used with logwatch), rather than a whole 24 hours' worth. Example: Apache access log; assume it's large enough to be rotated. Rotation happens at midnight (logrotate.timer) and the file is renamed to e.g. access_log-20181018.xz. When cron.daily runs (at DAILY_TIME from /etc/sysconfig/cron, let's say 04:00, or at boot and 24 hours thereafter if DAILY_TIME is not set), logwatch reports on /var/log/apache2/access_log, which only contains entries after midnight. With the default range of "yesterday", nothing will be reported*. *It would be via logwatch's archive processing (enabled by default), except that the shipped version of logwatch does not handle xz archives, only gz & bz2. Fix: replace the /etc/cron.daily/0logwatch symlink with a systemd timer? There are systemd service/timer definitions in the logwatch git[1], although they may need some tweaking to conform to SUSE and/or upstream systemd standards, and to make it run before logrotate does. Additionally, the git master has also added xz archive support, and a few other fixes/improvements. I don't know when an actual release will be cut, though -- there's an unanswered post in their forum asking that very thing. [1] https://sourceforge.net/p/logwatch/git/ci/master/tree/ systemd stuff is under the scheduler subdirectory -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1125689] New: nghttp2 mistake in spec file
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1125689 Bug ID: 1125689 Summary: nghttp2 mistake in spec file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: holgerbruenjes(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in spec file from nghttp2-1.36.0-1.2.src.rpm and before the devel package require not the libnghttp2-asio correct require was libnghttp2 see pkgconfig file Libs: -L${libdir} -lnghttp2 %package -n %{soname}-devel Summary: Development files for nghttp2 Group: Development/Languages/C and C++ - Requires: %{soname_asio}%{sover_asio} = %{version} + Requires: %{soname}%{sover} = %{version} Provides: %{name}-devel -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1134616] New: nghttp2: fails to build with boost 1.70.0
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1134616 Bug ID: 1134616 Summary: nghttp2: fails to build with boost 1.70.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: tchvatal(a)suse.com Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com Blocks: 1134606 Found By: --- Blocker: --- This is a bug indicating that a package for whom you are maintainer in openSUSE:Factory no longer builds with the proposed Boost 1.70.0 and as such will require patching. You can see your package failing to build at, https://build.opensuse.org/package/show/home:adamm:boost_test/nghttp2 asio_server_connection.h:85:17: error: 'class boost::asio::ssl::stream<boost::asio::basic_stream_socket<boost::asio::ip::tcp> >' has no member named 'get_io_service' [ 121s] socket_.get_io_service(), socket_.lowest_layer().remote_endpoint(ec), [ 121s] ~~~~~~~~^~~~~~~~~~~~~~ https://stackoverflow.com/questions/39445636/alternative-to-deprecated-get-… Please patch the problem and submit the fixes as Boost 1.70.0 will be shortly submitted to Factory. If you are not maintainer, please let me know. Some packages do not have maintainers but only project maintainers, in which case I'm assigning the bug to the person doing most of recent changes and CC'ing the other maintainers. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1045287] New: systemd: mounts using "nofail" option are not correctly ordered during shutdown
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1045287 Bug ID: 1045287 Summary: systemd: mounts using "nofail" option are not correctly ordered during shutdown Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a mount entry in fstab uses the "nofail" option, systemd doesn't order the corresponding mount unit with a "Before=local-fs.target" so if the mount unit takes time to be activated, it won't delay the whole boot process. However by doing this, we also remove ordering constraint for the shutdown process. This can lead to the mount unit being stopped while some applications are still using the corresponding mount point. This problem was discussed in bug 1036962 but this bug was more about NFS or remote fs. In this case the fix already exists since v218 and remote fs automatically gain a Before=remote-fs.target after they're mounted. A similar fix has been submitted upstream for local fs which can be found here: https://github.com/systemd/systemd/pull/6102 and is waiting for approval. -- You are receiving this mail because: You are on the CC list for the bug.

2 4