[Bug 527856] New: boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

newer
[Bug 464363] sr revoke permission...

bugzilla_noreply＠novell.com

4 Aug 2009 4 Aug '09

08:12

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.

Show replies by date

bugzilla_noreply＠novell.com

4 Aug 4 Aug

15:54

New subject: [Bug 527856] boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

http://bugzilla.novell.com/show_bug.cgi?id=527856 User kasievers@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527856#c1 --- Comment #1 from Kay Sievers 2009-08-04 09:54:32 MDT --- Interesting approach. :) boot.udev_retry exists to cover a read-only roofs or /usr not mounted. It was never meant to cover dependencies of system services. Regarding to the fedora guys, this approach currently does not work at all. I guess, the bluetooth daemon should try to re-connect to dbus and not just exit. I have no problem changing the udev init script, if you let me know, what it should be changed to -- but I doubt it will work, and I'm sure it's the wrong thing to do. -- 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.

bugzilla_noreply＠novell.com

6 Aug 6 Aug

11:14

New subject: [Bug 527856] boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

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.

bugzilla_noreply＠novell.com

12:40

New subject: [Bug 527856] boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

http://bugzilla.novell.com/show_bug.cgi?id=527856 User kasievers@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527856#c3 --- Comment #3 from Kay Sievers 2009-08-06 06:40:00 MDT --- (In reply to comment #2)

...

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.

I know, but there seems to be a bit of confusion. I think the current udev will not even record these as failed events. :) I'll let you know if there is any solution upcoming. Thanks! -- 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.

bugzilla_noreply＠novell.com

17:28

New subject: [Bug 527856] boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

http://bugzilla.novell.com/show_bug.cgi?id=527856 User kasievers@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527856#c4 --- Comment #4 from Kay Sievers 2009-08-06 11:28:06 MDT --- Fedora uses an init script and unconditionally re-triggers all bluetooth events now: http://cvs.fedora.redhat.com/viewvc/devel/bluez/bluetooth.init?view=markup&sortby=date (I changed udev HEAD to make it possible to let these events fail. But that is not in Factory now, not enabled in the bluetooth rules, and also does not solve the D-Bus dependency for now.) -- 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.

bugzilla_noreply＠novell.com

17 Aug 17 Aug

12:59

New subject: [Bug 527856] boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

http://bugzilla.novell.com/show_bug.cgi?id=527856 User kasievers@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527856#c5 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@novell.com --- Comment #5 from Kay Sievers 2009-08-17 06:59:25 MDT --- *** Bug 528817 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=528817 -- 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.

bugzilla_noreply＠novell.com

13:01

New subject: [Bug 527856] bluetoothd not started on bootup

http://bugzilla.novell.com/show_bug.cgi?id=527856 User kasievers@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527856#c6 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kasievers@novell.com |seife@novell.com Summary|boot.udev_retry runs much |bluetoothd not started on |too early in the boot |bootup |process, preventing | |bluetoothd from working | --- Comment #6 from Kay Sievers 2009-08-17 07:01:19 MDT --- Let me know if you need udev to do anything here. Seems this needs to be fixed in bluetooth itself. Passing to Seife. -- 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.

bugzilla_noreply＠novell.com

19 Aug 19 Aug

13:38

New subject: [Bug 527856] bluetoothd not started on bootup

http://bugzilla.novell.com/show_bug.cgi?id=527856 User seife@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=527856#c7 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |kasievers@novell.com Resolution| |FIXED --- Comment #7 from Stefan Seyfried 2009-08-19 07:38:27 MDT --- I have simply put an simple init script into our package. I'm still discussing upstream how to do it there. -- 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.

5372

Age (days ago)

5387

Last active (days ago)

List overview

Download

7 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 527856] New: boot.udev_retry runs much too early in the boot process, preventing bluetoothd from working

tags

participants (1)