February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208404] New: grub2-probe[12874]: segfault at 1 in libc-2.31.so
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208404 Bug ID: 1208404 Summary: grub2-probe[12874]: segfault at 1 in libc-2.31.so Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864949 --> https://bugzilla.suse.com/attachment.cgi?id=864949&action=edit yast logs Observed post-installation in YaST logs, messages: > 2023-02-16T22:03:05.942935+00:00 install kernel: [ 153.695375][T12874] grub2-probe[12874]: segfault at 1 ip 00007feb5edcd738 sp 00007ffcfc2561d8 error 4 in libc-2.31.so[7feb5ec50000+1e6000] > 2023-02-16T22:03:05.950121+00:00 install kernel: [ 153.695393][T12874] Code: 0c 8a 8b 04 82 29 c8 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 c5 f9 6e c6 c4 41 31 ef c9 c4 e2 7d 78 c0 83 e1 3f 83 f9 20 77 38 <c5> 7e 6f 07 c4 c1 7d 74 c8 c4 c1 35 74 d0 c5 ed eb c9 c5 fd d7 c1 > 2023-02-16T22:03:06.155340+00:00 install kernel: [ 153.908941][T12963] grub2-probe[12963]: segfault at 1 ip 00007f707aa8a738 sp 00007fff8f866758 error 4 in libc-2.31.so[7f707a90d000+1e6000] > 2023-02-16T22:03:06.155348+00:00 install kernel: [ 153.908950][T12963] Code: 0c 8a 8b 04 82 29 c8 c3 66 2e 0f 1f 84 00 00 00 00 00 89 f9 c5 f9 6e c6 c4 41 31 ef c9 c4 e2 7d 78 c0 83 e1 3f 83 f9 20 77 38 <c5> 7e 6f 07 c4 c1 7d 74 c8 c4 c1 35 74 d0 c5 ed eb c9 c5 fd d7 c1 > 2023-02-16T22:03:08.330152+00:00 install kernel: [ 156.079627][T13185] ISO 9660 This was recovered from the rescue system, the system wasn't bootable. I have seen similar messages before, but the systems were usually bootable. So this might not be he reason for the failed boot, unsure. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1208400] New: nm-openvpn fails to connect to an existing VPN after recent update
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208400 Bug ID: 1208400 Summary: nm-openvpn fails to connect to an existing VPN after recent update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: miguel(a)rozsas.eng.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864945 --> https://bugzilla.suse.com/attachment.cgi?id=864945&action=edit output of "/usr/libexec/nm-openvpn-service --debug" After updating opensuse TW to 20230214 an existing openVPN fails to connect where it was working before. The file attached was created by following the guideline here: https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkM… Other VPN setups are working fine, just this one is failing. The affected VPN server is out of my control. It is a corporate VPN from the company where I work for. The Windows openVPN client in the last release it is still working fine with this particular VPN. The problem is my work is done on Linux, not windows. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1207023] New: util-linux-systemd-2.38.1-2.1 contains man pages for binaries found in util-linux-2.38.1-2.1
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207023 Bug ID: 1207023 Summary: util-linux-systemd-2.38.1-2.1 contains man pages for binaries found in util-linux-2.38.1-2.1 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: jared.hudson(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- util-linux-2.38.1-2.1.x86_64 util-linux-systemd-2.38.1-2.1.x86_64 util-linux-systemd-2.38.1-2.1 contains man pages for binaries found in util-linux-2.38.1-2.1 hostname:~ # rpm -ql util-linux-systemd-2.38.1-2.1.x86_64 | grep -c /man/ 121 hostname:~ # rpm -ql util-linux-2.38.1-2.1.x86_64 | grep -c /man/ 0 util-linux-2.37.4-4.3 and earlier had man pages. hostname:~ # rpm -qlp Downloads/util-linux-2.37.4-4.3.x86_64.rpm | grep -c /man/ 111 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1207788] New: gdm (fingerprint?): no password prompt, impossible to login
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207788 Bug ID: 1207788 Summary: gdm (fingerprint?): no password prompt, impossible to login Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864639 --> https://bugzilla.suse.com/attachment.cgi?id=864639&action=edit video of failed login attempts After boot, or after logout, it's impossible to log in because the password prompt is closed after a few milliseconds. - user clicks on name - password / fingerprint prompt appears, but vanishes almost immediately - user selection is displayed again The attached video demonstrates the effect. The issue "goes a way" after waiting a few minutes. I haven't been able to figure out exactly when this happens, or what condition needs to be fulfilled for it to happen. I have not seen this issue after locking the session, only when creating a new session. Note that this bug is *not* about unreliable fingerprint detection; that's also an issue but I have realized that that's unlikely to be ever solved. The issue reported here hasn't always been observed. I think I first saw it a month ago or so. Can't tell exactly. -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1208199] New: php8-fpm SIGABRT when using chroot option
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208199 Bug ID: 1208199 Summary: php8-fpm SIGABRT when using chroot option 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: silentworks(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, php8-fpm as of current version kills itself after executing anything on the spawn childs, it reports an overflow. ############## [13-Feb-2023 12:48:59] WARNING: [pool webmail] child 24741 exited on signal 6 (SIGABRT - core dumped) after 8.323155 seconds from start [13-Feb-2023 12:48:59] NOTICE: [pool webmail] child 24789 started [13-Feb-2023 12:49:00] WARNING: [pool webmail] child 24742 exited on signal 6 (SIGABRT - core dumped) after 9.250155 seconds from start [13-Feb-2023 12:49:00] NOTICE: [pool webmail] child 24799 started ########## gdb coredump load: ######################################### Reading symbols from /usr/sbin/php-fpm... Reading symbols from /root/.cache/debuginfod_client/059885d25ea288ba5d71218fbf100569e242ac7f/debuginfo... warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 24742] warning: Section `.reg-xstate/24742' in core file too small. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `php-fpm: pool webmail '. Program terminated with signal SIGABRT, Aborted. warning: Section `.reg-xstate/24742' in core file too small. #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00006b54496b1503 in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78 #2 0x00006b544965ee16 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00006b544964789c in __GI_abort () at abort.c:79 #4 0x00006b54496485d7 in __libc_message (fmt=fmt@entry=0x6b54497cc552 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150 #5 0x00006b5449746c4b in __GI___fortify_fail (msg=msg@entry=0x6b54497cc4f8 "buffer overflow detected") at fortify_fail.c:24 #6 0x00006b54497450c6 in __GI___chk_fail () at chk_fail.c:28 #7 0x00001493cdc53c5a in mempcpy (__len=10, __src=0x1493ce003708, __dest=0x1493cee706a0) at /usr/include/bits/string_fortified.h:45 #8 fake_data_segment (info=0x0, sysdb=0x1493cf01c040) at /usr/src/debug/php-8.1.15/ext/date/lib/parse_tz.c:917 #9 timelib_builtin_db () at /usr/src/debug/php-8.1.15/ext/date/lib/parse_tz.c:1080 #10 0x00001493cdc43d8d in get_timezone_info () at /usr/src/debug/php-8.1.15/ext/date/php_date.c:557 #11 0x00001493cdc468d5 in zif_strtotime (execute_data=0x6b5449014610, return_value=0x6b54490145d0) at /usr/src/debug/php-8.1.15/ext/date/php_date.c:1037 #12 0x00001493cde4cb5b in ZEND_DO_ICALL_SPEC_RETVAL_USED_HANDLER (execute_data=0x6b5449014510) at /usr/src/debug/php-8.1.15/Zend/zend_vm_execute.h:1297 #13 0x00001493cdeaa388 in execute_ex (ex=<optimized out>) at /usr/src/debug/php-8.1.15/Zend/zend_vm_execute.h:55585 #14 0x00001493cde0e6fc in zend_call_function (fci=0x78ee7809dd80, fci_cache=<optimized out>) at /usr/src/debug/php-8.1.15/Zend/zend_execute_API.c:912 #15 0x00001493cdf62392 in _call_user_function_impl (function_name=<optimized out>, object=0x0, named_params=0x0, params=0x78ee7809de00, param_count=1, retval_ptr=0x78ee7809ddf0) at /usr/src/debug/php-8.1.15/Zend/zend_execute_API.c:712 #16 ps_call_handler.constprop.0 (func=<optimized out>, argv=0x78ee7809de00, retval=0x78ee7809ddf0, argc=1) at /usr/src/debug/php-8.1.15/ext/session/mod_user.c:36 #17 0x00001493cdcc567f in ps_read_user (mod_data=<optimized out>, key=<optimized out>, val=0x78ee7809de38, maxlifetime=<optimized out>) at /usr/src/debug/php-8.1.15/ext/session/mod_user.c:144 #18 0x00001493cdcbf233 in php_session_initialize () at /usr/src/debug/php-8.1.15/ext/session/session.c:444 #19 0x00001493cdcbf820 in php_session_start () at /usr/src/debug/php-8.1.15/ext/session/session.c:1612 #20 0x00001493cdcc4fa7 in zif_session_start (execute_data=<optimized out>, return_value=0x78ee7809df70) at /usr/src/debug/php-8.1.15/ext/session/session.c:2533 #21 0x00001493cde4e6fd in ZEND_DO_ICALL_SPEC_RETVAL_UNUSED_HANDLER (execute_data=0x6b5449014450) at /usr/src/debug/php-8.1.15/Zend/zend_vm_execute.h:1235 #22 0x00001493cdeaa388 in execute_ex (ex=<optimized out>) at /usr/src/debug/php-8.1.15/Zend/zend_vm_execute.h:55585 #23 0x00001493cdeb067d in zend_execute (op_array=0x6b5449002000, return_value=0x0) at /usr/src/debug/php-8.1.15/Zend/zend_vm_execute.h:60151 #24 0x00001493cdf52f32 in zend_execute (return_value=0x0, op_array=0x6b5449002000) at /usr/src/debug/php-8.1.15/Zend/zend.c:1785 #25 zend_execute_scripts.constprop.1 (type=8, retval=0x0, file_count=3, file_count=3, retval=0x0, type=8) at /usr/src/debug/php-8.1.15/Zend/zend.c:1799 #26 0x00001493cdda41f8 in php_execute_script (primary_file=<optimized out>) at /usr/src/debug/php-8.1.15/main/main.c:2541 #27 0x00001493cdc3fd28 in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/php-8.1.15/sapi/fpm/fpm/fpm_main.c:1917 ####################################################### How to replicate? /etc/php8/fpm/php-fpm.d/test.conf: ################### [test] user = test group = test listen = 127.0.0.1:9001 pm = dynamic pm.max_children = 5 pm.start_servers = 2 pm.min_spare_servers = 1 pm.max_spare_servers = 3 chroot = /home/test process.dumpable = yes rlimit_core = unlimited ################### -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1208747] New: php8-APCu missing for aarch64 (and x86_64); Leap 15.4
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208747 Bug ID: 1208747 Summary: php8-APCu missing for aarch64 (and x86_64); Leap 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ro.wirth(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- php8-APCu is missing for aarch64 AND x86_64. (php7-APCu is available for both architectures.) Nextcloud server recommends it. I would like to get it from official repositories as all other php8 modules like php7-APCu so that the version matches the other modules. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1208673] New: Publishing:TeXLive/texlive: texlive-unicode-alphabets broken: "File `csvsimple.tmp.patch' not found. \input{csvsimple.tmp.patch}"
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208673 Bug ID: 1208673 Summary: Publishing:TeXLive/texlive: texlive-unicode-alphabets broken: "File `csvsimple.tmp.patch' not found. \input{csvsimple.tmp.patch}" 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: f.alexander.wilms(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following minimal working example causes an error: \documentclass{article} \usepackage[MUFI]{unicode-alphabets} \begin{document} test \end{document} File `csvsimple.tmp.patch' not found. \input{csvsimple.tmp.patch} The file is present in the upstream repository: https://github.com/mikkelee/latex-pua/blob/master/latex/csvsimple.tmp.patch… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203100] New: Disable fingerprint login doesn't work.
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203100 Bug ID: 1203100 Summary: Disable fingerprint login doesn't work. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: alynx.zhou(a)suse.com, yfjiang(a)suse.com, zcjia(a)suse.com Found By: --- Blocker: --- Env: openSUSE Leap 15.4 GNOME 41.2 gdm 41.3 fprintd 1.94.1 hardware: Thinkpad P15 Gen1 Steps: 1. Boot to desktop and login 2. Disable the fingerprint login in gnome-control-center -> Users 3. Logout or even restart 4. Try to login, stay on the input password screen and observe the warning message below the input field. Actual Result: The "Sorry, fingerprint authentication didn't work. Please try again." message keeps appearing every ~2 sec no matter whether I use the fingerprint scanner or not. From the journal log we can see the Fingerprint Authentication Daemon is started even we already disable it in gnome-control-center. ============================================================================== Sep 05 11:12:25 MiWiFi-R3600-srv dbus-daemon[1022]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested b> Sep 05 11:12:25 MiWiFi-R3600-srv systemd[1]: Starting Fingerprint Authentication Daemon... Sep 05 11:12:26 MiWiFi-R3600-srv dbus-daemon[1022]: [system] Successfully activated service 'net.reactivated.Fprint' Sep 05 11:12:26 MiWiFi-R3600-srv systemd[1]: Started Fingerprint Authentication Daemon. Sep 05 11:12:26 MiWiFi-R3600-srv gdm-fingerprint][828]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] term> Sep 05 11:12:29 MiWiFi-R3600-srv gdm-fingerprint][837]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] term> ============================================================================= Related issue: https://bugzilla.suse.com/show_bug.cgi?id=1203099 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1203099] New: Cannot unblock GNOME desktop using the fingerprint scanner
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203099 Bug ID: 1203099 Summary: Cannot unblock GNOME desktop using the fingerprint scanner Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: alynx.zhou(a)suse.com, mail(a)vsv.dev, yfjiang(a)suse.com, zcjia(a)suse.com Depends on: 1189621 Found By: Community User Blocker: --- Env: openSUSE Leap 15.4 GNOME 41.2 gdm 41.3 fprintd 1.94.1 hardware: Thinkpad P15 Gen1 +++ This bug was initially created as a clone of Bug #1189621 +++ Despite the fact that `fprintd` is installed, the fingerprints are configured and `fprintd-verify` recognizes them, I still cannot use the fingerprint scanner in order to unlock my GNOME session. Reproducible: Always Steps to Reproduce: 1. Install fprintd via `sudo zypper in fprintd` 2. Enable 'Fingerprint Login' in 'Gnome Settings > Users' GUI application and add a fingerprint 3. Verify that it works when invoking `fprintd-verify` from the command line: fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-match (done) 3. Lock the screen in GNOME 4. Try to unlock the screen Actual Results: Unlocking via the fingerprint scanner doesn't work. "Sorry, that didn't work. Please try again." message keeps appearing every ~2 sec no matter whether I use the fingerprint scanner or not. The session can be unlocked only by entering the password. Expected Results: Both password and fingerprint scan should unlock the GNOME session. ~> zypper info gnome-shell | grep Version Version : 40.3-4.1 ~> zypper info gdm | grep Version Version : 3.38.2-2.6 ~> zypper info fprintd | grep Version Version : 1.90.9-2.3 ~> cat /etc/os-release | grep VERSION_ID VERSION_ID="20210817" ~> sudo journalctl --since "10 min ago" | grep fingerprint Aug 19 19:58:55 vsv-thinkpad gdm-fingerprint][5155]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] Aug 19 19:58:58 vsv-thinkpad gdm-fingerprint][5162]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] Aug 19 19:59:00 vsv-thinkpad gdm-fingerprint][5168]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] Aug 19 19:59:03 vsv-thinkpad gdm-fingerprint][5171]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] ~> sudo fwupdmgr get-devices ... ��Prometheus: �� Device ID: 50efef912094e784a03628350441f6927c4920b0 �� Summary: Fingerprint reader �� Current version: 10.01.3273255 �� Vendor: Synaptics (USB:0x06CB) �� Install Duration: 2 seconds �� Serial Number: 60900456185485 �� GUIDs: 09e8bf16-3e69-50f5-bb66-c7a040248352 �� USB\VID_06CB&PID_00BD&REV_0000 �� 8088f861-6318-5b1e-9ce4-fbddbedb09ac �� USB\VID_06CB&PID_00BD �� Device Flags: �� Updatable �� Supported on remote server �� Cryptographic hash verification is available ~> uname -a Linux vsv-thinkpad 5.13.8-1-default #1 SMP Thu Aug 5 08:56:22 UTC 2021 (967c6a8) x86_64 x86_64 x86_64 GNU/Linux Hardware Model: Lenovo ThinkPad T14 Gen 1 (AMD) Windowing System: Wayland -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1208126] New: pythons-eventlet failed to utilize DNS servers in /etc/resolv.conf because of newdnspython.patch patch
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208126 Bug ID: 1208126 Summary: pythons-eventlet failed to utilize DNS servers in /etc/resolv.conf because of newdnspython.patch patch Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: Gyee(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- python3-eventlet (version 0.26.1) failed to utilize the servers in /etc/resolv.conf because of newdnspython.patch. https://build.opensuse.org/package/show/openSUSE:Leap:15.4/python-eventlet The problem is revealed with the following code. ----- import eventlet.support.greendns as gd p = gd.ResolverProxy() try: a = p.query('suse.com') print(a.rrset) except Exception as e: print(e) ----- Looking at the change logs, newdnspython.patch was added to support python3-dnspython 2.0.0. However dnspython 2.0.0 is *incompatible* with eventlet 0.26.1. See https://github.com/eventlet/eventlet/blob/v0.26.1/setup.py#L18 We need to remove newdnspython.patch. -- You are receiving this mail because: You are on the CC list for the bug.

1 7