Bug 191272 - Network Manager forgets that wireless exists after hibernation
Summary: Network Manager forgets that wireless exists after hibernation
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 5
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-10 12:56 UTC by Jesse Harris
Modified: 2008-03-28 16:21 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2008-03-28 16:21:57 UTC


Attachments (Terms of Use)

Description Jesse Harris 2006-05-10 12:56:21 UTC
Description of problem:

Using the ndiswrapper module, after a hibernate Network Manager does not
automatically connect to the wireless network.
Upon closer inspection (Clicking on NetworkManager) Wireless Network is no
longer available from the menu.
Manually restarted NetworkManager temporarily resolves the issue until next
hibernate.


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

0.6.0
How reproducible:

Consistenly

Steps to Reproduce:


1.  Hibernate FC5
2.  Try to connect to wireless network
  
Actual results:

Wireless is not even an Heading in NetworkManager applet.

Expected results:

Wireless should be detected and automatically connect

Additional info:
Could this be an ndiswrapper issue?

Comment 1 Jesse Harris 2006-05-10 12:57:47 UTC
(In reply to comment #0)
> Description of problem:
> 
> Using the ndiswrapper module, after a hibernate Network Manager does not
> automatically connect to the wireless network.
> Upon closer inspection (Clicking on NetworkManager) Wireless Network is no
> longer available from the menu.
> Manually restarted NetworkManager temporarily resolves the issue until next
> hibernate.
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 0.6.0
> How reproducible:
> 
> Consistenly
> 
> Steps to Reproduce:
> 
> 
> 1.  Hibernate FC5
> 2.  Try to connect to wireless network
>   
> Actual results:
> 
> Wireless is not even an Heading in NetworkManager applet.
> 
> Expected results:
> 
> Wireless should be detected and automatically connect
> 
> Additional info:
> Could this be an ndiswrapper issue?


One other note:  NetworkManager does not have the same problem when suspend is used.

Comment 2 Dan Williams 2008-02-12 03:11:34 UTC
Is this still an issue with recent ndiswrapper and latest FC5 kernels, or later
Fedora versions?

Comment 3 petrosyan 2008-03-28 16:21:57 UTC
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.


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