Bug 1217348

Summary: [Regression from Leap's GNOME 41.5] Quick off and back on toggling broken with bluetooth in gnome-control-center
Product: [openSUSE] openSUSE Distribution Reporter: ell1e <el>
Component: GNOMEAssignee: E-mail List <gnome-bugs>
Status: NEW --- QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None    
Version: Leap 16.0   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Screenshot showing "Off" toggle position combined with "On" toggle color

Description ell1e 2023-11-21 00:18:44 UTC
I just upgraded from Leap 15.5's GNOME 41.5 to Slowroll's GNOME 45.0, and there's a regression regarding quickly off and back on toggling of a bluetooth device in gnome-control-center's control panel in the device detail popup: it no longer works. The reason is that before, clicking the on/off toggle in 99% of cases showed some spinner only for some fractions of seconds, then went to an off state where I can click it again to retoggle back to on. This is no longer what happens, now 99% of the time it remains stuck as a spinner or goes back to "On" despite disconnecting(!) and then just stays like that, no longer allowing me to toggle back on. Only after a long time it sometimes corrects itself, sometimes not even at all, requiring me to toggle all of bluetooth off and back on to get anywhere from that point.

I'm suggesting severity major because bluetooth with some devices like mine is so utterly unreliable, that toggling devices off/on relatively quickly is basically required to use it at all.
Comment 1 ell1e 2023-11-21 00:41:29 UTC
Created attachment 870860 [details]
Screenshot showing "Off" toggle position combined with "On" toggle color

It seems like now, a lot of the time the bluetooth popup state when clicking details but not having touched anything, also often just shows some weird mix of "Off" toggle position but "On" toggle coloring. Or at least that's all I can make of it an end user, maybe this is actually a useful and obvious state that I'm just not quite smart enough to decipher.