[Bug 221601] New: bluez-utils: Documentation outdated
https://bugzilla.novell.com/show_bug.cgi?id=221601 Summary: bluez-utils: Documentation outdated Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: seife@novell.com ReportedBy: bwalle@novell.com QAContact: qa@suse.de The /usr/share/doc/packages/bluez-utils/README.SUSE is outdated: Current desktops are compatible with the new mechanism and the configuration in YaST seems to work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221601 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgollub@novell.com Status|NEW |ASSIGNED ------- Comment #1 from seife@novell.com 2006-11-16 02:22 MST ------- (In reply to comment #0)
The /usr/share/doc/packages/bluez-utils/README.SUSE is outdated:
yes :-)
Current desktops are compatible with the new mechanism
Ok
and the configuration in YaST seems to work.
I'm not absolutely sure about this one, but i will check. Thanks for reminding. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221601 ------- Comment #2 from bwalle@novell.com 2006-11-16 02:27 MST -------
Current desktops are compatible with the new mechanism
Ok
But I tested only the gnome applet. So maybe you can do a short test with KDE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221601 ------- Comment #3 from seife@novell.com 2006-11-16 07:06 MST ------- YaST works (sort of, the security settings might behave differently than expected, since the machine will be invisible after 3 minutes no matter what you set there). I have updated the README: ------------------------ These latest packages are updates to version 3.7, which brings some different configuration options. The whole process of providing a PIN for generating a link key for the bluetooth connection has changed. In the old version (2.x), a helper program was called that provided the PIN on its standard output. In SUSE, this taks was usually achieved by kbluetoothd. The standard pin helper also was able to read a PIN from /etc/bluetooth/pin. This is completely reworked now. Now a process called a "passkey agent" has to register on the D-Bus and provide the PIN upon request. Don't worry, this is easier than it sounds. You have to either: - set your PIN in /etc/bluetooth/hcid.conf: security auto; passkey "your_PIN"; This will only work for incoming connections and is not very useful because of that limitation. This is also the PIN set by the YaST2 bluetooth module. - set security to "user" in hcid.conf: security user; and then start passkey-agent before trying to pair your device: passkey-agent --default your_PIN Passkey-agent won't exit once the device is paired, you have to abort it with CTRL-C. Or you just start kbluetoothd (KDE, package kdebluetooth) or bluetooth-applet (GNOME, package bluez-gnome) which both contain a nice graphical passkey agent. If you updated from an older version, you have to remove the "auth" and "encrypt" lines from hcid.conf, otherwise it probably won't work. Another change is that per default, the adapter gets invisible after 3 minutes. You can set this value via the BlueZ-DBus-interface. If set to 0, it will stay discoverable. The easiest way to set this right now is to use the "apitest" utility from the bluez-test package: apitest GetMode # get the mode, "discoverable", "connectable", "off" apitest SetMode discoverable # set the mode apitest GetDiscoverableTimeout apitest SetDiscoverableTimeout 0 # forever You need to install at least the python-gtk and dbus-1-python packages to use apitest. There are probably some more hidden problems in this new release. If you find some of them, don't hesitate to report a bug on http://bugzilla.novell.com. Have a lot of fun... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221601 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #4 from seife@novell.com 2006-11-22 13:33 MST ------- package is in RC1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=221601 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com