Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Matthieu Herrb
On Sun, Feb 11, 2018 at 02:50:30PM +0100, Martin Pieuchot wrote: > On 11/02/18(Sun) 12:37, Matthieu Herrb wrote: > > Hi, > > > > I ugraded my laptop from sources to -current yesterday. Since then > > firefox stops resolving host names after a dozen of minutes or so. > > What do you mean with

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Matthieu Herrb
On Sun, Feb 11, 2018 at 04:51:47PM +0100, Landry Breuil wrote: > On Sun, Feb 11, 2018 at 03:13:07PM +0100, Matthieu Herrb wrote: > > On Sun, Feb 11, 2018 at 02:50:30PM +0100, Martin Pieuchot wrote: > > > On 11/02/18(Sun) 12:37, Matthieu Herrb wrote: > > > > Hi, > > > > > > > > I ugraded my laptop

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Landry Breuil
On Sun, Feb 11, 2018 at 03:13:07PM +0100, Matthieu Herrb wrote: > On Sun, Feb 11, 2018 at 02:50:30PM +0100, Martin Pieuchot wrote: > > On 11/02/18(Sun) 12:37, Matthieu Herrb wrote: > > > Hi, > > > > > > I ugraded my laptop from sources to -current yesterday. Since then > > > firefox stops

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Matthieu Herrb
On Sun, Feb 11, 2018 at 02:50:30PM +0100, Martin Pieuchot wrote: > On 11/02/18(Sun) 12:37, Matthieu Herrb wrote: > > Hi, > > > > I ugraded my laptop from sources to -current yesterday. Since then > > firefox stops resolving host names after a dozen of minutes or so. > > What do you mean with

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Martin Pieuchot
On 11/02/18(Sun) 12:37, Matthieu Herrb wrote: > Hi, > > I ugraded my laptop from sources to -current yesterday. Since then > firefox stops resolving host names after a dozen of minutes or so. What do you mean with "stops resolving host names"? What happens? What do you see? How did figure out

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Matthieu Herrb
On Sun, Feb 11, 2018 at 01:09:36PM +0100, Mark Kettenis wrote: > > From: "Peter N. M. Hansteen" > > Date: Sun, 11 Feb 2018 12:49:49 +0100 > > > > n 02/11/18 12:37, Matthieu Herrb wrote: > > > I ugraded my laptop from sources to -current yesterday. Since then > > > firefox stops

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Mark Kettenis
> From: "Peter N. M. Hansteen" > Date: Sun, 11 Feb 2018 12:49:49 +0100 > > n 02/11/18 12:37, Matthieu Herrb wrote: > > I ugraded my laptop from sources to -current yesterday. Since then > > firefox stops resolving host names after a dozen of minutes or so. > > The

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Otto Moerbeek
On Sun, Feb 11, 2018 at 12:37:09PM +0100, Matthieu Herrb wrote: > Hi, > > I ugraded my laptop from sources to -current yesterday. Since then > firefox stops resolving host names after a dozen of minutes or so. > The network.dnsCacheExpiration=0 setting mentionned by phessler on > mastodon

Re: firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Peter N. M. Hansteen
n 02/11/18 12:37, Matthieu Herrb wrote: > I ugraded my laptop from sources to -current yesterday. Since then > firefox stops resolving host names after a dozen of minutes or so. > The network.dnsCacheExpiration=0 setting mentionned by phessler on > mastodon doesn't help. > > It's not the firefox

firefox (or some rthread / network stuff) broken in -current

2018-02-11 Thread Matthieu Herrb
Hi, I ugraded my laptop from sources to -current yesterday. Since then firefox stops resolving host names after a dozen of minutes or so. The network.dnsCacheExpiration=0 setting mentionned by phessler on mastodon doesn't help. It's not the firefox port itself, since it started after I rebooted