dbus-c++: strange behavior when using gtkmm

[Cristi Posoiu]

I had a similar problem (though I'm not having 2 client programs) and in the
end I found the solution and just finished writing a fix.
Indeed it is a bug in the dbus-c++ GLib integration.
Please check the bug I opened,
https://bugs.freedesktop.org/show_bug.cgi?id=18282, and take the patch from
there.
You might need to remove the text heading, the last 2-3 lines, and the lines
with 'index XXX XXX' to be able to use the 'patch' program.

Hope that helps.
  Cristi Posoiu

(offtopic, for Vasile's monitoring: :-P )


Jesus Ruiz de Infante wrote:
> 
> [I started this thread on dbus-cplusplus-devel at lists.sourceforge.net but
> got no response,
> sorry for the crossposting. Hope it's OK]
> 
> It seems that in dbus-c++ there is a problem when the glib main loop must
> attend a dbus
> signal coming just after it called a dbus method. If that dbus signal
> handler tries to
> emit a sigc signal, the sigc signal is actually never emitted (or at
> least, a slot
> connected to it is never executed).
> [..................]
> 

-- 
View this message in context: http://www.nabble.com/dbus-c%2B%2B%3A-strange-behavior-when-using-gtkmm-tp19610503p20219377.html
Sent from the Free Desktop - dbus mailing list archive at Nabble.com.