Description of problem: I created a "new broadband connection" and attempted to use it, after that modem manager crashed. My device is: [112616.965217] usb 4-2: new full-speed USB device number 5 using uhci_hcd [112617.114258] usb 4-2: New USB device found, idVendor=1199, idProduct=6812 [112617.114272] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [112617.114279] usb 4-2: Product: Mini Card [112617.114286] usb 4-2: Manufacturer: Sierra Wireless, Incorporated [112617.121370] sierra 4-2:1.0: Sierra USB modem converter detected [112617.123438] usb 4-2: Sierra USB modem converter now attached to ttyUSB1 [112617.123514] usb 4-2: Sierra USB modem converter now attached to ttyUSB2 [112617.123582] usb 4-2: Sierra USB modem converter now attached to ttyUSB3 This worked without problems on Fedora 19 and older versions. Version-Release number of selected component: ModemManager-1.1.0-2.git20130913.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/sbin/ModemManager crash_function: mm_bearer_get_path executable: /usr/sbin/ModemManager kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (7 frames) #0 mm_bearer_get_path at mm-bearer.c:907 #1 modem_create_bearer_finish at sierra/mm-broadband-modem-sierra.c:1097 #2 create_bearer_ready at mm-iface-modem.c:323 #3 g_simple_async_result_complete at gsimpleasyncresult.c:777 #4 broadband_bearer_sierra_new_ready at sierra/mm-broadband-modem-sierra.c:1117 #5 g_simple_async_result_complete at gsimpleasyncresult.c:777 #6 complete_in_idle_cb at gsimpleasyncresult.c:789
Created attachment 887351 [details] File: backtrace
Created attachment 887352 [details] File: cgroup
Created attachment 887353 [details] File: core_backtrace
Created attachment 887354 [details] File: dso_list
Created attachment 887355 [details] File: environ
Created attachment 887356 [details] File: exploitable
Created attachment 887357 [details] File: limits
Created attachment 887358 [details] File: maps
Created attachment 887359 [details] File: open_fds
Created attachment 887360 [details] File: proc_pid_status
Created attachment 887361 [details] File: var_log_messages
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.
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.