main.conf issues

linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed

* main.conf issues
@ 2012-04-27 15:40 Kal Torak
  2012-04-27 20:26 ` Steffen Becker
  0 siblings, 1 reply; 6+ messages in thread
From: Kal Torak @ 2012-04-27 15:40 UTC (permalink / raw)
  To: linux-bluetooth

Hello, When I setup the main.conf with the values for Name, Class,
PairableTimeout and DiscoverableTimeout, and restart the bluetoothd,
hciconfig shows that nothing change name still the same, I cant "see"
the device from the outside(iscan is disabled), and the class still
0x000100, and I must re-do hciconfig hci name #### class #### and
hciconfig hci0 piscan by hand to make the device visible and try
streaming support, OTOH I just can't see and/or connect to the device.
a ConWise 6622 Bluetooth dongle.
I'm using bluez-4.99 and linux 3.2.15.Any information will be usefull...

Regards, 
Torak

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: main.conf issues
  2012-04-27 15:40 main.conf issues Kal Torak
@ 2012-04-27 20:26 ` Steffen Becker
  2012-04-29 11:44   ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 6+ messages in thread
From: Steffen Becker @ 2012-04-27 20:26 UTC (permalink / raw)
  To: Kal Torak; +Cc: linux-bluetooth

Hello Torak,

I'm not very familiar with BlueZ (also just asking questions on this 
mailing list), but what I can tell is that:
You have to setup this file:
/var/lib/bluetooth/<local-bdaddr>/config
At the moment I can't look up the right syntax for all the 
configuration, but if i remember right, for enabling discoverable mode 
you have to enter something like this in the config-file:

onmode discoverable
mode discoverable

For changing the name of your device, you have to edit this line in the 
config-file:

name <your-name>

Hope this helps you.
Regards,
Steffen


Am 27.04.2012 17:40, schrieb Kal Torak:
> Hello, When I setup the main.conf with the values for Name, Class,
> PairableTimeout and DiscoverableTimeout, and restart the bluetoothd,
> hciconfig shows that nothing change name still the same, I cant "see"
> the device from the outside(iscan is disabled), and the class still
> 0x000100, and I must re-do hciconfig hci name #### class #### and
> hciconfig hci0 piscan by hand to make the device visible and try
> streaming support, OTOH I just can't see and/or connect to the device.
> a ConWise 6622 Bluetooth dongle.
> I'm using bluez-4.99 and linux 3.2.15.Any information will be usefull...
>
> Regards,
> Torak
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: main.conf issues
  2012-04-27 20:26 ` Steffen Becker
@ 2012-04-29 11:44   ` Luiz Augusto von Dentz
  2012-05-01 18:20     ` Kal Torak
  0 siblings, 1 reply; 6+ messages in thread
From: Luiz Augusto von Dentz @ 2012-04-29 11:44 UTC (permalink / raw)
  To: Steffen Becker; +Cc: Kal Torak, linux-bluetooth

Hi,

On Fri, Apr 27, 2012 at 11:26 PM, Steffen Becker
<steffen.becker@tu-ilmenau.de> wrote:
> Hello Torak,
>
> I'm not very familiar with BlueZ (also just asking questions on this mailing
> list), but what I can tell is that:
> You have to setup this file:
> /var/lib/bluetooth/<local-bdaddr>/config
> At the moment I can't look up the right syntax for all the configuration,
> but if i remember right, for enabling discoverable mode you have to enter
> something like this in the config-file:
>
> onmode discoverable
> mode discoverable
>
> For changing the name of your device, you have to edit this line in the
> config-file:
>
> name <your-name>

Please no top-posting here, those files are not supposed to be
manually edited, use D-Bus API otherwise you may cause
inconsistencies.

>> Hello, When I setup the main.conf with the values for Name, Class,
>> PairableTimeout and DiscoverableTimeout, and restart the bluetoothd,
>> hciconfig shows that nothing change name still the same, I cant "see"
>> the device from the outside(iscan is disabled), and the class still
>> 0x000100, and I must re-do hciconfig hci name #### class #### and
>> hciconfig hci0 piscan by hand to make the device visible and try
>> streaming support, OTOH I just can't see and/or connect to the device.
>> a ConWise 6622 Bluetooth dongle.
>> I'm using bluez-4.99 and linux 3.2.15.Any information will be usefull...

You don't have to do that in main.conf, except for class, those values
are only used when there is nothing already configured, so to change
this you really should be using D-Bus. You can find under
tests/test-adapter how to set this permanently in the configuration of
the adapter.

Btw, for the class it actually gets updated automatically when you
register the services.

-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: main.conf issues
  2012-04-29 11:44   ` Luiz Augusto von Dentz
@ 2012-05-01 18:20     ` Kal Torak
  2012-05-02  8:08       ` Luiz Augusto von Dentz
  0 siblings, 1 reply; 6+ messages in thread
From: Kal Torak @ 2012-05-01 18:20 UTC (permalink / raw)
  To: linux-bluetooth

> Hi,
> 
> On Fri, Apr 27, 2012 at 11:26 PM, Steffen Becker
> <steffen.becker@tu-ilmenau.de> wrote:
> > Hello Torak,
> >
> > I'm not very familiar with BlueZ (also just asking questions on
> > this mailing list), but what I can tell is that:
> > You have to setup this file:
> > /var/lib/bluetooth/<local-bdaddr>/config
> > At the moment I can't look up the right syntax for all the
> > configuration, but if i remember right, for enabling discoverable
> > mode you have to enter something like this in the config-file:
> >
> > onmode discoverable
> > mode discoverable
> >
> > For changing the name of your device, you have to edit this line in
> > the config-file:
> >
> > name <your-name>
> 

Thanks for the reply and sorry for the delay...

> Please no top-posting here, those files are not supposed to be
> manually edited, use D-Bus API otherwise you may cause
> inconsistencies.
> 
> You don't have to do that in main.conf, except for class, those values
> are only used when there is nothing already configured, so to change
> this you really should be using D-Bus. You can find under
> tests/test-adapter how to set this permanently in the configuration of
> the adapter.
> 
I do that, via tests/test-adapter, and right now it works, thanks to
both. I was paired both devices, my phone with my pc and I can use
obex-stuff and so. But when I've paired devices, then this appears
at /var/log/messages

May  1 14:10:33 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Device"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
M1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"ay  1
14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2 matched
rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.AudioSource"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")
May  1 14:10:39 p5s800-vm dbus[411]: [system] Rejected send message, 2
matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Audio"
member="GetProperties" error name="(unset)" requested_reply="0"
destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")

and I think this say something about "why" I can't do "A2DP"

> Btw, for the class it actually gets updated automatically when you
> register the services.
> 
I'm trying to streaming audio from cellphone, to Computer, but there is
unlimited dbus and pulse errors upthere, I don't know If I should
register some services and really don't know how to do that...

Thank you for all information, I starting reading about dbus for see
if I can do something, again, if theres any information it will be
valuable... Regards

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: main.conf issues
  2012-05-01 18:20     ` Kal Torak
@ 2012-05-02  8:08       ` Luiz Augusto von Dentz
  2012-05-04 17:32         ` Kal Torak
  0 siblings, 1 reply; 6+ messages in thread
From: Luiz Augusto von Dentz @ 2012-05-02  8:08 UTC (permalink / raw)
  To: Kal Torak; +Cc: linux-bluetooth

Hi Kal,

On Tue, May 1, 2012 at 9:20 PM, Kal Torak <chronognosis@aim.com> wrote:
>> You don't have to do that in main.conf, except for class, those values
>> are only used when there is nothing already configured, so to change
>> this you really should be using D-Bus. You can find under
>> tests/test-adapter how to set this permanently in the configuration of
>> the adapter.
>>
> I do that, via tests/test-adapter, and right now it works, thanks to
> both. I was paired both devices, my phone with my pc and I can use
> obex-stuff and so. But when I've paired devices, then this appears
> at /var/log/messages
>
> May  1 14:10:33 p5s800-vm dbus[411]: [system] Rejected send message, 2
> matched rules; type="method_call", sender=":1.37" (uid=100 pid=1037
> comm="/usr/bin/pulseaudio --start ") interface="org.bluez.Device"
> member="GetProperties" error name="(unset)" requested_reply="0"
> destination="org.bluez" (uid=0 pid=603 comm="/usr/sbin/bluetoothd ")

It seems some security policy is blocking PulseAudio to send messages
to bluetoothd, check your /etc/dbus-1/system.d/bluetooth.conf, there
is a sample configuration file in the repository src/bluetooth.conf
which should work with PulseAudio.


-- 
Luiz Augusto von Dentz

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: main.conf issues
  2012-05-02  8:08       ` Luiz Augusto von Dentz
@ 2012-05-04 17:32         ` Kal Torak
  0 siblings, 0 replies; 6+ messages in thread
From: Kal Torak @ 2012-05-04 17:32 UTC (permalink / raw)
  To: linux-bluetooth

Wed, 2 May 2012 11:08:34 +0300
Luiz Augusto von Dentz <luiz.dentz@gmail.com> escribió:

> It seems some security policy is blocking PulseAudio to send messages
> to bluetoothd, check your /etc/dbus-1/system.d/bluetooth.conf, there
> is a sample configuration file in the repository src/bluetooth.conf
> which should work with PulseAudio.
> 
> 

Thank you Luiz, I solve that, rigth now I can call the methods
from dbus-send. But now I'm trying to complete mi initial purpose
Stream from the device, but I can't do that, when I try to do
org.bluez.AudioSource.Connect, the method return a error, Unable to
setup the stream, and bluetoohd logs Unable to select SEP
at /var/log/messages... What mean that ? SEP ?
Regards

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-05-04 17:32 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-04-27 15:40 main.conf issues Kal Torak
2012-04-27 20:26 ` Steffen Becker
2012-04-29 11:44   ` Luiz Augusto von Dentz
2012-05-01 18:20     ` Kal Torak
2012-05-02  8:08       ` Luiz Augusto von Dentz
2012-05-04 17:32         ` Kal Torak

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).