overview for 0WN3D

nmcli unable to connect to password protected home WiFi in c/[email protected]

[–] [email protected] 3 points 2 months ago* (last edited 2 months ago)

Is your keyboard layout set correctly?

I would suppose so, cause I used nmcli d WiFi connect SSID password PASSWORD, and the PASSWORD is displayed correctly.

Does the SSID or password have a , or weird character?

My password is alphanumeric, so that shouldn't be the issue. My SSID is alphanumeric + (), but I don't think that's the issue either cause I cannot connect to my password protected hotspot that is only alphanumeric.

nmcli unable to connect to password protected home WiFi in c/[email protected]

[–] [email protected] 1 points 2 months ago

Yea I tried, same issue

3

nmcli unable to connect to password protected home WiFi (lemmy.cafe)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/[email protected]

4 comments fedilink

Hey, I am trying to connect to my home WiFi using nmcli but can't seem to connect. The error is

Error: Connection activation failed: (7) Secrets were required, but not provided.

The journal logs are at the bottom.

Some context:

I am using arch linux ARM on a raspberry pi 4
I am able to connect to non-password protected networks (I created one by using a hotspot on my phone). Once I set a password for the hotspot, I am unable to connect to the same network
I've tried the solutions in https://wiki.archlinux.org/title/NetworkManager#Secrets_were_required.2C_but_not_provided, but no success
Previously, I was using netctl/netctl-auto and it worked for my use case for a while. But one day, it cannot connect so I can't ssh into my pi for a few days. I got frustrated and uninstalled it and installed nmcli which I am more familiar with. But now I can't seem to connect to a password protected network, so looking back, maybe it wasn't netctl that was the root cause of the issue.

logs

Aug 19 06:03:03 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:03:03 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:03:03 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:03:03 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:03:03 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:03:03 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:03:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:03:01 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:03:01 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:03:01 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:03:01 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:02:20 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:02:20 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:02:20 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:02:20 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:02:20 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:02:20 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:02:19 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:02:18 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:02:18 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:02:18 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:02:18 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:01:51 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:01:51 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:01:51 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:01:51 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:01:51 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:01:51 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:01:50 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:01:50 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:01:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:01:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:01:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:01:31 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:01:31 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:01:31 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:01:31 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:01:31 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:01:31 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:01:30 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:01:29 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:01:29 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:01:29 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:01:29 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:01:17 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:01:17 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:01:17 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:01:17 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:01:17 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:01:17 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:01:16 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:01:15 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:01:15 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:01:15 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:01:15 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:01:08 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:01:08 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:01:08 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:01:08 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:01:08 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:01:08 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:01:06 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:01:06 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:01:06 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:01:06 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:01:06 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:01:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:01:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:01:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:01:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:01:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:01:02 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:01:00 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:01:00 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:01:00 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:00:59 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:00:59 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:00:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:00:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:00:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:00:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:00:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:00:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:00:53 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:00:53 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:00:53 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:00:53 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:00:53 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:00:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:00:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:00:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:00:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:00:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:00:49 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:00:47 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:00:47 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:00:47 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:00:47 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:00:47 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:00:44 alarmpi wpa_supplicant[643]: wlan0: Reject scan trigger since one is already pending
Aug 19 06:00:44 alarmpi NetworkManager[435]: <info>  [1724018444.4181] device (p2p-dev-wlan0): supplicant management interface state: scanning -> inactive
Aug 19 06:00:44 alarmpi NetworkManager[435]: <info>  [1724018444.4179] device (wlan0): supplicant interface state: scanning -> inactive
Aug 19 06:00:44 alarmpi wpa_supplicant[643]: wlan0: Removed BSSID 18:82:8c:07:ef:44 from ignore list (clear)
Aug 19 06:00:43 alarmpi NetworkManager[435]: <info>  [1724018443.7438] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:43 alarmpi NetworkManager[435]: <warn>  [1724018443.7420] device (wlan0): Activation: failed for connection 'MyWIFI99'
Aug 19 06:00:43 alarmpi NetworkManager[435]: <info>  [1724018443.7405] manager: NetworkManager state is now DISCONNECTED
Aug 19 06:00:43 alarmpi NetworkManager[435]: <info>  [1724018443.7390] device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
Aug 19 06:00:43 alarmpi NetworkManager[435]: <warn>  [1724018443.7389] device (wlan0): no secrets: No agents were available for this request.
Aug 19 06:00:43 alarmpi NetworkManager[435]: <warn>  [1724018443.7373] device (wlan0): Activation: (wifi) asking for new secrets
Aug 19 06:00:43 alarmpi NetworkManager[435]: <info>  [1724018443.7357] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:43 alarmpi NetworkManager[435]: <warn>  [1724018443.7355] device (wlan0): Activation: (wifi) association took too long
Aug 19 06:00:40 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:00:40 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:00:40 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:00:40 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:00:40 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:00:40 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:00:38 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:00:38 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:00:38 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:00:38 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:00:38 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:00:34 alarmpi NetworkManager[435]: <info>  [1724018434.3423] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> scanning
Aug 19 06:00:34 alarmpi NetworkManager[435]: <info>  [1724018434.3422] device (wlan0): supplicant interface state: disconnected -> scanning
Aug 19 06:00:34 alarmpi NetworkManager[435]: <info>  [1724018434.2461] device (p2p-dev-wlan0): supplicant management interface state: associated -> disconnected
Aug 19 06:00:34 alarmpi NetworkManager[435]: <info>  [1724018434.2459] device (wlan0): supplicant interface state: associated -> disconnected
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: CTRL-EVENT-DSCP-POLICY clear_all
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="MyWIFI99" auth_failures=1 duration=10 reason=CONN_FAILED
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: BSSID 18:82:8c:07:ef:44 ignore list count incremented to 2, ignoring for 10 seconds
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: CTRL-EVENT-DISCONNECTED bssid=18:82:8c:07:ef:44 reason=3 locally_generated=1
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: nl80211: send_event_marker failed: Source based routing not supported
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: Added BSSID 18:82:8c:07:ef:44 into ignore list, ignoring for 10 seconds
Aug 19 06:00:34 alarmpi wpa_supplicant[643]: wlan0: Authentication with 18:82:8c:07:ef:44 timed out.
Aug 19 06:00:24 alarmpi NetworkManager[435]: <info>  [1724018424.2355] device (p2p-dev-wlan0): supplicant management interface state: associating -> associated
Aug 19 06:00:24 alarmpi NetworkManager[435]: <info>  [1724018424.2354] device (wlan0): supplicant interface state: associating -> associated
Aug 19 06:00:24 alarmpi wpa_supplicant[643]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Aug 19 06:00:24 alarmpi wpa_supplicant[643]: wlan0: Associated with 18:82:8c:07:ef:44
Aug 19 06:00:24 alarmpi systemd-networkd[306]: wlan0: Connected WiFi access point: MyWIFI99 (18:82:8c:07:ef:44)
Aug 19 06:00:24 alarmpi NetworkManager[435]: <info>  [1724018424.1339] device (p2p-dev-wlan0): supplicant management interface state: scanning -> associating
Aug 19 06:00:24 alarmpi NetworkManager[435]: <info>  [1724018424.1339] device (wlan0): supplicant interface state: scanning -> associating
Aug 19 06:00:24 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 06:00:24 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 06:00:24 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 06:00:24 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 06:00:24 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 06:00:24 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 06:00:24 alarmpi wpa_supplicant[643]: wlan0: Trying to associate with SSID 'MyWIFI99'
Aug 19 06:00:22 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 06:00:22 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 06:00:22 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 06:00:22 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 06:00:22 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0909] device (p2p-dev-wlan0): supplicant management interface state: inactive -> scanning
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0908] device (wlan0): supplicant interface state: inactive -> scanning
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0557] Config: added 'psk' value '<hidden>'
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0556] Config: added 'auth_alg' value 'OPEN'
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0556] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0556] Config: added 'bgscan' value 'simple:30:-70:86400'
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0555] Config: added 'scan_ssid' value '1'
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0555] Config: added 'ssid' value 'MyWIFI99'
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0554] device (wlan0): Activation: (wifi) connection 'MyWIFI99' has security, and secrets exist.  No new secrets needed.
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0547] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0539] device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0504] device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0503] device (wlan0): Activation: (wifi) access point 'MyWIFI99' has security, but secrets are required.
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0496] device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0487] manager: NetworkManager state is now CONNECTING
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0472] device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0462] audit: op="connection-add-activate" uuid="68b7ad1d-29b3-402d-b925-5cbdc0bb07cc" name="MyWIFI99" pid=799 uid=1001 result="success"
Aug 19 06:00:18 alarmpi NetworkManager[435]: <info>  [1724018418.0453] device (wlan0): Activation: starting connection 'MyWIFI99' (68b7ad1d-29b3-402d-b925-5cbdc0bb07cc)
Aug 19 06:00:01 alarmpi NetworkManager[435]: <info>  [1724018401.4961] audit: op="connection-delete" uuid="eed97363-aa98-4d50-abab-4826666ca0fc" name="MyWIFI99" pid=784 uid=1001 result="success"
Aug 19 05:59:43 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 05:59:43 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 05:59:43 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 05:59:43 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 05:59:43 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 05:59:43 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 05:59:42 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 05:59:41 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 05:59:41 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 05:59:41 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 05:59:41 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 05:59:14 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 05:59:14 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 05:59:14 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 05:59:14 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 05:59:14 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52
Aug 19 05:59:14 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd090 fail, reason -52
Aug 19 05:59:13 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02e fail, reason -52
Aug 19 05:59:12 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd02a fail, reason -52
Aug 19 05:59:12 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd026 fail, reason -52
Aug 19 05:59:12 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd022 fail, reason -52
Aug 19 05:59:12 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0x100e fail, reason -52
Aug 19 05:58:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a5 fail, reason -52
Aug 19 05:58:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd0a1 fail, reason -52
Aug 19 05:58:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd09d fail, reason -52
Aug 19 05:58:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd099 fail, reason -52
Aug 19 05:58:55 alarmpi kernel: brcmfmac: brcmf_set_channel: set chanspec 0xd095 fail, reason -52

17

Best way to get recommended videos (lemmy.cafe)

submitted 9 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]

7 comments fedilink

I know there was quite a bit of controversy surrounding YouTube's recommendation algorithms, but I can't seem to find a better alternative. What are the ways y'all find videos that are of interest?

I know we could use RSS and subscribe to our desired channels and get a better experience than YT's own subscription system, but what about channel/video discovery, those that you've never seen before? Is there a better way to find a video that might be interesting to you without kneeling before the almighty algorithm? Half of the recommended page on YT seems irrelevant to me, but I can't seem to find a better alternative.

Mosquito splinters in c/[email protected]

[–] [email protected] 1 points 10 months ago

Oh, ticks are rare in my region, that's why I have no prior experience with them.

I was thinking in the context of us slapping the mosquito would be equivalent to slamming a thumbtack into your skin which could increase the damage dealt and penetration depth.

61

Mosquito splinters (lemmy.cafe)

submitted 10 months ago by [email protected] to c/[email protected]

13 comments fedilink

Just a random shower thought.

Mosquito's proboscis is sharp enough to penetrate your skin. So when you smack it while it is in the process of drawing your blood, isn't there a chance of its proboscis being forcefully jammed into your skin, leading to some sort of "splinter"? Or does it somehow loses its stiffness the moment it feels the impact?

I've never encountered nor heard of such occurrence in my lifetime of killing those buggers, but wondering if such a thing is even possible. If such could happen, I could only imagine the risk associated with having a piece of foreign organic matter being embed in the body

MPV dropping frames and audio in c/[email protected]

[–] [email protected] 1 points 1 year ago

ok, here you go https://pastebin.com/uPc5S1LU

MPV dropping frames and audio in c/[email protected]

[–] [email protected] 1 points 1 year ago

Tried the settings on the GitHub, doesn't seem to work, and it also made the stuttering worse

opengl-pbo=yes
opengl-early-flush=no.
video-sync=display-resample

ok, here you go

https://pastebin.com/uPc5S1LU

MPV dropping frames and audio in c/[email protected]

[–] [email protected] 1 points 1 year ago (2 children)

Yea, it seems to be using 200% CPU. But I have vo=gpu though, so I'd thought the GPU would've taken some of the load.

If I am strapped for CPU resources, how do I make it so that MPV buffer or something instead of dropping the audio when this happens? Cause it is strange the even though the visuals are acceptable, it is the audio that fails before the video

22

MPV dropping frames and audio (lemmy.cafe)

submitted 1 year ago by [email protected] to c/[email protected]

6 comments fedilink

I've tried searching around and stuff but I couldn't find a working solution

Background: I am running Arch Linux on a Raspberry Pi, mainly as a media player.

When I run MPV, it seems to drop frames (1-2 per second). Visually, nothing looks wrong so I am fine with that.

The issue is that after playing for some duration, the audio will just disappear. I would then need to pause the video for a while or seek backwards for the audio to come back (sometimes it just comes back on its own when I leave it playing too). I suspect it may be due to the dropped frames or maybe it's due to insufficient system resource.

Could someone help suggest some config changes which may help with the issue? I am totally fine with the visual dropped frames, I just want to fix the audio issue.

This is my config.

input-ipc-server=/tmp/mpvsocket
ao=pipewire
volume=120
demuxer-readahead-secs=3                                
cache=yes

[Answered] Typehints for functions that have variable signatures in c/[email protected]

[–] [email protected] 2 points 1 year ago (1 children)

I think there's a spectrum here, and I'll clarify the stances.

The spectrum ranges from "Data shouldn't cause the function to do (something wildly) different" to "It should be allowed, even to the point of variable returns"

I think you stand on the former while I stand on the latter. Correct me if I'm wrong though, but that's the vibe I'm getting from the tone in your example.

Data shouldn’t drive the program in this way.

Suppose we have a function that calculates a price of an object. I feel it is agreeable for us to have compute_price(with_discount: bool), over compute_price_with_discount() + compute_price_without_discount()

You’ve basically spelled:

I feel your point your making in the example is a bit exaggerated. Again, coming back to my above example, I don't think we would construe it as compute_price('with_discount').

Maybe this is bandwagoning, but one of the reason for my stance is that there are quite a few examples of variable returns.

eg:

getattr may return a different type base on the key given
quite a few functions in numpy returns different things based on flags. SVD will return S if compute_uv=False and S,U,V otherwise

[Answered] Typehints for functions that have variable signatures in c/[email protected]

[–] [email protected] 1 points 1 year ago (1 children)

I thought about it, but it isn't as expressive as I wished.

Meaning if I do

a = foo(return_more=True)
or
a, b = foo(return_more=False)

it doesn't catch these errors for me.

In comparison, the other suggested solution does catch these.

[Answered] Typehints for functions that have variable signatures in c/[email protected]

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

yea, this is pretty close to what I'm looking for.

The only missing piece is the ability to define the overload methods on the bool

something like

@overload
def foo(return_more: True) -> (Data, Data)

@overload
def foo(return_more: False) -> Data

But I don't think such constructs are possible? I know it is possible in Typescript to define the types using constants, but I don't suppose Python allows for this?

EDIT: At first, when I tried the above, the typechecker said Literal[True] was not expected and I thought it was not possible. But after experimenting some, I figured out that it is actually possible. Added my solution to the OP

Thanks for the tip!

[Answered] Typehints for functions that have variable signatures in c/[email protected]

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (4 children)

but from a practical perspective, let's say you retrieve an object and can either return a subset of its fields as your API. Doesn't it make sense to re-use the same function, but change what fields are returned?

I'm specifically talking about the narrow use-case where your API returns either A or B of the fields, and won't extend it in the future

The alternative is to either duplicate the function, or extract it out which seems a bit overkill if it is only 2 different type of functions.

22

[Answered] Typehints for functions that have variable signatures (lemmy.cafe)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

18 comments fedilink

I know what I am asking is rather niche, but it has been bugging me for quite a while. Suppose I have the following function:

def foo(return_more: bool):
   ....
    if return_more:
        return data, more_data
   return data

You can imagine it is a function that may return more data if given a flag.

How should I typehint this function? When I use the function in both ways

data = foo(False)

data, more_data = foo(True)

either the first or the 2nd statement would say that the function cannot be assigned due to wrong size of return tuple.

Is having variable signature an anti-pattern? Is Python's typehinting mechanism not powerful enough and thus I am forced to ignore this error?

Edit: Thanks for all the suggestions. I was enlightened by this suggestion about the existence of overload and this solution fit my requirements perfectly

from typing import overload, Literal

@overload
def foo(return_more: Literal[False]) -> Data: ...

@overload
def foo(return_more: Literal[True]) -> tuple[Data, OtherData]: ...

def foo(return_more: bool) -> Data | tuple[Data, OtherData]:
   ....
    if return_more:
        return data, more_data
   return data

a = foo(False)
a,b = foo(True)
a,b = foo(False) # correctly identified as illegal