unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Wamm K. D." <jaft.r@outlook.com>
To: help-guix@gnu.org
Subject: Web Browsers Report being "Unable to Connect" after Wi-Fi Connection Drop Period
Date: Mon, 23 May 2022 14:34:34 -0500	[thread overview]
Message-ID: <BY5PR07MB7029196C0867F1BD403DDAA999D49@BY5PR07MB7029.namprd07.prod.outlook.com> (raw)

I think it's happened most often with IceCat but pretty much every
browser I've tried has done this.

I'm not sure the cause but my Wi-Fi card drops the connection, /really/
often; it sucks but it's what I've got.

The consequence is that I've noticed a particular behavior relatively
frequently: when the connection drops, the browser I'm using will get
stuck thinking that it cannot connect to the internet once the internet
connection comes back, sometimes (especially if I tried to load a page
while the internet connection was down). Trying to load any other page
results in the "Unable to Connect" (or equivalent) page.

I've tried IceCat, Ungoogled Chromium, Qutebrowser, Luakit, and Nyxt and
had the same experience, in some capacity, with all of them.

Loading a local HTML file works fine, during these spells, and I either
have to wait a variable length of time before the spell passes or
restart the browser.

It doesn't seem to be something which impacts all browsers, at the same
time: opening a new browser after one gets affected works fine or trying
to use one of the other browsers I had open (especially if I hadn't been
using this other browser while the internet connection had dropped).


             reply	other threads:[~2022-05-23 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 19:34 Wamm K. D. [this message]
2022-05-23 20:04 ` Web Browsers Report being "Unable to Connect" after Wi-Fi Connection Drop Period Ekaitz Zarraga
2022-05-23 20:07 ` raingloom
2022-05-23 21:09 ` Ricardo Wurmus
2022-05-23 21:45   ` raingloom
2022-05-24  5:49     ` Wamm K. D.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BY5PR07MB7029196C0867F1BD403DDAA999D49@BY5PR07MB7029.namprd07.prod.outlook.com \
    --to=jaft.r@outlook.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).