On Tue, 2014-07-01 at 16:52 -0600, Chris Hessing wrote:
Hi all,
I thought it might be an issue with the variant type I was sending in to some configuration setting that was later being parsed when I requested the connection become active. However, after going through my code to generate the settings, they all match what is documented here : https://developer.gnome.org/NetworkManager/0.9/ref-settings.html One interesting tidbit is that after Network Manager crashes, and is restarted by the system, the connection comes up fine and seems to work from then on. At this point, short of cracking open the Network Manager code, I am running out of ideas as to what it could be. Perhaps someone that understands the Network Manager code can shed some light on what might be going on?
Hi Chris, This looks like a bug in NetworkManager. The attached patch should fix it. I made a scratch build with this patch for Fedora 20: http://koji.fedoraproject.org/koji/taskinfo?taskID=7098885 could you test it please? Note, that this is broken for a long time, so although the patch is for NM master, the bug is similarly present on Fedora 20 as well as the older nm-0-9-8 branch. Interestingly, http://dbus.freedesktop.org/doc/dbus-glib/dbus-glib-Specializable-GType-System.html#DBUS-TYPE-G-UCHAR-ARRAY:CAPS says that we cannot pass a GByteArray instead of the expected GArray of uchar. But I think the comment is just wrong, because a GByteArray *is* actually a GArray. Thomas
Attachment:
0001-supplicant-fix-crash-passing-invalid-parameter-to-Ad.patch
Description: Text Data
Attachment:
signature.asc
Description: This is a digitally signed message part