[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2009-02-08 Thread Joel Parker
More info: I'm using an rt2500pci.

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2009-02-08 Thread Joel Parker
This affects me. Here's my syslog after resume:

Feb  8 12:17:01 family-laptop NetworkManager:   Waking up... 
Feb  8 12:17:01 family-laptop NetworkManager:   (eth0): now managed 
Feb  8 12:17:01 family-laptop NetworkManager:   (eth0): device state 
change: 1 -> 2 
Feb  8 12:17:01 family-laptop NetworkManager:   (eth0): bringing up 
device. 
Feb  8 12:17:01 family-laptop kernel: [ 1888.614760] ADDRCONF(NETDEV_UP): eth0: 
link is not ready
Feb  8 12:17:01 family-laptop NetworkManager:   (eth0): preparing device. 
Feb  8 12:17:01 family-laptop NetworkManager:   (eth0): deactivating 
device (reason: 2). 
Feb  8 12:17:01 family-laptop NetworkManager:   Unmanaged Device found; 
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Feb  8 12:17:01 family-laptop NetworkManager:   Unmanaged Device found; 
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) 
Feb  8 12:17:01 family-laptop NetworkManager:   (wlan0): now managed 
Feb  8 12:17:01 family-laptop NetworkManager:   (wlan0): device state 
change: 1 -> 2 
Feb  8 12:17:01 family-laptop NetworkManager:   (wlan0): bringing up 
device. 
Feb  8 12:17:01 family-laptop NetworkManager:   nm_device_hw_bring_up(): 
(wlan0): device not up after timeout! 
Feb  8 12:17:01 family-laptop NetworkManager:   (wlan0): deactivating 
device (reason: 2). 
Feb  8 12:17:01 family-laptop NetworkManager:   (wlan0): device state 
change: 2 -> 3 
Feb  8 12:17:01 family-laptop NetworkManager:   (wlan0): supplicant 
interface state change: 1 -> 2. 

Notice the WARN about wlan0.

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2009-01-02 Thread Collin Stocks
I concur. I had to add a few lines to my /etc/network/interfaces file to
make my wireless connection work consistently, thus avoiding using a
network manager entirely.

A minus to this is that if I want to connect to a friend's wireless
network or a hotspot, I have to comment out those lines and restart the
corresponding service (this has not happened recently, and I forget the
name of the service).

A plus is that I can use the internet before starting Xorg.

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2009-01-02 Thread DaveAbrahams
This bug is essentially back for Intrepid.  See also #222835

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2008-03-31 Thread Basilio Kublik
Hi there
Thanks for your time and feedback, I'm closing this report due your comment 
about not being an issue anymore. Thanks again for taking the time to report 
and comment this bug, and help to make Ubuntu better, please don't hesitate to 
report any future bugs you might find.

** Changed in: network-manager (Ubuntu)
 Assignee: Basilio Kublik (sourcercito) => (unassigned)
   Status: Incomplete => Fix Released

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2008-03-29 Thread Collin Stocks
That's great: somebody probably fixed it for the LTS version of Ubuntu.
Looking forward to 2008/04/24!

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2008-03-28 Thread Rocko
I've been trying to reproduce it in Hardy for the last ten days now,
including leaving it suspended overnight on a few occasions, but so far
I haven't seen it yet with either the wireless or wired connection.

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2008-03-20 Thread Collin Stocks
Well, you see... I don't use network-manager anymore. Instead I use Wicd
1.4.2 (http://wicd.sourceforge.net). If I get a chance, I'll try to
reproduce it from the live-cd dev release. One of the biggest problems
with this bug is that it is not always a problem: sometimes the wireless
stops working, sometimes not when I put my computer to sleep.

May I suggest that Wicd be the default network manager instead of
network-manager? It really has many more features and also fewer bugs.
It is incredibly easy to use, even if you do not want to use any of the
extra features it offers.

I'm really glad to see that this bug is getting some attention, though.

-- Collin

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2008-03-20 Thread Basilio Kublik
Hi there
do you still experience this issue with the current version of the 
application?, could you please try to reproduce this using the  live 
environment of the Desktop CD of the development release - Hardy Heron.

Thanks in advance

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low
 Assignee: (unassigned) => Basilio Kublik (sourcercito)
   Status: New => Incomplete

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 177053] Re: NetworkManager does not successfully reconnect to a wireless network after resume from suspend to ram.

2008-03-18 Thread Rocko
I can confirm this on Gutsy using both a wireless and wired network, but
it seems to also be related to how long the PC is offline - if it is
only suspended for a few seconds, it reconnects OK on resume.

In Gutsy, I can fix the problem by using the nm-applet's 'disable
networking' and 'enable networking' feature.

I haven't been able to reproduce it yet on Hardy (but I've only left it
suspended for up to ten minutes or so). one observation is that hardy
re-establishes the address much faster than gutsy - gutsy will take five
or more seconds, whereas in hardy it is usually connected in a second or
so.

-- 
NetworkManager does not successfully reconnect to a wireless network after 
resume from suspend to ram.
https://bugs.launchpad.net/bugs/177053
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs