Bug 586127 - [abrt] crash in NetworkManager-gnome-1:0.8.0-6.git20100408.fc12: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in NetworkManager-gnome-1:0.8.0-6.git20100408.fc12: Process /usr...
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:199c9f1bc5ae5e7d715847b732b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 20:45 UTC by Sean
Modified: 2010-06-28 22:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-28 22:27:16 UTC
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 (13.42 KB, text/plain)
2010-04-26 20:45 UTC, Sean 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Sean 2010-04-26 20:45:19 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nm-connection-editor
component: NetworkManager
executable: /usr/bin/nm-connection-editor
global_uuid: 199c9f1bc5ae5e7d715847b732b68e6459f4b425
kernel: 2.6.32.11-99.fc12.x86_64
package: NetworkManager-gnome-1:0.8.0-6.git20100408.fc12
rating: 4
reason: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Tried to change my default MTU setting using the networkmanager GUI
2.
3.
Comment 1 Sean 2010-04-26 20:45:24 UTC 
Created attachment 409288 [details]
File: backtrace
Comment 2 Dan Williams 2010-06-28 22:27:16 UTC 
Not enough debuginfo to figure out where the error is actually coming from, but this is likely a duplicate of bug 572466.
Note You need to log in before you can comment on or make changes to this bug.