public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Echtler <floe@butterbrot.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Can't connect to Trust Bluetooth mouse..
Date: Fri, 12 Sep 2008 09:14:06 +0200	[thread overview]
Message-ID: <1221203646.4280.5.camel@bernd.floe.gotdns.org> (raw)
In-Reply-To: <1220906328.24928.9.camel@cookie.hadess.net>


[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]

> > I just bought a Trust Bluetooth Mouse 15351. However, I can't connect to
> > it via bluez-gnome, nor via hcitool. Here's what hcidump shows when I
> > try:
> <snip>
> > Unfortunately, I have to admit I can't really make sense out of this,
> > except that it seems that the mouse terminates the connection after the
> > "Remote Name Request" command.. I have bluez 3.36 installed.
> In my experience with a similarly cheap Trust mouse, my advice is:
> change the batteries to known working ones, check that they make contact
> properly.
Thanks for the hint; I've used new batteries and checked the contacts.
Still, no luck. However, it looks like the problem is of a different
sort than I previously thought. IIRC connecting via hcitool isn't really
supposed to work for input devices anyway. When I try to connect via
bluetooth-applet, hcidump shows:

< HCI Command: Inquiry (0x01|0x0001) plen 5
    lap 0x9e8b33 len 8 num 0
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Result (0x02) plen 15
    bdaddr 11:11:12:11:1F:06 mode 1 clkoffset 0x1d51 class 0x002580
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00

And nothing else anymore, even after I click the connect button. Just an
empty window labeled "connecting to device..", but nothing else happens
(especially no bluetooth communication). In the console,
bluetooth-properties shows:

** (bluetooth-properties:7171): CRITICAL **: dbus_g_proxy_begin_call:
assertion `DBUS_IS_G_PROXY (proxy)' failed

So I'm getting suspicious that this is in fact a DBus problem.. any
ideas?

Many thanks, Yours, Florian

[-- Attachment #1.2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 363 bytes --]

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

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

  reply	other threads:[~2008-09-12  7:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08 20:16 [Bluez-devel] Can't connect to Trust Bluetooth mouse Florian Echtler
2008-09-08 20:38 ` Bastien Nocera
2008-09-12  7:14   ` Florian Echtler [this message]
2008-09-12  7:22     ` Florian Echtler

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=1221203646.4280.5.camel@bernd.floe.gotdns.org \
    --to=floe@butterbrot.org \
    --cc=bluez-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox