Bug 1052170

Summary: [abrt] ModemManager: _g_log_abort(): ModemManager killed by SIGABRT
Product: [Fedora] Fedora Reporter: tuxor <acc-bugz-redhat>
Component: ModemManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: afarrag, blachniom, dcbw, tobias.weise
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/358e6728fb412b4720fb7d0d1c7b113b917eff88
Whiteboard: abrt_hash:f537ced4280f8723ad2d27f7ee11c617c5d7dd81
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:24:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description tuxor 2014-01-13 12:43:28 UTC
Description of problem:
1. Try establishing an UMTS connection in NetzworkManager (using the on/off switch for the wwan card in gnome-settings)
2. The switch that turns the wwan card on/off in NetworkManager switches to "on" for a moment than immediately switches back to "off" and I see "connection is being established..."
3. I click again on the switch (because it's "off" even though it should be "on" now) right away
4. Again, the switch shows "on" for a moment and immediately jumps back to "off". But this time, the wwan card appears to be switched off in gnome-settings. So I click on the switch again.
5. This time, the switch shows "on" and stays like this, but the status never exceeds the "connection is being established..." state.
6. After a few seconds, ABRT tells me that ModemManager crashed.

Version-Release number of selected component:
ModemManager-1.1.0-2.git20130913.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/sbin/ModemManager
crash_function: _g_log_abort
executable:     /usr/sbin/ModemManager
kernel:         3.12.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (8 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 activate at mbm/mm-broadband-bearer-mbm.c:337
 #6 authenticate_ready at mbm/mm-broadband-bearer-mbm.c:372
 #7 g_simple_async_result_complete at gsimpleasyncresult.c:777
 #8 at_command_parse_response at mm-base-modem-at.c:499
 #9 handle_response at mm-at-serial-port.c:168
 #10 mm_serial_port_got_response at mm-serial-port.c:589
 #11 data_available at mm-serial-port.c:803

Comment 1 tuxor 2014-01-13 12:43:34 UTC
Created attachment 849314 [details]
File: backtrace

Comment 2 tuxor 2014-01-13 12:43:37 UTC
Created attachment 849315 [details]
File: cgroup

Comment 3 tuxor 2014-01-13 12:43:44 UTC
Created attachment 849316 [details]
File: core_backtrace

Comment 4 tuxor 2014-01-13 12:43:46 UTC
Created attachment 849317 [details]
File: dso_list

Comment 5 tuxor 2014-01-13 12:43:49 UTC
Created attachment 849318 [details]
File: environ

Comment 6 tuxor 2014-01-13 12:43:51 UTC
Created attachment 849319 [details]
File: limits

Comment 7 tuxor 2014-01-13 12:43:53 UTC
Created attachment 849320 [details]
File: maps

Comment 8 tuxor 2014-01-13 12:43:56 UTC
Created attachment 849321 [details]
File: open_fds

Comment 9 tuxor 2014-01-13 12:43:58 UTC
Created attachment 849322 [details]
File: proc_pid_status

Comment 10 tuxor 2014-01-13 12:44:00 UTC
Created attachment 849323 [details]
File: var_log_messages

Comment 11 blachniom 2014-04-02 18:42:21 UTC
Another user experienced a similar problem:

Tried to establish a WWAN connection using the nm-applet. The connection seemed to succeed (circling nm icon) and then it just reset to disconnected.
After that I retried the connection without any problems. No reboots necessary.

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/sbin/ModemManager
crash_function: _g_log_abort
executable:     /usr/sbin/ModemManager
kernel:         3.13.7-200.fc20.x86_64
package:        ModemManager-1.1.0-2.git20130913.fc20
reason:         ModemManager killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 12 Dan Williams 2014-04-04 18:35:39 UTC
Might be fixed by d818d9fe06 (bearer: consolidate unsolicited connection status reports) upstream.  This bug is specific to Ericsson MBM WWAN devices.

Comment 13 blachniom 2014-04-04 18:44:30 UTC
Thanks, I will try that, although my device is: "413c:8147 Dell Computer Corp. F3507g Mobile Broadband Module".

Comment 14 tobias.weise 2014-07-28 08:53:29 UTC
Another user experienced a similar problem:

After waking up from sleep to disk, trying to activate wan (mobile broadband) via gnome applet crashes Modem Manager. Connecting to mobile broadband works after crash.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/sbin/ModemManager
crash_function: _g_log_abort
executable:     /usr/sbin/ModemManager
kernel:         3.15.6-200.fc20.x86_64
package:        ModemManager-1.1.0-2.git20130913.fc20
reason:         ModemManager killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 15 Fedora End Of Life 2015-05-29 10:28:36 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2015-06-29 14:24:46 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.