On 30.05.2015 00:47, Northern Lights Info wrote: > Thanks for the response. If itâ??s a kernel module issue, which module > is needed? I havenâ??t seen any reference to kernel modules on this > subject. > > Do you have the required kernel modules installed? "Protocol not > available" sounds like > a kernel message. Modules can be found under networking in the > kernel configuration. > > Okay, I suppose this makes sense > > > You don't need to load module-bluez5-device directly. > module-bluetooth-discover is the only > module you need to load. module-bluetooth-discover loads then > module-bluez4-discover or > module-bluez5-discover depending on your bluez version and that > module automatically loads > module-bluez4-device or module-bluez5-device as soon as a > bluetooth device turns up. > > > As to your follow-up of whether or not things work when not logged in > as root, well, I canâ??t tell because if I create a user and log into > it, while PulseAudio launches fine, when I try to run bluetoothctl, I > get its prompt but then itâ??s dead in the water and doesnâ??t respond to > me typing. Before I learned of the system mode option, I tried > pulseaudio â??start â??D when logged in as root. If I quickly run the > bluetoothctl command sequence, I can connect to the speaker and then > do pacmd list-sinks and see it. I just doesnâ??t do the same thing in > system mode. I get that error. I did try copying my default.pa to > system.pa but that didnâ??t help. > > Hi, http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ states: When in system mode, module loading after startup is disabled for security reasons, which means: no hotplug handling in system mode Regards Georg -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20150530/fdf74c1c/attachment.html>
