From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Vinicius Gomes <vinicius.gomes@openbossa.org>,
pacho@condmat1.ciencias.uniovi.es,
linux-bluetooth@vger.kernel.org
Subject: Re: obexd-0.22 causes gnome-bluetooth sendto dialog to stop closing when operation ends
Date: Wed, 14 Apr 2010 10:19:53 +0300 [thread overview]
Message-ID: <p2q2d5a2c101004140019w21c6e680s47159a70d9f0bac7@mail.gmail.com> (raw)
In-Reply-To: <1271085759.6731.6348.camel@localhost.localdomain>
Hi,
On Mon, Apr 12, 2010 at 6:22 PM, Bastien Nocera <hadess@hadess.net> wrote:
> On Sat, 2010-04-10 at 11:17 -0300, Vinicius Gomes wrote:
>> Hi Pacho,
>>
>> 2010/4/10 Pacho Ramos <pacho@condmat1.ciencias.uniovi.es>:
>> > Hello
>> >
>> > This is a regression over obexd-0.21. After updating to 0.22,
>> > gnome-bluetooth sendto dialog no longer closes when operation finishes,
>> > even if file is already properly sent.
>> >
>>
>> We noticed this regression as well. Luiz already has a fix for this,
>> it was just not integrated yet.
>>
>> In case you want to take a look and perhaps help test it, the fix is here[1].
>
> Except that the patch is absolutely huge, and doesn't apply cleanly on
> 0.22 either.
For those wanting to have a quick fix for 0.22 you can revert
d57bffe46b71e17a640c11b389dd6da95f933729, which cause the extra
reference to be hold. In the meantime I will be doing some cleanups to
session code and moving the transfer logic to a separate file those
changes will probably be only available in 0.23.
--
Luiz Augusto von Dentz
Computer Engineer
prev parent reply other threads:[~2010-04-14 7:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 11:22 obexd-0.22 causes gnome-bluetooth sendto dialog to stop closing when operation ends Pacho Ramos
2010-04-10 14:17 ` Vinicius Gomes
2010-04-10 18:38 ` Pacho Ramos
2010-04-12 15:22 ` Bastien Nocera
2010-04-14 7:19 ` Luiz Augusto von Dentz [this message]
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=p2q2d5a2c101004140019w21c6e680s47159a70d9f0bac7@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pacho@condmat1.ciencias.uniovi.es \
--cc=vinicius.gomes@openbossa.org \
/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;
as well as URLs for NNTP newsgroup(s).