December 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1154091] opencv-devel is broken with "No rule to make target 'opencv_calib3d-NOTFOUND"
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1154091 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:11659:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1154091] opencv-devel is broken with "No rule to make target 'opencv_calib3d-NOTFOUND"
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1154091 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:12924:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1047247] chkstat tool can be tricked into trying to interpret the shell environment as a permissions file
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1047247 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:13182:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1142988] networking problems using cloud-init in leap 15.1 images
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1142988 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:13090:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078466] systemd: duplicated entries in tmpfiles.d
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1078466 http://bugzilla.suse.com/show_bug.cgi?id=1078466#c36 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ro(a)suse.com Flags|needinfo?(lnussel(a)suse.com) | --- Comment #36 from Ludwig Nussel <lnussel(a)suse.com> --- I don't see myself as maintainer of aaa_base but looks like there simply is no perfect solution yet and aaa_base accumulates all kinds of crap anyways so as long as we have some central place, why not. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155687] New: Bad install when using Tumbleweed live iso (20191030)
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1155687 Bug ID: 1155687 Summary: Bad install when using Tumbleweed live iso (20191030) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0 Build Identifier: I was alerted to this via a forum post: https://forums.opensuse.org/showthread.php/538068-You-can-t-install-from-th… So I downloaded the KDE live iso to give it a try. I mostly went with defaults for installing KDE, except that I used "ext4" for root and "/home". This was in a KVM virtual machine. The install itself seemed to go fine. The one peculiarity was that, at the end, it said it would reboot. But this was install from a live system, so of course it just dropped back to the live system instead of rebooting. The real problem came when I attempted to boot the newly installed system. I finished up with a black screen. Retrying, with " 3" at the end of the kernel bootline, I did successfully boot to a command line. There were several failure messages during boot. The seemed to indicate that some required system users and system groups were missing. I will attach Yast logs for the install, and a copy of the installed "/etc/passwd" and "/etc/group". Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 976985] New: tcl plugin for firefox throws error "undefined symbol: Tcl_Init"
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=976985 Bug ID: 976985 Summary: tcl plugin for firefox throws error "undefined symbol: Tcl_Init" 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: hguo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a freshly installed tumbleweed snapshot 20160417. When starting firefox while tclplug is installed, an error is printed in the firefox output: LoadPlugin: failed to initialize shared library /usr/lib64/browser-plugins/libnptcl3.1.so [/usr/lib64/browser-plugins/libnptcl3.1.so: undefined symbol: Tcl_Init] Hence the plugin is not usable. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1157498] permissions.secure: mismatch between comment and content
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1157498 http://bugzilla.suse.com/show_bug.cgi?id=1157498#c5 --- Comment #5 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1157498) was mentioned in https://build.opensuse.org/request/show/754442 Factory / permissions -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137688] yast2 tune: store sysrq setting in /etc/sysctl.d/
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1137688 http://bugzilla.suse.com/show_bug.cgi?id=1137688#c16 S. B. <sb56637(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sb56637(a)gmail.com | |) | --- Comment #16 from S. B. <sb56637(a)gmail.com> --- (In reply to Imobach Gonzalez Sosa from comment #15) > Actually, you could even try to load system settings with "sysctl --system". > It should give you a clue about where it is reading the values from. Ah yes, that helped: sysctl --system * Applying /boot/sysctl.conf-5.3.12-1-default ... kernel.hung_task_timeout_secs = 0 kernel.msgmax = 65536 kernel.msgmnb = 65536 kernel.shmmax = 0xffffffffffffffff kernel.shmall = 0x0fffffffffffff00 vm.dirty_ratio = 20 * Applying /etc/sysctl.d/30-yast.conf ... kernel.sysrq = 1 net.ipv4.ip_forward = 0 net.ipv6.conf.all.forwarding = 0 net.ipv4.tcp_syncookies = 1 * Applying /usr/lib/sysctl.d/50-default.conf ... net.ipv4.icmp_echo_ignore_broadcasts = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 net.ipv6.conf.default.use_tempaddr = 1 fs.inotify.max_user_watches = 65536 kernel.sysrq = 184 dev.cdrom.autoclose = 0 fs.protected_hardlinks = 1 fs.protected_symlinks = 1 kernel.kptr_restrict = 1 * Applying /usr/lib/sysctl.d/51-network.conf ... net.ipv4.conf.all.accept_redirects = 0 net.ipv4.conf.default.accept_redirects = 0 net.ipv4.conf.all.accept_source_route = 0 net.ipv4.conf.default.accept_source_route = 0 net.ipv6.conf.all.accept_redirects = 0 net.ipv6.conf.default.accept_redirects = 0 * Applying /etc/sysctl.d/99-sysctl.conf ... vm.swappiness = 1 vm.vfs_cache_pressure = 50 vm.dirty_background_bytes = 16777216 vm.dirty_bytes = 33554432 * Applying /etc/sysctl.conf ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124922] Service systemd-remount-fs.service failing often on transactional-update system
by bugzilla_noreply＠novell.com 05 Dec '19

05 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1124922 http://bugzilla.suse.com/show_bug.cgi?id=1124922#c8 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(okurz(a)suse.com) | --- Comment #8 from Oliver Kurz <okurz(a)suse.com> --- I am not aware of the problem reproducible in openQA tests. The problem was reported happening on the openQA *worker* machines, i.e. the machines *executing* the openQA tests. I checked on the machine openqaworker1.o.o and found in the service journal of systemd-remount-fs: ``` -- Reboot -- Nov 24 03:33:33 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Nov 25 03:31:13 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Nov 25 03:33:54 openqaworker1 systemd-remount-fs[784]: mount: /: mount point is busy. Nov 25 03:33:54 openqaworker1 systemd-remount-fs[784]: /usr/bin/mount for / exited with exit status 32. Nov 25 03:33:54 openqaworker1 systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Nov 25 03:33:54 openqaworker1 systemd[1]: Failed to start Remount Root and Kernel File Systems. Nov 25 03:33:54 openqaworker1 systemd[1]: systemd-remount-fs.service: Unit entered failed state. Nov 25 03:33:54 openqaworker1 systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. -- Reboot -- Nov 26 03:34:27 openqaworker1 systemd-remount-fs[793]: mount: /: mount point is busy. Nov 26 03:34:27 openqaworker1 systemd-remount-fs[793]: /usr/bin/mount for / exited with exit status 32. Nov 26 03:34:27 openqaworker1 systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE Nov 26 03:34:27 openqaworker1 systemd[1]: Failed to start Remount Root and Kernel File Systems. Nov 26 03:34:27 openqaworker1 systemd[1]: systemd-remount-fs.service: Unit entered failed state. Nov 26 03:34:27 openqaworker1 systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'. -- Reboot -- Nov 27 03:33:40 openqaworker1 systemd-remount-fs[801]: mount: /: mount point is busy. -- Reboot -- Nov 28 03:34:26 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Nov 29 03:31:20 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Nov 29 03:34:02 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Nov 30 03:31:43 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Nov 30 03:34:26 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Dec 01 03:31:45 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Dec 01 03:34:28 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Dec 03 03:30:21 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Dec 03 03:39:05 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Dec 04 03:31:45 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Dec 04 03:34:27 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Dec 05 03:30:17 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Dec 05 03:39:01 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Dec 05 13:00:50 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Dec 05 13:03:33 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. Dec 05 13:25:25 openqaworker1 systemd[1]: Stopped Remount Root and Kernel File Systems. -- Reboot -- Dec 05 13:28:07 openqaworker1 systemd[1]: Started Remount Root and Kernel File Systems. lines 179-236/236 (END) ``` so we were either "lucky" since Nov 27 or the problem has gone away recently. This seems to be supported by the other machines: ``` for i in aarch64 openqaworker1 openqaworker4 power8 imagetester rebel; do echo $i && ssh root@$i "journalctl -u systemd-remount-fs | grep 'busy' | tail -n 3"; done aarch64 openqaworker1 Nov 25 03:33:54 openqaworker1 systemd-remount-fs[784]: mount: /: mount point is busy. Nov 26 03:34:27 openqaworker1 systemd-remount-fs[793]: mount: /: mount point is busy. Nov 27 03:33:40 openqaworker1 systemd-remount-fs[801]: mount: /: mount point is busy. openqaworker4 Nov 24 03:34:09 openqaworker4 systemd-remount-fs[797]: mount: /: mount point is busy. Nov 26 03:33:44 openqaworker4 systemd-remount-fs[798]: mount: /: mount point is busy. Nov 27 03:33:27 openqaworker4 systemd-remount-fs[797]: mount: /: mount point is busy. power8 imagetester rebel Nov 23 03:32:31 rebel systemd-remount-fs[600]: mount: /: mount point is busy. Nov 27 03:32:34 rebel systemd-remount-fs[596]: mount: /: mount point is busy. Nov 28 03:32:31 rebel systemd-remount-fs[601]: mount: /: mount point is busy. ``` are you aware of any recent fixes which could coincide with this timeframe? -- You are receiving this mail because: You are on the CC list for the bug.

1 0