January 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1194099] Sound using headphones does not work after update yesterday.
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194099 https://bugzilla.suse.com/show_bug.cgi?id=1194099#c1 --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- *** Bug 1194204 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193124] New: tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193124 Bug ID: 1193124 Summary: tumbleweed release 20211124 with kernel 5.15.3 bluetooth fail Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tech(a)reachthetribes.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My pc is an ASUS ZenBook Flip S UX371EA. This does not seem to be a duplicate After tumbleweed release 20211124 with kernel update to 5.15.3, bluetooth fails to operate. It no longer shows up in the system tray, the bluetooth service under systemctl doesn't start, and the btusb module is not loaded to the new kernel. When it is manually added to the kernel and the bluetooth service is started, the bluetooth icon comes back to the system tray, but bluetooth will not pick up any devices. Here are the command results: on the 5.15 kernel > sudo rfkill ID TYPE DEVICE SOFT HARD 0 wlan asus-wlan unblocked unblocked 1 bluetooth asus-bluetooth unblocked unblocked 2 wlan phy0 unblocked unblocked When this command is run in the 5.14 kernel, there is another line that comes out that is missing here: 3 bluetooth hci0 unblocked unblocked on the 5.15 kernel, lsusb doesn't read anything with bluetooth > lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 13d3:56eb IMC Networks USB2.0 HD UVC WebCam Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub When this is run on the 5.14 kernel, the bluetooth adaptor shows up: Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth For journalctl on the 5.15 kernel: > journalctl -b | egrep -i bluetooth Nov 26 20:27:44 asustribetrek NetworkManager[780]: <info> [1637980064.3080] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so) Nov 26 20:27:48 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:27:50 asustribetrek kded5[1660]: bluedevil: Bluetooth operational changed false Nov 26 20:28:14 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:31:29 asustribetrek systemd[1]: Condition check resulted in Bluetooth service being skipped. Nov 26 20:31:30 asustribetrek kded5[5664]: bluedevil: Bluetooth operational changed false journalctl on the 5.14 kernel had significantly more results, as expected: > journalctl -b | egrep -i bluetooth Nov 26 20:35:16 asustribetrek NetworkManager[790]: <info> [1637980516.4366] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.32.12/libnm-device-plugin-bluetooth.so) Nov 26 20:35:17 asustribetrek kernel: Bluetooth: Core ver 2.22 Nov 26 20:35:17 asustribetrek kernel: NET: Registered PF_BLUETOOTH protocol family Nov 26 20:35:17 asustribetrek kernel: Bluetooth: HCI device and connection manager initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: HCI socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: L2CAP socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: SCO socket layer initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Device revision is 2 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Secure boot is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: OTP lock is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: API lock is enabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Debug lock is disabled Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi Nov 26 20:35:17 asustribetrek systemd[1]: Starting Bluetooth service... Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Bluetooth daemon 5.62 Nov 26 20:35:17 asustribetrek systemd[1]: Started Bluetooth service. Nov 26 20:35:17 asustribetrek systemd[1]: Reached target Bluetooth Support. Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Starting SDP server Nov 26 20:35:17 asustribetrek bluetoothd[1432]: Bluetooth management interface 1.21 initialized Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP filters: protocol multicast Nov 26 20:35:17 asustribetrek kernel: Bluetooth: BNEP socket layer initialized Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Waiting for firmware download to complete Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Firmware loaded in 1694554 usecs Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Waiting for device to boot Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Device booted in 14663 usecs Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Applying Intel DDC parameters completed Nov 26 20:35:19 asustribetrek kernel: Bluetooth: hci0: Firmware revision 0.4 build 5 week 39 2021 Nov 26 20:35:19 asustribetrek bluetoothd[1432]: Admin Policy Set interface registered Nov 26 20:35:19 asustribetrek bluetoothd[1432]: Admin Policy Status interface registered Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Player registered: sender=:1.33 path=/media_player0 Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM TTY layer initialized Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM socket layer initialized Nov 26 20:35:22 asustribetrek kernel: Bluetooth: RFCOMM ver 1.11 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/ldac Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx_hd Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_hd Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/aptx Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aac Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSink/sbc_xq Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/sbc_xq Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/faststream_duplex Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Nov 26 20:35:22 asustribetrek bluetoothd[1432]: Endpoint registered: sender=:1.33 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Nov 26 20:35:24 asustribetrek kded5[1784]: bluedevil: Bluetooth operational changed true For dmesg on the 5.15 kernel, the results were empty: > dmesg | grep -i bluetooth For dmesg on the 5.14 kernel, there were lots of results as expected: > dmesg | grep -i bluetooth [ 5.769571] Bluetooth: Core ver 2.22 [ 5.769616] NET: Registered PF_BLUETOOTH protocol family [ 5.769618] Bluetooth: HCI device and connection manager initialized [ 5.769622] Bluetooth: HCI socket layer initialized [ 5.769628] Bluetooth: L2CAP socket layer initialized [ 5.769633] Bluetooth: SCO socket layer initialized [ 5.915512] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018 [ 5.916500] Bluetooth: hci0: Device revision is 2 [ 5.916511] Bluetooth: hci0: Secure boot is enabled [ 5.916513] Bluetooth: hci0: OTP lock is enabled [ 5.916514] Bluetooth: hci0: API lock is enabled [ 5.916515] Bluetooth: hci0: Debug lock is disabled [ 5.916516] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 5.963172] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi [ 6.003424] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.003428] Bluetooth: BNEP filters: protocol multicast [ 6.003431] Bluetooth: BNEP socket layer initialized [ 7.696847] Bluetooth: hci0: Waiting for firmware download to complete [ 7.698400] Bluetooth: hci0: Firmware loaded in 1694554 usecs [ 7.698487] Bluetooth: hci0: Waiting for device to boot [ 7.713473] Bluetooth: hci0: Device booted in 14663 usecs [ 7.714204] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc [ 7.716402] Bluetooth: hci0: Applying Intel DDC parameters completed [ 7.719474] Bluetooth: hci0: Firmware revision 0.4 build 5 week 39 2021 [ 11.170866] Bluetooth: RFCOMM TTY layer initialized [ 11.170873] Bluetooth: RFCOMM socket layer initialized [ 11.170877] Bluetooth: RFCOMM ver 1.11 -- You are receiving this mail because: You are on the CC list for the bug.

1 62

[Bug 1194199] New: zypper dup on multiple HPE servers freezes, resulting system will not start
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194199 Bug ID: 1194199 Summary: zypper dup on multiple HPE servers freezes, resulting system will not start Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: bob(a)muhlenberg.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 854887 --> http://bugzilla.opensuse.org/attachment.cgi?id=854887&action=edit Rapidly scrolling errors after startup, post fozen zypper dup On two different HPE DL-380 and DL-360 ( Gen 8 and Gen 9 ) servers I performed zypper dup and after installing perhaps half of the packages, the zypper dup stalls and the system becomes unresponsive. The system looses network connectivity and appears to be frozen. After waiting a long time ( a day ) we rebooted the system, on booting the system boots through GRUB and after a few seconds haangs ( usually at a green "three dots" screen ). On booting via Advanced Options --> Recovery It is observed various dracut errors a couple seconds into startup, followed by a continuous stream of errors about 10 a second: dracut-initqueue[PID]: udevadm: error while loading shared libraries: libsystemd-shared-246.so cannot open shared object file: no such file or directory This scrolls continuously with a new PID on every line. This never ends and the system is non-responsive. I am going to attempt to do an in place upgrade with the latest DVD ISO. In both instances the prior release installed was old ( 2020 or early 2021 vintage? ). If this is a known issue is there a way to recoup the system? If not, what do you need, log wise? Given this is two different physical systems and two different prior releases, it may be a serious issue. The first time I saw this was about 2 weeks ago. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1193134] [Build 20211126] openQA test fails in cups
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193134 https://bugzilla.suse.com/show_bug.cgi?id=1193134#c1 --- Comment #1 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: nis_server https://openqa.opensuse.org/tests/2118452 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184924] [Build 134.3] openQA test fails in kdump_and_crash - forced crash didn't result into expected reboot
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1184924 https://bugzilla.suse.com/show_bug.cgi?id=1184924#c46 --- Comment #46 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: jeos-extra@aarch64-HD24G https://openqa.opensuse.org/tests/2118404 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194212] New: systemd-journal-flush.service failed
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194212 Bug ID: 1194212 Summary: systemd-journal-flush.service failed 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- jshand@johns-pc:~> systemctl status systemd-journal-flush.service � systemd-journal-flush.service - Flush Journal to Persistent Storage Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static) Active: failed (Result: timeout) since Mon 2022-01-03 10:36:13 NZDT; 1h 17min ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 531 ExecStart=journalctl --flush (code=killed, signal=TERM) Main PID: 531 (code=killed, signal=TERM) CPU: 9ms Jan 03 10:34:43 johns-pc systemd[1]: Starting Flush Journal to Persistent Storage... Jan 03 10:36:13 johns-pc systemd[1]: systemd-journal-flush.service: start operation timed out. Terminating. Jan 03 10:36:13 johns-pc systemd[1]: systemd-journal-flush.service: Main process exited, code=killed, status=15/TERM Jan 03 10:36:13 johns-pc systemd[1]: systemd-journal-flush.service: Failed with result 'timeout'. Jan 03 10:36:13 johns-pc systemd[1]: Failed to start Flush Journal to Persistent Storage. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1122176] [Build 20190115] openQA test fails in steam
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1122176 https://bugzilla.suse.com/show_bug.cgi?id=1122176#c17 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |VERIFIED Resolution|WONTFIX |FIXED --- Comment #17 from Oliver Kurz <okurz(a)suse.com> --- agreed. Latest test https://openqa.opensuse.org/tests/2118440#step/steam/21 in the scenario https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor… looks just fine -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194193] Difficult login to bugzilla.opensuse.org
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194193 https://bugzilla.suse.com/show_bug.cgi?id=1194193#c3 --- Comment #3 from Nikolay Sabelnikov <79625490833(a)yandex.ru> --- (In reply to Andreas Stieger from comment #2) > Seen here for about a week I can observe this problem for 2 months, just no one gave it to me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194210] The "Report bug" button leads to an inactive resource.
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194210 http://bugzilla.opensuse.org/show_bug.cgi?id=1194210#c10 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- right. *** This bug has been marked as a duplicate of bug 1194193 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194210] New: The "Report bug" button leads to an inactive resource.
by bugzilla_noreply＠suse.com 02 Jan '22

02 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194210 Bug ID: 1194210 Summary: The "Report bug" button leads to an inactive resource. Classification: Internal Novell Products Product: openSUSE Build Service Version: master Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: webui Assignee: hvogel(a)suse.com Reporter: 79625490833(a)yandex.ru QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- Hello. Fix the link. The "error in report" button leads to https://bugzilla.opensuse.org/enter_bug.cgi?classification=7340&product=ope… Should lead here: https://bugzilla.suse.com/ -- You are receiving this mail because: You are on the CC list for the bug.

1 5