https://bugzilla.novell.com/show_bug.cgi?id=810573
https://bugzilla.novell.com/show_bug.cgi?id=810573#c2
Roland Wirth changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|DUPLICATE |
--- Comment #2 from Roland Wirth 2013-03-27 21:55:04 UTC ---
I think this is a different bug. The NetworkManager interface seems to have
changed so that instead of a StateChange signal a StateChanged signal is now
emitted on the DBus (according to the NM documentation, the StateChange signal
is marked deprecated in the 0.7 and vanished from the 0.9 DBus interface).
However, ypbind only reacts on the old signal name, not the new one: ypbind
reacts on a manually sent StateChange using the enum value for
NM_STATE_CONNECTED_GLOBAL (70) as argument. This enum value not being
recognized caused #698030. The new signal name is ignored, as can be seen from
the log.
Looking at the code of the ypbind DBus client, I think a fix of this bug is
easy:
Directly before the NmState enum in src/ypbind_dbus_nm.c is the define
#define NM_DBUS_VPN_SIGNAL_STATE_CHANGE "StateChange"
changing this to "StateChanged" shold fix the problem (hopefully).
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
