Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-08-06 Thread Hendrik Boom
On Sat, 03 Aug 2013 16:29:06 -0500, Selim T. Erdogan wrote: > Hendrik Boom, 3.08.2013: >> >> Every other program on my laptop finds the right IP number for >> slashdot. >> It's just Chromium that doesn't. Even Chrome gets it right. Somewhere >> Chromium has hidden state I can't expunge. > >

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-08-04 Thread Curt
On 2013-08-03, Hendrik Boom wrote: > > And if the secret bit of state I can't expunge ends up getting synced > along with the bookmarks, things may get worse instead of better. You moved (I haven't been following the thread) the '~/.config/chromium' directory out of the way already ('mv chromium

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-08-03 Thread Selim T. Erdogan
Hendrik Boom, 3.08.2013: > > Every other program on my laptop finds the right IP number for slashdot. > It's just Chromium that doesn't. Even Chrome gets it right. Somewhere > Chromium has hidden state I can't expunge. You could try purging the package ("apt-get remove --purge ...") and g

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-08-03 Thread Hendrik Boom
On Fri, 19 Jul 2013 06:45:26 -0400, Stephen Allen wrote: > On Thu, Jul 18, 2013 at 04:43:07PM +, Hendrik Boom wrote: >> It's been most of a week now, and the problem persists. >> Chromium still insists on going to the website normally known as >> topoi.pooq.com when I request slashdot.org. >>

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-07-19 Thread Paul Cartwright
  ---end quoted text--- Why would you need to copy your bookmarks? Presumably you used bookmark sync with Chromium, thus they will be available to Google-Chrome when you login into your Google account the 1st time in Chrome. Have you tried using a different DNS server

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-07-19 Thread Stephen Allen
On Thu, Jul 18, 2013 at 04:43:07PM +, Hendrik Boom wrote: > On Sun, 14 Jul 2013 14:57:14 +, Hendrik Boom wrote: > > > On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote: > > > >> On Sat, Jul 13, 2013 at 08:39:10PM +, Hendrik Boom wrote: > >>> For some reason, chromium seems to have

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-07-18 Thread Hendrik Boom
On Sun, 14 Jul 2013 14:57:14 +, Hendrik Boom wrote: > On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote: > >> On Sat, Jul 13, 2013 at 08:39:10PM +, Hendrik Boom wrote: >>> For some reason, chromium seems to have got it stuck in its head that >>> slashdot,org is at 69.165.131.134. At l

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-07-14 Thread Igor Cicimov
Do you have nscd running by any chance? On 15/07/2013 12:58 AM, "Hendrik Boom" wrote: > On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote: > > > On Sat, Jul 13, 2013 at 08:39:10PM +, Hendrik Boom wrote: > >> For some reason, chromium seems to have got it stuck in its head that > >> slashd

Re: Deleting chromium DNS cache entry doesn't seem to help.

2013-07-14 Thread Hendrik Boom
On Sat, 13 Jul 2013 16:53:01 -0400, staticsafe wrote: > On Sat, Jul 13, 2013 at 08:39:10PM +, Hendrik Boom wrote: >> For some reason, chromium seems to have got it stuck in its head that >> slashdot,org is at 69.165.131.134. At least, when I try to browse to >> slashdot.org using chromium, th

Re: Deleting chromium DNS cache entry

2013-07-13 Thread staticsafe
On Sat, Jul 13, 2013 at 08:39:10PM +, Hendrik Boom wrote: > For some reason, chromium seems to have got it stuck in its head that > slashdot,org is at 69.165.131.134. At least, when I try to browse to > slashdot.org using chromium, the displayed contents are identical to the > contents at 1

Deleting chromium DNS cache entry

2013-07-13 Thread Hendrik Boom
For some reason, chromium seems to have got it stuck in its head that slashdot,org is at 69.165.131.134. At least, when I try to browse to slashdot.org using chromium, the displayed contents are identical to the contents at 16.165.131.134, which contains my personal web site. Firefox and chrom