March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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

[Bug 1023335] New: X11:Deepin: Deepin Desktop Environment for X11:Deepin?
by bugzilla_noreply＠novell.com 20 Apr '21

20 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1023335 Bug ID: 1023335 Summary: X11:Deepin: Deepin Desktop Environment for X11:Deepin? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: i(a)marguerite.su Reporter: sb56637(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Hello X11:Deepin maintainers, Would it be possible to package the latest version of the Deepin Desktop Environment for openSUSE Leap 42.2 and Tumbleweed? DDE appears to be quite portable now, and it is working extremely well on Arch and Manjaro. There are also several sources of RPM spec files for Fedora that should be relatively easy to compile for openSUSE: https://github.com/FZUG/repo/tree/master/rpms/deepin_project https://github.com/cz-guardian/fedora-deepin/ https://copr.fedorainfracloud.org/coprs/mosquito/deepin/ https://copr.fedorainfracloud.org/coprs/jstepanek/deepin/ I release SuseStudio images of openSUSE Leap and Tumbleweed, and I would love to offer a Deepin version as well. Thanks a lot, Sam -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 927268] New: clang link fails with undefined reference to `__stack_chk_guard'
by bugzilla_noreply＠novell.com 18 Apr '21

18 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=927268 Bug ID: 927268 Summary: clang link fails with undefined reference to `__stack_chk_guard' Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: PowerPC-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dap(a)open.by QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 631137 --> http://bugzilla.opensuse.org/attachment.cgi?id=631137&action=edit Full build log. Upstream report: https://llvm.org/bugs/show_bug.cgi?id=22248 My build log error: [ 35s] CMakeFiles/huffar.dir/compress.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] CMakeFiles/huffar.dir/extract.c.o:(.toc+0x0): undefined reference to `__stack_chk_guard' [ 35s] clang-3.5: error: linker command failed with exit code 1 (use -v to see invocation) [ 35s] CMakeFiles/huffar.dir/build.make:163: recipe for target 'huffar' failed [ 35s] make[2]: *** [huffar] Error 1 Check attachment for full log. #opensuse-ppc(a)irc.freenode.net: k0da: dark_ss, it seems you've hit an LLVM bug. It adds extra symbol. k0da: dark_ss, you can open an opensuse bug though for that issue. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1059012] New: Since upgrade to GNOME 3.26, gnome-shell crashes and reloads upon unlocking screen
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1059012 Bug ID: 1059012 Summary: Since upgrade to GNOME 3.26, gnome-shell crashes and reloads upon unlocking screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Every time when unlocking a locked screen, gnome-shell crashes and spits the following journal log entries: SSep 17 16:50:16 gnome-shell[8734]: Allocating size to ShellEmbeddedWindow 0x5628e771a970 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: gtk_widget_get_window: assertion 'GTK_IS_WIDGET (widget)' failed Sep 17 16:50:16 gnome-shell[8734]: Allocating size to ShellEmbeddedWindow 0x5628e771ac30 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Sep 17 16:50:20 kernel: gnome-shell[8734]: segfault at 600287 ip 00007f2eb28d07f6 sp 00007ffd1db9dd50 error 4 in libgobject-2.0.so.0.5400.0[7f2eb289a000+53000] Sep 17 16:50:20 systemd[1]: Started Process Core Dump (PID 9154/UID 0). Sep 17 16:50:20 systemd-coredump[9155]: Resource limits disable core dumping for process 8734 (gnome-shell). Sep 17 16:50:20 systemd-coredump[9155]: Process 8734 (gnome-shell) of user 1000 dumped core. Sep 17 16:50:20 polkitd[868]: Unregistered Authentication Agent for unix-session:1 (system bus name :1.276, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_GB.UTF-8) (disconnected from bus Sep 17 16:50:20 gnome-session-binary[1661]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 17 16:50:20 gnome-session[1661]: gnome-session-binary[1661]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 -- You are receiving this mail because: You are on the CC list for the bug.

2 9