Re: Network Manager crashes after a configuration is added and a connection is attempted.

[Chris Hessing <chsoftworks gmail com>]

On 7/2/2014 12:00 PM, Thomas Haller wrote:
> On Wed, 2014-07-02 at 09:41 -0600, Chris Hessing wrote:
> > On 7/2/2014 7:43 AM, Dan Williams wrote:
> > > On Wed, 2014-07-02 at 11:26 +0200, Thomas Haller wrote:
> > > > 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.
> > > Patch looks right to me.  It's likely unnoticed because these days most
> > > certificates use the "path" scheme instead of the blob scheme, and thus
> > > this code doesn't get triggered.
> > >
> > > > 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.
> > > We should look at this a bit more; I ran into this when doing the
> > > wwan-ipv6 stuff and it did cause a crash that was fixed by using GArray
> > > instead of GByteArray.  But we've been using GByteArray for a really
> > > long time, so I'm sure that at some point in the past this worked.
> > >
> > > Dan
> > Hi guys,
> >
> > Thanks for the patch and the info.   I'll look in to changing my code to
> > use the path method instead of the blob method.   I know I used the path
> > method in the past, but there was some issue I ran in to that made me
> > move to the blob method.    As I move back toward the path method I'll
> > update you guys if I happen to trigger or remember why I went that way.
> >
> >
> > Thanks again for the info!
>
> Hey,
>
> I opened Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=1115538
> for this. The next version NetworkManager-0.9.9.0-41.git20131003.fc20
> will bring a fix.
>
> @Chris, you can also install the new package manually, before it is
> stable. Get the packages from
> https://admin.fedoraproject.org/updates/NetworkManager-0.9.9.0-41.git20131003.fc20 .
>
> I was not so much interested in why you happened to change the method
> path vs. blob. Instead I would be very much interested whether the
> problem is actually fixed. Thank you!! ;-)
>
> ciao,
> Thomas

Nope, the patch didn't seem to fix it.  I am seeing the same log 
output.   I also double checked the Network Manager -V output, and it is 
"0.9.9.0-41.git20131003.fc20" which appears to be the version you wanted 
me to test.

What other information can I provide that might help?

FWIW, I mentioned the stuff about the path version because that is what 
I used to use, but something made me move away from it.   That something 
was either a restriction in the OS, or a different bug in Network 
Manager.  If it was a bug, I figured you would be interested.