[Bug 217073] New: unable to pair with mobile phone
https://bugzilla.novell.com/show_bug.cgi?id=217073 Summary: unable to pair with mobile phone Product: openSUSE 10.2 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: sbrabec@novell.com QAContact: qa@suse.de After running of YaST and enabling Bluetooth and filling PIN (and additionally filling the same pin into /etc/bluetooth/pin and restarting bluetooth, I am not able to pair with my mobile phone: - In mobile phone: My devices -> Add new device - search is able to find other devices, but not the computer I am using. - "obexftp -b [my MAC here] -g telecom/pb.vcf": Phone asks for key and then reports that the key does not match. In SuSE Linux 10.1, the same configuration works. My phone is SE T630. Dongle was connected during boot. My hcid.conf: # # HCI daemon configuration file. # # HCId options options { # Automatically initialize new devices autoinit yes; # Security Manager mode # none - Security manager disabled # auto - Use local PIN for incoming connections # user - Always ask user for a PIN # security auto; # Pairing mode # none - Pairing disabled # multi - Allow pairing with already paired devices # once - Pair once and deny successive attempts pairing multi; # Default PIN code for incoming connections passkey "[my pin here]"; } # Default settings for HCI devices device { # Local device name # %d - device id # %h - host name name "hammer"; # Local device class # e.g. # 0xsss100 = Computer # 0xsss104 = Computer Desktop # 0xsss108 = Computer Server # 0xsss10c = Computer Laptop # The 'sss' above defines the service-class (not quite, only the # first 11 bits, the next 11 define the device-class, than 2 format bits.) # See https://www.bluetooth.org/foundry/assignnumb/document/baseband # for more information. # 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)" # 0x020bbb stands for "Networking (LAN, Ad hoc, ...)" class 0x3e0100; # Default packet type #pkt_type DH1,DM1,HV1; # Inquiry and Page scan # valid parameters: enable | disable iscan enable; pscan enable; # Default link mode # none - no specific policy # accept - always accept incoming connections # master - become master on incoming connections, # deny role switch on outgoing connections lm accept; # Default link policy # none - no specific policy # rswitch - allow role switch # hold - allow hold mode # sniff - allow sniff mode # park - allow park mode lp rswitch,hold,sniff,park; } -- 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=217073 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|unable to pair with mobile |Bluetooth: unable to pair with mobile phone |phone | -- 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=217073 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lslezak@novell.com |screening@forge.provo.novell| |.com | -- 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=217073 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@novell.com AssignedTo|lslezak@novell.com |behlert@novell.com Component|Network |Mobile Devices ------- Comment #1 from lslezak@novell.com 2006-11-06 00:58 MST ------- The config files seem to be correct, reassigning to mobile-devices team... -- 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=217073 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@novell.com AssignedTo|behlert@novell.com |seife@novell.com ------- Comment #2 from behlert@novell.com 2006-11-06 07:08 MST ------- Seife, I think this is related to the changed Bluez-structure -- 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=217073 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgollub@novell.com Status|NEW |ASSIGNED ------- Comment #3 from seife@novell.com 2006-11-06 11:27 MST ------- yes. Pairing now works differrent. Read README.SUSE-factory in the bluez-utils doc, and / or use bluez-gnome or the latest kdebluetooth (not yet in stable-x86, changelog newer than Nov. 3.) as a passkey-agent. -- 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=217073 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Comment #4 from seife@novell.com 2006-11-06 11:27 MST ------- if it doesn't work as described in the README, please reopen. -- 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=217073 sbrabec@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WORKSFORME | ------- Comment #5 from sbrabec@novell.com 2006-11-08 09:35 MST ------- 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 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 I guess that we should have a GUI for making device visible. -- 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=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.
https://bugzilla.novell.com/show_bug.cgi?id=217073 dgollub@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #7 from dgollub@novell.com 2006-11-11 03:56 MST ------- (In reply to comment #5)
The second problem: Making device visible does not work:
~> apitest SetMode discoverabe ^^^^^^^^ typo ... a 'l' is missing
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 There was a typo in REAME.SUSE-factory:
apitest SetMode discoverabe changed it to: apitest SetMode discoverable I also renamed from README.SUSE-factory to REAMDE.SUSE. Seife: I hope you agree. I checked in fixed package.
I guess that we should have a GUI for making device visible.
There is a nice configuration dialog in the latest release of bluez-gnome 0.6 (from 2006-10-22). For this you should open a new bug and assignee it to the bluez-gnome package maintainer. Also i guess this have to be accepted by AJ. -- 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=217073 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