Hello,
On 30 November 2015 at 12:26, Pau Espin Pedrol <[email protected]> wrote:
> Hi Michal,
>
> you may want to use "dbus-monitor" when unsure about the dbus
> messages/signals being sent. I find that tool quite useful, it already
> helped me find dbus-related errors in the past.
>
> About the "refuses to talk to my program afterwards" part, I recall reading
> somewhere that the dbus server can drop the connection if the client is not
> acting properly, but I never checked it.
>
Thanks for the suggestion with dbus-monitor
I receive NameLost for my dbus address just after sending the message.
The constructed message signature is o{s{ay}s{y}s{s}}. Is that valid?
If not should not eldbus prevent constructing such message?
I have only version 1.8.6 since Debian ships that.
A program that successfully calls the interface gives this in dbus-monitor:
method call time=1448964553.860814 sender=:1.905 ->
destination=org.bluez serial=15 path=/org/bluez/hci0;
interface=org.bluez.Media1; member=RegisterEndpoint
object path "/test/testenkrumppel/u1000/hci0"
array [
dict entry(
string "UUID"
variant string "0000110A-0000-1000-8000-00805F9B34FB"
)
dict entry(
string "Codec"
variant byte 0
)
dict entry(
string "Capabilities"
variant array of bytes [
ff ff 02 fa
]
)
]
https://gist.github.com/hramrach/606ae05725f49eeaabf3
Thanks
Michal
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
