Bug 863554 - NetworkManager-0.9.7.0-2.git20121004.fc18.i686 segfault at ffffffff
Summary: NetworkManager-0.9.7.0-2.git20121004.fc18.i686 segfault at ffffffff
Keywords:
Status: CLOSED DUPLICATE of bug 865009
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-05 19:03 UTC by Sergei LITVINENKO
Modified: 2012-10-31 13:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-31 13:08:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Sergei LITVINENKO 2012-10-05 19:03:59 UTC 
Description of problem:
[ 4620.014189] NetworkManager[3194]: segfault at ffffffff ip 49a41ce0 sp bfb8e120 error 4 in libglib-2.0.so.0.3400.0[499de000+129000]


Version-Release number of selected component (if applicable):
NetworkManager-0.9.7.0-2.git20121004.fc18.i686
NetworkManager-glib-0.9.7.0-2.git20121004.fc18.i686

How reproducible:
100%

Steps to Reproduce:
1. Update NetworkManager to 0.9.7.0-2.git20121004
2.
3.
  
Actual results:
[ 4620.014189] NetworkManager[3194]: segfault at ffffffff ip 49a41ce0 sp bfb8e120 error 4 in libglib-2.0.so.0.3400.0[499de000+129000]

Expected results:
NetworkManager work without faults.

Additional info:
NetworkManager-0.9.7.0-1.git20120820.fc18.i686, NetworkManager-glib-0.9.7.0-1.git20120820.fc18.i686 are not affected
Comment 1 Jirka Klimes 2012-10-16 07:06:25 UTC 
Do you happen to have a stacktrace from the crash? Possibly from the ABRT?
What are the steps to reproduce?

Could you install NM from https://bugzilla.redhat.com/show_bug.cgi?id=865009#c15 and see if it fixes the crash? And please add a karma if it works.
Comment 2 Jirka Klimes 2012-10-31 13:08:10 UTC 

*** This bug has been marked as a duplicate of bug 865009 ***
Note You need to log in before you can comment on or make changes to this bug.