All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] PM325 by LG cell phone - pairing failed
Date: Fri, 09 Jun 2006 09:08:24 +0200	[thread overview]
Message-ID: <1149836904.6618.4.camel@localhost> (raw)
In-Reply-To: <44891608.2030906@personnelware.com>

Hi Carl,

> I am trying to pair my phone to my ubuntu/dapper laptop . 
> carl@asus17:~$ lsusb
> 
> Bus 003 Device 002: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth
> carl@asus17:~$ cat /etc/bluetooth/pin
> 1234
> carl@asus17:~$ sudo /etc/init.d/bluez-utils start
> 
> On the phone:  menu, bluetooth, add new, Searching and Pairing,
> it shows asus17-0, I select that, phone prompts "Enter PIN code", I 
> enter 1234<Next> and within a second get "pairing failed"
> 
> guessing because of this:
> 
> Jun  9 00:37:42 localhost gconfd (root-7749): starting (version 2.14.0), 
> pid 7749 user 'root'
> Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
> "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only 
> configuration source at position 0
> Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
> "xml:readwrite:/root/.gconf" to a writable configuration source at 
> position 1
> Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
> "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only 
> configuration source at position 2
> Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
> "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only 
> configuration source at position 3
> Jun  9 00:37:42 localhost gconfd (root-7749): Resolved address 
> "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration 
> source at position 4
> Jun  9 00:38:42 localhost gconfd (root-7749): GConf server is not in 
> use, shutting down.
> Jun  9 00:38:42 localhost gconfd (root-7749): Exiting
> 
> Jun  9 01:03:08 localhost hcid[8572]: Bluetooth HCI daemon
> Jun  9 01:03:08 localhost hcid[8572]: Can't get system message bus name: 
> Connection ":1.15" is not allowed to own the service "org.bluez" due to 
> security policies in the configuration file
> Jun  9 01:03:08 localhost hcid[8572]: Starting security manager 0
> Jun  9 01:03:08 localhost sdpd[8577]: Bluetooth SDP daemon
> 
> 
> I probably need to file a bug report with ubuntu, but I would like to 
> get some feedback from the experts so that the report has some useful info.

for the "security policies" error you should really file a bug report
with Ubuntu. For the rest show us the output of "hcidump -X -V" while
you are trying to pair. I suspect that you PIN help isn't called
properly.

Regards

Marcel




_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-06-09  7:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09  6:32 [Bluez-users] PM325 by LG cell phone - pairing failed Carl K
2006-06-09  7:08 ` Marcel Holtmann [this message]
2006-06-09  8:02   ` Carl K
2006-06-09  8:07     ` Marcel Holtmann
2006-06-09  8:27       ` Carl K
2006-06-09  8:40         ` Marcel Holtmann
2006-06-09  9:38           ` Carl K

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1149836904.6618.4.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.