September 2021 - openSUSE Bugs - openSUSE Mailing Lists

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

[Bug 1177800] New: [Ten64] getsysinfo caused kernel error (synchronous external abort)
by bugzilla_noreply＠suse.com 08 Jul '22

08 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1177800 Bug ID: 1177800 Summary: [Ten64] getsysinfo caused kernel error (synchronous external abort) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: afaerber(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matt(a)traverse.com.au, snwint(a)suse.com, yousaf.kaukab(a)suse.com Found By: --- Blocker: --- Running `getsysinfo` (via ssh) on Tumbleweed 20201011 with kernel-default 5.9.0 from Kernel:HEAD repository caused a kernel error, with ssh getting stuck and reconnections failing. Serial login still worked. zehn:~ # getsysinfo /proc/bus/input /proc/cpuinfo /proc/device-tree /proc/devices /proc/fb /proc/filesystems /proc/interrupts /proc/iomem /proc/ioports /proc/meminfo /proc/modules /proc/net/dev /proc/partitions /proc/scsi /proc/tty /proc/version /sys /usr/sbin/getsysinfo: line 23: 2761 Segmentation fault cp -x -a --parents "$i" "$dir/$host" 2> /dev/null /var/lib/hardware/udi /proc/mounts System data written to: /tmp/zehn.tar.gz zehn:~ # [ 544.956478] Internal error: synchronous external abort: 96000210 [#1] SMP [ 544.963295] Modules linked in: af_packet ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security iscsi_ibft iscsi_boot_sysfs ip_set nfnetlink ebtable_filter ebtables rfkill ip6table_filter ip6_tables iptable_filter ip_tables x_tables fsl_dpaa2_ptp ptp_qoriq fsl_dpaa2_eth phylink xgmac_mdio hid_generic fsl_mc_dpio usbhid cdc_acm i2c_mux_pca954x i2c_mux tpm_i2c_atmel spi_fsl_qspi qoriq_thermal leds_gpio optee tee uio_pdrv_genirq uio qoriq_cpufreq nls_iso8859_1 nls_cp437 vfat fat drm xhci_plat_hcd xhci_hcd usbcore caam_jr mmc_block libdes authenc caamhash_desc caamalg_desc crypto_engine rtc_ds1307 mp886x aes_ce_blk crypto_simd cryptd aes_ce_cipher crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce dpaa2_console nvme nvme_core dwc3 sdhci_of_esdhc caam sdhci_pltfm ulpi [ 544.963547] error sdhci udc_core roles mmc_core i2c_imx btrfs blake2b_generic libcrc32c xor xor_neon raid6_pq sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 545.066303] CPU: 0 PID: 2761 Comm: cp Not tainted 5.9.0-1.g11733e1-default #1 openSUSE Tumbleweed (unreleased) [ 545.076303] Hardware name: traverse ten64/ten64, BIOS 2020.07-rc1-g1d4a3d9d5c 07/28/2020 [ 545.084393] pstate: 60000085 (nZCv daIf -PAN -UAO BTYPE=--) [ 545.089967] pc : dw_pcie_read+0x48/0xc0 [ 545.093799] lr : dw_pcie_access_other_conf.isra.0+0xc4/0x120 [ 545.099452] sp : ffff800012203bf0 [ 545.102759] x29: ffff800012203bf0 x28: 0000000000000400 [ 545.108067] x27: ffff00833e683400 x26: ffff008348240000 [ 545.113375] x25: ffff800010085000 x24: 0000000000000000 [ 545.118683] x23: ffff00834b239880 x22: ffff800012203cc4 [ 545.123991] x21: 0000000000000004 x20: 0000000000000400 [ 545.129299] x19: ffff00834b2398a8 x18: 0000000000000000 [ 545.134607] x17: 0000000000000000 x16: ffffafadaf1be170 [ 545.139915] x15: 0000000000000000 x14: 0000000000000000 [ 545.145222] x13: 0000000000000000 x12: 0000000000000040 [ 545.150530] x11: ffff00834bd8c920 x10: 0000000000000000 [ 545.155837] x9 : ffffafadaf12e8f4 x8 : 0000000002080000 [ 545.161145] x7 : 0000000000000000 x6 : ffff800010f00000 [ 545.166452] x5 : 0000000000000000 x4 : 0000000000000908 [ 545.171759] x3 : 0000000000000003 x2 : ffff800012203cc4 [ 545.177066] x1 : 0000000000000004 x0 : ffff800010085400 [ 545.182374] Call trace: [ 545.184816] dw_pcie_read+0x48/0xc0 [ 545.188298] dw_pcie_rd_conf+0x11c/0x150 [ 545.192217] pci_user_read_config_dword+0xa8/0x190 [ 545.197004] pci_read_config+0x1f8/0x264 [ 545.200923] sysfs_kf_bin_read+0x78/0xa0 [ 545.204840] kernfs_file_direct_read+0x90/0x220 [ 545.209365] kernfs_fop_read+0x44/0x50 [ 545.213111] vfs_read+0xb8/0x1e4 [ 545.216334] ksys_read+0x78/0x110 [ 545.219643] __arm64_sys_read+0x28/0x34 [ 545.223476] el0_svc_common.constprop.0+0x84/0x230 [ 545.228261] do_el0_svc+0x30/0xa0 [ 545.231572] el0_svc+0x18/0x50 [ 545.234621] el0_sync_handler+0x90/0x254 [ 545.238538] el0_sync+0x158/0x180 [ 545.241849] Code: 528010e0 d50323bf b900005f d65f03c0 (b9400001) [ 545.247941] ---[ end trace 68383e7eecaae870 ]--- -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1110456] New: rsyslog not logging most messages
by bugzilla_noreply＠novell.com 07 Jul '22

07 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1110456 Bug ID: 1110456 Summary: rsyslog not logging most messages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On SLES, all messages I see in journalctl are also available in /var/log/messages. On Kubic, where we use rsyslog, nearly no message I see in journalctl can be found in /var/log/messages. So something with journalctl and rsyslog is configured wrong. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1068678] New: Package rsyslog requires package system-user-news
by bugzilla_noreply＠novell.com 07 Jul '22

07 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1068678 Bug ID: 1068678 Summary: Package rsyslog requires package system-user-news 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: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When installing rsyslog in Tumbleweed there are warning messages that the user news is not present (chown: invalid user: 'news:news'). Unless rsyslog is changed to not using news, the package should require the package "system-user-news". -- You are receiving this mail because: You are on the CC list for the bug.

2 2