November 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1178518] New: [led controller] can not disable it -- taken as an analog controller (game controller)
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178518 Bug ID: 1178518 Summary: [led controller] can not disable it -- taken as an analog controller (game controller) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: soundlord(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: There is a led controler on the mother board (B550 phantom gaming 4 -- azrock). Disabled at bios --> still taken as a game controler Used the [https://forums.opensuse.org/showthread.php/545680-azrock-led-controller-tak…] advices... without success. Reproducible: Always Steps to Reproduce: 1. boot 2. launch a game emulator (different than mame) 3. seek for system settings -> game controllers 4. impossible to blacklist the "azrock led controller" Actual Results: Still no way to play favorite games with keyboard as the game controller seem to have mmore priority on the different input devices. Expected Results: Disable led controller to see if it is still taken as a game controller. Manufacturer: ASRock Serial #: A02019100900 Class 0 ((Defined at Interface level)) Subclass 0 Protocol 0 USB Version 1.01 Vendor ID 0x26ce Product ID 0x1a2 Revision 0.00 Speed 12 Mbit/s Channels 0 Max. Packet Size 8 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1178347] New: The clock in the Gnome top bar disagrees with the system clock
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178347 Bug ID: 1178347 Summary: The clock in the Gnome top bar disagrees with the system clock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- At the moment (some minutes before I click "Submit bug") typing "date" at a shell prompt answers lun nov 2 10:08:19 CET 2020 (i.e., Monday 2 November 2020, 10:08:19 CET) which is correct for my timezone (Europe/Brussels) but the clock on the top bar of the Gnome window manager said (at the same time) lun 2 Nov 11:08:21. This is not a manifestation of bug 1116498 because until I saw that bug, my /etc/sysconfig/clock contained the weird values TIMEZONE="Europe/Brussels" DEFAULT_TIMEZONE="GMT" where Europe/Brussels is correct but GMT is none of my winter time, my summer time, or my hardware clock time (see bug 116498 comment #5 for details) and just now I changed DEFAULT_TIMEZONE to "CET" by means of Yast2 → System → Sysconfig Editor → Other → etc → sysconfig → clock → DEFAULT_TIMEZONE then logged out of X (which showed that the clock on the KDE login prompt was set correctly) and back in, and nothing had changed. AFAIK, the clock in the Gnome topbar believes that Europe/Brussels is still on summer time, while both the "date" program and the KDE display manager's login window know that it is now on winter time. (My display manager is kdm but my window manager is gnome.) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1178369] /etc/sysctl.conf contains disable_ipv6, but IPv6 still active after reboot
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178369 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178369] /etc/sysctl.conf contains disable_ipv6, but IPv6 still active after reboot
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178369 https://bugzilla.suse.com/show_bug.cgi?id=1178369#c4 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui(a)suse.com --- Comment #4 from Franck Bui <fbui(a)suse.com> --- (In reply to Freek de Kruijf from comment #2) > After giving the command "sysctl --system" and having > /etc/sysctl.d/70-yast.conf in place, IPv6 also became disabled. > It looks like this command does not get executed during the boot process. I manually created /etc/sysctl.d/70-yast.conf with "net.ipv6.conf.all.disable_ipv6 = 1" and rebooted and it worked as expected - ipv6 was disabled. Just to make sure, you did reboot after yast2 created this conf file, right ? If so can you try to restart systemd-sysctl.service manually and see if ipv6 get disabled this way ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172475] Random screen flashing after suspend on KDE
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1172475 https://bugzilla.suse.com/show_bug.cgi?id=1172475#c9 Miroslav Beneš <mbenes(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mbenes(a)suse.com --- Comment #9 from Miroslav Beneš <mbenes(a)suse.com> --- Piotr, I presume this is still a problem. Could you share the kernel log after the issue manifests itself, please? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178102] Blender not find nvcc
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178102 https://bugzilla.suse.com/show_bug.cgi?id=1178102#c7 --- Comment #7 from Marcus Rückert <mrueckert(a)suse.com> --- a cuda rpm should setup the PATH to include the binaries in the search list. it is not blender providing the binaries. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178478] [rpm4.16] apache2 fails to build
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1178478 https://bugzilla.suse.com/show_bug.cgi?id=1178478#c1 --- Comment #1 from Petr Gajdos <pgajdos(a)suse.com> --- As I looked at it today, yes, you are probably correct. Originally I wanted to take hackweek to include httpd testing (apache-test) in the file, perhaps is time to take some innovation time sooner. I plan to look at it next week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092648] Move modprobe configuration to /usr/lib/modprobe.d
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1092648 https://bugzilla.suse.com/show_bug.cgi?id=1092648#c29 --- Comment #29 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1092648) was mentioned in https://build.opensuse.org/request/show/846461 Factory / kmod -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1142604] VUL-1: CVE-2019-14248: nasm: NULL pointer dereference in asm/pragma.c leading to Segmentation fault
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

https://bugzilla.suse.com/show_bug.cgi?id=1142604 https://bugzilla.suse.com/show_bug.cgi?id=1142604#c5 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Michael Vetter <mvetter(a)suse.com> --- Tumbleweed is at 2.15.05 now and not affected anymore $ nasm -felf64 nullderef_nasm-2.14.02_pragma_limit $ ls nullderef_nasm-2.14.02_pragma_limit nullderef_nasm-2.14.o -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1178505] New: pipewire-media-session crashes on headset connect
by bugzilla_noreply＠suse.com 06 Nov '20

06 Nov '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1178505 Bug ID: 1178505 Summary: pipewire-media-session crashes on headset connect Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: victor.zhestkov(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /usr/bin/pipewire-media-session crashes on first connection of the headset after system boot, but works fine on disconnecting and connecting the headset back. Message: Process 6710 (pipewire-media-) of user 1000 dumped core. Stack trace of thread 6710: #0 0x00007f9d94c14e70 pw_proxy_add_listener (libpipewire-0.3.so.0 + 0x55e70) #1 0x00005616eafa8dc6 reserve_release (pipewire-media-session + 0x17dc6) #2 0x00005616eafa35a3 object_handler (pipewire-media-session + 0x125a3) #3 0x00007f9d94b87501 dbus_connection_dispatch (libdbus-1.so.3 + 0x1a501) #4 0x00007f9d94710376 dispatch_cb (libspa-dbus.so + 0x1376) #5 0x00007f9d94c6a5db loop_iterate (libspa-support.so + 0x75db) #6 0x00007f9d94bfbf7b pw_main_loop_run (libpipewire-0.3.so.0 + 0x3cf7b) #7 0x00005616eafa1046 main (pipewire-media-session + 0x10046) #8 0x00007f9d949cbe0a __libc_start_main (libc.so.6 + 0x27e0a) #9 0x00005616eafa139a _start (pipewire-media-session + 0x1039a) Stack trace of thread 6711: #0 0x00007f9d94aa3ff6 epoll_wait (libc.so.6 + 0xffff6) #1 0x00007f9d94c731b4 impl_pollfd_wait (libspa-support.so + 0x101b4) #2 0x00007f9d94c6a544 loop_iterate (libspa-support.so + 0x7544) #3 0x00007f9d94be6dd8 do_loop (libpipewire-0.3.so.0 + 0x27dd8) #4 0x00007f9d94985eb1 start_thread (libpthread.so.0 + 0x8eb1) #5 0x00007f9d94aa3ccf __clone (libc.so.6 + 0xffccf) (gdb) bt #0 spa_hook_list_append (data=data@entry=0x5616ebdd4220, funcs=funcs@entry=0x5616eafd4fe0 <sync_complete_release>, hook=hook@entry=0x5616ebdd4250, list=0x48) at ../spa/include/spa/utils/hook.h:94 #1 pw_proxy_add_listener (proxy=0x0, listener=listener@entry=0x5616ebdd4250, events=events@entry=0x5616eafd4fe0 <sync_complete_release>, data=data@entry=0x5616ebdd4220) at ../src/pipewire/proxy.c:202 #2 0x00005616eafa8dc6 in reserve_release (data=0x5616ebdd4220, d=<optimized out>, forced=<optimized out>) at ../src/examples/media-session/alsa-monitor.c:634 #3 0x00005616eafa35a3 in object_handler (c=0x5616ebd63710, m=m@entry=0x5616ebdc5cc0, userdata=userdata@entry=0x5616ebdb2890) at ../src/examples/media-session/reserve.c:131 #4 0x00007f9d94b87501 in _dbus_object_tree_dispatch_and_unlock (found_object=<synthetic pointer>, message=<optimized out>, tree=0x5616ebd63b60) at dbus-object-tree.c:1020 #5 dbus_connection_dispatch (connection=0x5616ebd63710) at dbus-connection.c:4745 #6 dbus_connection_dispatch (connection=0x5616ebd63710) at dbus-connection.c:4576 #7 0x00007f9d94710376 in dispatch_cb (userdata=0x5616ebd62960) at ../spa/plugins/support/dbus.c:67 #8 0x00007f9d94c6a5db in loop_iterate (object=0x5616ebd43368, timeout=<optimized out>) at ../spa/plugins/support/loop.c:306 #9 0x00007f9d94bfbf7b in pw_main_loop_run (loop=0x5616ebd43220) at ../src/pipewire/main-loop.c:156 #10 0x00005616eafa1046 in main (argc=<optimized out>, argv=<optimized out>) at ../src/examples/media-session/media-session.c:2222 -- You are receiving this mail because: You are on the CC list for the bug.

1 2