Le mardi 29 mars 2011 à 20:54 +0200, Simon Paillard a écrit :
And that is actually #578019.
https://bug-38263-attachments.webkit.org/attachment.cgi?id=54769 (attached
again) works and saves my laptop battery and name server.
Thanks a lot for the analysis and digging, it’s much appreciated.
forwarded 578019 https://bugs.webkit.org/show_bug.cgi?id=38263
tag 578019 +patch
thanks
On Sat, Mar 26, 2011 at 01:56:17PM +0100, Simon Paillard wrote:
On Sun, Mar 20, 2011 at 08:23:54PM +0100, Simon Paillard wrote:
On Sun, Mar 20, 2011 at 03:44:28PM -0300, Gustavo Noronha Silva wrote:
On
On Sun, Mar 20, 2011 at 08:23:54PM +0100, Simon Paillard wrote:
On Sun, Mar 20, 2011 at 03:44:28PM -0300, Gustavo Noronha Silva wrote:
On Sat, 2011-03-19 at 01:41 +0100, Simon Paillard wrote:
[..]
- unless a DNS request fails for a host, then further requests for that
uri
(example
On Sun, 2011-03-20 at 20:23 +0100, Simon Paillard wrote:
- Load any page (e.g. www.debian.org or even a 404, like
http://people.debian.org/~spaillard/test.html).
- Run wireshark/tshark and follow DNS requests:
(dns.flags.response == 0) (dns.qry.type == 0x0001)
- Force a reload of the
On Sat, 2011-03-19 at 01:41 +0100, Simon Paillard wrote:
This is likely a problem in libsoup, or on GResolver. I'll ask Dan
Winship.
Any luck?
No, sorry, I dropped the ball on this.
(Re-Ping)
As I met this again in the context of Debian WWW mirrors (one mirror removed
from the DNS
On Sun, Mar 20, 2011 at 03:44:28PM -0300, Gustavo Noronha Silva wrote:
On Sat, 2011-03-19 at 01:41 +0100, Simon Paillard wrote:
This is likely a problem in libsoup, or on GResolver. I'll ask Dan
Winship.
Any luck?
No, sorry, I dropped the ball on this.
As I met this again in
Hi,
On Mon, Mar 29, 2010 at 10:20:38AM +0200, Julien Cristau wrote:
On Mon, Mar 8, 2010 at 09:58:18 -0300, Gustavo Noronha Silva wrote:
On Sat, 2010-03-06 at 14:03 +0100, Julien Cristau wrote:
I seem to be seeing this too. Trying to connect to www.google.com right
now results in a
On Mon, Mar 8, 2010 at 09:58:18 -0300, Gustavo Noronha Silva wrote:
On Sat, 2010-03-06 at 14:03 +0100, Julien Cristau wrote:
I seem to be seeing this too. Trying to connect to www.google.com right
now results in a connect() to 2a00:1450:8007::93, which fails with
ENETUNREACH, and
On Sat, 2010-03-06 at 14:03 +0100, Julien Cristau wrote:
I seem to be seeing this too. Trying to connect to www.google.com right
now results in a connect() to 2a00:1450:8007::93, which fails with
ENETUNREACH, and epiphany immediately returns an error page instead of
trying one of the other
tag 558125 - moreinfo unreproducible
kthxbye
On Sun, Feb 28, 2010 at 15:59:03 +0100, Apelete Seketeli wrote:
Hi,
Are you still experiencing this bug ? Please try again with a new
epiphany release and see if it has been solved.
I seem to be seeing this too. Trying to connect to
Hi,
Are you still experiencing this bug ? Please try again with a new
epiphany release and see if it has been solved.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: epiphany-browser
Version: 2.29.1-2
Severity: important
epiphany caches the decision to use ipv4 or ipv6 even over network
topology changes. My notebook regulary switches between networks with
ipv6 connection and without. epiphany always uses the cached decision
and displays a failure if
12 matches
Mail list logo
