From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id rcBzF+fS11/gFwAA0tVLHw (envelope-from ) for ; Mon, 14 Dec 2020 21:02:31 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2 with LMTPS id oOm9EufS119APAAAB5/wlQ (envelope-from ) for ; Mon, 14 Dec 2020 21:02:31 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id C7A579403A6 for ; Mon, 14 Dec 2020 21:02:30 +0000 (UTC) Received: from localhost ([::1]:36622 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kouzF-0006cf-MH for larch@yhetil.org; Mon, 14 Dec 2020 16:02:29 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:53434) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kouy7-0006DO-Pi for help-guix@gnu.org; Mon, 14 Dec 2020 16:01:19 -0500 Received: from dustycloud.org ([2600:3c02::f03c:91ff:feae:cb51]:47900) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kouy6-00038c-5A for help-guix@gnu.org; Mon, 14 Dec 2020 16:01:19 -0500 Received: from twig (localhost [127.0.0.1]) by dustycloud.org (Postfix) with ESMTPS id 4D98B26641 for ; Mon, 14 Dec 2020 16:01:16 -0500 (EST) User-agent: mu4e 1.4.13; emacs 27.1 From: Christopher Lemmer Webber To: help-guix@gnu.org Subject: A weird thing about network connections in Icecat (and Firefox) on Guix Date: Mon, 14 Dec 2020 16:00:43 -0500 Message-ID: <87y2i0hzlw.fsf@dustycloud.org> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2600:3c02::f03c:91ff:feae:cb51; envelope-from=cwebber@dustycloud.org; helo=dustycloud.org X-Spam_score_int: 14 X-Spam_score: 1.4 X-Spam_bar: + X-Spam_report: (1.4 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.31 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of help-guix-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=help-guix-bounces@gnu.org X-Migadu-Queue-Id: C7A579403A6 X-Spam-Score: -2.31 X-Migadu-Scanner: scn0.migadu.com X-TUID: YT2Bay8k11lD The same thing happens in Icecat as it does in nonguix's Firefox. (I mention the firefox thing to indicate that I *don't* think it's icecat-specific code). I've had this happen on my computer and have found it weird/disturbing for a while, but recently I found it's also happening on my spouse's computer, but only once she switched to Guix also. Wondering what's going on. (Maybe this should be filed as a bug, not sure.) Here's roughly the scenario: - Have icecat/firefox open and browsing websites. - Oops, something happens to the network. Maybe the wifi router goes out briefly or something. - You're back! You can ssh into servers again and connect to irc, and even ungoogled-chromium seems fine to browse websites. - But weirdly... you have to restart icecat/firefox for things to work right again. But weirdly... this isn't the case on my spouse's Debian install, etc. And I also only started experiencing it when I started running Guix. No particularly unusual extensions, just ublock origin, https everywhere, tree style tabs. I've turned off proxy settings in firefox to be sure. No change afaict. It's so strange. It's easy enough to fix but I'm disturbed that it's happening at all. It's as if there was some sneaky connection that firefox was making and which got broken until I restarted the browser. Or maybe it's just some massive caching bug that acts similarly. Disturbing. Anyone else experience the same? I tried describing this and it sounded like I was the only one having the issue a couple of years ago. Now that I'm not my only household member experiencing the same, I suspect we are probably not alone...? - Chris