March 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1004201] New: System hangs during boot due to loop trying to load nvidia modules
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1004201 Bug ID: 1004201 Summary: System hangs during boot due to loop trying to load nvidia modules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: marcelo.jimenez(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lspci is: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 730] (rev a1) Nvidia site explicitly says that the 367.44 driver does support GT 730. In my opinion, there are two problems here: 1 - The system initialization should not loop forever trying to load a module it has already tryed to load and failed 2 - The 367.44 NVIDIA driver should support my hardware. The NVRM messages repeat forever: ... Oct 09 09:17:23 linux-af78 kernel: [drm] Initialized drm 1.1.0 20060810 Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: module license 'NVIDIA' taints kernel. Oct 09 09:17:23 linux-af78 kernel: Disabling lock debugging due to kernel taint Oct 09 09:17:23 linux-af78 systemd-journal[120]: Journal started Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0) Oct 09 09:17:23 linux-af78 systemd[1]: Started Journal Service. ... Oct 09 09:17:31 linux-af78 systemd[1]: Mounting /home... Oct 09 09:17:31 linux-af78 mtp-probe[579]: checking bus 6, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb6/6-1" Oct 09 09:17:31 linux-af78 mtp-probe[578]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb5/5-2" Oct 09 09:17:31 linux-af78 mtp-probe[578]: bus: 5, device: 2 was not an MTP device Oct 09 09:17:31 linux-af78 mtp-probe[579]: bus: 6, device: 2 was not an MTP device Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Mounted /home. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Reached target Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Oct 09 09:17:32 linux-af78 systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Oct 09 09:17:32 linux-af78 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1059001] New: kded5 or kdeint5 crashes after systemctl restart NetworkManager
by bugzilla_noreply＠novell.com 12 Jun '22

12 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1059001 Bug ID: 1059001 Summary: kded5 or kdeint5 crashes after systemctl restart NetworkManager Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: drnn_1076(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: When I resume my laptop after suspending it. I got no connection to the my wireless network. I get the list of wireless networks available but when I hit "connect" nothing happens. So I restart the NetworkManager using "systemctl restart NetworkManager" and it works again properly. I'm getting however the following crash of kded5 or kdeint5 immediately after restarting the NetworkManager: for kded5: kded5 PID: 11541 Signal: Segmentation fault (11) Time: 17/09/2017 10:48:35 for kdeinit5: kdeninit5 PID:2138 Signal: Segmentation fault (11) Time ... Note: It might be related to the touchpad conflicting with my usb mouse. Reproducible: Always Steps to Reproduce: 1. Systemctl restart NetwrokManager 2. Crash kded5 3. Close the crash window and everything works ok Kded5 developer information Application: kded5 (kded5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc16a5dbd40 (LWP 11541))] Thread 9 (Thread 0x7fc10affd700 (LWP 11572)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fc10b7fe700 (LWP 11571)): #0 0x00007fc164747ba4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x00007fc164702ce6 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc116ec8f37 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fc10bfff700 (LWP 11565)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc1647030c2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc111f71456 in () at /usr/lib64/libgio-2.0.so.0 #4 0x00007fc164729c05 in () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc110f34700 (LWP 11564)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc164702e81 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fc164729c05 in () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc1141ef700 (LWP 11562)): #0 0x00007fc169f21cc8 in read () at /lib64/libc.so.6 #1 0x00007fc164746850 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc16470280b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc164702cd0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #9 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #10 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc14def9700 (LWP 11546)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #7 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #8 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc14f429700 (LWP 11545)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164702d29 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #4 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1679ce31a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x00007fc168566a45 in () at /usr/lib64/libQt5DBus.so.5 #7 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #9 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fc15cff1700 (LWP 11542)): #0 0x00007fc169f2612b in poll () at /lib64/libc.so.6 #1 0x00007fc164498387 in () at /usr/lib64/libxcb.so.1 #2 0x00007fc16449a17a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x00007fc15fdb64b9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007fc1679d2d2e in () at /usr/lib64/libQt5Core.so.5 #5 0x00007fc1673822f8 in start_thread () at /lib64/libpthread.so.0 #6 0x00007fc169f305ef in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fc16a5dbd40 (LWP 11541)): [KCrash Handler] #6 0x00007fc1664457d9 in XPending () at /usr/lib64/libX11.so.6 #7 0x00007fc1137ca9e8 in () at /usr/lib64/qt5/plugins/kded_touchpad.so #8 0x00007fc1137caa3e in () at /usr/lib64/qt5/plugins/kded_touchpad.so #9 0x00007fc167bcd25a in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #10 0x00007fc167bd9128 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #11 0x00007fc167bd9492 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #12 0x00007fc1697629bc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #13 0x00007fc169769d74 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #14 0x00007fc167b9fd48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #15 0x00007fc167bf628d in () at /usr/lib64/libQt5Core.so.5 #16 0x00007fc164702b77 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x00007fc164702da8 in () at /usr/lib64/libglib-2.0.so.0 #18 0x00007fc164702e3c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x00007fc167bf56ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #20 0x00007fc167b9e35a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #21 0x00007fc167ba6be4 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #22 0x00007fc16a200e1a in kdemain () at /usr/lib64/libkdeinit5_kded5.so #23 0x00007fc169e5af1a in __libc_start_main () at /lib64/libc.so.6 #24 0x0000558fc350f7fa in _start () -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1113755] New: [openssl1.1.1][staging] python fails to build / errorin the test suite
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1113755 Bug ID: 1113755 Summary: [openssl1.1.1][staging] python fails to build / errorin the test suite Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openssl is being updated to version 1.1.1 - which currently causes failures of python The error can be seen in Staging:C https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… >From the log file: [ 216s] Run tests sequentially [ 216s] 0:00:00 load avg: 1.65 [ 1/19] test_urllib [ 216s] 0:00:00 load avg: 1.65 [ 2/19] test_ssl [ 218s] test test_ssl failed -- multiple errors occurred; run in verbose mode for details [ 218s] 0:00:01 load avg: 1.65 [ 3/19/1] test_hashlib -- test_ssl failed [ 218s] 0:00:02 load avg: 1.65 [ 4/19/1] test_hmac [ 218s] 0:00:02 load avg: 1.65 [ 5/19/1] test_urllib2_localnet [ 219s] Traceback (most recent call last): [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/SocketServer.py", line 290, in _handle_request_noblock [ 219s] self.process_request(request, client_address) [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/SocketServer.py", line 318, in process_request [ 219s] self.finish_request(request, client_address) [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/SocketServer.py", line 331, in finish_request [ 219s] self.RequestHandlerClass(request, client_address, self) [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/SocketServer.py", line 652, in __init__ [ 219s] self.handle() [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/BaseHTTPServer.py", line 340, in handle [ 219s] self.handle_one_request() [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/BaseHTTPServer.py", line 310, in handle_one_request [ 219s] self.raw_requestline = self.rfile.readline(65537) [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/socket.py", line 480, in readline [ 219s] data = self._sock.recv(self._rbufsize) [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/ssl.py", line 780, in recv [ 219s] return self.read(buflen) [ 219s] File "/home/abuild/rpmbuild/BUILD/Python-2.7.15/Lib/ssl.py", line 667, in read [ 219s] v = self._sslobj.read(len) [ 219s] error: [Errno 104] Connection reset by peer [ 219s] test test_urllib2_localnet produced unexpected output: [ 219s] ********************************************************************** (other failures might happen too) -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1084650] New: GCC 8: python-base is miscompiled
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084650 Bug ID: 1084650 Summary: GCC 8: python-base is miscompiled 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: --- Due to that: https://bugs.python.org/issue27987#msg311323 -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1081750] New: python tarfile uses random order
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1081750 Bug ID: 1081750 Summary: python tarfile uses random order Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tchvatal(a)suse.com Blocks: 1041090 Found By: Development Blocker: --- There are various Factory packages that use the obs_scm service to generate source tarballs at build time. However, https://github.com/python/cpython/pull/2263 is only accepted into python-3.7 so packages like obs-service-product_converter still produce different build results every time. IMHO we should do a backport of the patch. Upstream python was afraid that users might rely on files being handled in (unpredictable) filesystem order. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1078326] New: python-devel has dependency on /usr/bin/python3
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1078326 Bug ID: 1078326 Summary: python-devel has dependency on /usr/bin/python3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Another bug discovered by accident - sh** happens :) python-devel (python2 variant) has a dependency on /usr/bin/python3 - which sounds just weird digging a bit into the files and their headers, the offending file seems to be (in pyton-devel): /usr/lib64/python2.7/test/bisect.py:#!/usr/bin/python3 It being installed in py2.7 directories should imply it also wants to use python2.7 There is a 2nd file in python-devel that references python3, but that is likely less damaging: /usr/lib64/python2.7/config/Makefile.pre:PYTHON_FOR_REGEN=python3 -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1073748] New: Segfault in libpython2.7.so.1
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1073748 Bug ID: 1073748 Summary: Segfault in libpython2.7.so.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: daniel(a)saltstack.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We are experiencing a SegFault with python2.7 when trying to run our test suite. [ 860.345322] salt-call[18552]: segfault at 3ea0 ip 00007ff59cede8bc sp 00007ffefe1e2170 error 4 in libpython2.7.so.1.0[7ff59ce0b000+1ae000] This is happening with the 42.2 ami on Amazon AWS, as well as 42.2 and 42.3 on Linode. We are running our test suite salt states here https://github.com/saltstack/salt-jenkins We are calling `salt-call --local state.apply git.salt pillar='{testing_dir: /tmp/kitchen/testing, clone_repo: false, salttesting_namespec: "salttesting==2017.6.1"}' saltenv=2017.7` It does have to be called as the exec from ssh for this to fail. I am attaching the core dump. Thanks, Daniel -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 899330] New: Interfaces does not automatically show up in firewall with NetworkManager
by bugzilla_noreply＠novell.com 05 Jun '22

05 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=899330 Bug ID: 899330 Summary: Interfaces does not automatically show up in firewall with NetworkManager Classification: openSUSE Product: openSUSE Factory Version: 201408* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: razirazo_90(a)live.com.my QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using NetworkManager, network interfaces does not listed in firewall. I have to manually configure it using Wicked Service first, to make it registered in firewall. And then use networkManager back. This is troublesome, for example when setting up internet sharing you can't proceed to zone assign and Network masquerade until you do the step above. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1102737] New: Install does not work on Pentium III machine
by bugzilla_noreply＠novell.com 04 Jun '22

04 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1102737 Bug ID: 1102737 Summary: Install does not work on Pentium III machine 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: srid(a)rkmail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tried installing Tumbleweed on my Tualatin machine, but it fails to get to repository with following error: OpenSSL internal error, assertion failed: FATAL FIPS SELFTEST FAILURE Tried booting with fips=0, it does not help. I guess libssl wants something like SSE2, NX-bit or some other feature this old CPU lacks. Is there some chance of working around that issue? I know you'll likely don't want to bother with such an old hardware, but 'i586' in iso name 'openSUSE-Tumbleweed-NET-i586-Snapshot20180723-Media.iso' is a little bit confusing. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1080259] New: HPC modules show wrong summary
by bugzilla_noreply＠novell.com 03 Jun '22

03 Jun '22

http://bugzilla.suse.com/show_bug.cgi?id=1080259 Bug ID: 1080259 Summary: HPC modules show wrong summary Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cgoll(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Most of the HPC lmod modules show the wrong summary. E.g. for the package openmpi-gnu-hpc thethe command module spider outputs openmpi: openmpi/1.10.7 Dependency package for openmpi_1_10_7-gnu-hpc-devel-static which is self refering and useless. It should be "A powerful implementation of MPI" -- You are receiving this mail because: You are on the CC list for the bug.

2 13