May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225147] Kernel hard lockup under mild GPU load
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225147 https://bugzilla.suse.com/show_bug.cgi?id=1225147#c4 --- Comment #4 from llyyr <llyyr.public(a)gmail.com> --- (In reply to Takashi Iwai from comment #3) > Thanks. > > As a blind shot (as it's a 6.7 regression), could you try later a test > patched kernel in OBS home:tiwai:bsc1219983 repo? Once after the build > finishes, the package will appear at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1219983/standard/ Has the same issue, I get hard lockup. I'd imagine it's related to power management or gpu clocks because these crashes are very similar to what happens when you're running a very unstable overclock and you stress your system a little. Except I'm not overclocking. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225277] New: Cant update
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225277 Bug ID: 1225277 Summary: Cant update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: mak343(a)live.co.uk QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- <html>Dependency resolution failed:<br/><br/>the to be installed tlp-1.6.1-2.1.noarch conflicts with 'tuned' provided by the to be installed tuned-2.22.1.2+git.86ac977-3.1.noarch</html> -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1211428] Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 ted chang <monkeyboyted(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|https://www.lg.com/ca_en/tv | |-soundbars/lcd-tvs/32ld450/ | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211428] Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 ted chang <monkeyboyted(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://www.lg.com/ca_en/tv | |-soundbars/lcd-tvs/32ld450/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225280] New: Custom Shortcut is missing
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225280 Bug ID: 1225280 Summary: Custom Shortcut is missing Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Previously I was able to create a custom shortcut key combination that was sending a static defined text to wherever needed. Any idea if it was intentionally removed ? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1224462] RC2 Tik installer / first boot doesn't prompt for hostname
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224462 https://bugzilla.suse.com/show_bug.cgi?id=1224462#c8 --- Comment #8 from Richard Brown <rbrown(a)suse.com> --- (In reply to Mike Watkins from comment #7) > For hostname, hostnamectl is the easiest solution. I have taken to using > combustion for other things in recent tests, although I have been facing > some errors which leave me at an emergency prompt. > > That leads me to ask: Is it possible under Tik that combustion runs before > the network is defined? That’s the default behaviour unless the user explicitly requests the network in combustion.. and even then combustion can be used to redefine it -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224462] RC2 Tik installer / first boot doesn't prompt for hostname
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224462 https://bugzilla.suse.com/show_bug.cgi?id=1224462#c7 --- Comment #7 from Mike Watkins <solutionroute(a)gmail.com> --- For hostname, hostnamectl is the easiest solution. I have taken to using combustion for other things in recent tests, although I have been facing some errors which leave me at an emergency prompt. That leads me to ask: Is it possible under Tik that combustion runs before the network is defined? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223619] New: Unexpected messages from rtl8812au regarding address ("Current addr" vs. "Expected addr")
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223619 Bug ID: 1223619 Summary: Unexpected messages from rtl8812au regarding address ("Current addr" vs. "Expected addr") Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In Leap 15.5 using kernel 5.14.21-150500.55.59-default (or previous) and rtl8812au-kmp-default-5.13.6+git20220905.a8450b0_k5.14.21_150500.53-lp155.1.37.x86_64 I see frequent messages regarding the address, like these: May 02 01:08:30 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: MY MA CA DD RE SS 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:08:30 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 (where MY MA CA DD RE SS is the MAC address of my WLAN adapter) This triggers: May 02 01:08:30 i7g4x4a.site kernel: netdevice: wlan0: Incorrect netdev->dev_addr May 02 01:08:30 i7g4x4a.site kernel: WARNING: CPU: 1 PID: 1996 at ../net/core/dev_addr_lists.c:513 dev_addr_check+0xbb/0x140 and a lengthy call trace like this: May 02 01:08:30 i7g4x4a.site kernel: Call Trace: May 02 01:08:30 i7g4x4a.site kernel: <TASK> May 02 01:08:30 i7g4x4a.site kernel: __dev_open+0x3f/0x190 May 02 01:08:30 i7g4x4a.site kernel: __dev_change_flags+0x178/0x1d0 May 02 01:08:30 i7g4x4a.site kernel: dev_change_flags+0x23/0x60 May 02 01:08:30 i7g4x4a.site kernel: do_setlink+0x319/0x1070 May 02 01:08:30 i7g4x4a.site kernel: ? do_setlink+0x710/0x1070 May 02 01:08:30 i7g4x4a.site kernel: ? do_setlink+0x710/0x1070 May 02 01:08:30 i7g4x4a.site kernel: ? __nla_parse+0x4e/0x60 May 02 01:08:30 i7g4x4a.site kernel: __rtnl_newlink+0x567/0x910 May 02 01:08:30 i7g4x4a.site kernel: ? __kmalloc_node_track_caller+0x1ba/0x3b0 May 02 01:08:30 i7g4x4a.site kernel: ? pskb_expand_head+0x71/0x300 May 02 01:08:30 i7g4x4a.site kernel: ? inet6_fill_ifla6_attrs+0x469/0x490 May 02 01:08:30 i7g4x4a.site kernel: ? kmalloc_reserve+0x2e/0x80 May 02 01:08:30 i7g4x4a.site kernel: ? apparmor_inet_conn_request+0x40/0x40 May 02 01:08:30 i7g4x4a.site kernel: ? __switch_to_asm+0x3a/0x60 May 02 01:08:30 i7g4x4a.site kernel: ? finish_task_switch+0x8a/0x2d0 May 02 01:08:30 i7g4x4a.site kernel: ? kmem_cache_alloc_trace+0x4f/0x4c0 May 02 01:08:30 i7g4x4a.site kernel: rtnl_newlink+0x47/0x70 May 02 01:08:30 i7g4x4a.site kernel: ? ns_capable_common+0x27/0x50 May 02 01:08:30 i7g4x4a.site kernel: rtnetlink_rcv_msg+0x134/0x370 May 02 01:08:30 i7g4x4a.site kernel: ? __kmalloc_node_track_caller+0x1ba/0x3b0 May 02 01:08:30 i7g4x4a.site kernel: ? rtnl_calcit.isra.35+0x140/0x140 May 02 01:08:30 i7g4x4a.site kernel: netlink_rcv_skb+0x50/0x100 May 02 01:08:30 i7g4x4a.site kernel: netlink_unicast+0x1b6/0x280 May 02 01:08:30 i7g4x4a.site kernel: netlink_sendmsg+0x320/0x450 May 02 01:08:30 i7g4x4a.site kernel: sock_sendmsg+0x5f/0x70 May 02 01:08:30 i7g4x4a.site kernel: ____sys_sendmsg+0x1ee/0x250 May 02 01:08:30 i7g4x4a.site kernel: ? copy_msghdr_from_user+0x5c/0x90 May 02 01:08:30 i7g4x4a.site kernel: ? path_openat+0x3ce/0x1130 May 02 01:08:30 i7g4x4a.site kernel: ___sys_sendmsg+0x88/0xd0 May 02 01:08:30 i7g4x4a.site kernel: ? proc_put_char.part.3+0x20/0x20 May 02 01:08:30 i7g4x4a.site kernel: ? proc_put_char.part.3+0x20/0x20 May 02 01:08:30 i7g4x4a.site kernel: ? __do_proc_dointvec+0x2a1/0x3b0 May 02 01:08:30 i7g4x4a.site kernel: ? __rtnl_unlock+0x27/0x60 May 02 01:08:30 i7g4x4a.site kernel: ? netdev_run_todo+0x5e/0x300 May 02 01:08:30 i7g4x4a.site kernel: ? addrconf_sysctl_forward+0x117/0x250 May 02 01:08:30 i7g4x4a.site kernel: ? copyin+0x1c/0x30 May 02 01:08:30 i7g4x4a.site kernel: ? __sys_sendmsg+0x5e/0xa0 May 02 01:08:30 i7g4x4a.site kernel: __sys_sendmsg+0x5e/0xa0 May 02 01:08:30 i7g4x4a.site kernel: ? call_rcu+0x39b/0x7c0 May 02 01:08:30 i7g4x4a.site kernel: do_syscall_64+0x5b/0x80 May 02 01:08:30 i7g4x4a.site kernel: ? __SCT__preempt_schedule_notrace+0x8/0x8 May 02 01:08:30 i7g4x4a.site kernel: ? exit_to_user_mode_prepare+0xfe/0x240 May 02 01:08:30 i7g4x4a.site kernel: ? syscall_exit_to_user_mode+0x1f/0x40 May 02 01:08:30 i7g4x4a.site kernel: ? do_syscall_64+0x67/0x80 May 02 01:08:30 i7g4x4a.site kernel: ? ksys_write+0x66/0xe0 May 02 01:08:30 i7g4x4a.site kernel: ? syscall_exit_to_user_mode+0x1f/0x40 May 02 01:08:30 i7g4x4a.site kernel: ? do_syscall_64+0x67/0x80 May 02 01:08:30 i7g4x4a.site kernel: ? syscall_exit_to_user_mode+0x1f/0x40 May 02 01:08:30 i7g4x4a.site kernel: ? do_syscall_64+0x67/0x80 May 02 01:08:30 i7g4x4a.site kernel: ? exc_page_fault+0x67/0x150 May 02 01:08:30 i7g4x4a.site kernel: entry_SYSCALL_64_after_hwframe+0x6b/0xd5 Sometimes I also see different addresses like this: May 02 01:08:30 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: c2 41 1e 72 ba f9 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:08:30 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:15:17 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: 7a ef b1 5f b8 c6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:15:17 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:22:05 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: 12 2c af dc 80 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:22:05 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:28:53 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: b6 9b 46 b5 da 4e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:28:53 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:35:41 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: fa d4 6a 27 61 70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:35:41 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:42:30 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: 66 a4 51 f3 4a 38 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:42:30 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:49:19 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Current addr: 72 57 6b 4e 58 51 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 May 02 01:49:19 i7g4x4a.site kernel: rtl8812au 3-4:1.0 wlan0: Expected addr: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The WLAN adapter seems to work OK, but each of those messages creates a call stack in the journal, so that should go away. Device info (it seems TP-LINK does not like to set the serial number): ... Vendor: usb 0x2357 "TP-Link" Device: usb 0x010e "Archer T4UH v2 [Realtek RTL8812AU]" Serial ID: "123456" Driver: "rtl8812au" Driver Modules: "8812au" Device File: wlan0 ... WLAN encryption modes: TKIP CCMP WLAN authentication modes: open wpa-psk wpa-eap ... -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1214013] New: Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 Bug ID: 1214013 Summary: Shutdown did not finish (PC was not powered off, no obvious error logged) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major 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 Target Milestone: --- Found By: --- Blocker: --- Created attachment 868645 --> https://bugzilla.suse.com/attachment.cgi?id=868645&action=edit Screenshot when shutdown should power off the PC Maybe the issue is related to an MD-RAID being verified (see Bug 1214004), but the system did not power off. The last message in journal were: Aug 05 01:47:01 pc.site systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Aug 05 01:47:01 pc.site systemd[1]: Stopping Device-mapper event daemon... Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd detected break while being idle for 0 second(s), exiting. Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd shutting down. Aug 05 01:47:01 pc.site systemd[1]: dm-event.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Stopped Device-mapper event daemon. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Shutdown. Aug 05 01:47:01 pc.site systemd[1]: Reached target Late Shutdown Services. Aug 05 01:47:01 pc.site systemd[1]: systemd-poweroff.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Finished System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Shutting down. Aug 05 01:47:01 pc.site systemd-shutdown[1]: Syncing filesystems and block devices. Aug 05 01:47:03 pc.site systemd-shutdown[1]: Sending SIGTERM to remaining processes... Aug 05 01:47:03 pc.site haveged[1265]: haveged: Stopping due to signal 15 Aug 05 01:47:03 pc.site haveged[1265]: haveged starting up Aug 05 01:47:03 pc.site systemd-journald[1132]: Journal stopped I'm also adding a screenshot showing the last messages (that would last until I pressed the power button). Kernel was 5.14.21-150500.55.12-default The only other thing that looked unusual was this: ... Aug 05 01:46:59 pc.site systemd[1]: Stopped Record System Boot/Shutdown in UTMP. Aug 05 01:46:59 pc.site systemd[1]: Stopping Security Auditing Service... Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 is still in use. Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Failed to deactivate: Device or resource busy Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Control process exited, code=exited, status=1> Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Failed with result 'exit-code'. Aug 05 01:46:59 pc.site systemd[1]: Stopped Cryptography Setup for cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5. Aug 05 01:46:59 pc.site auditd[1679]: The audit daemon is exiting. Aug 05 01:46:59 pc.site kernel: kauditd_printk_skb: 50 callbacks suppressed Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.741:562): op=set audit_pid=0 old=1679 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site auditctl[3127]: enabled 0 Aug 05 01:46:59 pc.site auditctl[3127]: failure 1 Aug 05 01:46:59 pc.site auditctl[3127]: pid 0 Aug 05 01:46:59 pc.site auditctl[3127]: rate_limit 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_limit 64 Aug 05 01:46:59 pc.site auditctl[3127]: lost 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog 1 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time 15000 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time_actual 0 Aug 05 01:46:59 pc.site auditctl[3127]: No rules Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.853:563): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site systemd[1]: auditd.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Security Auditing Service. Aug 05 01:46:59 pc.site systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Create Volatile Files and Directories. Aug 05 01:47:00 pc.site systemd[1]: dracut-shutdown.service: Deactivated successfully. Aug 05 01:47:00 pc.site systemd[1]: Stopped Restore /run/initramfs on shutdown. Aug 05 01:47:00 pc.site systemd[1]: Stopped target Local File Systems. Aug 05 01:47:00 pc.site systemd[1]: Unmounting /home... ... The LUKS device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 contains the PV for the system VG, so it makes no sense trying to deactivate that before unmounting the system filesystems. Layout is like this: # pvs PV VG Fmt Attr PSize PFree /dev/mapper/cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 system lvm2 a-- 199,98g 3,88g # vgs VG #PV #LV #SN Attr VSize VFree system 1 6 0 wz--n- 199,98g 3,88g # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert android system Vwi-aotz-- 50,00g thinpool 55,19 floppies system Vwi-a-tz-- 1,00g thinpool 15,18 home system -wi-ao---- 50,00g root system -wi-ao---- 32,00g swap system -wi-ao---- 4,00g thinpool system twi-aotz-- 110,00g 25,23 22,76 (System was upgraded from Leap 15.4 where shutdown worked) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221702] New: Bluetooth headphones not reconnecting upon logging in
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221702 Bug ID: 1221702 Summary: Bluetooth headphones not reconnecting upon logging in Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: kjchmielewski(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873633 --> https://bugzilla.suse.com/attachment.cgi?id=873633&action=edit hwinfo I installed opensuse leap 15.6 beta on my laptop using official ISO, then I installed the pipewire-pulseaudio package. Next, I paired Bluetooth headphones in the Bluetooth settings, and the output device was correctly added in the sound settings. The problem is that after logging out or restarting the system, the headphones do not automatically connect if they are turned on all the time. I have to turn off and turn on the headphones' power again, or initiate connection manually for them to connect and become available as an output device in the sound settings. Is this expected beheviour? In leap version 15.5, this works as I expect, that is, after logging out or restarting, the Bluetooth connection disconnects, but upon logging in, the devices are automatically connected, even if they are continuously powered on and there is no need to turn them on again, or reconnect manually. -- You are receiving this mail because: You are on the CC list for the bug.

1 7