GNOME Bugzilla – Bug 734624
ModemManager 1.0 crashed with SIGSEGV in interface_disabling_step (null pointer)
Last modified: 2014-10-29 22:25:43 UTC
See downstream Ubuntu bug report with stack traces: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1354514 Seems like it is some sort of null pointer. Maybe a race condition if disabling while disabling is already started?
Reporter says it happens frequently... I wouldn't mind to see it reproduced in ModemManager 1.2 or git master.
(In reply to comment #1) > Reporter says it happens frequently... I wouldn't mind to see it reproduced in > ModemManager 1.2 or git master. Note that I actually checked the code, but it's not very clear where the segfault could happen, that's why I'm asking for testing with a newer version... :)
Actually, after I got the trace myself, I looked at the code and also didn't understand where the segfault can happen. Unfortunately I am not able to test with newer version as I'm now 1000km away from the machine I got this bug on. If I'll be there again, I'll test and debug it. But feel free to close this bug for now.
In Ubuntu, it is possible to test modemmanager 1.2 either using a prerelease of Ubuntu 14.10, or this PPA: https://launchpad.net/~luc-willems/+archive/ubuntu/backport
(In reply to comment #3) > Actually, after I got the trace myself, I looked at the code and also didn't > understand where the segfault can happen. > > Unfortunately I am not able to test with newer version as I'm now 1000km away > from the machine I got this bug on. If I'll be there again, I'll test and debug > it. But feel free to close this bug for now. I'll mark it as resolved for now. If you get it reproduced, please open a new bug in the freedesktop bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product=ModemManager