Bug 704723 - bluetooth, power on/off
Summary: bluetooth, power on/off
Keywords:
Status: CLOSED DUPLICATE of bug 727106
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-14 11:49 UTC by Tomasz R
Modified: 2012-06-06 12:56 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 12:56:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tomasz R 2011-05-14 11:49:01 UTC
Description of problem:
When I disable and restart or suspend system, I couldn't enable bluetooth. I have to enable bluetooth and restart system and adapter will be work than.

Version-Release number of selected component (if applicable):
bluez-libs-4.87-5.fc15.x86_64
bluez-4.87-5.fc15.x86_64

How reproducible:
please read description of problem

  
Actual results:
I couldn't work with bluetooth

Expected results:
It should be available with problem disable/enable bluetooth when I want.

Comment 1 Jacek Pawlyta 2011-05-21 12:29:23 UTC
The same is here.
Bluetooth worked fine with kernel-2.6.38, after update to kernel 2.6.39-0.fc16.x86_64 my Bluetooth usb dongle stays inactive when resuming from suspend.
I have to manually remove it from usb port and install again.

I think the problem is not with bluez but with kernel

Comment 2 Bastien Nocera 2011-06-21 13:47:18 UTC
What's the output of "hciconfig" after resuming from suspend?

Comment 3 Tomasz R 2011-06-21 15:20:22 UTC
$ hciconfig -a
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:0 acl:0 sco:0 commands:0 errors:0

Comment 4 Bastien Nocera 2011-06-21 15:29:01 UTC
No Bluetooth address, kernel problem.

Comment 5 Jacek Pawlyta 2011-11-25 08:48:35 UTC
this is a probably the same problem as in here https://bugzilla.redhat.com/show_bug.cgi?id=727106

Comment 6 Josh Boyer 2012-06-06 12:56:30 UTC

*** This bug has been marked as a duplicate of bug 727106 ***


Note You need to log in before you can comment on or make changes to this bug.