Waybar: Network sometimes shows as disconnected when it's not

Created on 15 Jun 2019 · 16Comments · Source: Alexays/Waybar

I often get the network shown as Disconnected when it's actually not. Restarting waybar fixes it. Let me know what kind of information you need to debug this.

bug

Source

pedrocr

👍25

Most helpful comment

I've been able to reproduce this reliably.

System: Arch Linux, systemd-networkd, iwd

/etc/systemd/network/25-wireless.network:

[Match]
Name=wlan0

[Network]
DHCP=yes

Steps to reproduce:

Connect to network A: iwctl station wlan0 connect A
Connect to network B: iwctl station wlan0 connect B
Restart waybar. At this point, the network B should be shown by the Network module.
Connect back to network A: iwctl station wlan0 connect A. The network module will now show a disconnected state.

The problem can be temporarily resolved by either:

Restarting waybar
Restarting systemd-networkd: systemctl restart systemd-networkd.service

Running waybar with --log-level trace reveals nothing about the bug.

GrantMoyer on 19 Oct 2019

👍7

All 16 comments

It seems like https://github.com/Alexays/Waybar/issues/354 came back. I'm also experiencing this.

FreeFull on 15 Jun 2019

👍6

Same problem today came. Shows "disconnected" all time, excepting time wifi-menu is open in terminal
Arch Linux
Waybar v0.6.6-28-gfcf2d18 (May 30 2019, branch 'master')
UPD: reconnected to WIFI with netctl-auto, fixed problem
No data in output excepting messages Gdk-WARNING **: 15:04:30.647: Couldn't map as window 0x5577c9792650 as popup because it doesn't have a parent

niktob560 on 16 Jun 2019

Experiencing the same issue, but on my end, it seems related to multihead and/or sleep. Whenever I come back from sleep, the status shows disconnected until I reload sway, and sometimes, one of the screen shows my SSID while the other shows up disconnected.

apognu on 8 Jul 2019

👍2

I see this happen a lot when I change Wifi networks. I think I can reproduce this mostly at will.

pedrocr on 9 Jul 2019

I came here to post an issue that https://github.com/Alexays/Waybar/issues/354 was back and found this issue. In my case, the network connection is just out of date. For example it would show wireless as active when I would have deactivated it.

MichaelAquilina on 29 Jul 2019

Am also affected, though I cannot link directly to sleep

farid-fari on 31 Jul 2019

This is really annoying. I wondered today if it was something to do with changing between APs with the same SSID.

pedrocr on 16 Aug 2019

I've been able to reproduce this reliably.

System: Arch Linux, systemd-networkd, iwd

/etc/systemd/network/25-wireless.network:

[Match]
Name=wlan0

[Network]
DHCP=yes

Steps to reproduce:

Connect to network A: iwctl station wlan0 connect A
Connect to network B: iwctl station wlan0 connect B
Restart waybar. At this point, the network B should be shown by the Network module.
Connect back to network A: iwctl station wlan0 connect A. The network module will now show a disconnected state.

The problem can be temporarily resolved by either:

Restarting waybar
Restarting systemd-networkd: systemctl restart systemd-networkd.service

Running waybar with --log-level trace reveals nothing about the bug.

GrantMoyer on 19 Oct 2019

👍7

In my case uncommenting Interface wlp4s0line in config and letting the ip be static solves the problem.

Before that change, ip addr showed lot of ip6 addresses and 2 ip4 addresses. I changed to static ip and now I have just one ip4 and one ip6. The problem has gone.

I have 2 wireless nets in my house so If I go to the garden it connects to the second net.

Neules on 25 Apr 2020

I'm having the same problem with Arch, sway and current master, restarting waybar or disabling&enabling the output waybar is using also updates it.

chron-isch on 3 Jul 2020

👍1

Same here with Waybar v0.9.2 (Apr 11 2020, branch 'master') on Ubuntu 20.04 with sway 1.4-f681d529 (Jan 22 2020, branch 'heads/1.4')

varac on 3 Jul 2020

I can reproduce this issue with iwd by simply switching to another AP or even by simply disconnecting and reconnecting to the same one.

I'm trying to monitor the events passed to Network::handleEvents, but it looks like I miss many events when I use a debugger compared to just printing nlmsg_type to stdout. I don't now much about libnl so I can't say if that's just some timeout or a race condition somewhere in the code. Also, I can't reproduce a single case where Network::checkNewInterface finds a valid interface.
From what I see I am quite confident that #511 is the same issue as this one.

For now I managed to work around the issue by skipping checkNewInterface and just kicking the timer https://github.com/GbGp/Waybar/commit/3271258d97c0710e6de9a619cd87dc8f12fd7d15, but I'm not sure what I'm breaking there.

GbGp on 17 Oct 2020

Same here with NetworkManager on Arch Linux (Waybar v0.9.4)

dR3b on 20 Oct 2020

Arch Linux kernel 5.9.1-arch1-1 / Waybar v0.9.4 / sway version v1.5
iwd / systemd-networkd

Looking at the logs, it lost carrier and reconnected.
Oct 22 10:29:01 systemd-networkd[239]: wlan0: Gained carrier
Oct 22 10:29:01 systemd-networkd[239]: wlan0: DHCPv4 address 10.0.1.87/23 via 10.0.0.1
Oct 22 10:29:49 systemd-networkd[239]: wlan0: Lost carrier
Oct 22 10:29:49 systemd-networkd[239]: wlan0: DHCP lease lost
Oct 22 10:29:49 systemd-networkd[239]: wlan0: DHCPv6 lease lost
Oct 22 10:29:50 systemd-networkd[239]: wlan0: Gained carrier
Oct 22 10:29:50 systemd-networkd[239]: wlan0: Lost carrier
Oct 22 10:29:50 systemd-networkd[239]: wlan0: DHCPv6 lease lost
Oct 22 10:29:51 systemd-networkd[239]: wlan0: Gained carrier
Oct 22 10:29:51 systemd-networkd[239]: wlan0: DHCPv4 address 10.0.1.87/23 via 10.0.0.1

journal -xe
Oct 22 10:29:50 kernel: iwlwifi 0000:02:00.0: No beacon heard and the time event is over already...
Oct 22 10:29:50 kernel: wlan0: Connection to AP cc:f4:11:4b:e0:a3 lost
Oct 22 10:29:50 iwd[332]: Received Deauthentication event, reason: 4, from_ap: false
Oct 22 10:29:50 systemd-networkd[239]: wlan0: Lost carrier
Oct 22 10:29:50 systemd-networkd[239]: wlan0: DHCPv6 lease lost
Oct 22 10:29:50 kernel: wlan0: authenticate with cc:f4:11:4b:e0:a3
Oct 22 10:29:50 kernel: wlan0: send auth to cc:f4:11:4b:e0:a3 (try 1/3)
Oct 22 10:29:51 kernel: wlan0: authenticated
Oct 22 10:29:51 kernel: wlan0: associate with cc:f4:11:4b:e0:a3 (try 1/3)
Oct 22 10:29:51 kernel: wlan0: RX AssocResp from cc:f4:11:4b:e0:a3 (capab=0x1011 status=0 aid=12)
Oct 22 10:29:51 kernel: wlan0: associated
Oct 22 10:29:51 systemd-networkd[239]: wlan0: Gained carrier
Oct 22 10:29:51 systemd-networkd[239]: wlan0: DHCPv4 address 10.0.1.87/23 via 10.0.0.1
Oct 22 10:29:51 kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by cc:f4:11:4b:e0:a3
Oct 22 10:30:21 systemd[1]: systemd-hostnamed.service: Succeeded.

Wondering if its more related to iwd or systemd / kernel, still weird the module isn't picking up the connect status.

endorsystems on 22 Oct 2020

Same problem here with latest everything:

5.9.14-arch1-1
waybar 0.9.4-5
networkmanager 1.26.4-1

Restarting waybar shows my connection again, but after a few minutes it goes back to showing "disconnected" again. When the network drops and wpa_supplicant immediately reconnects, waybar loses track of the connection forever.