From: Bastien Nocera <hadess@hadess.net>
To: Pacho Ramos <pacho@gentoo.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Cannot send files to PC from phone
Date: Sat, 22 Mar 2014 12:23:53 +0100 [thread overview]
Message-ID: <1395487433.1597.60.camel@nuvo> (raw)
In-Reply-To: <1395481944.1364.2.camel@belkin5>
On Sat, 2014-03-22 at 10:52 +0100, Pacho Ramos wrote:
> We get this errors:
> obexd[1944]: OBEX daemon 5.16
> obexd[1944]: CONNECT(0x0), (null)(0xffffffff)
> obexd[1944]: CONNECT(0x0), (null)(0x0)
> obexd[1944]: PUT(0x2), (null)(0xffffffff)
> obexd[1944]: PUT(0x2), FORBIDDEN(0x43)
> obexd[1944]: DISCONNECT(0x1), (null)(0xffffffff)
> obexd[1944]: DISCONNECT(0x1), SUCCESS(0x20)
> obexd[1944]: disconnected: Transport got disconnected
>
> Looks similar to:
> https://bugzilla.novell.com/show_bug.cgi?id=842688
>
> But we are applying Fedora patches to not need to use systemd --user and
> still get the problems :/
>
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-wireless/bluez/bluez-5.16.ebuild?view=markup
> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-wireless/bluez/files/0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch?revision=1.1&view=markup
What are you using as the server (computer) side program? Is it
gnome-user-share, or the obex test application in bluez?
Simply having obexd installed isn't enough, you need an application to
control it and handle authorisation, etc.
next prev parent reply other threads:[~2014-03-22 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 9:52 Cannot send files to PC from phone Pacho Ramos
2014-03-22 11:23 ` Bastien Nocera [this message]
2014-03-22 11:45 ` Pacho Ramos
2014-03-22 11:49 ` Pacho Ramos
2014-04-08 19:02 ` Pacho Ramos
2014-04-09 10:15 ` Bastien Nocera
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=1395487433.1597.60.camel@nuvo \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pacho@gentoo.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).