October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1133122] New: LTO: cmocka build fails
by bugzilla_noreply＠novell.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1133122 Bug ID: 1133122 Summary: LTO: cmocka build fails 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails with: [ 64s] [ LINE ] --- /home/abuild/rpmbuild/BUILD/cmocka-1.1.1/tests/test_group_setup_assert.c:13: error: Failure! It's due to a known issue: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88643 -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1176095] New: pahole segfaults on SLE15 {SP1,SP2} kernel debuginfo
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1176095 Bug ID: 1176095 Summary: pahole segfaults on SLE15 {SP1,SP2} kernel debuginfo Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: tdevries(a)suse.com Reporter: mkoutny(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I saw this on Tumbleweed [1] dwarves-1.17-2.3.x86_64 ## Steps to reproduce: > $ sshfs l3mule.suse.de:/ ~/mule -o follow_symlinks > $ pahole -C mem_cgroup ~/mule/var/cache/crash-setup/15sp2/x86_64/5.3.18-24.9-default ## Expected behavior prints information about given struct ## Actual behavior Loads (16309) of messages like: > tag__recode_dwarf_type: couldn't find 0x734713 type for 0x3e (pointer_type)! > tag__recode_dwarf_type: couldn't find 0x22 type for 0x75 (array_type)! > tag__recode_dwarf_type: couldn't find 0x73472d type for 0x10d (pointer_type)! > tag__recode_dwarf_type: couldn't find 0xf1 type for 0x128 (typedef)! > tag__recode_dwarf_type: couldn't find 0x10d type for 0x15c (const_type)! > tag__recode_dwarf_type: couldn't find 0x14 type for 0x133 (variable)! > [...] > namespace__recode_dwarf_types: couldn't find 0x1d6 type for 0x24c (member)! > namespace__recode_dwarf_types: couldn't find 0x1d6 type for 0x258 (member)! > [...] > ftype__recode_dwarf_types: couldn't find 0x6436 type for 0x446c7 (formal_parameter)! > ftype__recode_dwarf_types: couldn't find 0x22 type for 0x446cc (formal_parameter)! > ftype__recode_dwarf_types: couldn't find 0x18e0d type for 0x446d1 (formal_parameter)! > ftype__recode_dwarf_types: couldn't find 0x734761 type for 0x446d6 (formal_parameter)! and eventually segfaults in > #0 0x00007f8537ad351d tag__natural_alignment (libdwarves.so.1 + 0xf51d) > #1 0x00007f8537ad359b tag__natural_alignment (libdwarves.so.1 + 0xf59b) > #2 0x00007f8537ad4d29 type__check_structs_at_unnatural_alignments (libdwarves.so.1 + 0x10d29) > #3 0x00007f8537ad4ebb class__infer_packed_attributes (libdwarves.so.1 + 0x10ebb) > #4 0x00007f8537ada6f8 __class__fprintf (libdwarves.so.1 + 0x166f8) > #5 0x00007f8537ada141 tag__fprintf (libdwarves.so.1 + 0x16141) > #6 0x000055a77b4e50df pahole_stealer (pahole + 0x50df) > #7 0x00007f8537ae8dbe cus__load_module (libdwarves.so.1 + 0x24dbe) > #8 0x00007f8537ae9101 cus__process_dwflmod (libdwarves.so.1 + 0x25101) > #9 0x00007f85378af6c1 dwfl_getmodules (libdw.so.1 + 0x506c1) > #10 0x00007f8537ae107d dwarf__load_file.lto_priv.0 (libdwarves.so.1 + 0x1d07d) > #11 0x00007f8537ad52e1 cus__load_file (libdwarves.so.1 + 0x112e1) > #12 0x00007f8537ad8e28 cus__load_files (libdwarves.so.1 + 0x14e28) > #13 0x000055a77b4e350a main (pahole + 0x350a) > #14 0x00007f8537923cca __libc_start_main (libc.so.6 + 0x26cca) > #15 0x000055a77b4e364a _start (pahole + 0x364a) (Bug assignment is an educated guess.) [1] pahole from Leap 15.2 (dwarves-1.11-lp152.3.9) failed at the task too (didn't crash though) and it worked with 4.12 kernel debuginfo. I'm filing the bug against the newer version. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1181130] New: gitolite: add nginx to group git
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1181130 Bug ID: 1181130 Summary: gitolite: add nginx to group git Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: cunix(a)mail.de QA Contact: qa-bugs(a)suse.de CC: chris(a)computersalat.de, ngompa13(a)gmail.com Found By: --- Blocker: --- As beginner I tried to setup pagure with nginx on Leap 15.2 following [1]. nginx produced error log containing: connect() to unix:/srv/gitolite/.pagure_web.sock failed (13: Permission denied) while connecting to upstream For me it looks as nginx is not allowed to access directory /srv/gitolite . Adding user "nginx" to group "git" worked for me. Perhaps what is done in [2] to "wwwrun" should be replicated for "nginx"? CC to maintainers of gitolite and pagure who probably know much better and might be able to tell what I did wrong or misunderstood. [1] https://build.opensuse.org/package/view_file/openSUSE:Leap:15.2/pagure/pagu… [2] https://build.opensuse.org/package/view_file/devel:tools:scm/gitolite/gitol… line 81-83 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1127690] New: haveged: Couldn't initialize HAVEGE rng 9
by bugzilla_noreply＠novell.com 12 Jul '22

12 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1127690 Bug ID: 1127690 Summary: haveged: Couldn't initialize HAVEGE rng 9 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- haveged can not be started on the mustang boards when running leap 51.1 adding the "--data 16" option as workaround allows starting the daemon, please see also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866306 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1141928] New: python-acme will break on November 1st
by bugzilla_noreply＠novell.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1141928 Bug ID: 1141928 Summary: python-acme will break on November 1st Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bmw(a)eff.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This bug affects the python*-acme packages in Leap 15.0 and 15.1. If there is already a version of python*-acme frozen in Leap 15.2, it is affected if it is not version 0.34.0 or greater. The python*-acme packages will no longer work with Let’s Encrypt’s “ACMEv2” endpoint which is their RFC 8555 compliant endpoint starting November 1st. See https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauth… for more details about this change. As one of the upstream maintainers of this library, I would recommend backporting python-acme 0.34.0 or greater to all supported versions of openSUSE. There are no breaking changes to the Python API and no dependencies should have to be updated. If you do this, to flag a couple changes for you that you may want to know about: * Some of the code in the library has been deprecated in recent versions and while it still works just fine it is causing Python DeprecationWarnings. See https://docs.python.org/3/library/warnings.html if you're not familiar with this. * There is an extremely minor change in the requests sent by the library. The previous versions were not RFC 8555 compliant and there are no known ACME CAs that rely on this non-standard behavior, but it's something you may want to know about. More details about this change are at https://github.com/certbot/certbot/pull/6975. If either of these changes are especially worrisome to you, I could tell you the changes that need to be backported to an earlier version of python-acme, however, I do not recommend this as it will result packages that have been less thoroughly tested. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1119619] New: certbot does not renew certificates (again)
by bugzilla_noreply＠novell.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1119619 Bug ID: 1119619 Summary: certbot does not renew certificates (again) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jimc(a)math.ucla.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Formerly I had python-certbot-0.26.1-1.1.noarch and it could renew certs. Now I have python3-certbot-0.28.0-2.1.noarch on OpenSuSE Tumbleweed VERSION="20181208" This is the one with the dependency on python-mock restored/added. It says "No renewals were attempted" on both of my hosts that use certbot. I tracked this down to a (non) migration issue: formerly the state dir was /etc/certbot but now it is /etc/letsencrypt, which of course contains no lineages, so no renewals were attempted. Workaround: mv /etc/letsencrypt /etc/letsencrypt.empty mv /etc/certbot /etc/letsencrypt ln -s letsencrypt certbot The symlink is so explicit filenames in config files, or symlinks in e.g. /etc/openssl/private, will still find the cert and key until I locate and fix them. Tested: my Apache webserver still can authenticate using the (not quite expired) old cert. I ran "certbot renew", its webroot challenges were acceptable (despite some DNAT stuff), and the report was: Congratulations, all renewals succeeded... (list of 1 renewed cert). Testing: the webserver successfully uses the new cert. By the way, old logs are in /var/log/certbot which is still there but is supplanted by /var/log/letsencrypt. It would be nice if the python3-certbot and python2-certbot packages had a migration script for users who are having trouble figuring out why their certs are not being renewed. I'm not sure whether migration scripts in packages should be reported upstream, or to the distro; if the former, let me know and I'll open a ticket upstream. Also I set the component to "security" since the X.509 certificate's purpose is security, but if a different component would be more appropriate please feel free to change it. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1190566] New: Python 3.6 does not include the compat fixes to work with OpenSSL 3.0.0
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1190566 Bug ID: 1190566 Summary: Python 3.6 does not include the compat fixes to work with OpenSSL 3.0.0 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: pmonrealgonzalez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Python 3.10, 3.9 and 3.8 have released the compatibility fixes to build and work with OpenSSL 3.0.0. But python 3.6 does not include these fixes and it seems that upstream is not going to port them to 3.6. Note that many packages fail to build due to this in the staging project where we are testing the OpenSSL 3.0.0 update: * https://build.opensuse.org/project/show/openSUSE:Factory:Staging:Gcc7 I'm not sure about the plans to keep 3.6 in Factory or not. But, if 3.6 is going to stay in Factory for long, it would be convenient to have these fixes also in Factory in that case. Here is the upstream bug for this task with all the required commits: * Make Python compatible with OpenSSL 3.0.0: https://bugs.python.org/issue38820 -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1192106] New: [Tumbleweed][security][pam][Build_20211026] zypper in pam_mount failed
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1192106 Bug ID: 1192106 Summary: [Tumbleweed][security][pam][Build_20211026] zypper in pam_mount failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: weixuan.hao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- susetest:~ # uname -m x86_64 susetest:~ # cat /etc/*release NAME="openSUSE Tumbleweed" # VERSION="20211026" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20211026" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20211026" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" Issue description: susetest:~ # zypper in pam_mount Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW package is going to be installed: pam_mount 1 new package to install. Overall download size: 0 B. Already cached: 110.7 KiB. After the operation, additional 303.4 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y In cache pam_mount-2.18-1.7.x86_64.rpm (1/1), 110.7 KiB (303.4 KiB unpacked) Checking for file conflicts: ..................................................................................................................................[done] (1/1) Installing: pam_mount-2.18-1.7.x86_64 ..................................................................................................................[error] Installation of pam_mount-2.18-1.7.x86_64 failed: Error: Subprocess failed. Error: RPM failed: error: unpacking of archive failed on file /usr/sbin/mount.crypt;617a4de9: cpio: open failed - No such file or directory error: pam_mount-2.18-1.7.x86_64: install failed Abort, retry, ignore? [a/r/i] (a): a Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1149986] New: telegram-desktop cannot be started with enabled GTK integration and libqt5-qtstyleplugins-platformtheme-gtk2 installed
by bugzilla_noreply＠novell.com 10 Jul '22

10 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1149986 Bug ID: 1149986 Summary: telegram-desktop cannot be started with enabled GTK integration and libqt5-qtstyleplugins-platformtheme-gtk2 installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: tux93(a)opensuse.org Reporter: tux93(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to start telegram-desktop built with enabled GTK integration and libqt5-qtstyleplugins-platformtheme-gtk2 installed fails with > ~>telegram-desktop > (telegram-desktop:4205): GLib-GObject-WARNING **: 17:15:44.346: cannot register existing type 'GdkDisplayManager' > (telegram-desktop:4205): GLib-CRITICAL **: 17:15:44.346: g_once_init_leave: assertion 'result != 0' failed > (telegram-desktop:4205): GLib-GObject-CRITICAL **: 17:15:44.346: g_object_new_with_properties: assertion 'G_TYPE_IS_OBJECT (object_type)' failed Currently this is resolved by a conflict of telegram-desktop with libqt5-qtstyleplugins-platformtheme-gtk2 which leads to cunfusion of users (bug 1148509) Ideally the root cause should be found and patched. A package without the conflict for testing can be found at https://build.opensuse.org/project/show/home:tux93:tdesktop-no-conflict -- You are receiving this mail because: You are on the CC list for the bug.

2 33

[Bug 1188085] New: The package tpm2-tools do not have tests properly configured
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188085 Bug ID: 1188085 Summary: The package tpm2-tools do not have tests properly configured 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: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package tpm2-tools is not really running the unit tests nor the integration tests. This is critical because there are several bugs upstream that only seems evident when LTO optimization is activated, that is the default now. One example is: https://github.com/tpm2-software/tpm2-tools/issues/2767 (boo#1187316) -- You are receiving this mail because: You are on the CC list for the bug.

1 3