Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: kdebluetooth: The KDE Bluetooth Framework https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=186452 ------- Additional Comments From paul@xxxxxxxxxxxx 2006-06-23 09:48 EST ------- (In reply to comment #18) > kbluepin is just a tiny program that pops up a dialog asking for the bluetooth > pairing PIN, which the user enters in the dialog, and then spits out this pin on > stdout before exiting. When running it as a normal user from the command line > it does exactly this, but that's useless. In normal circumstances, the > bluetooth system (hcid) calls this program when a bluetooth device requests > pairing with a PIN, and no, as it is now, it doesn't work as it should, the > dialog doesn't appear, and the pairing eventually fails with a timeout (as it > doesn't know the PIN). I agree, it is very odd that it is looking in so many > directories. Let's try a different approach. Put SELinux in permissive mode: # setenforce 0 Then try it again (it should work) See what SELinux denials are logged for this (after the setenforce). -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review