Bug 1057568 - Bluetooth devices not discovered on Acer Aspire E1-530
Summary: Bluetooth devices not discovered on Acer Aspire E1-530
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 19
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-24 11:37 UTC by network
Modified: 2015-02-17 19:55 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Fedora 19 on Acer Aspire E1-530 running Mate desktop.
Last Closed: 2015-02-17 19:55:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of hciconfig (603 bytes, text/plain)
2014-01-24 11:39 UTC, network
no flags Details
lsmod (3.01 KB, text/plain)
2014-01-24 11:40 UTC, network
no flags Details
lspci (1.53 KB, text/plain)
2014-01-24 11:41 UTC, network
no flags Details
lsusb (522 bytes, text/plain)
2014-01-24 11:42 UTC, network
no flags Details
usb-devices (2.80 KB, text/plain)
2014-01-24 11:43 UTC, network
no flags Details

Description network 2014-01-24 11:37:48 UTC
Description of problem:
Clicking on the USB button in the UI and then "Set up New Device" then "Forward". No devices are ever detected and it remains in the "Searching for devices" state forever.

Sorry to not be more technical but my understanding of Bluetooth is non-existant. I believe the problem may be the same as Ubuntu are having:

http://ubuntuforums.org/showthread.php?t=2197320

I have attached a number of diagnostic outputs.

Version-Release number of selected component (if applicable):

Fedora 19, Mate desktop, all current errata. Kernel 3.12.8-200.fc19.i686.PAE .

How reproducible:

Every time.

Steps to Reproduce:
1. Attempt to add new Bluetooth device
2. Watch the "Searching for devices" spinner
3. No devices are found

Actual results:
No devices found.

Expected results:
Devices found.

Additional info:

Comment 1 network 2014-01-24 11:39:23 UTC
Created attachment 854898 [details]
Output of hciconfig

Comment 2 network 2014-01-24 11:40:38 UTC
Created attachment 854900 [details]
lsmod

Comment 3 network 2014-01-24 11:41:18 UTC
Created attachment 854901 [details]
lspci

Comment 4 network 2014-01-24 11:42:53 UTC
Created attachment 854902 [details]
lsusb

Comment 5 network 2014-01-24 11:43:29 UTC
Created attachment 854903 [details]
usb-devices

Comment 6 Fedora End Of Life 2015-01-09 21:08:29 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2015-02-17 19:55:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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