* Re: [Bluez-users] A2DPD fails to init with a2dp_make_listen_socket: (errno=13:Permission denied)Cannot bind socket
2007-04-24 9:09 ` [Bluez-users] A2DPD fails to init with a2dp_make_listen_socket: (errno=13:Permission denied)Cannot bind socket TJ
@ 2007-04-24 9:53 ` Frederic Dalleau
2007-04-25 9:00 ` TJ
2007-04-25 13:56 ` TJ
1 sibling, 1 reply; 4+ messages in thread
From: Frederic Dalleau @ 2007-04-24 9:53 UTC (permalink / raw)
To: BlueZ users
Hi,
thank you for the softvol trick.
It looks like you already have a2dpd running.
maybe killall a2dpd before could help
TJ wrote:
> Hi (Third attempt to reach the list),
>
> While I have got headsetd working fine, but I can't get a2dpd to run.
> It gives the following messages:
>
> A2DPD[17:06:13.085]: init_ipc: Selected IPC: unix, addr=127.0.0.1,
> bcst=127.0.0.255, port=21453
> A2DPD[17:06:13.085]: make_daemon_process: a2dpd [Apr 17 2007 09:46:05]
> starting ...
> A2DPD[17:06:13.085]: main: (errno=9:Bad file descriptor)a2dpd
> addr=00:13:17:C5:39:94 timer=4000 us [Apr 17 2007 09:46:12]
> A2DPD[17:06:13.085]: a2dpd_signal_init: Getting on DBUS
> A2DPD[17:06:13.086]: a2dpd_signal_init: Installing watch
> A2DPD[17:06:13.086]: add_dbus_watch: Added watch 0 0x809b960 disabled
> A2DPD[17:06:13.086]: add_dbus_watch: Added watch 1 0x809b988 enabled
> A2DPD[17:06:13.086]: a2dpd_signal_init: Registering object
> path: /com/access/a2dpd
> A2DPD[17:06:13.086]: a2dpd_signal_init: Acquiring service: com.access.a2dpd
> A2DPD[17:06:13.087]: a2dpd_signal_init: OK
> A2DPD[17:06:13.087]: a2dpd_signal_init: OK
> A2DPD[17:06:13.087]: a2dpd_register_sdp: OK
> A2DPD[17:06:13.087]: add_avrtg:
> A2DPD[17:06:13.088]: add_a2source:
> A2DPD[17:06:13.088]: main_loop:
> A2DPD[17:06:13.088]: make_server_socket:
> A2DPD[17:06:13.088]: a2dp_make_listen_socket: (errno=13:Permission
> denied)Cannot bind socket 6 for psm 25
> A2DPD[17:06:13.088]: main_loop: Cannot get AVDTP socket
> A2DPD[17:06:14.091]: main_loop:
> A2DPD[17:06:14.091]: make_server_socket:
> A2DPD[17:06:14.091]: main_loop: (errno=98:Address already in use)Cannot get
> UNIX socket
> A2DPD[17:06:15.095]: main_loop:
> A2DPD[17:06:15.095]: make_server_socket:
> A2DPD[17:06:15.095]: main_loop: (errno=98:Address already in use)Cannot get
> UNIX socket
> A2DPD[17:06:16.099]: main_loop:
> A2DPD[17:06:16.099]: make_server_socket:
> A2DPD[17:06:16.099]: main_loop: (errno=98:Address already in use)Cannot get
> UNIX socket
>
> This is from CVS on 2007-04-17, I did an update today (2007-04-19) but there
> doesn't seem to be any changes.
>
> Using libsbc 0.0cvs20070327-1 (Debian testing package)
>
> This is on Debian testing with bluez-utils 3.7-1, linux kernel 2.6.20.
>
> I should say that I installed plugz into my home directory and I run all the
> daemons as my user not root. I have PATH, LD_*, etc setup and I created
> symlinks in /usr/lib/alsa-lib to the files in the alsa-lib under my home
> dir, since I didn't know how else to tell ALSA where to look.
>
>
> On a more positive note here is an asoundrc to give you a headset volume
> control in the alsa mixer:
>
> pcm.!default {
> type softvol
> slave {
> pcm "headset"
> }
>
> control {
> name "Bluetooth Headset"
> card 0
> count 1
> }
> }
>
> Add this to the asoundrc shipped with plugz, you don't have to call
> it !default. You can now use any alsa mixer app to control volume (and so
> create key bindings). Obviously this means you can disable soft mixer in
> xmms and tell it to use "Bluetooth Headset".
>
> Make sure that the control name (here "Bluetooth Headset") doesn't already
> exist in your mixer as a real (hw) control.
>
> Thanks for any help.
>
> Thorben.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [Bluez-users] A2DPD fails to init with a2dp_make_listen_socket: (errno=13:Permission denied)Cannot bind socket
2007-04-24 9:09 ` [Bluez-users] A2DPD fails to init with a2dp_make_listen_socket: (errno=13:Permission denied)Cannot bind socket TJ
2007-04-24 9:53 ` Frederic Dalleau
@ 2007-04-25 13:56 ` TJ
1 sibling, 0 replies; 4+ messages in thread
From: TJ @ 2007-04-25 13:56 UTC (permalink / raw)
To: BlueZ users
Hi,
>
> While I have got headsetd working fine, but I can't get a2dpd to run.
> It gives the following messages:
>
...
>
> This is from CVS on 2007-04-17, I did an update today (2007-04-19) but
> there doesn't seem to be any changes.
>
> Using libsbc 0.0cvs20070327-1 (Debian testing package)
>
> This is on Debian testing with bluez-utils 3.7-1, linux kernel 2.6.20.
>
> I should say that I installed plugz into my home directory and I run all
> the daemons as my user not root. I have PATH, LD_*, etc setup and I
> created symlinks in /usr/lib/alsa-lib to the files in the alsa-lib under
> my home dir, since I didn't know how else to tell ALSA where to look.
>
It appears to run OK as root (from my homedir):
~$ sudo Linux/bin/a2dpd --nofork --file .a2dprc
A2DPD[14:50:01.264]: main: Config file .a2dprc
A2DPD[14:50:01.265]: init_ipc: Selected IPC: unix, addr=127.0.0.1,
bcst=127.0.0.255, port=21453
A2DPD[14:50:01.265]: make_daemon_process: a2dpd [Apr 17 2007 09:46:05]
starting ...
A2DPD[14:50:01.265]: main: (errno=9:Bad file descriptor)Linux/bin/a2dpd
addr=00:13:17:C5:39:94 timer=4000 us [Apr 17 2007 09:46:12]
A2DPD[14:50:01.265]: a2dpd_signal_init: Getting on DBUS
A2DPD[14:50:01.266]: a2dpd_signal_init: Installing watch
A2DPD[14:50:01.266]: add_dbus_watch: Added watch 0 0x809b8e0 disabled
A2DPD[14:50:01.267]: add_dbus_watch: Added watch 1 0x809b908 enabled
A2DPD[14:50:01.267]: a2dpd_signal_init: Registering object
path: /com/access/a2dpd
A2DPD[14:50:01.267]: a2dpd_signal_init: Acquiring service: com.access.a2dpd
A2DPD[14:50:01.267]: a2dpd_signal_init: OK
A2DPD[14:50:01.267]: a2dpd_signal_init: OK
A2DPD[14:50:01.267]: a2dpd_register_sdp: OK
A2DPD[14:50:01.267]: add_avrtg:
A2DPD[14:50:01.268]: add_a2source:
A2DPD[14:50:01.268]: main_loop:
A2DPD[14:50:01.268]: make_server_socket:
A2DPD[14:50:01.268]: bta2dpdevicenew:
A2DPD[14:50:01.268]: a2dpd_signal_address_changed: 00:13:17:C5:39:94
A2DPD[14:50:01.268]: a2dpd_signal_set_socket: Signal socket set to 7
A2DPD[14:50:01.269]: a2dpd_signal_state: Disconnected
A2DPD[14:50:01.269]: a2dp_alloc:
A2DPD[14:50:01.269]: a2dp_alloc: (a2dp = 0x80a92c0)
A2DPD[14:50:01.269]: a2dp_new: 00:13:17:C5:39:94, 44100
A2DPD[14:50:01.269]: a2dp_new: State AVDTP_STATE_DISCONNECTED
A2DPD[14:50:01.269]: alsa_new:
A2DPD[14:50:01.269]: alsa_new: device=plughw:0,0, framerate=44100
A2DPD[14:50:01.269]: alsa_new: State ALSA_STATE_DISCONNECTED
A2DPD[14:50:01.269]: alsa_new: returning 0x80ab448
A2DPD[14:50:01.269]: sco_new:
A2DPD[14:50:01.269]: sco_new: State SCO_STATE_DISCONNECTED
A2DPD[14:50:01.269]: sco_state_disconnect: Filtering state : already
disconnected
A2DPD[14:50:01.269]: main_loop: Bluetooth Device Settings [44100 hz, 2
channels, 16 bits]
A2DPD[14:50:01.270]: avrcp_new: Listening for AVRCP on socket 9
A2DPD[14:50:01.270]: avrcp_new: 0x80ab558
Surely it must be possible to run as a normal users? don't the docs say
_not_ to run a2pdp as root. While running as root I can play anything from
my user, only if the playing app is running as root, which is not at all
ideal.
I would assume this is a permissions issue. Obviously my user can write
to /tmp, and headsetd runs fine as my user to bluetooth/alsa comms must be
ok?
So what is causing this?
Thorben
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 4+ messages in thread