[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 --- Comment #10 from TraceyC --- Thanks for the new logs. I do see the play and pause events. The maintainers will need to dig into this further. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 Andrew Dixon changed: What|Removed |Added Resolution|FIXED |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 --- Comment #9 from Andrew Dixon --- Here's me just pressing the play/pause button 4 times. This headset only has one button for play/pause btw. [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2 [NEW] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep1 Agent registered [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: active [CHG] Device 7C:01:3E:1D:DD:95 RSSI: 0xffa0 (-96) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffb0 (-80) [CHG] Device A8:08:CF:4D:C3:93 RSSI: 0xff9e (-98) [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: idle [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffaa (-86) [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: active [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffb4 (-76) [CHG] Device A8:08:CF:4D:C3:93 RSSI: 0xff9d (-99) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffa2 (-94) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffbc (-68) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd2 (-46) [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: idle [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffb0 (-80) [CHG] Device A8:08:CF:4D:C3:93 RSSI: 0xff9d (-99) [CHG] Device 7C:01:3E:1D:DD:95 RSSI: 0xff9f (-97) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 Andrew Dixon changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #8 from Andrew Dixon --- (In reply to TraceyC from comment #7) > Unfortunately, since the log order and sequence of events is indeterminate, > it's not useful. Can you please run bluetoothctl, reproduce the bug and just > copy and paste the output? For instance, this is what it looks like when I > pause and play audio: > > > bluetoothctl > [NEW] Media /org/bluez/hci0 > SupportedUUIDs: 110a--1000-8000-00805f9b34fb > SupportedUUIDs: 110b--1000-8000-00805f9b34fb > [NEW] Transport /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/fd0 > [NEW] Endpoint /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/sep3 > [NEW] Endpoint /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/sep2 > [NEW] Endpoint /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/sep1 > Agent registered > [CHG] Transport /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/fd0 State: idle > [CHG] Transport /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/fd0 State: active > [WF-1000XM4]> > > The idle and active events are pause and play. > > Thanks [NEW] Media /org/bluez/hci0 SupportedUUIDs: 110a--1000-8000-00805f9b34fb SupportedUUIDs: 110b--1000-8000-00805f9b34fb Agent registered [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device 78:93:C3:98:A5:ED LegacyPairing: yes [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffab (-85) [CHG] Device A8:08:CF:4D:C3:93 RSSI: 0xff9e (-98) [CHG] Device A8:08:CF:4D:C3:93 UUIDs: 1105--1000-8000-00805f9b34fb [CHG] Device A8:08:CF:4D:C3:93 UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device A8:08:CF:4D:C3:93 UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device A8:08:CF:4D:C3:93 UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device A8:08:CF:4D:C3:93 UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device A8:08:CF:4D:C3:93 UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 7C:01:3E:1D:DD:95 RSSI is nil [CHG] Device 38:06:E6:5E:B8:7B RSSI is nil [CHG] Device A8:08:CF:4D:C3:93 RSSI is nil [CHG] Device 78:93:C3:98:A5:ED RSSI is nil [CHG] Device F4:20:15:D4:74:D7 RSSI is nil [CHG] Controller FC:B0:DE:7E:55:BE Discovering: no [CHG] Device E4:61:F4:2A:78:39 Connected: yes [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep1 [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2 [NEW] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 Delay: 0x04d8 (1240) [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: active [CHG] Controller FC:B0:DE:7E:55:BE Discovering: yes [CHG] Device 78:93:C3:98:A5:ED LegacyPairing: no [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffa8 (-88) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd4 (-44) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffaa (-86) [CHG] Device 7C:01:3E:1D:DD:95 RSSI: 0xff9e (-98) [DEL] Device A8:08:CF:4D:C3:93 BUSH_A8:08:CF:4D:84:95 [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: idle [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd3 (-45) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffa9 (-87) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffb2 (-78) [CHG] Device 7C:01:3E:1D:DD:95 RSSI: 0xffa1 (-95) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffbc (-68) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd1 (-47) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffad (-83) [NEW] Device A8:08:CF:4D:C3:93 BUSH_A8:08:CF:4D:84:95 [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffa7 (-89) [CHG] Device 7C:01:3E:1D:DD:95 RSSI: 0xffa2 (-94) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffbc (-68) [CHG] Device A8:08:CF:4D:C3:93 RSSI is nil [CHG] Device 7C:01:3E:1D:DD:95 RSSI is nil [CHG] Device 38:06:E6:5E:B8:7B RSSI is nil [CHG] Device F4:20:15:D4:74:D7 RSSI is nil [CHG] Device 78:93:C3:98:A5:ED RSSI is nil [CHG] Controller FC:B0:DE:7E:55:BE Discovering: no [DEL] Device A8:08:CF:4D:C3:93 BUSH_A8:08:CF:4D:84:95 [CHG] Controller FC:B0:DE:7E:55:BE Discovering: yes [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffa9 (-87) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [DEL] Device 38:06:E6:5E:B8:7B [LG] webOS TV UT81006LA [DEL] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [NEW] Device 38:06:E6:5E:B8:7B [LG] webOS TV UT81006LA [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffbb (-69) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd1 (-47) [NEW] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffa8 (-88) [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: active [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffa8 (-88) [CHG] Device 78:93:C3:98:A5:ED RSSI: 0xffbb (-69) [NEW] Device A8:08:CF:4D:C3:93 BUSH_A8:08:CF:4D:84:95 -- Y
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 TraceyC changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from TraceyC --- Unfortunately, since the log order and sequence of events is indeterminate, it's not useful. Can you please run bluetoothctl, reproduce the bug and just copy and paste the output? For instance, this is what it looks like when I pause and play audio: > bluetoothctl [NEW] Media /org/bluez/hci0 SupportedUUIDs: 110a--1000-8000-00805f9b34fb SupportedUUIDs: 110b--1000-8000-00805f9b34fb [NEW] Transport /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/fd0 [NEW] Endpoint /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/sep3 [NEW] Endpoint /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/sep2 [NEW] Endpoint /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/sep1 Agent registered [CHG] Transport /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/fd0 State: idle [CHG] Transport /org/bluez/hci0/dev_AC_80_0A_08_3B_7B/fd0 State: active [WF-1000XM4]> The idle and active events are pause and play. Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 --- Comment #6 from Andrew Dixon --- I'm sorry, looks like I accidentally copied a previous attempt to run bluetoothctl as well. The true run starts about a third of the way down. For some reason, using tee garbled the logfile. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 Andrew Dixon changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 --- Comment #5 from Andrew Dixon --- (In reply to TraceyC from comment #4) > Thanks. I'm not sure why this was set to FIXED. > > I'd like to see what events are emitted by the headset when you press the > play/pause button. > > 1. Run this command, verify you see your headset shown in the prompt > bluetoothctl > 2. Reproduce the bug, then log back in > 3. Copy the output from the terminal into this report > > When you have added the information, please set this back to REPORTED. > Thanks again. Here's the log. I made sure to connect the headphones just after starting bluetoothctl so you can see which one it is. It's the only BT device connected. [NEW] Media /org/bluez/hci0 SupportedUUIDs: 110a--1000-8000-00805f9b34fb SupportedUUIDs: 110b--1000-8000-00805f9b34fb [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2 [NEW] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep1 Agent registered [DEL] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [NEW] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffad (-83) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd4 (-44) [NEW] Device 00:17:53:3A:77:B3 00-17-53-3A-77-B3 [DEL] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 [DEL] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep1 [DEL] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2 [SIGNAL] BREDR.Disconnected - org.bluez.Reason.Remote, Connection terminated by remote user [SIGNAL] Disconnected - org.bluez.Reason.Remote, Connection terminated by remote user [CHG] Device E4:61:F4:2A:78:39 Connected: no [CHG] Device 00:17:53:3A:77:B3 LegacyPairing: no [CHG] Device 00:17:53:3A:77:B3 RSSI: 0xffa2 (-94) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device E4:61:F4:2A:78:39 Connected: yes [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep1 [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2 [NEW] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 Delay: 0x04d8 (1240) [DEL] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffa2 (-94) [NEW] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd3 (-45) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffad (-83) [CHG] Device 7C:01:3E:1D:DD:95 RSSI is nil [CHG] Device 00:17:53:3A:77:B3 RSSI is nil [CHG] Device 38:06:E6:5E:B8:7B RSSI is nil [CHG] Device F4:20:15:D4:74:D7 RSSI is nil [CHG] Controller FC:B0:DE:7E:55:BE Discovering: no [JBL TUNE570BT]> [JBL TUNE570BT]> [JBL TUNE570BT]> exit daisy@bazzite:/var/home/daisy$ bluetoothctl > headset.log daisy@bazzite:/var/home/daisy$ stdbuf -oL bluetoothctl | tee bluetooth_log.txt [NEW] Media /org/bluez/hci0 SupportedUUIDs: 110a--1000-8000-00805f9b34fb SupportedUUIDs: 110b--1000-8000-00805f9b34fb Agent registered [CHG] Controller FC:B0:DE:7E:55:BE Discovering: yes [NEW] Device 72:F0:07:86:6E:5E C81 [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd2 (-46) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xff9c (-100) [DEL] Device 10:A5:1D:A4:F8:DE WKGBKMNML3 [CHG] Device E4:61:F4:2A:78:39 Connected: yes [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep1 [NEW] Endpoint /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2 [NEW] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 Delay: 0x04d8 (1240) [DEL] Device 00:03:19:3D:BB:40 00-03-19-3D-BB-40 [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffae (-82) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd4 (-44) [CHG] Device 72:F0:07:86:6E:5E RSSI: 0xff9f (-97) [NEW] Device 7C:01:3E:1D:DD:95 [LG] webOS TV UA75006LA [NEW] Device 10:A5:1D:A4:F8:DE WKGBKMNML3 [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd6 (-42) [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffac (-84) [CHG] Device 7C:01:3E:1D:DD:95 RSSI: 0xff9f (-97) [CHG] Device 72:F0:07:86:6E:5E RSSI: 0xffa3 (-93) [CHG] Device 10:A5:1D:A4:F8:DE RSSI: 0xffa3 (-93) [CHG] Device F4:20:15:D4:74:D7 RSSI: 0xffd3 (-45) [CHG] Device 72:F0:07:86:6E:5E RSSI: 0xffa5 (-91) [CHG] Device 72:F0:07:86:6E:5E ManufacturerData.Key: 0x7262 (29282) [CHG] Device 72:F0:07:86:6E:5E ManufacturerData.Value: 32 32 78 78 11 22 33 44 55 66 aa bb 00 0022xx."3DUf [CHG] Device 38:06:E6:5E:B8:7B RSSI: 0xffac (-84) [CHG] Transport /org/bluez/hci0/dev_E4_61_F4_2A_78_39/sep2/fd0 State: active [CHG] Device 10:A5:1D:A4:F8:DE RSSI: 0xffa2 (-94) [CHG] Device 10:A5:1D:A4:F8:DE TxPower is nil [CHG] Device 10:A5:1D:A4:F8:DE RSSI is nil [CHG] Device 7C:01:3E:1D:DD:95 RSSI is nil [CHG] Device 38:06:E6:5E:B8:7B RSSI is nil [CHG] Device F4:20:15:D4:74:D7 RSSI is nil [CHG] Device 72:F0:07:86:6E:5E RSSI is nil [CHG] Controller FC:B0:DE:7E:55:BE Discovering: no [CHG] Transport /org
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 TraceyC changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #4 from TraceyC --- Thanks. I'm not sure why this was set to FIXED. I'd like to see what events are emitted by the headset when you press the play/pause button. 1. Run this command, verify you see your headset shown in the prompt bluetoothctl 2. Reproduce the bug, then log back in 3. Copy the output from the terminal into this report When you have added the information, please set this back to REPORTED. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 Andrew Dixon changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Andrew Dixon --- (In reply to TraceyC from comment #2) > I am not able to reproduce on Plasma built from git-master using bluetooth > earbuds with tap to play/pause > Earbuds: Sony WF-1000XM4 > Sites: Video on inv.nadeko.net, video on youtube.com > > Using your steps to reproduce: > - The first image displays on the screen locker > - Tapping to play displays the desktop, music does not play > - The next tap starts the video playing > > Is this specific to Netflix by any chance, or does it happen with other > sites? I tried it with Youtube and the same thing happens. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 TraceyC changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||[email protected] Resolution|--- |WAITINGFORINFO --- Comment #2 from TraceyC --- I am not able to reproduce on Plasma built from git-master using bluetooth earbuds with tap to play/pause Earbuds: Sony WF-1000XM4 Sites: Video on inv.nadeko.net, video on youtube.com Using your steps to reproduce: - The first image displays on the screen locker - Tapping to play displays the desktop, music does not play - The next tap starts the video playing Is this specific to Netflix by any chance, or does it happen with other sites? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 520109] Bluetooth headset's Play/Pause Button ignored for purposes of "unlock screen on activity during grace period" feature
https://bugs.kde.org/show_bug.cgi?id=520109 Nate Graham changed: What|Removed |Added Summary|Bluetooth headphone |Bluetooth headset's |Play/Pause Button Ignored. |Play/Pause Button ignored ||for purposes of "unlock ||screen on activity during ||grace period" feature CC||[email protected] --- Comment #1 from Nate Graham --- I cannot reproduce the issue with a physical play/pause button on my keyboard, and unfortunately I don't have a Bluetooth headset with one of these buttons on it. -- You are receiving this mail because: You are watching all bug changes.
