On Tue, 2026-03-17 at 12:14 +0000, Patrick O'Callaghan wrote: > On Mon, 2026-03-16 at 14:57 +0000, Patrick O'Callaghan wrote: > > On Sun, 2026-03-15 at 13:02 -0500, Roger Heflin wrote: > > > The script I have is really doing a full restart on the entire BT > > > stack from the OS/software side, it is possible that a power > > > on/off > > > has a similar effect to at least the first and last power > > > off/power > > > on > > > commands I have in the script. The power off/on worked for me > > > for > > > a > > > while before I need to do the full stack reset. > > > > bluetoothctl power off/on seems to do the trick. > > I spoke too soon. At least some of the time it doesn't fully come > back, > e.g. scrolling and cursor movement work but buttons are ignored. I > might need to unload/reload the kernel module as you suggest.
Two things: 1) You can change the timeout value by editing: /var/lib/bluetooth/<ID>/info I bumped it up to 10000 and it seems to work. It even survives reboots. 2) If that isn't enough, you can just reload the service: sudo systemctl restart bluetooth That seems safer than unloading/loading kernel modules explicitly or doing the power on/off (which didn't always work for me), so I created a little one-liner to make it easier to type. You could put it in a timer loop, but it will then reload even if it hasn't actually timed out so I prefer not to. I can pull up Yakuake with a function key if I need the terminal to type into. None of this should really be necessary of course. poc -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
