From: Luis Felipe <luis.felipe.la@protonmail.com>
To: help guix <help-guix@gnu.org>
Subject: Can't reconnect to WiFi easily
Date: Fri, 21 Oct 2022 19:27:49 +0000 [thread overview]
Message-ID: <-Ax28D1CNSuwTi3wP5vULVPLS547XvO0CkU8-fxbCl6G4N3NoLSBmj1IbSMMYxZrUAIFEPU_AoJJ0WHOA0TgVhCSPnivPHTa27RDKHMMLw4=@protonmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1764 bytes --]
§ Summary
Recently, I had to switch to using WiFi to access the Internet and it hasn't been a nice experience. I don't know the root of the problem or problems, but I notice that I'm the only one affected by these (I'm the only Guix System user in the local network).
I don't do anything special to connect to WiFi; I use GNOME, so I simply select the local network in GNOME Configuration and connect to it.
I'm using Guix System 4716cea, and whatever the GNOME desktop uses to connect to the Internet.
§ The problem(s)
I lose connection twice or three times a day and the system can't connect back automatically when/if it loses connection.
When this happens, many times GNOME's WiFi indicator fails to tell me the real state of the connection. Sometimes there is no connection and it says there is, and vice versa.
I used to be able to restart the networking service as follows:
❚ sudo herd stop networking
❚ sudo herd start networking
But after upgrading my system (currently 4716cea), the first command just seems to hang and never returns, no matter the terminal I run it on. Ctrl+C does nothing.
I see no other option but rebooting. But that also fails. For example, when I tell GNOME to reboot, the process hangs in a black screen displaying two messages that read
❚ ModemManager[416]: <info> caught signal, shutting down...
❚ ModemManager[416]: <info> could not acquire the 'org.freedesktop.ModemManager1' service name
After this, I have to restart the machine physically.
I know WiFi networks are not that stable, but my system/machine seems to be the only one that can't recover from connection failure.
Any help is very welcome,
---
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
next reply other threads:[~2022-10-22 0:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 19:27 Luis Felipe [this message]
2022-10-22 0:23 ` Can't reconnect to WiFi easily Felix Lechner via
2022-10-22 14:41 ` Luis Felipe
2022-11-01 0:10 ` Luis Felipe
2022-11-01 1:42 ` Felix Lechner via
2022-11-01 9:42 ` phodina
2022-11-02 19:45 ` Luis Felipe
2022-11-02 21:42 ` Felix Lechner via
2022-11-03 15:48 ` Luis Felipe
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='-Ax28D1CNSuwTi3wP5vULVPLS547XvO0CkU8-fxbCl6G4N3NoLSBmj1IbSMMYxZrUAIFEPU_AoJJ0WHOA0TgVhCSPnivPHTa27RDKHMMLw4=@protonmail.com' \
--to=luis.felipe.la@protonmail.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).