November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[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 1115436] New: cacti: migrate from cron to systemd timers
by bugzilla_noreply＠novell.com 11 May '21

11 May '21

http://bugzilla.suse.com/show_bug.cgi?id=1115436 Bug ID: 1115436 Summary: cacti: migrate from cron to systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: liedke(a)rz.uni-mannheim.de Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kstreitova(a)suse.com Found By: --- Blocker: --- This bug is part of TRACKERBUG bug#1115430. Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers. It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason. Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service". -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[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 1091516] New: gdm login screen is scaled to 200% apparently
by bugzilla_noreply＠novell.com 10 May '21

10 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1091516 Bug ID: 1091516 Summary: gdm login screen is scaled to 200% apparently Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: wolfgang(a)rosenauer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've got a 14 inch laptop with resolution 2560x1440. My Gnome session settings are to not scale (100%) and I only scale fonts to my needs. Still GDM decides to scale my screen which looks like 200%. Ok, GDM does not know anything about my personal settings at this point but it seems scaling to 200% with the resolution and size as outlined above is quite overkill? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1079832] New: VUL-0: CVE-2018-6789: exim: Buffer overflow in an utility function
by bugzilla_noreply＠novell.com 06 May '21

06 May '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1079832 Bug ID: 1079832 Summary: VUL-0: CVE-2018-6789: exim: Buffer overflow in an utility function Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/199626/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jsegitz(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- Heiko Schlittermann: CVE-2018-6789 Exim 4.90 and earlier =================================== There is a buffer overflow in an utility function, if some pre-conditions are met. Using a handcrafted message, remote code execution seems to be possible. A patch exists already and is being tested. Currently we're unsure about the severity, we *believe*, an exploit is difficult. A mitigation isn't known. Next steps: * t0: Distros will get access to our "security" non-public git repo (based on the SSH keys known to us) * t0 +7d: Patch will be published on the official public git repo t0 will be around 2018-02-08. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6789 http://seclists.org/oss-sec/2018/q1/133 https://exim.org/security/CVE-2018-6789.txt -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1095817] New: containers packages fail randomly due to %check
by bugzilla_noreply＠novell.com 30 Apr '21

30 Apr '21

http://bugzilla.suse.com/show_bug.cgi?id=1095817 Bug ID: 1095817 Summary: containers packages fail randomly due to %check Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We've had tests in the %check section for a long time, but to be honest they've been nothing but a source of trouble. We end up having to run smoke tests anyway, and I'm not aware of a single time %check has actually caught an issue (and it has also caused many issues). So we have to remove it from basically all of our container packages (docker/containerd/runc/docker-libnetwork and the corresponding Kubic packages). -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[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