You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope I didn't miss the address to report the problem. So I'm using Ubuntu MATE 22.04 and reporting two things:
In Control Center when I launch Settings, the Ayatana dialog on several tabs does not show any content in the settings area (and in all likelihood, it should show). I'm specifically reporting Bluetooth here.
The Bluetooth setting in the indicator in the tray itself (it has two switches, "Visible" and "Bluetooth") does not keep its setting ("Visible" switcher keeps its setting), that is, at each reboot of the system, Bluetooth (and the switcher itself ) are active again. It should be added here that in Dconf Editor there is a setting only for "Visible", and not for Bluetooth itself. I should also add that the "Bluetooth" switcher itself works correctly (turns BT on and off).
Did I notice this correctly that there are problems or am I mistaken?
The text was updated successfully, but these errors were encountered:
I hope I didn't miss the address to report the problem. So I'm using Ubuntu MATE 22.04 and reporting two things:
In Control Center when I launch Settings, the Ayatana dialog on several tabs does not show any content in the settings area (and in all likelihood, it should show). I'm specifically reporting Bluetooth here.
The Bluetooth setting in the indicator in the tray itself (it has two switches, "Visible" and "Bluetooth") does not keep its setting ("Visible" switcher keeps its setting), that is, at each reboot of the system, Bluetooth (and the switcher itself ) are active again. It should be added here that in Dconf Editor there is a setting only for "Visible", and not for Bluetooth itself. I should also add that the "Bluetooth" switcher itself works correctly (turns BT on and off).
Did I notice this correctly that there are problems or am I mistaken?
The text was updated successfully, but these errors were encountered: