Description of problem: Was grsync in files from one tera station to another Version-Release number of selected component: NetworkManager-0.9.9.0-33.git20131003.fc20 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: _g_log_abort executable: /usr/sbin/NetworkManager kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (4 frames) #2 _g_log_abort at gmessages.c:255 #5 manager_new_ready at modem-manager/nm-modem-manager.c:562 #6 g_task_return_now at gtask.c:1108 #7 complete_in_idle_cb at gtask.c:1117
Created attachment 886676 [details] File: backtrace
Created attachment 886677 [details] File: cgroup
Created attachment 886678 [details] File: core_backtrace
Created attachment 886679 [details] File: dso_list
Created attachment 886680 [details] File: environ
Created attachment 886681 [details] File: limits
Created attachment 886682 [details] File: maps
Created attachment 886683 [details] File: open_fds
Created attachment 886684 [details] File: proc_pid_status
Created attachment 886685 [details] File: var_log_messages
NetworkManager crashes due to a failing assertion: Apr 15 18:31:19 fd20.local NetworkManager[600]: ERROR:modem-manager/nm-modem-manager.c:562:manager_new_ready: assertion failed: (!self->priv->modem_manager_1) But there might be a ModemManager crash before that caused the NM crash: Apr 15 18:26:54 fd20.local dbus[632]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.7" (uid=0 pid=600 comm="/usr/sbin/NetworkManager --no-daemon ") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.ModemManager1" (uid=0 pid=3116 comm="/usr/sbin/ModemManager ") Apr 15 18:26:54 fd20.local NetworkManager[600]: <info> ModemManager disappeared from bus Do you see a ModemManager crash? Are you able to reproduce the problem at all? I can see it happened twice in the logs. If you can still see the problem, it would be great if you could follow these instructions and get debug logs: https://wiki.gnome.org/Projects/NetworkManager/Debugging#Debugging_NetworkManager_0.8_and_0.9_3G_connections
I will try this when it craches again or can I run it now for you. I have not seen any ModemManager crash.
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.