Ubuntu
network-manager package

Network manager falsly reports "No network connection" after hibernation on Tribe-2

Bug #122917 reported by Marc Tardif
4
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Fix Released
Medium
Alexander Sack
Ubuntu ubuntu-7.10-beta

Bug Description

After resuming from hibernation on Tribe-2, the network manager reports "No network connection". However, ifconfig -a shows that the eth0 network interface is up and an IP address has been assigned to it. Even pinging to the outside works.

This problem has been reproduced on a few laptops and desktops, so it seems to be generalized.

Tags: hwct
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Alexander, could you have a look at this? Is it a known duplicate (seems to happen on several machines)? Does it have the information you need?

Changed in network-manager:
assignee: nobody → asac
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Marc, are you still seeing this in later tribes?

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

We need an update on this bug. Is this still an issue post-tribe5?

Changed in network-manager:
status: Confirmed → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

from what i can tell this should be fixed now, because we don't try to deal with interfaces managed by ifupdown anymore.

Changed in network-manager:
status: Incomplete → Fix Released
Revision history for this message
Marc Tardif (cr3) wrote :

I have tested hibernation on several laptops running beta and the network manager has behaved properly each time. This bug could be closed as far as I'm concerned.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.