Bug 220207

Summary:	Trust dialog pops up after resuming from sleep even when permanent trust is setup
Product:	[Frameworks and Libraries] kbluetooth	Reporter:	Venky <venkythegeek>
Component:	general	Assignee:	Alex Fiestas <afiestas>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	lamarque
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Venky 2009-12-27 02:00:15 UTC

Version:           4.04RC2-1 (using KDE 4.3.4)
OS:                Linux
Installed from:    Archlinux Packages

I have successfully paired  my Logitech Cordless MediaBoard Pro PlayStation 3
(http://www.amazon.com/Logitech-PlayStation-3-Cordless-MediaBoard-Pro/dp/B000W5RBQE)
using kbluetooth 4.0.4RC2-1
The bluez version is bluez version is 4.58-1

I have also set the trust to be permanent as seen here
http://imagebin.ca/view/yWUAmSix.html
But after my bluetooth keyboard / computer restarts/resumes, I lose the trust level setting and get a trust dialog popup and I have to manually click "always trust" to make the keyboard pair and work again.
Here is the screen shot of what happens after the bluetooth resumes from sleep http://imagebin.ca/view/F5rO_Nm.html

Comment 1 Alex Fiestas 2009-12-28 00:25:21 UTC

Wo, interesting
I'll look at this tomorrow.

Thanks!

Comment 2 Venky 2009-12-28 00:35:15 UTC

That will be awesome

On Sun, Dec 27, 2009 at 5:25 PM, Alex Fiestas <alex@eyeos.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=220207
>
>
>
>
>
> --- Comment #1 from Alex Fiestas <alex eyeos org>  2009-12-28 00:25:21 ---
> Wo, interesting
> I'll look at this tomorrow.
>
> Thanks!
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Comment 3 Alex Fiestas 2010-01-31 21:20:16 UTC

I don't have my bt device here right now but I should receive it in a couple of days, then I'll test this again.

Thanks again for the great bug report! :)

Comment 4 Lamarque V. Souza 2011-04-11 19:47:42 UTC


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