openSUSE Bugs July 2021

bugs@lists.opensuse.org

1 participants
3177 discussions

[Bug 925275] New: NVIDIA Driver not installable

by bugzilla_noreply＠novell.com

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 weeks, 1 day

[Bug 1004201] New: System hangs during boot due to loop trying to load nvidia modules

by bugzilla_noreply＠novell.com

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 weeks, 2 days

[Bug 1179981] New: EFI on raid1: grub2-install fails to update nvram

by bugzilla_noreply＠suse.com

https://bugzilla.suse.com/show_bug.cgi?id=1179981 Bug ID: 1179981 Summary: EFI on raid1: grub2-install fails to update nvram Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: jjletho67-esus(a)yahoo.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844418 --> https://bugzilla.suse.com/attachment.cgi?id=844418&action=edit Partitions layout I installed openSUSE LEAP 15.2 on a kvm virtual machine with ovmf firmware. My disks layout is configured for a full redundancy, so the efi partition is on raid1 (I've already used this layout on openSUSE 42.3 and by doc it should be supported https://doc.opensuse.org/documentation/leap/startup/single-html/book-opensu…) I'm attaching the partition layout. All file systems are ext4, secureboot is disabled The machine has worked fine ( i rebooted severak times) until i performed a a full patch (zypper patch). At the next reboot grub was not able to boot the os and stop with the error: "error: verification requested but nobody cares" I immediately found this bug https://bugzilla.suse.com/show_bug.cgi?id=1175766 but the solving patch was already installed. Curiously i was able to boot with the installation disk, selecting the "boot from hard disk" option. I tried to launch grub2-install --verbose manually and it ended up with this error: " ... grub2-install: info: copying `/boot/grub2/x86_64-efi/core.efi' -> `/boot/efi/EFI/opensuse/grubx64.efi'. grub2-install: info: Registering with EFI: distributor = `opensuse', path = `\EFI\opensuse\grubx64.efi', ESP at mduuid/9182c46b9d469f79b48850b68f3371a5. grub2-install: info: executing efibootmgr --version </dev/null >/dev/null. grub2-install: info: executing modprobe -q efivars. grub2-install: info: executing efibootmgr -c -d. efibootmgr: option requires an argument -- 'd' efibootmgr version 14 usage: efibootmgr [options] -a | --active sets bootnum active -A | --inactive sets bootnum inactive -b | --bootnum XXXX modify BootXXXX (hex) -B | --delete-bootnum delete bootnum (specified with -b) --delete delete entry by bootnum (-b), by UUID (-P) or by disk+partition[+file] (-d -p -l) -c | --create create new variable bootnum and add to bootorder -C | --create-only create new variable bootnum and do not ... " My speculation is that efibootmgr hasn't the disks parameter due to the raid configuration of the efi partition. Some updated packages has "lost" the ability to deal properly with EFI on raid1 STEP TO REPRODUCE: Install LEAP 15.2 with the same partitions layout described above. Perform a "zypper patch" and reboot it ACTUAL RESULTS: the system does not boot, grub stops with "error: verification requested but nobody cares" EXPECTED RESULTS: the system continues to boot properly -- You are receiving this mail because: You are on the CC list for the bug.

2 weeks, 2 days

[Bug 1188608] New: openblas 0.3.16 causes segfaults

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1188608 Bug ID: 1188608 Summary: openblas 0.3.16 causes segfaults Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: code(a)bnavigator.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- From the comments on the package in openSUSE:Factory https://build.opensuse.org/package/show/openSUSE:Factory/openblas#comment-1… Andre Barros Please, update to OpenBLAS to 3.17, as some optimizations were causing segfaults and reverted. See: https://github.com/xianyi/OpenBLAS/blob/develop/Changelog.txt. Andre Barros It seems that octave 6.3.0 build failures (on test phase) may be associated to this on Tumbleweed. Andre Barros OK, this really needs a better explanation. I have Tumbleweed and Leap 15.3 installed on different computers, and on both of them I use the Science repo to provide some more packages I need. Downgrading to default versions (3.13 on Leap and 3.14 on Tumbleweed) fixes the problem with Octave, as I was able to build version 6.3 and also run the tests (make check-local) without unknown failures. It probably affects other numerical packages too. Regards, Andr� ---- Packages where I see this: python-photutils python-astropy:test many more -- You are receiving this mail because: You are on the CC list for the bug.

2 weeks, 2 days

[Bug 1027519] New: Xen: Missing upstream bug fixes

by bugzilla_noreply＠novell.com

http://bugzilla.suse.com/show_bug.cgi?id=1027519 Bug ID: 1027519 Summary: Xen: Missing upstream bug fixes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs(a)suse.de Reporter: carnold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are upstream patches fixing bugs needed for this version of Xen. -- You are receiving this mail because: You are on the CC list for the bug.

2 weeks, 3 days

[Bug 1184069] New: GRUB on a crypted partition takes > 10 seconds to unlock the filesystem

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184069 Bug ID: 1184069 Summary: GRUB on a crypted partition takes > 10 seconds to unlock the filesystem Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: p.heinlein(a)heinlein-support.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed 15.2 plain vanilla on a Thinkpad X1.Extreme Gen.3 with a ~2 TB NVME and I set a crypto disc password during installation (in YaST). Grub needs > 10 seconds to unlock the key, so booting is very slow. It's very similar to https://unix.stackexchange.com/questions/369414/grub-takes-too-long-to-unlo… https://bbs.archlinux.org/viewtopic.php?id=228865 so I also think, that the crypto or number of iterations is way to expensive here and needs too much time. Maybe the SUSE team should/could look for a similar safe, but faster method (SHA256?) here? -- You are receiving this mail because: You are on the CC list for the bug.

2 weeks, 3 days

[Bug 1127690] New: haveged: Couldn't initialize HAVEGE rng 9

by bugzilla_noreply＠novell.com

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 weeks, 3 days

[Bug 1059001] New: kded5 or kdeint5 crashes after systemctl restart NetworkManager

by bugzilla_noreply＠novell.com

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 weeks, 4 days

[Bug 1184141] New: coturn.service: syscall restrictions are too strict

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1184141 Bug ID: 1184141 Summary: coturn.service: syscall restrictions are too strict Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: xm.koutny+suse.com(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm running coturn-4.5.2-lp152.20.1.x86_64 from network:telephony (on Leap 15.2). I updated from 4.5.1 (Leap) which worked fine but now I'm running into troubles: 1) Started process will terminate soon with SIGSYS 2) After resolving this, it'll fail with > 0: : ERROR: main: Cannot configure any meaningful IP listener address I strace'd both issues: 1) (very early at the start of binary, fails even with other executables, most likely anything linked with pthread) > 1974 set_tid_address(0x7fefc2c04290) = 1974 > 1974 set_robust_list(0x7fefc2c042a0, 24) = 0 > 1974 rt_sigaction(SIGRTMIN, {sa_handler=0x7fefc1fc5bf0, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7fefc1fd22d0}, NULL, 8) = 0 > 1974 rt_sigaction(SIGRT_1, {sa_handler=0x7fefc1fc5c90, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7fefc1fd22d0}, NULL, 8) = 0 > 1974 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 > 1974 prlimit64(0, RLIMIT_STACK, NULL, <unfinished ...>) = ? > 1 <... epoll_pwait resumed>[{EPOLLHUP, {u32=2326093456, u64=94697765035664}}], 50, -1, NULL, 8) = 1 > 1974 +++ killed by SIGSYS +++ 2) > 2168 write(3, "0: : WARNING: cannot find privat"..., 69) = 69 > 2168 write(3, "0: : WARNING: cannot start TLS a"..., 95) = 95 > 2168 write(3, "0: : NO EXPLICIT LISTENER ADDRES"..., 53) = 53 > 2168 write(3, "0: : ===========Discovering list"..., 58) = 58 > 2168 socket(AF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = -1 EAFNOSUPPORT (Address family not supported by protocol) > 2168 write(3, "0: : ERROR: main: Cannot configu"..., 70) = 70 The following .service file modification fixes the issue for me: -SystemCallFilter=~@clock @debug @module @mount @raw-io @reboot @swap @privileged @resources @cpu-emulation @obsolete -RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX +SystemCallFilter=~@clock @debug @module @mount @raw-io @reboot @swap @privileged @cpu-emulation @obsolete +RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX AF_NETLINK Note that the first change may not be needed with systemd newer than v235 [1] (I guess I shouldn't be running coturn from network:telephony on Leap). [1] 4c3a917617 ("seccomp: include prlimit64 and ugetrlimit in @default") v235~15^2~3 -- You are receiving this mail because: You are on the CC list for the bug.

2 weeks, 6 days

[Bug 1162224] New: Installed version missmatch between libpython3_6m1_0 and python3-base (problem for cmake)

by bugzilla_noreply＠novell.com

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 weeks, 6 days

← Newer
1
2
3
4
5
6
7
...
318
Older →

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs July 2021