April 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1186005] New: "postconf: fatal: parameter inet_interfaces: no local interface found for ::1" update upgrade
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1186005 Bug ID: 1186005 Summary: "postconf: fatal: parameter inet_interfaces: no local interface found for ::1" update upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running `zypper dup` for current Tumbleweed, but also for previous rounds of upgrades, I noticed postfix is issuing fatal errors. My system has IPv6 disabled, i.e., is running IPv4 only. (327/422) Installing: postfix-3.5.10-1.2.x86_64 ...[done] Additional rpm output: postconf: fatal: parameter inet_interfaces: no local interface found for ::1 Executing upgrade-configuration. /usr/sbin/postconf: fatal: parameter inet_interfaces: no local interface found for ::1 Updating /etc/sysconfig/postfix ... Updating /etc/sysconfig/mail ... -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1197991] New: VUL-1: CVE-2022-1207: radare2: Out-of-bounds read allows reading sensitive information
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197991 Bug ID: 1197991 Summary: VUL-1: CVE-2022-1207: radare2: Out-of-bounds read allows reading sensitive information Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/327886/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: stefan.bruens(a)rwth-aachen.de Reporter: cahu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-1207 Out-of-bounds read in GitHub repository radareorg/radare2 prior to 5.6.8. This vulnerability allows attackers to read sensitive information from outside the allocated buffer boundary. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-1207 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1207 https://github.com/radareorg/radare2/commit/605785b65dd356d46d4487faa41dbf9… https://huntr.dev/bounties/7b979e76-ae54-4132-b455-0833e45195eb -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1197980] Compose key does not work as expected on Swiss Keyboard (same as bug 1142273 for OS 15.1)
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197980 https://bugzilla.suse.com/show_bug.cgi?id=1197980#c10 --- Comment #10 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. So this means we never made an update for Leap 15.1 (boo# 1142273) and didn't fix it for Leap 15.2/15.3 either apparently. Looks like things haved changed in Leap 15.3 already since Leap 15.1, so my workaround from https://bugzilla.suse.com/show_bug.cgi?id=1142273#c19 doesn't work on Leap 15.3 either. :-( -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197964] New: regression: salt-minion sign-in failure after update
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197964 Bug ID: 1197964 Summary: regression: salt-minion sign-in failure after update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Salt Assignee: salt-maintainers(a)suse.de Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I use salt to manage a mixture of Leap and Tumbleweed hosts. Because salt-minions can connect to newer masters, but not the other way around, I use Tumbleweed to host my master. Since the recent upgrade to salt-minion-3002.2-150300.53.10.1.x86_64 on my Leap minions, they fail to connect to the master, with the following error (somewhat cut down, as indicated by ellipsis): Apr 02 13:22:51 dogprod salt-minion[9971]: [ERROR ] Error while bringing up minion for multi-master. Is master at master1 responding? Apr 02 13:23:01 dogprod salt-minion[9971]: [ERROR ] Sign-in attempt failed: {'enc': 'pub', 'pub_key': '-----BEGIN PUBLIC KEY-----\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzS6pLmz10lMkgNZVUauW\nMv3GvjpiR+pQQzgXP9qgTJHhb01Hw2MM0ociT2a+GjLFq6fF9PHQ9DHDUM0aw55+\n7LYIUbrdZJ1n8J02Sknd5pfZdDjOGzsI6t409loNX98FD9EI7m1jP4iCzeSFmjrG\nWU0ZGUw2Th58ZE7zn+CFiy7Sws/B/D2yIRoKB58v+Cri9pUJMmA7T/e2/JGEKPle\nz8ENYYmx21AlTgyLZibPc7T17LgiF7od+sTlSKYW9Y/q0pKR/ZUJb9I9YIdh/eDS\nYz2cz5h41F9qMfoZFYJ0Ao6DVbAw2KbNq9Hkwyq+qdLTwEAO7AX0mbJyNlOlRK4V\n5QIDAQAB\n-----END PUBLIC KEY-----\n', 'publish_port': 4505, 'token': b"\xd6\xc75.$\n\x02\xb8\x9b\t\x89[\xe8\xbag@\x9f\xdaW\xc6\x95\xe5iB\xfd\x06\x98fD\nd}...", 'aes': b'\xa1\xab\xceu\x1eg;g\xe3\xe0\xd8\xf4g\xc7\x93\xb2\xfd\xab\xa8`\x00\xb7\xee\xee\x0f(}V|6(\x9d)\x0e\xf3...', 'sig': b'!J\xd6\xa1\x9c\xe2\xa4\xd2p\x1a\x91\x02\xeek\xae-\x95\xa1\x8b...'} I have tried to clear all caches and start with freshly generated PKI material, but it doesn't help. The minion configuration is minimal: state_output: changes state_output_diff: True master: master1 The master configuration is similarly sparse, except it also defines some GitFS sources for states and pillar data. Reverting the Leap minions back to salt-minion-3002.2-150300.53.7.2.x86_64 fixes the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1197627] [RPI] Unexpected XHCI event TRB
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197627 Matthias Brugger <mbrugger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Bootloader Assignee|kernel-bugs(a)opensuse.org |mbrugger(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197980] Compose key does not work as expected on Swiss Keyboard (same as bug 1142273 for OS 15.1)
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197980 https://bugzilla.suse.com/show_bug.cgi?id=1197980#c9 --- Comment #9 from Stefan Hundhammer <shundhammer(a)suse.com> --- For 15.4, we did a major change in this area; hopefully that fixes this Swiss keyboard as well: https://github.com/yast/yast-country/blob/master/keyboard/src/lib/y2keyboar… { "description" => _("German (Switzerland)"), "alias" => "german-ch", "code" => "ch", "legacy_code" => "sg-latin1", "suggested_for_lang" => ["de_CH"] }, as part of https://github.com/yast/yast-country/pull/288 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197779] lvm extent size can be 4GB or greater
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197779 https://bugzilla.suse.com/show_bug.cgi?id=1197779#c10 --- Comment #10 from Arvin Schnell <aschnell(a)suse.com> --- (In reply to Liencres from comment #9) > The LVs created seem to inherit the default_extent_size of 4MiB, rather than > the existing extent size, which is what I expected. I'm guessing this may > be due to the region call in LvmVg::Impl in storage/Devices/LvnVg.Impl* > (which may also need the ULL_HACK). It works for me. I checked the block size of the generated logical volume after using the YaST partitioner by looking in /var/log/YaST2/storage in the file 04-committed.xml. Also all the relevant calls in Lvm{Vg/Lv} seem to use the ULL_HACK. Surely there could still be problems with AutoYaST. But for that the autoinst.xml file and the complete YaST logs are needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197896] [Build 20220328] openQA test fails in yast2_samba
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1197896 https://bugzilla.suse.com/show_bug.cgi?id=1197896#c3 William Brown <william.brown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(william.brown@sus | |e.com) | --- Comment #3 from William Brown <william.brown(a)suse.com> --- (In reply to Samuel Cabrero from comment #2) > The problem is the samba schema bundled with 389-ds does not have this > attribute definition: > > Openldap schema in samba-doc: > > # grep -i sambaminpwdlength /usr/share/doc/packages/samba/examples/LDAP/samba.ldif > > olcAttributeTypes: {35}( 1.3.6.1.4.1.7165.2.1.58 NAME 'sambaMinPwdLength' DESC > > ase $ sambaMinPwdLength $ sambaPwdHistoryLength $ sambaLogonToChgPwd $ sambaM > > # > > 389-ds bundled samba schemas: > > > # grep -i sambaminpwdlength /usr/share/dirsrv/schema/60samba3.ldif > > # > > # grep -i sambaminpwdlength /usr/share/dirsrv/data/60samba.ldif > > # > @William, pull request to https://github.com/389ds/389-ds-base right? The team is a bit picky about the format of commit messages and how the pr's are done, so I've done this on your behalf. https://github.com/389ds/389-ds-base/pull/5248 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197985] New: double free in libldap since upgrading to 2.5.9 on dlclose
by bugzilla_noreply＠suse.com 03 Apr '22

03 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197985 Bug ID: 1197985 Summary: double free in libldap since upgrading to 2.5.9 on dlclose Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007f477d53b1e3 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78 #2 0x00007f477d4eb306 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007f477d4d4813 in __GI_abort () at abort.c:79 #4 0x00007f477d52e1b7 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f477d674618 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #5 0x00007f477d545c9c in malloc_printerr (str=str@entry=0x7f477d677260 "double free or corruption (out)") at malloc.c:5664 #6 0x00007f477d547ef0 in _int_free (av=0x7f477d6aeaa0 <main_arena>, p=0x7f47789219e0 <sb_sasl_generic_read+704>, have_lock=<optimized out>) at malloc.c:4588 #7 0x00007f477d54a753 in __GI___libc_free (mem=<optimized out>) at malloc.c:3391 #8 0x00007f477781b6b7 in ldap_int_destroy_global_options () at /usr/src/debug/openldap2-2.5.9-72.1.x86_64/libraries/libldap/init.c:543 #9 0x00007f477da32182 in call_destructors (closure=closure@entry=0x563c1da1e990) at dl-close.c:129 #10 0x00007f477d60ef65 in __GI__dl_catch_exception (exception=exception@entry=0x0, operate=operate@entry=0x7f477da3213e <call_destructors>, args=args@entry=0x563c1da1e990) at /usr/src/debug/glibc-2.35-2.1.x86_64/elf/dl-error-skeleton.c:182 #11 0x00007f477da326b6 in _dl_close_worker (map=map@entry=0x563c1daab7c0, force=force@entry=false) at dl-close.c:292 #12 0x00007f477da3313b in _dl_close (_map=0x563c1daab7c0) at dl-close.c:818 #13 0x00007f477d60ef08 in __GI__dl_catch_exception (exception=exception@entry=0x7ffeaa6fc950, operate=<optimized out>, args=<optimized out>) at /usr/src/debug/glibc-2.35-2.1.x86_64/elf/dl-error-skeleton.c:208 #14 0x00007f477d60efe3 in __GI__dl_catch_error (objname=0x7ffeaa6fc9a8, errstring=0x7ffeaa6fc9b0, mallocedp=0x7ffeaa6fc9a7, operate=<optimized out>, args=<optimized out>) at /usr/src/debug/glibc-2.35-2.1.x86_64/elf/dl-error-skeleton.c:227 #15 0x00007f477d5347ce in _dlerror_run (operate=<optimized out>, args=<optimized out>) at dlerror.c:138 #16 0x00007f477d5344d8 in __dlclose (handle=<optimized out>) at dlclose.c:31 #17 0x00007f4778a15c31 in library_free (library=0x563c1c9769d0) at /home/abuild/rpmbuild/BUILDROOT/rubygem-ffi-1.15.5-1.7.x86_64/usr/lib64/ruby/gems/2.7.0/gems/ffi-1.15.5/ext/ffi_c/DynamicLibrary.c:171 #18 0x00007f477d77d6c5 in run_final (zombie=94816153083400, objspace=0x563c16c39830) at /usr/src/debug/ruby2.7-2.7.5-25.15.x86_64/gc.c:3372 #19 finalize_list (objspace=objspace@entry=0x563c16c39830, zombie=94816153083400) at /usr/src/debug/ruby2.7-2.7.5-25.15.x86_64/gc.c:3391 #20 0x00007f477d77dbaf in rb_objspace_call_finalizer (objspace=0x563c16c39830) at /usr/src/debug/ruby2.7-2.7.5-25.15.x86_64/gc.c:3536 #21 0x00007f477d76fd33 in rb_ec_finalize (ec=0x563c16c39cc0) at /usr/src/debug/ruby2.7-2.7.5-25.15.x86_64/eval.c:152 #22 rb_ec_cleanup (ec=ec@entry=0x563c16c39cc0, ex=<optimized out>) at /usr/src/debug/ruby2.7-2.7.5-25.15.x86_64/eval.c:256 #23 0x00007f477d76ffa2 in ruby_run_node (n=0x563c16c3fef8) at /usr/src/debug/ruby2.7-2.7.5-25.15.x86_64/eval.c:336 #24 0x0000563c1520210b in main (argc=<optimized out>, argv=<optimized out>) at ./main.c:50 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1197984] New: X11:common:Factory/papirus-folders: Error: Unable to find 'adwaita' color in 'Papirus'
by bugzilla_noreply＠suse.com 03 Apr '22

03 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197984 Bug ID: 1197984 Summary: X11:common:Factory/papirus-folders: Error: Unable to find 'adwaita' color in 'Papirus' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the new Adwaita color isn't showing up when running papirus-folders -l and when trying to set it regardless: papirus-folders -C adwaita papirus-folders: Error: Unable to find 'adwaita' color in 'Papirus' -- You are receiving this mail because: You are on the CC list for the bug.

1 4