<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>118786</bug_id>
          
          <creation_ts>2006-01-12 08:44 0000</creation_ts>
          <short_desc>bluetooth init.d should use dbus service when available</short_desc>
          <delta_ts>2006-05-18 07:28:33 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>2005.1</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>minor</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>jan@spitalnik.net</reporter>
          <assigned_to>cardoe@gentoo.org</assigned_to>
          <cc>ed@catmur.co.uk</cc>
    
    <cc>liquidx@gentoo.org</cc>
    
    <cc>mobile@gentoo.org</cc>
    
    <cc>neil@darlow.co.uk</cc>
    
    <cc>nuno.araujo@russo79.com</cc>

      

      
          <long_desc isprivate="0">
            <who>jan@spitalnik.net</who>
            <bug_when>2006-01-12 08:44:31 0000</bug_when>
            <thetext>Hi,

bluez-utils&apos; bluetooth init.d should &apos;use dbus&apos;, as it can be compiled to support dbus. In such scenario, bluetooth is started before dbus and hcid fails to start.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jan@spitalnik.net</who>
            <bug_when>2006-01-12 08:45:14 0000</bug_when>
            <thetext>Created an attachment (id=76912)
bluetooth init.d patch

</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nivw2002@fastmail.fm</who>
            <bug_when>2006-01-13 05:22:00 0000</bug_when>
            <thetext>I second the motion to fix this ASAP and shipout.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>zarhan@iki.fi</who>
            <bug_when>2006-01-30 00:57:44 0000</bug_when>
            <thetext>Noticed this problem as well. As a workaround I set dbus to start up at &quot;boot&quot; 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..</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2006-02-06 11:15:56 0000</bug_when>
            <thetext>cc&apos;ing dbus maintainer. can we have the above discussed before coldplug added to dbus&apos; init.d script?

i&apos;ll go about adding the required things into bluez-utils&apos; init.d too</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2006-02-07 05:01:32 0000</bug_when>
            <thetext>added &quot;after dbus&quot; to bluez-utils 2.25&apos;s init.d script. now just missing dbus&apos;s init script to run before coldplug</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>liquidx@gentoo.org</who>
            <bug_when>2006-02-07 13:16:49 0000</bug_when>
            <thetext>reassigning for further action with the dbus init script.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nivw2002@fastmail.fm</who>
            <bug_when>2006-03-26 04:11:06 0000</bug_when>
            <thetext>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?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jakub@gentoo.org</who>
            <bug_when>2006-04-17 03:23:40 0000</bug_when>
            <thetext>(In reply to comment #5)
&gt; added &quot;after dbus&quot; to bluez-utils 2.25&apos;s init.d script. now just missing dbus&apos;s
&gt; init script to run before coldplug

&quot;after coldplug&quot; is bogus w/ &gt;=udev-089, it should be just removed from the dbus init script when that version goes stable. Same for bluetooth init script.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jakub@gentoo.org</who>
            <bug_when>2006-04-17 03:24:39 0000</bug_when>
            <thetext>*** Bug 130235 has been marked as a duplicate of this bug. ***</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>uberlord@gentoo.org</who>
            <bug_when>2006-05-18 07:28:33 0000</bug_when>
            <thetext>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.</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="1"
              isprivate="0"
          >
            <attachid>76912</attachid>
            <date>2006-01-12 08:45 0000</date>
            <desc>bluetooth init.d patch</desc>
            <filename>bluetooth.patch</filename>
            <type>text/plain</type>
            <data encoding="base64">LS0tIGJsdWV0b290aC5vcmlnCTIwMDYtMDEtMTIgMTc6Mzg6MDIuMDAwMDAwMDAwICswMTAwCisr
KyBibHVldG9vdGgJMjAwNi0wMS0xMiAxNzozODoyMi4wMDAwMDAwMDAgKzAxMDAKQEAgLTcsNiAr
Nyw3IEBAIFVBUlRfQ09ORj0iL2V0Yy9ibHVldG9vdGgvdWFydCIKIAogZGVwZW5kKCkgewogCWFm
dGVyIGNvbGRwbHVnCisJdXNlIGRidXMKIH0KIAogc3RhcnRfdWFydHMoKSB7Cg==
</data>        

          </attachment>
    </bug>

</bugzilla>