From: "David Stockwell" <dstockwell@frequency-one.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Bluez-utils-3.30 plugins failing at startup
Date: Sat, 26 Apr 2008 17:25:00 -0500 [thread overview]
Message-ID: <00b401c8a7ec$5f957550$6701a8c0@freqonedev> (raw)
[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]
I have been working to get a simple connection working between BlueZ and a CSR Bluetooth module. I have again hit a roadblock in
that when initializing the libxxxxx.so plugins, the call to g_module_open fails as shown in the following:
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libnetwork.so: invalid mode for dlopen():
Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libserial.so: invalid mode for dlopen():
Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libinput.so: invalid mode for dlopen():
Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libaudio.so: invalid mode for dlopen():
Invalid argument
It appears that the dlopen() is failing when called within g_module_open, which is called from /utils/hcid/plugin.c
In my configure, after specifying all of the various directories, I select --enable-debug and --enable-all; I get no errors in the
make and make install. The .so and .la files are all in the /usr/lib/bluetooth/plugins directory. What am I missing?
Interestingly, and probably because I have modified the audio.conf file, the audio service DOES register itself, despite the failure
of the libaudio.so plugin, as shown in the following...
Apr 26 16:27:28 freqonec001 hcid[2817]: Registering service object: ident=audio, name=Audio service (/org/bluez/service_audio)
When I try to Activate the audio service, it falls over, because under 3.30, the service apparently is looking for a plugin, and not
the daemon that was used in 3.29 and before (I think I have this right).
Apr 26 16:34:48 freqonec001 hcid[2817]: /org/bluez: org.bluez.Manager.ActivateService()
Apr 26 16:34:48 freqonec001 hcid[2817]: Unable to execute /usr/lib/bluetooth/bluetoothd-service-audio
Prior to today, to get SOMETHING [sort-of] working, I copied a 3.29 version of bluetoothd-service-audio into the /usr/lib/bluetooth
directory and it had some functionality. However, once I renamed that module to take it out of the equation, ActivateService fails:
Exec format error.
The entire startup log (this time around) is attached.
David Stockwell
[-- Attachment #2: 20080426 Bluez startup.log --]
[-- Type: application/octet-stream, Size: 2113 bytes --]
Apr 26 16:27:27 freqonec001 hcid[2817]: Bluetooth HCI daemon
Apr 26 16:27:27 freqonec001 hcid[2817]: Enabling debug information
Apr 26 16:27:27 freqonec001 hcid[2817]: Registering experimental manager path
Apr 26 16:27:27 freqonec001 hcid[2817]: Registering experimental manager interface
Apr 26 16:27:27 freqonec001 hcid[2817]: HCI dev 0 registered
Apr 26 16:27:27 freqonec001 hcid[2817]: Starting SDP server
Apr 26 16:27:27 freqonec001 hcid[2817]: Adding rec : 0x8089c10
Apr 26 16:27:27 freqonec001 hcid[2817]: with handle : 0x1
Apr 26 16:27:27 freqonec001 hcid[2817]: Adding rec : 0x8089dd8
Apr 26 16:27:27 freqonec001 hcid[2817]: with handle : 0x0
Apr 26 16:27:27 freqonec001 hcid[2817]: Service classes 0x00
Apr 26 16:27:28 freqonec001 hcid[2817]: Loading plugins /usr/lib/bluetooth/plugins
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libnetwork.so: invalid mode for dlopen(): Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libserial.so: invalid mode for dlopen(): Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libinput.so: invalid mode for dlopen(): Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Can't load plugin: /usr/lib/bluetooth/plugins/libaudio.so: invalid mode for dlopen(): Invalid argument
Apr 26 16:27:28 freqonec001 hcid[2817]: Registering service object: ident=audio, name=Audio service (/org/bluez/service_audio)
Apr 26 16:27:28 freqonec001 hcid[2817]: HCI dev 0 up
Apr 26 16:27:28 freqonec001 hcid[2817]: Device hci0 has been added
Apr 26 16:27:28 freqonec001 hcid[2817]: Starting security manager 0
Apr 26 16:27:28 freqonec001 hcid[2817]: Device hci0 has been activated
Apr 26 16:27:28 freqonec001 hcid[2817]: child 2848 exited
Apr 26 16:27:28 freqonec001 hcid[2817]: child 2877 exited
Apr 26 16:34:48 freqonec001 hcid[2817]: /org/bluez: org.bluez.Manager.ActivateService()
Apr 26 16:34:48 freqonec001 hcid[2817]: Unable to execute /usr/lib/bluetooth/bluetoothd-service-audio
[-- Attachment #3: Type: text/plain, Size: 320 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2008-04-26 22:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='00b401c8a7ec$5f957550$6701a8c0@freqonedev' \
--to=dstockwell@frequency-one.com \
--cc=bluez-devel@lists.sourceforge.net \
/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