Bug 460833

Summary: NetworkManager fails to start; restart crashes X
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: medium    
Version: rawhideCC: dcbw, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-08 14:32:24 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:

Description Horst H. von Brand 2008-09-01 18:28:45 UTC
Description of problem:
After the monster update, NM just doesn't start ("dead but pidfile exists"). Running "service NetworkManager restart" ends the Gnome session.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.11.svn4022.fc10.x86_64
initscripts-8.81-1.x86_64

How reproducible:
Always


Steps to Reproduce:
1. Start Gnome session. No NM running
2. su root -c "service NetworkManager restart"
3.
  
Actual results:
Gnome session ends abruptly.

Expected results:
Get WiFi connection...

Additional info:
intel 4695 WiFi; intel Mobile GM965/GL960 graphics card

Comment 1 Horst H. von Brand 2008-09-08 14:32:24 UTC
Now it works, but the versions reported above haven't. Some other update fixed this (kernel?).

Marking as WORKSFORME in want of some better description of the "solution".