http://bugzilla.novell.com/show_bug.cgi?id=527856
User seife@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=527856#c2
--- Comment #2 from Stefan Seyfried 2009-08-06 05:14:38 MDT ---
I would be happy if you would discuss this with upstream - Marcel and Bastien
;)
Actually the change was coming from Fedora and Marcel agreed and accepted it.
What we do right now is:
ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd --udev"
If dbus iss not running, bluetoothd will "exit 1".
The system now relies on a later run of "/sbin/udevadm trigger --type=failed"
to then start bluetoothd after dbus.
/sbin/udevadm trigger --type=failed
Stupid question: is the second failure still recoreded by udev? Means: can I
just create a bluetoothd init script that runs
/sbin/udevadm trigger --type=failed --subsystem-match=bluetooth
and that is surely run after dbus is up? Will that work? Would be an easy
solution ;)
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.