Bug 137647

Summary: Computer not visible to other devices unless GNOME bluetooth-applet/bluetooth-properties is run
Product: [Unmaintained] kde-bluetooth Reporter: MartinG <gronslet>
Component: kbluetoothdAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: bharatbhardwaj017, laurent.rineau
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description MartinG 2006-11-21 00:23:45 UTC 
Version:           0.99-beta1 (using KDE KDE 3.5.5)
Installed from:    Fedora RPMs
Compiler:          i386-redhat-linux 
OS:                Linux

I have had a hard time trying to pair my laptop and phone, and tried several different settings in "/etc/bluetooth/hcid.conf", "/etc/bluetooth/rfcomm.conf", "link_key" and "pin" without luck in Fedora Core 6. No matter what I did, I could not make the PC visible for my phone(s). 

By chance, I discovered the GNOME utility "bluetooth-applet", that can be configured with "bluetooth-properties". Only when this is set to "Visible and connectable for other devices", the laptop became visible and I could pair the devices.

I file this as a bug, as obviously, KDE Bluetooth should be able to change that setting too. Is it so that Fedora has its own way of overriding the settings in /etc/bluetooth/? Where are the config files that decides if the computer is visible or not?
Comment 1 gvsreddy 2007-06-17 10:15:48 UTC 
*** This bug has been confirmed by popular vote. ***
Comment 2 Daniel Gollub 2007-07-10 18:47:35 UTC 
kdebluetooth 1.0-beta3 got kind of rewritten to support the BlueZ D-Bus API.
kbluetooth (aka. kbluetoothd tryicon) is now able to configure the mode of Bluetooth interfaces/adapters. discoverable, connectable, ... like bluetooth-properties of bluez-gnome does.