Bug 689289 – modem-manager crashed with SIGSEGV

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 689289 - modem-manager crashed with SIGSEGV


Summary:	modem-manager crashed with SIGSEGV


Status:	RESOLVED FIXED

Product:	NetworkManager
Classification:	Platform
Component:	ModemManager
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	NetworkManager maintainer(s)
QA Contact:	NetworkManager maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-11-29 15:40 UTC by Nobuto MURATA
Modified:	2012-11-30 15:09 UTC

See Also:	https://launchpad.net/bugs/1083659
GNOME target:	---
GNOME version:	---

Attachments
debug log of modem-manager (58.91 KB, text/x-log) 2012-11-29 15:44 UTC, Nobuto MURATA	Details
backtrace of modem-manager (10.67 KB, text/x-log) 2012-11-29 15:46 UTC, Nobuto MURATA	Details
valgrind log (9.42 KB, text/x-log) 2012-11-29 15:47 UTC, Nobuto MURATA	Details
valgrind with -dbg package (9.27 KB, text/plain) 2012-11-29 15:59 UTC, Nobuto MURATA	Details
log when crash happens (13.46 KB, text/plain) 2012-11-29 16:16 UTC, Nobuto MURATA	Details

Description Nobuto MURATA 2012-11-29 15:40:59 UTC

Forwarded from:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1083659

modemmanager:
  Installed: 0.6.0.0.really+git201211281825.1195-0~pkg164~raring1
  (daily build of 0.6 branch)

DistroRelease: Ubuntu 13.04

How to reproduce:
 1. attach au/huawei DATA07 USB modem.
 2. click "Enable Mobile Broadband" in network-manager indicator
 3. create "au(KDDI) connection" under Japan region with the wizard, then connect it.

Comment 1 Nobuto MURATA 2012-11-29 15:44:50 UTC

Created attachment 230205 [details]
debug log of modem-manager

Adding --log-level=DEBUG to modem-manager can avoid segfault and keep modem-manager running.

Comment 2 Nobuto MURATA 2012-11-29 15:46:12 UTC

Created attachment 230206 [details]
backtrace of modem-manager

Comment 3 Nobuto MURATA 2012-11-29 15:47:19 UTC

Created attachment 230207 [details]
valgrind log

G_SLICE=always-malloc valgrind --log-file=valgrind.out /usr/sbin/modem-manager

Comment 4 Nobuto MURATA 2012-11-29 15:59:00 UTC

Created attachment 230208 [details]
valgrind with -dbg package

Please kindly disregard my last valgrind log. That was without -dbg package.
This is a new valgrind with modemmanager-dbg package.

Comment 5 Nobuto MURATA 2012-11-29 16:16:15 UTC

Created attachment 230209 [details]
log when crash happens

Comment 6 Aleksander Morgado 2012-11-30 12:40:01 UTC

Thanks; specially for the second valgrind log with -dbg installed :-)

I think this should be enough to get the issue analyzed.

Comment 7 Aleksander Morgado 2012-11-30 15:09:04 UTC

I fixed the memory errors, ended up being some double free of a GError. I'll set the bug as fixed, please reopen if the crash still happens.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.