[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#461730: marked as done (linux-2.6: Cannot pair with bluetooth headset with 2.6.21+)

Your message dated Wed, 5 Aug 2009 19:45:24 +0200
with message-id <20090805174524.GE10306@inutil.org>
and subject line Re: linux-2.6: Cannot pair with bluetooth headset with 2.6.21+
has caused the Debian Bug report #461730,
regarding linux-2.6: Cannot pair with bluetooth headset with 2.6.21+
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
461730: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461730
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-2.6
Version: 2.6.21-6
Severity: normal

I recently tried and failed to pair with a bluetooth headset that used
to work some time ago.  Specifically, any attempt to establish a
connection to the device (with "hcitool cc") would appear to be
successful, with hci_create_connection() returning 0, yet no connection
could be found.

After a few joyful hours of downgrading and rebooting, it turns out that
the kernel is to blame.  I'm getting this erratic behavior with
2.6.21-2-k7 and 2.6.23-1-686, but not with 2.6.18-5-k7.  (I couldn't
test 2.6.20-1-k7, due to the PATA bug.)

I'm reluctant at this point to spend more time compiling/rebooting on my
own if it may turn out to be useless after all.  However, if you need
more information and/or want me to try stuff out, I'd be glad to do my
part.  Just let me know how I should proceed from here.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (1001, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Fri, Feb 13, 2009 at 07:10:51PM -0500, Frédéric Brière wrote:
> On Sun, Jan 04, 2009 at 06:17:33PM +0100, Moritz Muehlenhoff wrote:
> > Does this error still occur with the Lenny kernel?
> 
> I don't know about lenny specifically, but this behavior is still
> present in vanilla 2.6.26.
> 
> I don't know if this is a problem any longer, though.  I opened this bug
> back when I was using bluetooth-alsa (now removed from Debian), which
> required a connection to be established manually.  bluez-audio will
> establish a connection on demand, and does so just fine once a link key
> is obtained (which is still performed by "hcitool cc").
> 
> I can't comment on whether or not this issue might affect someone else;
> all I can say is that it no longer bothers me.  (I did notice that the
> Ubuntu bug I linked to has now been marked as resolved.)
> 
> Please feel free to close this report.  If someone objects, they are
> welcome to reopen it under their own name.

Thanks for the feedback, closing the bug, then.

Cheers,
        Moritz

--- End Message ---
Reply to: