November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 921577] New: doxygen build failure for Power8 because double free or corruption
by bugzilla_noreply＠novell.com 21 May '21

21 May '21

http://bugzilla.suse.com/show_bug.cgi?id=921577 Bug ID: 921577 Summary: doxygen build failure for Power8 because double free or corruption Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: PowerPC-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- doxygen build failure for Power8 because double free or corruption === ... [ 241s] Generating docs for compound B/home/abuild/rpmbuild/BUILD/doxygen-1.8.9.1/vhdlparser/TokenManager.h:19: warning: Unsupported xml/html tag <EOF> found [ 248s] *** Error in `./bin/doxygen': double free or corruption (fasttop): 0x000001001077bcf0 *** [ 248s] ======= Backtrace: ========= [ 248s] /lib64/libc.so.6(+0x836c0)[0x3fffa7ec36c0] [ 248s] /lib64/libc.so.6(+0x8ba84)[0x3fffa7ecba84] [ 248s] /lib64/libc.so.6(+0x8cadc)[0x3fffa7eccadc] [ 248s] /lib64/libc.so.6(cfree+0xd0)[0x3fffa7ed0a30] [ 248s] /usr/lib64/libstdc++.so.6(_ZdlPv+0x20)[0x3fffa819ce10] [ 248s] ./bin/doxygen[0x106620e4] [ 248s] ./bin/doxygen[0x1053ba84] [ 248s] ./bin/doxygen[0x1053bb18] [ 248s] ./bin/doxygen[0x106a0a44] [ 248s] /lib64/libpthread.so.0(+0x9454)[0x3fffa8299454] [ 248s] /lib64/libc.so.6(clone+0xe4)[0x3fffa7f4e0c4] ... === detailed log in doxygen_opensuse_ppc64le_failure.log attachment -- You are receiving this mail because: You are on the CC list for the bug.

2 42

[Bug 1057349] New: postfix/smtpd[3493]: fatal: bad string length 0 < 1: smtpd_sasl_path =
by bugzilla_noreply＠novell.com 12 May '21

12 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1057349 Bug ID: 1057349 Summary: postfix/smtpd[3493]: fatal: bad string length 0 < 1: smtpd_sasl_path = 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: qingming.su(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The problem is found by fetchmail, which fails to fetch mail from a remote mailserver (runing postfix+dovecot) The console output looks like: admin@localhost:~> fetchmail -v --ssl mail.openqa.suse fetchmail: 6.3.26 querying mail.openqa.suse (protocol POP3) at Wed 06 Sep 2017 03:12:03 PM CST: poll started Trying to connect to 10.67.18.229/995...connected. fetchmail: Server certificate: fetchmail: Issuer Organization: SUSE fetchmail: Issuer CommonName: openQA CA fetchmail: Subject CommonName: mail.openqa.suse fetchmail: mail.openqa.suse key fingerprint: 4E:FD:84:BE:B5:6C:BF:B0:75:F2:F4:EF:E8:7F:50:9E fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< AUTH-RESP-CODE fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN fetchmail: POP3< . fetchmail: POP3> USER admin fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< +OK Logged in. fetchmail: POP3> STAT fetchmail: POP3< +OK 2 1446 fetchmail: POP3> LAST fetchmail: POP3< -ERR Unknown command: LAST fetchmail: Unknown command: LAST fetchmail: POP3> UIDL fetchmail: POP3< +OK fetchmail: POP3< 1 00000016599145ec fetchmail: POP3< 2 00000017599145ec fetchmail: POP3< . 2 messages for admin at mail.openqa.suse (1446 octets). fetchmail: POP3> LIST 1 fetchmail: POP3< +OK 1 741 fetchmail: POP3> TOP 1 99999999 fetchmail: POP3< +OK reading message admin@mail.openqa.suse:1 of 2 (741 octets) Trying to connect to ::1/25...connected. <fetchmail hangs here> The system journal disclosures the real issue: Sep 06 15:03:49 localhost postfix/smtpd[3442]: fatal: bad string length 0 < 1: smtpd_sasl_path = Sep 06 15:03:50 localhost postfix/master[2712]: warning: process /usr/lib/postfix/smtpd pid 3442 exit status 1 Sep 06 15:03:50 localhost postfix/master[2712]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling The error can be fixed by editing the configuration file /etc/postfix/main.cf, comment out the following lines: smtpd_sasl_path = smtpd_sasl_type = Note: the new lines look like: #smtpd_sasl_path = #smtpd_sasl_type = -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1037846] New: rpm -qf shows files as part of postfix, despite "files or directories still exist but are no longer part of Postfix"
by bugzilla_noreply＠novell.com 12 May '21

12 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1037846 Bug ID: 1037846 Summary: rpm -qf shows files as part of postfix, despite "files or directories still exist but are no longer part of Postfix" 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 saw the following when updating postfix the last few times: (18/50) Installing: postfix-3.2.0-4.1.x86_64 .............................[done] Additional rpm output: warning: /etc/postfix/main.cf created as /etc/postfix/main.cf.rpmnew Executing upgrade-configuration. Note: the following files or directories still exist but are no longer part of Postfix: /etc/postfix/postfix-files /etc/postfix/postfix-script /etc/postfix/post-install Updating /etc/sysconfig/postfix ... Updating /etc/sysconfig/mail ... Alas: > rpm -qf /etc/postfix/postfix-files postfix-3.2.0-4.1.x86_64 > rpm -qf /etc/postfix/postfix-script postfix-3.2.0-4.1.x86_64 > rpm -qf /etc/postfix/post-install postfix-3.2.0-4.1.x86_64 Isn't that inconsistent? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1042529] New: YaST submodule windows don't remember their size and position when opened as standalone programs
by bugzilla_noreply＠novell.com 11 May '21

11 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1042529 Bug ID: 1042529 Summary: YaST submodule windows don't remember their size and position when opened as standalone programs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: pointedstick(a)zoho.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Steps to reproduce: 1. Open any YaST submodule directly (e.g. search for "Software Management" from KRunner) 2. Adjust the window size and position 3. Close the window 4. Open it again the same way as in 1 Expected results: - The window spawns with the same size and position as it had when you last closed it Actual results: - The window opens at position 0,0 with a size of 1344x771. Additional information: - YaST's main window behaves properly and remembers its position; it's only submodule windows when opened directly that exhibit this issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1003362] New: server:monitoring/nagios: Bug
by bugzilla_noreply＠novell.com 11 May '21

11 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1003362 Bug ID: 1003362 Summary: server:monitoring/nagios: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: lars.vogdt(a)suse.com Reporter: ian.mcconnell(a)denbridgemarine.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: nix(a)opensuse.org Found By: --- Blocker: --- Created attachment 696185 --> http://bugzilla.opensuse.org/attachment.cgi?id=696185&action=edit Fix permissions on command files. nagios creates the following files with the wrong permissions: # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 13:47 live prw-rw---- 1 nagios nagios 0 Oct 6 13:47 nagios.cmd For nagvis to access them, they need to be in group "nagcmd" srw-rw---- 1 nagios nagcmd 0 Oct 6 13:47 live prw-rw---- 1 nagios nagcmd 0 Oct 6 13:47 nagios.cmd Since "nagios.cmd" is a named pipe, the permission can be changed once to correct it, but "live" needs changing each time "nagios" is run. The following lines in /etc/nagios/nagios.cfg set these files: command_file=/var/spool/nagios/nagios.cmd broker_module=/usr/lib/check_mk/livestatus-nagios4.o /var/spool/nagios/live I noticed that the file "/usr/lib/nagios/nagios-exec-start-pre" tried to set these permissions by setting the variable nagios_cmdgrp. nagios_cmdgrp="$(get_var nagios_cmdgrp)" but nagois_cmdgrp isn't in /etc/nagios/nagios.cfg. It can't be added as nagios complains about an unknown definition and won't start. Also the line : ${nagios_cmdgrp:-nagcmd} doesn't seem to work for me when /bin/sh is linked to bash /bin/sh --version GNU bash, version 4.2.47(1)-release (x86_64-suse-linux-gnu) nagios_cmdgrp="" echo $nagios_cmdgrp : ${nagios_cmdgrp:-nagcmd} echo $nagios_cmdgrp : ${nagios_cmdgrp:=nagcmd} echo $nagios_cmdgrp nagcmd nagios_cmdgrp="xxxx" : ${nagios_cmdgrp:=nagcmd} echo $nagios_cmdgrp xxxx Unfortunately changing : ${nagios_cmdgrp:-nagcmd} to : ${nagios_cmdgrp:=nagcmd} doesn't fix the permissions on the command files # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 14:16 live prw-rw---- 1 nagios nagios 0 Oct 6 14:16 nagios.cmd as these are created after the process "nagios" starts. A workaround is to add the line ExecStartPost=/usr/lib/nagios/nagios-exec-start-post to nagios.service. I have attached the nagios-exec-start-post script. This works with # systemctl start nagios.service # systemctl restart nagios.service but for # systemctl reload nagios.service I get the wrong permissions: # ls -l /var/spool/nagios/ srw-rw---- 1 nagios nagios 0 Oct 6 14:23 live prw-rw---- 1 nagios nagcmd 0 Oct 6 14:16 nagios.cmd These are the nagios packages I installed: nagios-4.2.1-1.1.x86_64 nagios-www-4.2.1-1.1.x86_64 nagios-www-dch-4.2.1-1.1.x86_64 pnp4nagios-0.6.25-6.24.x86_64 pnp4nagios-nagios-0.6.25-6.24.x86_64 nagvis-1.8.5-3.1.noarch mk-livestatus-1.2.8p11-3.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1029970] New: ksh has binaries in /bin
by bugzilla_noreply＠novell.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029970 Bug ID: 1029970 Summary: ksh has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ksh has binaries in /bin ksh is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1029976] New: sysvinit-tools has binaries in /bin
by bugzilla_noreply＠novell.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1029976 Bug ID: 1029976 Summary: sysvinit-tools has binaries in /bin 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- sysvinit-tools is one of the remaining packages in Tumbleweed to install binaries to /bin. Please make sure all binaries previously in /usr go to %_bindir (aka /usr/bin), and /bin contains a symlink to those. See https://bugzilla.opensuse.org/show_bug.cgi?id=1029961 for an overview. If you need assistance, don't hesitate to ask. General discussions should happen in the meta bug (see previous link). -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1051429] New: docker and runc failed to build with kernel 4.12 on ppc64le
by bugzilla_noreply＠novell.com 30 Apr '21

30 Apr '21

http://bugzilla.suse.com/show_bug.cgi?id=1051429 Bug ID: 1051429 Summary: docker and runc failed to build with kernel 4.12 on ppc64le Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de CC: asarai(a)suse.com, jmassaguerpla(a)suse.com, jslaby(a)suse.com, normand(a)linux.vnet.ibm.com Found By: --- Blocker: --- Currently we see docker[1] and runc[2] failed to build with kernel 4.12[3] in the staging project, and it does happened only on ppc64le build. [1] https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… [2] https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… [3] https://build.opensuse.org/request/show/512894 -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 986593] New: security/john: Tools in run/ not packaged and undefined maintainer of john
by bugzilla_noreply＠novell.com 25 Apr '21

25 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=986593 Bug ID: 986593 Summary: security/john: Tools in run/ not packaged and undefined maintainer of john Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: meissner(a)suse.com Found By: --- Blocker: --- The tools which are in run/ in the jumbo-repository[2] are not packaged. The tools like pdf2john.py (and other *2john programs) are very helpful (or essential) to work with john. Beside packing them into the john-package, another possibility would be to create a john-tools package. Which variant do you prefer? (I can help with packaging in July) And: The mentioned maintainer-email on OBS (solar(a)false.com) is not reachable (no MX or A record for that domain. And: By clicking "report bug" on https://build.opensuse.org/package/show/security/john "lars.vogdt(a)microfocus.dmm" was assigned, but bugzilla did not accept this input. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1028399] New: zypper could use a function to show package version release notes, like `dnf updateinfo info`
by bugzilla_noreply＠novell.com 23 Apr '21

23 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1028399 Bug ID: 1028399 Summary: zypper could use a function to show package version release notes, like `dnf updateinfo info` Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: pointedstick(a)zoho.com QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- I'm using OpenSUSE Tumbleweed. Some updated packages are available, and I want to read their release notes so I can find out what's changing. On Fedora, I would do the following: `dnf updateinfo --refresh info <package name, or empty to see all>` zypper doesn't seem to have a similar feature, which is a shame! It should. -- You are receiving this mail because: You are on the CC list for the bug.

2 4