Extension is only visible when Bluetooth is already turned on.

[Northguy]

Tried using the extension on Pop!OS. The extension is visible when Bluetooth is turned on and can then be used to enter Bluetooth settings, or turn the Bluetooth off, but once Bluetooth is turned off, the extension disappears: it is not possible to use the extension to re-enable the Bluetooth. For this I need to enter the original settings menu and enable bluetooth from there. Once enabled there, the extension becomes visible again.

It would be very convenient when the bluetooth extension is always visible

If more detailed debug info is required, please specify (and how to obtain).

[BlankParticle]

Hello, thanks for reporting. Can you provide some screenshot of what do you want to mean?

I work with Gnome 45 and enabling/disabling Bluetooth can be done from quick settings panel. I am not sure how it's over at PopOS.

[Northguy]

Hi @BlankParticle have a look at video contained in attached ZIP. A video says more than 1000 screenshots ;-)

simplescreenrecorder-2023-11-11_19.45.41.zip

[BlankParticle]

I am pretty sure that turn off button is not provided by the extension but provided by Pop!OS itself. Does this happen only when the extension is installed?

[Northguy]

When the extension is not installed, there is no way to change bluetooth settings in the quick panel, then I always need to go through the ' generic' settings to enable/disable. Therefore this extension is helpful, but only if it persistent (also when bluetooth is off)

[BlankParticle]

Ok, I will boot up Pop!Os in vm to check on stuff probably tomorrow, until then please provide your system config. Like the version of the extension, gnome version, distro, etc.

A default neofetch would be enough to get the general idea. We can go into specific details if I can't replicate the issue. Also check with version of the extension you are running.

[Northguy]

Hi,

I installed the latest available extension from the website.

$ neofetch
             /////////////                northguy@SurfacePro3 
         /////////////////////            ------------------- 
      ///////*767////////////////         OS: Pop!_OS 22.04 LTS x86_64 
    //////7676767676*//////////////       Host: Surface Pro 3 1 
   /////76767//7676767//////////////      Kernel: 6.5.6-76060506-generic 
  /////767676///*76767///////////////     Uptime: 9 mins 
 ///////767676///76767.///7676*///////    Packages: 1927 (dpkg), 19 (flatpak), 11 (snap) 
/////////767676//76767///767676////////   Shell: bash 5.1.16 
//////////76767676767////76767/////////   Resolution: 2160x1440 
///////////76767676//////7676//////////   DE: GNOME 42.5 
////////////,7676,///////767///////////   WM: Mutter 
/////////////*7676///////76////////////   WM Theme: Pop 
///////////////7676////////////////////   Theme: Pop-dark [GTK2/3] 
 ///////////////7676///767////////////    Icons: Pop [GTK2/3] 
  //////////////////////'////////////     Terminal: gnome-terminal 
   //////.7676767676767676767,//////      CPU: Intel i3-4020Y (4) @ 1.500GHz 
    /////767676767676767676767/////       GPU: Intel Device 0a1e 
      ///////////////////////////         Memory: 2105MiB / 3812MiB 
         /////////////////////
             /////////////                                        
                                                                  

[BlankParticle]

Screencast from 2023-11-12 13-05-27.webm

Hello, Is this what behaviour you wanted?

Edit: I have added the fix in Readme Troubleshooting Guide

[Northguy]

That looks exactly like expected behaviour. I'll check out the troubleshooting guide. I'll consider this issue closed. Thanks for the effort.