Open mahlonsmith opened 2 years ago
Ah, and I now see the commit message at https://github.com/mvidner/ruby-dbus/commit/ac217605270ecf5beefdade9598e6556217e68b0.
Not sure yet if that's still the case (10 years ago), but if so, this issue is actually a feature request. :-)
You're right, UNIX_FD is not actually implemented. A major reason is that the spec is vague about the file descriptors are actually passed, and I was not determined enough to dig it up in other implementations. The Bluetooth use case looks a bit complex but fortunately there's UDisks OpenDevice which is simple enough for me to try and figure it out.
Excellent!
Found this project as well, and I can confirm it works -- clearly a very specific use case, and using a gio library C extension - but more stuff to dig into to see what is going on under the hood, at least. (I'll also be diggin'...)
Heya!
I'm using ruby-dbus to attempt a Bluetooth serial profile callback, and I'm running into a "Tried to send message with Unix file descriptors to a client that doesn't support that." error message from dbus.
It's entirely possible I'm defining the callback incorrectly, but I think that's correct. Example profile definition and registration (as defined here)
When an RFCOMM compatible client connects, the dbus monitor shows it disconnect immediately (the callback doesn't fire at all).
It seems like it's complaining specifically about the second argument to the NewConnection method.
Is there a different path I should be taking to tackle this?
Thanks for any insight provided.