public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patryk Zawadzki" <patrys@pld-linux.org>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Recent bluez-gnome problems
Date: Wed, 26 Mar 2008 17:37:41 +0100	[thread overview]
Message-ID: <89b6ba3a0803260937i21870643xa2207770239d469a@mail.gmail.com> (raw)
In-Reply-To: <81E635B3-43C3-4956-B5ED-D9C4BFE8E235@holtmann.org>

On Wed, Mar 26, 2008 at 5:29 PM, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Patryk,
>  > I'm in the middle of packaging bluez-gnome 0.25 for PLD Linux. I
>  > already have obex-data-server (with --enable-system-config) packaged
>  > but hit a strange problem.
>  don't use --enable-system-config unless you know what this implies.
>  Running ODS inside the user session is good enough.

So you suggest we disable it in distro builds? Will do. I thought it
only affected system bus activation?

>  > The interface is visible and hcid is running. I've noticed the
>  > transfer service is no longer part of bluez-utils. First I was unable
>  > to get bluez to a point where it detects any devices. I can see my
>  > laptop from my cell phone but not the other way araound. After bonding
>  > (initialized from the phone) I can send files from my laptop to my
>  > cell phone (it shows bonded devices even if discovery fails to work).
>  > I can't send any files from the phone and I can't browse the phone
>  > contents (phone asks for permission but nautilus shows "connect
>  > failed" when trying to use gvfs-mount obex://[...]/).
>  >
>  > bluez-* is 3.29, obex-data-server is 0.3
>  I don't see a problem here. The latest bluez-gnome has options to
>  enable file transfer and push service.

yes, the options are there but there seems to be a problem with device
discovery somewhere in my setup. Is running hcid enough for the device
detection to work? It seems only the already paired devices show up
(it worked fine at least with bluez-gnome 0.15) so I assume it only
displays a memorized list of devices not doing discovery at all. How
do I debug it? I'm a programmer so if you point me to the right
internals I think I could fix the issues or at least provide you with
more info.

-- 
Patryk Zawadzki
PLD Linux Distribution

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2008-03-26 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 22:40 [Bluez-users] Recent bluez-gnome problems Patryk Zawadzki
2008-03-26 16:29 ` Marcel Holtmann
2008-03-26 16:37   ` Patryk Zawadzki [this message]
2008-03-26 16:40     ` Marcel Holtmann
2008-03-27 19:29       ` Patryk Zawadzki
2008-03-27 23:15         ` Marcel Holtmann
2008-04-02 19:44           ` Patryk Zawadzki
2008-04-02 19:50             ` Marcel Holtmann

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=89b6ba3a0803260937i21870643xa2207770239d469a@mail.gmail.com \
    --to=patrys@pld-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox