Bug 199737 - NetworkManager crashes after VPN connection fails
Summary: NetworkManager crashes after VPN connection fails
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 5
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2006-07-21 17:48 UTC by Zack Cerza
Modified: 2008-05-06 16:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-06 16:09:00 UTC
Type: ---

Attachments (Terms of Use)
/var/log/messages snippet, with secrets x-ed out (2.62 KB, text/plain)
2006-07-21 17:48 UTC, Zack Cerza
no flags Details

Description Zack Cerza 2006-07-21 17:48:15 UTC
Description of problem:
I tried to connect to my VPN with NetworkManager, which has never actually
failed me yet. Well, this time it failed. And the NetworkManager daemon died.

Version-Release number of selected component (if applicable):

Comment 1 Zack Cerza 2006-07-21 17:48:15 UTC
Created attachment 132826 [details]
/var/log/messages snippet, with secrets x-ed out

Comment 2 Zack Cerza 2006-08-18 18:19:15 UTC
Still happens every time I boot up. The first VPN connectoin attempt takes the
NetworkManager daemon down, and I have to restart it manually, as root.


Comment 3 Tim Reilly 2006-10-03 17:02:44 UTC
I get this problem, too, and have been for a while. 

Comment 4 Bug Zapper 2008-04-04 03:21:25 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 5 Bug Zapper 2008-05-06 16:08:58 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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