Actually, as I tried to explain, what's going on is this; 1. After wakeup TB immediately tries to reconnect 2. TB calls nsHostResolver to resolve the server name which immediately gets an error because at this time, the network interface is not yet up 3. nsHostResolver treats this error (in fact, any error) as an unknown host, and puts that that "fact" in its cache 4. TB recognizes that the request is not initiated by the user and therefore suppresses any UI level error message
5. User comes around and clicks "Get Mail" 6. TB again calls nsHostResolver to resolve the server name, which returns "unknown host" from its cache 7. This time the request IS initiated by the user so an error message is shown 8. Not until the cache entry expires can the user successfully reconnect Having said that, it seems that this problem is gone in TB 10.0! /C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/584529 Title: Thunderbird complains there is no connection on resume from suspend, when there is a connection To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/584529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
