Bug 348894

Hi,
bluedevil-monolithic is started by Bluedevil KDED module. You have old KDE4 Bluedevil (due to Bluez 4 in Ubuntu) and Plasma 5, so it looks like kded4 is not started.

You should fix it by adding kded4 to autostart programs.

Hey David, thanks for your answer, I ran killall bluedevil-monolithic and then I ran kded4 but I don't see bluedevil-monolithic running and no bluetooth in the system tray.

I do see /usr/sbin/bluetoothd -n running as root, is this ok?

Now, how would this be solved properly? should I uninstall bluez ?

(In reply to Franco Pellegrini from comment #2)
> Hey David, thanks for your answer, I ran killall bluedevil-monolithic and
> then I ran kded4 but I don't see bluedevil-monolithic running and no
> bluetooth in the system tray.

Can you check if bluedevil module is loaded? 
Check output of:   qdbus org.kde.kded /kded loadedModules

> I do see /usr/sbin/bluetoothd -n running as root, is this ok?

That's fine.

> Now, how would this be solved properly? should I uninstall bluez ?

No, you won't have working Bluetooth without BlueZ.

$ qdbus org.kde.kded /kded loadedModules
networkstatus
kcookiejar

$ ps aux | grep kded
frapell   1310  0.0  0.0   6292    32 ?        S    Jun06   0:00 /usr/lib/x86_64-linux-gnu/libexec/kf5/start_kdeinit --kded +kcminit_startup
frapell   1315  0.0  0.8 1823420 104376 ?      Sl   Jun06   0:19 kded5 [kdeinit5]                                      
frapell  14306  0.0  0.2 267424 25616 pts/25   S    15:37   0:00 kded4


$ ps aux | grep bluedevil
Shows nothing.

(In reply to Franco Pellegrini from comment #4)
> $ qdbus org.kde.kded /kded loadedModules
> networkstatus
> kcookiejar
> 

What about if you try to load it?
qdbus org.kde.kded /kded loadModule bluedevil

Great, I got "true" and system tray is now visible. I still don't see configuration in system settings though... Now, how do I make this automatic on Login ?

Also, reading your response in https://bugs.kde.org/show_bug.cgi?id=348895 maybe my problems are related to not having the real latest bluedevil and should just wait?

(In reply to Franco Pellegrini from comment #6)
> Great, I got "true" and system tray is now visible. I still don't see
> configuration in system settings though... Now, how do I make this automatic
> on Login ?

qdbus org.kde.kded /kded setModuleAutoloading bluedevil true

This should fix it.

But I wonder why it wasn't set as autoloaded by default? Did you update your installation (and maybe disable Bluedevil module before?) or was it a clean installation?

Sorry, when you mention "qdbus org.kde.kded /kded setModuleAutoloading bluedevil true", means to just run this once, and it should remain enabled.

Also, I need to add kded4 to the "Startup and Shutdown" system settings, right?

As per your question, I did a clean installation from scratch for Kubuntu 15.04 and then upgraded to latest packages following instructions in http://www.kubuntu.org/news/kde-applications-15041-available-kubuntu-1504

(In reply to Franco Pellegrini from comment #9)
> Sorry, when you mention "qdbus org.kde.kded /kded setModuleAutoloading
> bluedevil true", means to just run this once, and it should remain enabled.

This should make it permanent - that is it should automatically load bluedevil module on kded4 startup.
So yes, you should only run this once.

> Also, I need to add kded4 to the "Startup and Shutdown" system settings,
> right?

If it is not started otherwise, then yes.

I'm closing it as Kubuntu downstream issue.

Tried the qdbus org.kde.kded /kded setModuleAutoloading bluedevil true
qdbus org.kde.kded /kded loadModule bluedevil 
to manually load the module and it works.

Tried the
qdbus org.kde.kded /kded setModuleAutoloading bluedevil true
to have the module autoload, and it does not seem to do anything.

Any clue