June 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1183488] New: Cannot pair Sony WF-1000XM3 (bluetooth 5.0 device) and use for audio
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183488 Bug ID: 1183488 Summary: Cannot pair Sony WF-1000XM3 (bluetooth 5.0 device) and use for audio Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The Sony "earplugs" WF-1000XM3 are two devices that should somehow pair as a single device. With Linux it does not work correctly for reasons unknown. It means I see the device connected, but I can't select it as audio output device. One effect are repeating syslog messages like this: kernel: Bluetooth: hci0: advertising data len corrected Using hcidump I get messages like this: > HCI Event: LE Meta Event (0x3e) plen 42 LE Advertising Report ADV_IND - Connectable undirected advertising (0) bdaddr 94:DB:56:12:34:56 (Public) Unknown type 0x16 with 5 bytes data TX power level: 244 Complete service classes: 0xfe03 Complete local name: 'LE_WF-1000XM3' RSSI: -49 > HCI Event: LE Meta Event (0x3e) plen 35 LE Advertising Report SCAN_RSP - Scan Response (4) bdaddr 94:DB:56:12:34:56 (Public) Unknown type 0xff with 21 bytes data RSSI: -49 > HCI Event: LE Meta Event (0x3e) plen 42 LE Advertising Report ADV_IND - Connectable undirected advertising (0) bdaddr 94:DB:56:12:34:56 (Public) Unknown type 0x16 with 5 bytes data TX power level: 244 Complete service classes: 0xfe03 Complete local name: 'LE_WF-1000XM3' RSSI: -49 Trying a manual pair via bluetoothctl, I can scan, pair, and connect. Seems the bluetooth stack is not ready for BT 5.0 devices, or the device is somewhat non-standard. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1200077] New: openSUSE-Leap-15.4-GNOME-Live-x86_64-Build6.157-Media.iso does not boot
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200077 Bug ID: 1200077 Summary: openSUSE-Leap-15.4-GNOME-Live-x86_64-Build6.157-Media. iso does not boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I downloaded openSUSE-Leap-15.4-GNOME-Live-x86_64-Build6.157-Media.iso, verified the SHA-256 checksum OK, and wrote it on an USB stick using "dd". Whenever I try to boot from the stick with my Lenovo TP E15 2nd gen, the boot attempt quickly returns to BIOS. Initially I had tried with Secure boot enabled, but even with Secure Boot disabled, it won't boot (same effect). I could boot Tails 5.0 without a problem, however. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1194991] supertux2: ca-certificate problem
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1194991 https://bugzilla.suse.com/show_bug.cgi?id=1194991#c2 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|lnussel(a)suse.com |joop.boonen(a)boonen.org --- Comment #2 from Ludwig Nussel <lnussel(a)suse.com> --- There's zero details, nor any explanation why this would be a ca-certificates problem. The screenshot suggests that the game hardcodes locations of certificates though. It shouldn't do that but call SSL_CTX_set_default_verify_paths() instead (gnutls_certificate_set_x509_system_trust(cred) if it uses gnutls) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199618] [Build 20220516] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1199618 https://bugzilla.suse.com/show_bug.cgi?id=1199618#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: jeos-ltp-syscalls@aarch64-HD24G https://openqa.opensuse.org/tests/2396570#step/fanotify16/1 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` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196256] [Build 20220219] openQA test fails in podman_firewall
by bugzilla_noreply＠suse.com 01 Jun '22

01 Jun '22

https://bugzilla.suse.com/show_bug.cgi?id=1196256 https://bugzilla.suse.com/show_bug.cgi?id=1196256#c3 --- Comment #3 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: containers_image https://openqa.opensuse.org/tests/2396478#step/podman_firewall/1 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` Expect the next reminder at the earliest in 112 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.

1 0