April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1137383] New: python-virtualenv: creating virtualenvs fails in directories with colons
by bugzilla_noreply＠novell.com 21 Jun '22

21 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137383 Bug ID: 1137383 Summary: python-virtualenv: creating virtualenvs fails in directories with colons 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: sebix+novell.com(a)sebix.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I was unable to add the address of the maintainer (according to OBS) as assignee. With colons -> error: ----- username@computername:~/tmp/path:with:colons> python3 -m virtualenv -p python3 testingvenv Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/username/tmp/path:with:colons/testingvenv/bin/python3 Also creating executable in /home/username/tmp/path:with:colons/testingvenv/bin/python Fatal Python error: initfsencoding: Unable to get the locale encoding ModuleNotFoundError: No module named 'encodings' Current thread 0x00007ff630c0e680 (most recent call first): ERROR: The executable /home/username/tmp/path:with:colons/testingvenv/bin/python3 is not functioning ERROR: It thinks sys.prefix is '/home/username/tmp/path:with:colons' (should be '/home/username/tmp/path:with:colons/testingvenv') ERROR: virtualenv is not compatible with this system or executable ----- username@computername:~/tmp/path:with:colons> python2 -m virtualenv -p python2 testingvenv2 Already using interpreter /usr/bin/python2 New python executable in /home/username/tmp/path:with:colons/testingvenv2/bin/python2 Also creating executable in /home/username/tmp/path:with:colons/testingvenv2/bin/python ImportError: No module named site ERROR: The executable /home/username/tmp/path:with:colons/testingvenv2/bin/python2 is not functioning ERROR: It thinks sys.prefix is u'/home/username/tmp/path:with:colons' (should be u'/home/username/tmp/path:with:colons/testingvenv2') ERROR: virtualenv is not compatible with this system or executable ------ Without colons -> no error: ----- username@computername:~/tmp/pathwithoutcolons> python3 -m virtualenv -p python3 testingvenv Already using interpreter /usr/bin/python3 Using base prefix '/usr' New python executable in /home/username/tmp/pathwithoutcolons/testingvenv/bin/python3 Also creating executable in /home/username/tmp/pathwithoutcolons/testingvenv/bin/python Installing setuptools, pip, wheel... done. ----- -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1091291] New: GNOME:Factory/gnome-disk-utility: function bd_loop_setup_from_fd not found
by bugzilla_noreply＠novell.com 21 Jun '22

21 Jun '22

2 1

[Bug 1170826] New: Go packages miss binutils-gold dependency
by bugzilla_noreply＠novell.com 17 Jun '22

17 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1170826 Bug ID: 1170826 Summary: Go packages miss binutils-gold dependency Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On arm and aarch64, 'go' requires 'binutils-gold' dependency at runtime, but go packages only require it as BuildRequires. So, binutils-gold must be installed manually, which breaks some builds in OBS, such as rclone [0]. Without 'binutils-gold', we ge the following error: [ 138s] /usr/lib64/go/1.11/pkg/tool/linux_arm64/link: running gcc failed: exit status 1 [ 138s] collect2: fatal error: cannot find 'ld' So, we need to add 'Requires: binutils-gold' to all go1.x packages. [0]: https://build.opensuse.org/package/show/network/rclone -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 925275] New: NVIDIA Driver not installable
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=925275 Bug ID: 925275 Summary: NVIDIA Driver not installable Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fbernasek(a)netscape.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 629479 --> http://bugzilla.opensuse.org/attachment.cgi?id=629479&action=edit nvidia driver install log install opensuse tumbleweed 20150329 no problems. after reboot i like to install the NVIDIA-346.47 or 349.12 with booth the same problem can't install the driver. now i update with the kernel from the kernel:stable repositories the same problem. 20150328 the same problem -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[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 1162224] New: Installed version missmatch between libpython3_6m1_0 and python3-base (problem for cmake)
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1162224 Bug ID: 1162224 Summary: Installed version missmatch between libpython3_6m1_0 and python3-base (problem for cmake) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tbechtold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my system (Leap 15.1), libpython3_6m1_0 is already installed: # zypper se -s -i libpython3 S | Name | Type | Version | Arch | Repository --+------------------+---------+-------------------+--------+------------ i | libpython3_6m1_0 | package | 3.6.9-lp151.6.4.1 | x86_64 | repo-update Now I install python3-base with `zypper in python3-base` (which is available in a newer version): # zypper se -s -i python3-base S | Name | Type | Version | Arch | Repository ---+--------------+---------+--------------------+--------+------------ i+ | python3-base | package | 3.6.10-lp151.6.7.1 | x86_64 | repo-update With that, libpython3_6m1_0 will not be updated: # zypper se -s -i libpython3 S | Name | Type | Version | Arch | Repository --+------------------+---------+-------------------+--------+------------ i | libpython3_6m1_0 | package | 3.6.9-lp151.6.4.1 | x86_64 | repo-update The problem seems to be a missing dependency on the version itself: # rpm -q --requires python3-base|grep libpython3 libpython3.6m.so.1.0()(64bit) This situation creates problems with cmake (eg. when you try to build ceph): 02:24:35 -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.6.9", minimum required is "3") 02:24:35 -- Found PythonLibs: /usr/lib64/libpython3.6m.so (found suitable version "3.6.10", minimum required is "3") [...] 02:24:38 -- Found Python3Interp: /usr/bin/python3 (found suitable version "3.6.9", minimum required is "3") 02:24:38 CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message): 02:24:38 Could NOT find Python3Libs: Found unsuitable version "3.6.10", but required 02:24:38 is exact version "3.6.9" (found /usr/lib64/libpython3.6m.so) 02:24:38 Call Stack (most recent call first): 02:24:38 /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:376 (_FPHSA_FAILURE_MESSAGE) 02:24:38 cmake/modules/FindPython3Libs.cmake:280 (FIND_PACKAGE_HANDLE_STANDARD_ARGS) 02:24:38 src/CMakeLists.txt:232 (find_package) -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1153830] New: No application launcher for Phyton IDLE in K-launcher.
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1153830 Bug ID: 1153830 Summary: No application launcher for Phyton IDLE in K-launcher. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: soren.thor91(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installing the python-idle and python3-idle packages, no application launcher is visible at the program menu. I have this problem on both mine Opensuse Leap 15.1 installs, different computers. Expected result: A visible program launcher under the development category in the K-launcher for IDLE3/ Pyhon IDLE or similar. Actual result: No program launcher for the python-idle or similar is nowhere to found. I have tried to search for it in the menu and check all the applications categories. Way to duplicate the bug: Install python3-idle or python-idle Temporary workaround: Open the terminal and run idle or idle3 and the graphical environment opens. System information: Opensuse 15.1 python-idle 2.7.14-lp151.10.7.1 python3-idle 3.6.5-lp151.5.2 KDE plasma 5.12.8 KDE framework: 5.55.0 Qt version: 5.9.7 Kernel: 4.12.14-lp151.28.20-default -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1149792] New: openssl 1.1.1c causes build failures in other packages
by bugzilla_noreply＠novell.com 10 Jun '22

10 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1149792 Bug ID: 1149792 Summary: openssl 1.1.1c causes build failures in other packages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: vcizek(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/project/show/openSUSE:Leap:15.2:Staging:B: Build failed apr-util (i586, x86_64) Build failed fipscheck (i586, x86_64) Build failed git (i586, x86_64) Build failed mysql-connector-cpp (x86_64) Build failed neon (i586, x86_64) Build failed openslp (i586, x86_64) Build failed perl-DBD-mysql (i586, x86_64) Build failed perl-IO-Socket-SSL (i586, x86_64) Build failed perl-Net-SSLeay (i586, x86_64) Build failed python (i586, x86_64) Build failed python-M2Crypto (i586, x86_64) Build failed python-pyOpenSSL (i586, x86_64) Build failed python-tornado (i586, x86_64) Build failed python3 (i586, x86_64) Build failed thrift (i586, x86_64) Some are as simple as a missing dependency on zlib, others are less obvious. Could you please take a look? -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[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