http://bugzilla.novell.com/show_bug.cgi?id=527856 Summary: boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: kasievers@novell.com ReportedBy: seife@novell.com QAContact: qa@suse.de CC: thoenig@novell.com Found By: Development /etc/init.d/boot.udev_retry runs much too early in the boot process. For example, bluetoothd now relies on being started by udev_retry, but for this to work, udev_retry needs to run when dbus is already up. This is not the case now and thus bluetoothd is not started at boot if the adapter is already plugged in. Note that this behaviour is plain upstream bluetoothd and I am not going to hack suse specific stuff into bluez again. So either we need to start d-bus earlier, or we need to postpone boot.udev_retry. -- 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.