https://bugzilla.novell.com/show_bug.cgi?id=217073 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED ------- Comment #6 from seife@novell.com 2006-11-11 02:24 MST ------- (In reply to comment #5)
bluez-gnome works well and does what is expected, if it is running. But just now it's confusing that YaST interface allows to set PIN without any effect.
the PIN set in yast is for incoming connections only. I agree that this is confusing and that we have to think about that interface.
The second problem: Making device visible does not work:
~> apitest SetMode discoverabe Traceback (most recent call last): File "/usr/bin/apitest", line 432, in <module> tester.run() File "/usr/bin/apitest", line 415, in run self.call_dev_dbus_func() File "/usr/bin/apitest", line 238, in call_dev_dbus_func self.device.SetMode(self.cmd_args[0]) File "/usr/lib64/python2.5/site-packages/dbus/proxies.py", line 25, in __call__ ret = self._proxy_method (*args, **keywords) File "/usr/lib64/python2.5/site-packages/dbus/proxies.py", line 102, in __call__ reply_message = self._connection.send_with_reply_and_block(message, timeout) File "dbus_bindings.pyx", line 456, in dbus_bindings.Connection.send_with_reply_and_block TypeError: exceptions must be strings, classes, or instances, not type
ok, i will look into that.
I guess that we should have a GUI for making device visible.
i´m sure that Marcel will accept patches to bluez-gnome :-) -- 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.