Bug 701050 - BlueDevil 1.1 requires libbluedevil 1.9 to work properly
Summary: BlueDevil 1.1 requires libbluedevil 1.9 to work properly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libbluedevil
Version: 14
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Reznik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-30 16:12 UTC by Rajeesh
Modified: 2011-05-19 05:06 UTC (History)
5 users (show)

Fixed In Version: bluedevil-1.1-2.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-17 20:56:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rajeesh 2011-04-30 16:12:41 UTC
Description of problem:
Cannot pair devices which falls into legacy pairing category without libbluedevil-1.9

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

How reproducible:
Always

Steps to Reproduce:
1. Start bluetooth-wizard, which starts scan for devices
2. Choose listed phone (iPhone 3GS), click "Next"
3.
  
Actual results:
Next page waits forever asking to enter the pin appeared on phone, but no pin shows up either in computer or in phone

Expected results:
Pin shows in the computer, same is asked for by the phone

Additional info:
The issue is that bluedevil-1.1 LegacyPairingPage::initializePage tries to connect to the signal BlueDevil::Device::registered and invokes method BlueDevil::Device::registerDeviceAsync; both are not available in libbluedevil-1.8.1 but introduced in libbledevil-1.9

Please update libbluedevil to 1.9

Comment 1 Jaroslav Reznik 2011-05-02 08:27:38 UTC
libbluedevil 1.9 is not officially released yet, or at least I can't fing it in usual places. But it's already tagged in GIT (it wasn't in time of 1.1 build) - so I try to import this tag.

Thanks for report.

Comment 2 Fedora Update System 2011-05-03 16:56:49 UTC
bluedevil-1.1-2.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/bluedevil-1.1-2.fc14

Comment 3 Fedora Update System 2011-05-03 16:57:57 UTC
bluedevil-1.1-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/bluedevil-1.1-2.fc15

Comment 4 Fedora Update System 2011-05-04 00:55:48 UTC
Package bluedevil-1.1-2.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing bluedevil-1.1-2.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/bluedevil-1.1-2.fc14
then log in and leave karma (feedback).

Comment 5 Rajeesh 2011-05-05 18:41:10 UTC
Forgot to push libbluedevil update? Doesn't show up in updates-testing and hence bluedevil-1.1.2 doesn't work.

Comment 6 Jaroslav Reznik 2011-05-13 14:52:15 UTC
(In reply to comment #5)
> Forgot to push libbluedevil update? Doesn't show up in updates-testing and
> hence bluedevil-1.1.2 doesn't work.

Yep, sorry for that and thanks for spotting it. Could you please try current build + karma in Bodhi? I don't have hw to test with but the missing signal/method are available in current build.

Comment 7 Rajeesh 2011-05-15 18:17:16 UTC
Tested, works fine. Closing the bug (hope that's okay).

Thanks a lot!

Comment 8 Kevin Kofler 2011-05-16 03:15:48 UTC
> Closing the bug (hope that's okay).

No, it's not!

The bug should only be closed when the update is pushed to stable. Bodhi will do that automatically.

Reopening.

Comment 9 Fedora Update System 2011-05-17 20:56:32 UTC
bluedevil-1.1-2.fc14, libbluedevil-1.9-0.1.20110502git.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2011-05-19 05:06:17 UTC
bluedevil-1.1-2.fc15, libbluedevil-1.9-0.1.20110502git.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


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