Any particular reason you cross-posted this between aur-general and arch-general? On Tue, 2011-03-22 at 03:59 +0100, Seblu wrote:

Hello,

It was a few things I could not explain with bluez and udev.

When my system start killswitch off and i toggle killswitch after, bluetoothd is auto started. When my system starts with killswitch on, bluetoothd is not started. (a bit confusing)

After adding hooks in rc, bluetoothd refuse to start at boot because it needs dbus! If I searched on google before trying to debug I saved a few hours: https://bbs.archlinux.org/viewtopic.php?id=112161

And yes, that's the case for most problems...

So, this situation is a bit confusing, so why do not remove /lib/udev/rules.d/97-bluetooth.rules? From my test bluetoothd, doesn't kill itself when it's run by /etc/rc.d/bluetooth.

Regards,

2011/3/22 Ng Oon-Ee :

Any particular reason you cross-posted this between aur-general and arch-general? I got screwed by the auto-completion

On Tue, 2011-03-22 at 03:59 +0100, Seblu wrote:

...

Hello,

It was a few things I could not explain with bluez and udev.

When my system start killswitch off and i toggle killswitch after, bluetoothd is auto started. When my system starts with killswitch on, bluetoothd is not started. (a bit confusing)

After adding hooks in rc, bluetoothd refuse to start at boot because it needs dbus! If I searched on google before trying to debug I saved a few hours: https://bbs.archlinux.org/viewtopic.php?id=112161

And yes, that's the case for most problems...

...

So, this situation is a bit confusing, so why do not remove /lib/udev/rules.d/97-bluetooth.rules? From my test bluetoothd, doesn't kill itself when it's run by /etc/rc.d/bluetooth.

Regards,

-- Sébastien Luttringer www.seblu.net