On Sat, Mar 26, 2011 at 7:29 PM, Seblu se...@seblu.net wrote:
My understanding: Let initscripts start bluetoothd and not udev (it
should not use to manage services).
I have been looking a bit more into this (reading the discussions on
the bluez mailinglist). From what I can see Sebastien is
On Thu, Mar 24, 2011 at 10:20 AM, Tom Gundersen t...@jklm.no wrote:
On Thu, Mar 24, 2011 at 2:44 AM, Seblu se...@seblu.net wrote:
# Run helper every time a Bluetooth device appears
# On remove actions, bluetoothd should go away by itself
ACTION==add|change, SUBSYSTEM==bluetooth,
On Thu, Mar 24, 2011 at 2:44 AM, Seblu se...@seblu.net wrote:
# Run helper every time a Bluetooth device appears
# On remove actions, bluetoothd should go away by itself
ACTION==add|change, SUBSYSTEM==bluetooth,
RUN{fail_event_on_error}+=/usr/sbin/bluetoothd --udev
And after booting (so
On Tue, Mar 22, 2011 at 12:13 PM, Tom Gundersen t...@jklm.no wrote:
On Tue, Mar 22, 2011 at 11:25 AM, Seblu se...@seblu.net wrote:
Could you try replacing your bluetooth rules with:
# Run helper every time a Bluetooth device appears
# On remove actions, bluetoothd should go away by itself
On Tue, Mar 22, 2011 at 3:59 AM, Seblu se...@seblu.net wrote:
So, this situation is a bit confusing, so why do not remove
/lib/udev/rules.d/97-bluetooth.rules?
I don't think it is a good idea to remove these rules, at they allow
bluez to be started on demand rather than unconditionally. I'd
2011/3/22 Ng Oon-Ee ngoo...@gmail.com:
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
On Tue, Mar 22, 2011 at 8:44 AM, Tom Gundersen t...@jklm.no wrote:
On Tue, Mar 22, 2011 at 3:59 AM, Seblu se...@seblu.net wrote:
So, this situation is a bit confusing, so why do not remove
/lib/udev/rules.d/97-bluetooth.rules?
I don't think it is a good idea to remove these rules, at they
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
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
9 matches
Mail list logo
