Period, because the decision to use D-Bus as inter-process communication for Bluetooth has been made a long time ago. This means it is a purely technical decision. And yes, I am not even going to argue about it. There is no other sane way except you wanna live in the stone age of Unix operating systems. Same as HAL is using D-Bus and other core services of a modern Linux operating system.
Have a look at /etc/dbus-1/event.d/ for a change. Don't blame D-Bus that it re-configures your Ethernet devices. That is simply plain wrong. D-Bus is only a inter-process communication standard used by many application and services. That it is configured to automatically start NetworkManager is _not_ a D-Bus problem. D-Bus is not doing anything except inter-process communication. -- hcid coupled with dbus https://bugs.launchpad.net/bugs/151845 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
