First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 118786
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Doug Goldstein <cardoe@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Jan Spitalnik <jan@spitalnik.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
bluetooth.patch bluetooth init.d patch patch Jan Spitalnik 2006-01-12 08:45 0000 217 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 118786 depends on: Show dependency tree
Show dependency graph
Bug 118786 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-01-12 08:44 0000 
Hi,

bluez-utils' bluetooth init.d should 'use dbus', as it can be compiled to
support dbus. In such scenario, bluetooth is started before dbus and hcid fails
to start.

------- Comment #1 From Jan Spitalnik 2006-01-12 08:45:14 0000 ------- 
Created an attachment (id=76912) [edit]
bluetooth init.d patch

------- Comment #2 From Niv Vaizer 2006-01-13 05:22:00 0000 ------- 
I second the motion to fix this ASAP and shipout.

------- Comment #3 From Antti Mäkelä 2006-01-30 00:57:44 0000 ------- 
Noticed this problem as well. As a workaround I set dbus to start up at "boot"
softlevel.

However, if using bluez-2.24 with the udev rule, the bluetooth may start
immediately after coldplug regardless. So I thing dbus should also be set to
start before coldplug..

------- Comment #4 From Alastair Tse (RETIRED) 2006-02-06 11:15:56 0000 ------- 
cc'ing dbus maintainer. can we have the above discussed before coldplug added
to dbus' init.d script?

i'll go about adding the required things into bluez-utils' init.d too

------- Comment #5 From Alastair Tse (RETIRED) 2006-02-07 05:01:32 0000 ------- 
added "after dbus" to bluez-utils 2.25's init.d script. now just missing dbus's
init script to run before coldplug

------- Comment #6 From Alastair Tse (RETIRED) 2006-02-07 13:16:49 0000 ------- 
reassigning for further action with the dbus init script.

------- Comment #7 From Niv Vaizer 2006-03-26 04:11:06 0000 ------- 
hi, took me some time to figure this out :-\
net-wireless/bluez-utils-2.25 has the dbus issue
when can we expect a fix?

------- Comment #8 From Jakub Moc 2006-04-17 03:23:40 0000 ------- 
(In reply to comment #5)
> added "after dbus" to bluez-utils 2.25's init.d script. now just missing dbus's
> init script to run before coldplug

"after coldplug" is bogus w/ >=udev-089, it should be just removed from the
dbus init script when that version goes stable. Same for bluetooth init script.

------- Comment #9 From Jakub Moc 2006-04-17 03:24:39 0000 ------- 
*** Bug 130235 has been marked as a duplicate of this bug. ***

------- Comment #10 From Roy Marples (RETIRED) 2006-05-18 07:28:33 0000 ------- 
net-wireless/bluez-utils-2.25-r1 changes the init script to need dbus when
emerged with dbus support which fixes the initial bug report.

after coldplug should be removed from the init script when the coldplug package
is removed from portage.
First Last Prev Next    No search results available      Search page      Enter new bug