which commands are executed by the "bluetooth enable" button?
There are two buttons for triggering Bluetooth availability by a mouse click, and they appear to do some magic. I would need to find out about this, I am searching for the commands which become executed by these buttons. After a reboot Bluetooth is still deactivated, and for activating it I can go here: System Settings - Network - Bluetooth There, I find emphasized by alarming color "Bluetooth is disabled" and next to it is then nicely provided an "Enable" button which perfectly works. After Bluetooth becomes activated in this way, then there appears the related System Tray icon in the panel of KDE Plasma, and from now on I can there deactivate Bluetooth, or activate it there again, forth and back, repeatedly, which works as expected. In another thread I asked how to set a keyboard shortcut for this activation/deactivation of Bluetooth, and quickly got the very helpful answer how to set the needed "custom shortcut" (Thanks, Helge!). However, the command which has to become executed by the shortcut troubles. It worked for Helge, but not for me, and the Internet is full about the problem and error message as I receive it. There obviously is something more going on behind this buttons, than simply calling the commands "bluetoothctl power on" or "bluetoothctl power off". I tested the "bluetoothctl" command interactively on a CLI as the user or with sudo and got with sub-command "devices" (and others) the error message: "No default controller available". The internet is full of questions about this and by now I could not find any good answer. There are suggestions that the problem would have been solved after a cold start (not simply a reboot), after driver re-installation, booting into Windows and back into Linux, and many more weird solutions. BUT: if I use the mouse in order to trigger the button, then bluetooth becomes enabled or disabled without any problems, forth and back, repeatedly. And if it first becomes enabled by the mouse click on the button, I then afterwards also succeed on the CLI with the commands given as a normal user "bluetoothctl power off" and "bluetoothctl power on", forth and back, repeatedly (and also the keyboard shortcut works for me, then). Once I use the mouse for deactivating Bluetooth by the button, then the bluetoothctl commands again fail with said error message. Obviously, the buttons know the magic trick how to activate/deactivate the communication with the present hardware at a state, when bluetoothctl cannot succeed to get access to the device. I should add, that "systemctl status bluetooth" confirms this service to all the time being active, and obviously there are no drivers or configurations missing - the buttons can do the job. So, nothing is missing but to find out which commands these buttons trigger. Well, I am now searching for this full series of commands, for achieving on the CLI the same result as these buttons are doing it. Could you help? Marco.
Re: How to set this keyboard shortcut?
On 28.04.20 21:05, Helge Reimer wrote: Am Dienstag, 28. April 2020, 18:46:19 CEST schrieb Marco Möller: I would like to have this "Enable" button (or the functionality it calls) to become triggered by a keyboard shortcut and would like to know where and how to configure this shortcut. Hi Marco, go to Systemsettings -> Workspace - Shortcuts -> own Shortcuts. Then select 'Edit -> new -> global Shortcut -> Command/Adress' Set up your trigger and enter 'bluetoothctl power on' in the Action tab. I tried it and it works. But no toggle. This is great information. I now understand where and how to set the shortcut, Thanks a lot! Danke, Helge! The command itself is not working, though. I tested the command interactively on a CLI as the user or with sudo and got with sub-command "devices" (and others) the error message: "No default controller available". The internet is full of questions about this and by now I could not find any good answer. There are suggestions that the problem would have been solved after a cold start (not simply a reboot), after driver re-installation, booting into Windows and back into Linux, and many more weird solutions. BUT: if I use the mouse in order to trigger the button, then bluetooth becomes enabled or disabled without any problems, forth and back, repeatedly. And if it first becomes enabled by the mouse click on the button, then I also succeed on the CLI with the commands given as a user "bluetoothctl power off" and "bluetoothctl power on", forth and back, repeatedly, AND ALSO the keyboard shortcut works. Once I use the mouse for deactivating bluetooth by the button, then the bluetoothctl commands again fail with said error message. So, there is obviously something more what this button is doing, before setting the power on and after setting the power off. It knows the magic trick how to activate/deactivate the communication with the the present hardware, something what according to my internet search only few people know about. I will continue this topic now in a new thread, as the keyboard shortcut question is well answered, and finding all needed bluetooth controlling commands might better appear with a different subject line in its own thread. Gruß! Marco.
Re: How to set this keyboard shortcut?
Am Dienstag, 28. April 2020, 18:46:19 CEST schrieb Marco Möller: > I would like to have this "Enable" button (or the functionality it > calls) to become triggered by a keyboard shortcut and would like to know > where and how to configure this shortcut. Hi Marco, go to Systemsettings -> Workspace - Shortcuts -> own Shortcuts. Then select 'Edit -> new -> global Shortcut -> Command/Adress' Set up your trigger and enter 'bluetoothctl power on' in the Action tab. I tried it and it works. But no toggle. -- Gruß Helge
How to set this keyboard shortcut?
After my question on forum.kde.org did not really came to a result, I will try it here. I asked for how to define a "keyboard shortcut to enable or activate bluetooth". The question is not about how to enable the bluetooth service in the OS, the question is about how to assign a shortcut to the function of a button which KDE Plasma provides for enabling the service. I can enable this particular service by a mouse click, as KDE Plasma provides a button for this. You can find it here: System Settings - Network - Bluetooth There, emphasized by alarming color it is written: "Bluetooth is disabled" and next to it is nicely provided an "Enable" button which perfectly works. I would like to have this "Enable" button (or the functionality it calls) to become triggered by a keyboard shortcut and would like to know where and how to configure this shortcut. I could imaging, although not finding it readily offered in the System Settings - Workspace - Shortcuts - Global Shortcuts section, that it still might be possible to maybe (how?) configure this in the Custom Shortcuts section or maybe by directly editing a configuration file (which line has to be added to which file?). Well, this is what I am searching for. Operating System: Debian GNU/Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.62. Qt Version: 5.12.5 Kernel Version: 5.5.0-2-amd64 Any help is appreciated! Marco.
Re: KDE Apps 20.04 (and Plasma) for Debian
Le 27.04.2020 23:43, Martin Steigerwald a écrit : Rainer Dorsch - 27.04.20, 23:07:02 CEST: just wondering, if anybody tried Norbert's repo for sid and bullseye Of course I would love to see current Plasma and especially KF packaged, Guys, I'm writing from KDE Neon which I'm trying for 3 months now. If all you want is up to date KDE packages, then you should have a look. But... understandably, it is built upon a stable base : Ubuntu LTS. So, you will not have latest softwares for anything but KDE. You can't have the best of both worlds. And frankly, KDE is in a polishing phase, there is no big changes and big benefits to update. Rather, there is lot of small changes that happens in a lot of parts that nobody use 24 hour a day. So, I've worked with KDE Neon for three months. I didn't change anything in the default KDE configuration. Coming from Sid, the desktop wasn't the big fresh air I would have expected. A bit more stable, but I guess it is because of Ubuntu LTS, not KDE. Actualy, it is a bit boring to use daily — because I like Sid : in Sid there is often something to do, to check, to discover, up to date softwares in most parts, very good package descriptions (opposite to nothing at all in Ubuntu LTS), a lot of options to try, very good READMEs from debian teams, KDE packages to debug, etc. Sid is fun and I like to report bugs. And also there is no miracles in KDE Neon : annoying KDE bugs are still here. Don't expect too much in latest KDE packages. There is more changes in underlying softwares, stay in Sid if you want the latest. --- Librement, Xavier Brochard xav...@alternatif.org La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre Rosnay)
Re: KDE Apps 20.04 (and Plasma) for Debian
In data martedì 28 aprile 2020 00:19:26 CEST, Ihor Antonov ha scritto: > I have started the work to compare Ubuntu's and Norbert's debdiffs, and in > the > end I plan to submit PRs to to kde repositories in Salsa. Hopefully there > will > be someone to review and accept it as I am new to Debian packaging. One note about submitting work: while we certainly are fine with MRs, please consider coordinating with us in our development list, which is pkg-kde-talk (see [1]), especially when planning many changes. This way it is easier to know whether anyone is working on that already, and possibly review part of the changes ahead instead of having to review (and ask you to resend/update) lots of MRs. [1] https://qt-kde-team.pages.debian.net/qtkde.html Thanks, -- Pino Toscano signature.asc Description: This is a digitally signed message part.
