Bug 1088045

Summary: [abrt] NetworkManager: _g_log_abort(): NetworkManager killed by SIGABRT
Product: [Fedora] Fedora Reporter: midi-man
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dcbw, jklimes, midi-man
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fbbe75930374e460b6349be4f0d391b488c4e91c
Whiteboard: abrt_hash:360799a07f2414e257ea21593f5d6f142f65bcb4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:07:08 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 midi-man 2014-04-15 22:36:57 UTC
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

Comment 1 midi-man 2014-04-15 22:37:01 UTC
Created attachment 886676 [details]
File: backtrace

Comment 2 midi-man 2014-04-15 22:37:02 UTC
Created attachment 886677 [details]
File: cgroup

Comment 3 midi-man 2014-04-15 22:37:04 UTC
Created attachment 886678 [details]
File: core_backtrace

Comment 4 midi-man 2014-04-15 22:37:06 UTC
Created attachment 886679 [details]
File: dso_list

Comment 5 midi-man 2014-04-15 22:37:07 UTC
Created attachment 886680 [details]
File: environ

Comment 6 midi-man 2014-04-15 22:37:09 UTC
Created attachment 886681 [details]
File: limits

Comment 7 midi-man 2014-04-15 22:37:11 UTC
Created attachment 886682 [details]
File: maps

Comment 8 midi-man 2014-04-15 22:37:12 UTC
Created attachment 886683 [details]
File: open_fds

Comment 9 midi-man 2014-04-15 22:37:14 UTC
Created attachment 886684 [details]
File: proc_pid_status

Comment 10 midi-man 2014-04-15 22:37:16 UTC
Created attachment 886685 [details]
File: var_log_messages

Comment 11 Jirka Klimes 2014-04-16 08:07:54 UTC
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

Comment 12 midi-man 2014-06-10 00:52:22 UTC
I will try this when it craches again or can I run it now for you. 
I have not seen any ModemManager crash.

Comment 13 Fedora End Of Life 2015-05-29 11:34:57 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 14 Fedora End Of Life 2015-06-29 20:07:08 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.