November 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1153239] segfault in libgc.so
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1153239 http://bugzilla.opensuse.org/show_bug.cgi?id=1153239#c4 Tom de Vries <tdevries(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|segfault in libgc.so when |segfault in libgc.so |guile app linked with gold | --- Comment #4 from Tom de Vries <tdevries(a)suse.com> --- On tumbleweed: ... $ cat test.c #include "gc.h" int main (void) { GC_INIT (); return 0; } ... compiled like: ... $ gcc test.c -lgc ... ... $ ./a.out; echo $? 0 ... and: ... $ gdb -q -ex run --args ./a.out Reading symbols from ./a.out... Starting program: a.out [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. GC_find_limit_with_bound (bound=0x0, up=0, p=<optimized out>) at extra/../os_dep.c:1011 1011 GC_noop1((word)(*result)); (gdb) bt #0 GC_find_limit_with_bound (bound=0x0, up=0, p=<optimized out>) at extra/../os_dep.c:1011 #1 0x00007ffff7d4de83 in GC_find_limit (up=0, p=<optimized out>) at extra/../os_dep.c:1023 #2 GC_init_linux_data_start () at extra/../os_dep.c:463 #3 GC_init_linux_data_start () at extra/../os_dep.c:430 #4 GC_init () at extra/../misc.c:1190 #5 GC_init () at extra/../misc.c:901 #6 0x000000000040112f in main () ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191384] kernel-source: Move rpm macros to %_rpmmacrodir
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191384 http://bugzilla.opensuse.org/show_bug.cgi?id=1191384#c10 --- Comment #10 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1191384) was mentioned in https://build.opensuse.org/request/show/928854 15.2 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191229] New: [Staging][rpm4.17] Kernel fails to build with rpm 4.17
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191229 Bug ID: 1191229 Summary: [Staging][rpm4.17] Kernel fails to build with rpm 4.17 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- RPM 4.17 has been submitted for inclusion into Tumbleweed. There is at least one backwards incompatible change that affects the kernel builds. The build fails with: [ 134s] error: /home/abuild/rpmbuild/SOURCES/kernel-source.spec: line 130: %verbose: unexpected argument [ 134s] 2< (%verbose) The problem there is that %{verbose} is no longer a 'function' taking an argument, but rather a variable, set to 0/1. In other packages where we encountered this issue, we simply gave up on the construct of using verbose to adjust the build log level -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1172073] New: kernel-devel and kernel-source need Obsolete for previous package rebuilds of the same version
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1172073 Bug ID: 1172073 Summary: kernel-devel and kernel-source need Obsolete for previous package rebuilds of the same version Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel-devel and kernel-source both provide multiversion(kernel) so zypper tries to install multiple versions in parallel instead of updating them. Different kernel versions are installed in different locations, but when kernel package is rebuilt it has the same kernel version but different RPM release. So two packages that differ only in second digit RPM release cannot really be installed side by side - they either conflict or they contain exactly the same files. Binary kernel packages include Obsoletes for package rebuilds: bor@tw:~> rpm -q --obsoletes kernel-default-devel-5.6.12-1.3 kernel-bigsmp-devel <= 3.1 kernel-default-devel = 5.6.12-1.1 kernel-default-devel = 5.6.12-1.2 which forces zypper to remove previous package rebuilds for the same kernel version even though it normally would try to install all of them. These obsoletes are not included in kernel-devel or kernel-source, so zypper installs all of them. This does not fail because they are pure source packages and contain exactly the same files which is allowed by RPM. But this is rather confusing as in reality they are not installed "side by side" - the last installed version overwrites all files. This also triggers https://bugzilla.opensuse.org/show_bug.cgi?id=1171224, where zypper fails to removed those extra packages. bor@tw:~> rpm -qa kernel-devel kernel-devel-5.5.9-1.2.noarch kernel-devel-5.5.7-1.1.noarch kernel-devel-5.4.10-1.1.noarch kernel-devel-5.6.2-1.2.noarch kernel-devel-5.6.11-1.4.noarch kernel-devel-5.6.11-1.2.noarch kernel-devel-5.6.4-1.1.noarch kernel-devel-5.6.12-1.3.noarch bor@tw:~> I'd say for consistency all kernel packages, both source and binary, should have the same set of Obsoletes for the package rebuilds. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1192275] New: munin-node: hddtemp_smartctl broken
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192275 Bug ID: 1192275 Summary: munin-node: hddtemp_smartctl broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: martin(a)oneiros.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since upgrading munin-node today, the hddtemp_smartctl doesn't graph any new values. /var/log/munin/munin-node.log is filled with these errors: 2021/11/02-21:40:33 [22215] Error output from hddtemp_smartctl: 2021/11/02-21:40:33 [22215] [ERROR] Command /usr/sbin/smartctl -A --nocheck=standby /dev/sda on drive sda failed with exit(2): Smartctl open device: /dev/sda failed: No such device at /etc/munin/plugins/hddtemp_smartctl line 274. 2021/11/02-21:40:33 [22215] [ERROR] Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdb on drive sdb failed with exit(2): Smartctl open device: /dev/sdb failed: No such device at /etc/munin/plugins/hddtemp_smartctl line 274. 2021/11/02-21:40:33 [22215] [ERROR] Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdc on drive sdc failed with exit(2): Smartctl open device: /dev/sdc failed: No such device at /etc/munin/plugins/hddtemp_smartctl line 274. 2021/11/02-21:40:33 [22215] [ERROR] Command /usr/sbin/smartctl -A --nocheck=standby /dev/sdd on drive sdd failed with exit(2): Smartctl open device: /dev/sdd failed: No such device at /etc/munin/plugins/hddtemp_smartctl line 274. 2021/11/02-21:40:33 [22215] [ERROR] Command /usr/sbin/smartctl -A --nocheck=standby /dev/sde on drive sde failed with exit(2): Smartctl open device: /dev/sde failed: No such device at /etc/munin/plugins/hddtemp_smartctl line 274. It was working before. The config is [hddtemp_smartctl] user root It works with munin-run: > sudo munin-run hddtemp_smartctl sda.value 40 sdb.value 37 sdc.value 36 sdd.value 35 sde.value 29 > rpm -qi munin-node Name : munin-node Version : 2.0.66 Release : lp152.71.1 Architecture: noarch Install Date: Di 02 Nov 2021 18:35:52 CET Group : System/Monitoring Size : 1508608 License : GPL-2.0-only Signature : DSA/SHA1, Di 02 Nov 2021 14:31:03 CET, Key ID a5c23697ee454f98 Source RPM : munin-2.0.66-lp152.71.1.src.rpm Build Date : Di 02 Nov 2021 14:30:42 CET Build Host : old-atreju5 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/server:monitoring URL : http://munin-monitoring.org/ Summary : Network-wide graphing framework (node) Description : Munin is a highly flexible and powerful solution used to create graphs of virtually everything imaginable throughout your network, while still maintaining a rattling ease of installation and configuration. This package contains node software. You should install it on all the nodes in your network. It will know how to extract all sorts of data from the node it runs on, and will wait for the gatherer to request this data for further processing. It includes a range of plugins capable of extracting common values such as cpu usage, network usage, load average, and so on. Creating your own plugins which are capable of extracting other system-specific values is very easy, and is often done in a matter of minutes. You can also create plugins which relay information from other devices in your network that can't run Munin, such as a switch or a server running another operating system, by using SNMP or similar technology. Munin is written in Perl, and relies heavily on Tobi Oetiker's excellent RRDtool. To see a real example of Munin in action, take a peek at <http://www.linpro.no/projects/munin/example/>. Distribution: server:monitoring / openSUSE_Leap_15.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1168628] New: network:cluster/warewulf: Bug on vnfs-SUSE-Make-sure-no-repos-are-left-over-when-adding-a-list-of-repositories.patch
by bugzilla_noreply＠novell.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1168628 Bug ID: 1168628 Summary: network:cluster/warewulf: Bug on vnfs-SUSE-Make-sure-no-repos-are-left-over-when-adding -a-list-of-repositories.patch Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: burnus(a)gmx.de Reporter: runappz(a)gmail.com QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: eich(a)suse.com, scorot(a)free.fr Found By: --- Blocker: --- Reused $i in bash script, which was firstly declared as number and then as string. The following patch should fix this. --- vnfs-SUSE-Make-sure-no-repos-are-left-over-when-adding-a-list-of-repositories.patch +++ vnfs-SUSE-Make-sure-no-repos-are-left-over-when-adding-a-list-of-repositories.patch.new @@ -38,8 +38,8 @@ + done + + cnt=0 -+ for i in `echo $ZYP_MIRROR | sed -e 's/,/ /'`; do -+ $ZYP_CMD ar $i repo-$((cnt++)) ++ for repourl in `echo $ZYP_MIRROR | sed -e 's/,/ /'`; do ++ $ZYP_CMD ar $repourl repo-$((cnt++)) + done + fi + -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1192178] AutoYaST <authorized_key> not working on openSUSE Tumbleweed
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192178 https://bugzilla.suse.com/show_bug.cgi?id=1192178#c3 --- Comment #3 from David Diaz <dgonzalez(a)suse.com> --- (In reply to Jos� Iv�n L�pez Gonz�lez from comment #1) > David, could you please check if this is related with your fix here [1]? > Thanks! Somehow it _was_, but unfortunately this fix itself isn't enough to avoid the described problem. I suspect that we have another check [1] that should be improved in order to have it working as expected during (auto)installation too. I'll continue investigating it. [1] https://github.com/yast/yast-users/blob/f6d4a583ee13c16201145bf68e2f2028e55… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188143] Firewall Zone-Interface association not applied with "Reload"
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188143 https://bugzilla.suse.com/show_bug.cgi?id=1188143#c5 Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez(a)suse.com Flags| |needinfo?(jreidinger(a)suse.c | |om) --- Comment #5 from Jos� Iv�n L�pez Gonz�lez <jlopez(a)suse.com> --- Any feedback here? Josef, if no feedback, do you think YaST should use `firewall-cmd --reload`? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192091] 5.14.14 assumes USB controller as dead
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192091 https://bugzilla.suse.com/show_bug.cgi?id=1192091#c3 --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- FWIW, the test kernel is available at http://download.opensuse.org/repositories/home:/tiwai:/bsc1192091/standard/ It's be appreciated if you can test it quickly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188264] New: VUL-0: CVE-2021-32747: icingaweb2: custom variables are exposed to unauthorized users
by bugzilla_noreply＠suse.com 02 Nov '21

02 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188264 Bug ID: 1188264 Summary: VUL-0: CVE-2021-32747: icingaweb2: custom variables are exposed to unauthorized users Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other URL: https://smash.suse.de/issue/303774/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: nix(a)opensuse.org Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2021-32747 Icinga Web 2 is an open source monitoring web interface, framework, and command-line interface. A vulnerability in which custom variables are exposed to unauthorized users exists between versions 2.0.0 and 2.8.2. Custom variables are user-defined keys and values on configuration objects in Icinga 2. These are commonly used to reference secrets in other configurations such as check commands to be able to authenticate with a service being checked. Icinga Web 2 displays these custom variables to logged in users with access to said hosts or services. In order to protect the secrets from being visible to anyone, it's possible to setup protection rules and blacklists in a user's role. Protection rules result in `***` being shown instead of the original value, the key will remain. Backlists will hide a custom variable entirely from the user. Besides using the UI, custom variables can also be accessed differently by using an undocumented URL parameter. By adding a parameter to the affected routes, Icinga Web 2 will show these columns additionally in the respective list. This parameter is also respected when exporting to JSON or CSV. Protection rules and blacklists however have no effect in this case. Custom variables are shown as-is in the result. The issue has been fixed in the 2.9.0, 2.8.3, and 2.7.5 releases. As a workaround, one may set up a restriction to hide hosts and services with the custom variable in question. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-32747 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32747 https://github.com/Icinga/icingaweb2/releases/tag/v2.7.5 https://github.com/Icinga/icingaweb2/releases/tag/v2.8.3 https://github.com/Icinga/icingaweb2/security/advisories/GHSA-2xv9-886q-p7xx https://github.com/Icinga/icingaweb2/releases/tag/v2.9.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 1