Re: Bluetooth service - was manually fixing IPs

2011-03-30 Thread Michal Schmidt
On Tue, 29 Mar 2011 17:34:39 -0500 Ian Pilcher wrote: On 03/29/2011 03:01 PM, Lennart Poettering wrote: Can you paste the kmsg context of the starting please? [ 42.087581] systemd[1]: Got D-Bus activation request for bluetooth.service The bluez D-Bus service activates bluetooth.service

Re: Bluetooth service - was manually fixing IPs

2011-03-30 Thread Bill Nottingham
Michal Schmidt (mschm...@redhat.com) said: Compare this with org.freedesktop.NetworkManager.service which uses an indirect alias that can be enabled/disabled by systemctl: SystemdService=dbus-org.freedesktop.NetworkManager.service This was discussed in February on systemd-devel:

Re: Bluetooth service - was manually fixing IPs

2011-03-29 Thread Lennart Poettering
On Tue, 29.03.11 14:39, Ian Pilcher (arequip...@gmail.com) wrote: On 03/29/2011 02:31 PM, Lennart Poettering wrote: Please paste systemctl show bluetooth.service, which should tell us what pulled it in. Here it is. Id=bluetooth.service Names=bluetooth.service

Re: Bluetooth service - was manually fixing IPs

2011-03-29 Thread Lennart Poettering
On Tue, 29.03.11 14:54, Ian Pilcher (arequip...@gmail.com) wrote: On 03/29/2011 02:44 PM, Lennart Poettering wrote: Maybe something started it manually? Looks like it happens when I log in to KDE. I assume this means that KDE isn't using D-BUS to start the service, right? If it were,

Re: Bluetooth service - was manually fixing IPs

2011-03-29 Thread Ian Pilcher
On 03/29/2011 03:01 PM, Lennart Poettering wrote: Can you paste the kmsg context of the starting please? [ 42.087581] systemd[1]: Got D-Bus activation request for bluetooth.service [ 42.099029] systemd[1]: Trying to enqueue job bluetooth.service/start/replace [ 42.099342] systemd[1]: