Bug 623444 - [abrt] NetworkManager-1:0.8.1-2.el6: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV)
[abrt] NetworkManager-1:0.8.1-2.el6: Process /usr/sbin/NetworkManager was kil...
Status: CLOSED INSUFFICIENT_DATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager (Show other bugs)
6.0
x86_64 Linux
low Severity medium
: rc
: ---
Assigned To: Dan Williams
desktop-bugs@redhat.com
abrt_hash:75a68a6058a192aa967c3bd8c66...
: RHELNAK
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-11 15:48 EDT by Zack Cerza
Modified: 2010-08-11 20:29 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-08-11 20:29:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (2.05 KB, text/plain)
2010-08-11 15:48 EDT, Zack Cerza
no flags Details

  None (edit)
Description Zack Cerza 2010-08-11 15:48:19 EDT
abrt version: 1.1.12
architecture: x86_64
Attached file: backtrace
cmdline: NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid
component: NetworkManager
executable: /usr/sbin/NetworkManager
kernel: 2.6.32-44.el6.x86_64
package: NetworkManager-1:0.8.1-2.el6
rating: 0
reason: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
time: 1278627615
uid: 0

How to reproduce
-----
1. 
2. 
3.
Comment 1 Zack Cerza 2010-08-11 15:48:21 EDT
Created attachment 438274 [details]
File: backtrace
Comment 2 Zack Cerza 2010-08-11 15:50:28 EDT
Sorry if this is useless; I just noticed that abrt found this crash a while back.
Comment 4 RHEL Product and Program Management 2010-08-11 16:18:47 EDT
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 5 Dan Williams 2010-08-11 20:29:03 EDT
Yeah, kinda useless :(  Lets see if the others have more info.

Note You need to log in before you can comment on or make changes to this bug.