Solved in my case! Problem is diagnosed: dig AAAA google.com is timing out dig google.com works
Opera apperently waits for IPv6 lookup before it continues with IPv4 lookup Setting Network connections IPv4 settings to method: `Automatic (DHCP) addresses` only and putting the (ISP) DNS address manually works. Now dig AAAA google.com gives an answer immediately (ipv4) instead of timing out. Opera is working as speedy as ever. So the new firmware of the modem somehow changed DNS settings with the results that IPv6 requests are timing out. Probably Firefox does IPv6 and IPv4 requests synchronously and goes with the first result, while Opera starts with IPv6 and follows with IPv4. Note: The error messages with opera -debugdns are still there. But the delay is gone. dns: Resolving 'xml.opera.com' dns: Thread created dns: Trying IPv6 lookup for host 'xml.opera.com'... dns: gethostbyname failed with return value 22 (Invalid argument). hostent pointer:(nil) dns: Trying IPv4 lookup for host 'xml.opera.com'... dns: gethostbyname succeeded -- Opera browser running very slow https://bugs.launchpad.net/bugs/174209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
