@TribbleSmasher why would you need BT for a working system?
Well you don't
in theory and we offered the option to disable bluetooth service completely for those that would never need it, to speed up booting etc.
but...Initially the bluetooth stack was accessed only with external tools an all was fine. Later I added some additional functionality to scan the currently available bluetooth devices dynamically, this required direct calls to the BlueZ bluetooth stack via DBUS using libdbus. Here is where the issue comes because when the BlueZ service was not running (disabled or stopped) libdbus triggered an Abort() rather than returning some kind of service not available error code. Unfortunately raising a SIGABRT promptly caused our front end to do just that every boot resulting in the black screen issue.
I've worked through and ensured that no dbus calls are made if the bluetooth stack is unavailable and the update will come out very soon. Still needs further testing.
In the meantime, work around is don't disable bluetooth.
