[gnome-bluetooth] Re: PATCH interoperability issues because of no disconnect

Allen Hubbe allenbh at gmail.com
Sat Jun 30 23:30:20 BST 2007


Ok, I got it to build.  My problem was I didn't set CFLAGS and LDFLAGS
for configure, since I didn't install what I was working on.

I found one error in the patch for gnome-bluetooth: typo
btctl_obex_client_disconnet should be btctl_obex_client_disconnect.

These patches DID fix my problem :D so test test test if you have send
problems, too.

Allen

PS ... I still don't know if my emails are getting to the mailing
list, is it just really slow?  I'm sitting here replying to emails in
my sent-messages folder!

On 6/30/07, Allen Hubbe <allenbh at gmail.com> wrote:
> I have this symptom where I can send files from my phone just fine,
> but I can't successfully receive them.  From a dump of the traffic, I
> can see that the data is transferred successfully and the receiver
> responds 200 (OK) in both directions.  The only difference I could see
> is that my phone sends OBEX Disconnect before tearing down the link,
> but my computer just tears down the link.
>
> I attached a couple patches that I think fix this problem (not tested,
> because I'm having a really hard time getting gnome-bluetooth to
> build).  See attachments.
>
> I'll describe the libbtctl patch first, since the gnome-bluetooth
> patch doesn't make sense without it.  I added the
> btctl_obex_client_disconnect function which causes an obex disconnect
> request to be sent.  Also, I added a signal for handling the
> disconnect response from the link partner.
>
> The gnome-bluetooth patch doesn't call gtk_main_quit after the last
> transfer, instead it calls the new btctl_obex_client_disconnect
> function.  gtk_main_quit is moved to a callback, called when the
> disconnect response is received.
>
>
> Not sure if my previous email got through, sorry if I am repeating myself.
>
> Allen
>
>


More information about the gnome-bluetooth mailing list