Comment # 11 on bug 1175536 from Aayush Agarwal

(In reply to Aayush Agarwal from comment #10)
> (In reply to Al Cho from comment #9)
> > (In reply to Aayush Agarwal from comment #8)
> > > (In reply to Al Cho from comment #7)
> > > > (In reply to Aayush Agarwal from comment #6)
> > > > > Sorry for the delay; just moved to the 20200826 snapshot. I couldn't find
> > > > > the bluetooth directory in /usr/lib. Has it changed?
> > > > 
> > > > No, it's not, and it's weird ....
> > > > You can use "rpm -ql bluez" to find where is it.
> > > 
> > > It seems that bluetooth has been moved to libexec.
> > > 
> > > On running "/usr/libexec/bluetooth/bluetoothd -d" I am getting:
> > > 
> > > D-Bus setup failed: Name already in use
> > > 
> > > Apologies for the very newbie-ish situation, but I am completely unfamiliar
> > > with the workings of D-Bus. I don't know how to temporarily remove it and
> > > restore it again. I did try some things in
> > > https://askubuntu.com/questions/723671/d-bus-setup-failed-name-already-in-use
> > > 
> > > But I probably got it wrong, because D-Bus still complained that the name
> > > was already in use after rfkill block, systemctl stop and /usr/libexec/ -d.
> > 
> > Basically you can use "kill <pid>" to kill the process pid and run 
> > "/usr/libexec/bluetooth/bluetoothd -d" ... that should works.
> 
> If I kill the bluetoothd process, it automatically restarts. This is even
> after I rfkill block bluetooth and switch it off from the KDE UI.

The problem is still present in the latest snapshot. Killing bluethoothd is
ineffective because the program automatically restarts. Is there some way to
prevent that so that I could run bluetoothd with debugging option flag?

Thank you.