Description of problem: tried to connect to WWAN after wake-up after sleep via gnome-shell applet. Version-Release number of selected component: ModemManager-1.4.0-1.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/sbin/ModemManager crash_function: mm_base_bearer_get_path executable: /usr/sbin/ModemManager kernel: 3.17.0-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (7 frames) #0 mm_base_bearer_get_path at mm-base-bearer.c:911 #1 modem_create_bearer_finish at mbm/mm-broadband-modem-mbm.c:91 #2 create_bearer_ready at mm-iface-modem.c:491 #3 g_simple_async_result_complete at gsimpleasyncresult.c:763 #4 broadband_bearer_mbm_new_ready at mbm/mm-broadband-modem-mbm.c:111 #5 g_simple_async_result_complete at gsimpleasyncresult.c:763 #6 complete_in_idle_cb at gsimpleasyncresult.c:775
Created attachment 947253 [details] File: backtrace
Created attachment 947254 [details] File: cgroup
Created attachment 947255 [details] File: core_backtrace
Created attachment 947256 [details] File: dso_list
Created attachment 947257 [details] File: environ
Created attachment 947258 [details] File: exploitable
Created attachment 947259 [details] File: limits
Created attachment 947260 [details] File: maps
Created attachment 947261 [details] File: open_fds
Created attachment 947262 [details] File: proc_pid_status
Created attachment 947263 [details] File: var_log_messages
Another user experienced a similar problem: Error occurred after waking from sleep and trying to establish a wwan connection. After restart of ModemManager, connection could be established without a problem. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/sbin/ModemManager crash_function: mm_base_bearer_get_path executable: /usr/sbin/ModemManager kernel: 3.18.8-201.fc21.x86_64 package: ModemManager-1.4.4-2.fc21 reason: ModemManager killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.