wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04
I'll post more useful details (journalctl log) as a comment to this bug report.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: dbus 1.8.12-1ubuntu5
Uname: Linux 4.0.0-040000rc5
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Apr 2 18:18:56 2015
InstallationDate: Installed on 2015-03-27 (5 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)
Enrico (enricobe) wrote : | #1 |
- Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
- JournalErrors.txt Edit (29.3 KiB, text/plain; charset="utf-8")
- ProcEnviron.txt Edit (100 bytes, text/plain; charset="utf-8")
- upstart.dbus.log.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Enrico (enricobe) wrote : | #2 |
Launchpad Janitor (janitor) wrote : | #3 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in dbus (Ubuntu): | |
status: | New → Confirmed |
Changed in dbus (Ubuntu): | |
importance: | Undecided → Medium |
Plurtu (plurtu) wrote : | #4 |
I get this same dbus error but it does not prevent wifi from successfully reconnecting after sleep when testing with "systemctl suspend".
Plurtu (plurtu) wrote : | #5 |
I isolated the problem down to an incompatibility between xfce4-power-manager and systemd. When the suspend timeout is reached or the lid is closed, the network manager is being woken before the system has suspended which causes it not to wake on resume.
Switching from systemd back to Upstart fixes the problem.
Enrico (enricobe) wrote : | #6 |
Thank you very much Plurtu.
There will be a fix for the problem or we must always use upstart?
Jonathan Byrne (jonathan-yamame) wrote : | #7 |
I'm seeing something very much like this (same syslog messages, e.g.) but the differences are:
1) It's on a wired interface (802.1x wired)
2) Suspend isn't involved; it never works
3) Wireless 802.1x works perfectly on the same machine (although I haven't tried suspending it; it's my work machine and is always lid-open in a dock)
Hardware is a new ThinkPad W541 with Ultradock (but wired 802.1x doesn't work undocked, either).
OS is a fresh install of Ubuntu 15.04.
I'll try switching to Upstart later today and see if that helps; FWIW, I booted a live 14.04 DVD and wired 802.1x didn't work there, either, so I don't have high hopes for Upstart, but I'll try it.
Jonathan Byrne (jonathan-yamame) wrote : | #8 |
Update: Using upstart instead of systemd made no difference: wired 802.1x still gets that failure.
Launchpad Janitor (janitor) wrote : | #9 |
Status changed to 'Confirmed' because the bug affects multiple users.
Changed in systemd (Ubuntu): | |
status: | New → Confirmed |
Changed in systemd (Ubuntu): | |
importance: | Undecided → Medium |
Denilson Sá (denilsonsa) wrote : | #10 |
My system: Asus X450CA runnning Lubuntu 15.04.
Case 1:
The laptop not connected to anything else. I close down the lid, the laptop goes to sleep. I open the lid, the laptop wakes up. And the Wi-Fi seems to work okay afterwards.
Case 2:
The laptop connected to an external HDMI monitor (i.e. dual-head setup). This way, closing the lid does not make the laptop sleep. I can press Fn+F1 to start the sleeping procedure. Afterwards, I can press the power button to wake the laptop up. After it wakes up, Wi-Fi does not work anymore, and I need to run "sudo service network-manager restart".
In both cases, I have LXDE environment, with OpenBox and xfce4-power-
I have not tried too many variations, though; but I hope this helps reproducing the issue.
dumpstar (dumpstar) wrote : | #11 |
Does this on Xubuntu 15.04 also.
Vindicator (vindicator) wrote : | #12 |
I'm experiencing this with the regular Gnome 15.04.
It happened while I've been continuously switching "Enable Wi-fi" on/off while messing with my router because my SSID wasn't showing.
It was from a desktop after a reboot.
Restarting the "NetworkManager
$ journalctl -xe
*****
Jul 16 07:36:33 devx64 wpa_supplicant[
Jul 16 07:36:33 devx64 NetworkManager[
Jul 16 07:36:33 devx64 NetworkManager[
Jul 16 07:36:33 devx64 NetworkManager[
Jul 16 07:36:33 devx64 NetworkManager[
Jul 16 07:37:02 devx64 NetworkManager[
Jul 16 07:37:02 devx64 NetworkManager[
Jul 16 07:37:02 devx64 wpa_supplicant[
Jul 16 07:37:02 devx64 wpa_supplicant[
Jul 16 07:37:02 devx64 NetworkManager[
Jul 16 07:37:02 devx64 NetworkManager[
Jul 16 07:37:02 devx64 NetworkManager[
Jul 16 07:37:02 devx64 NetworkManager[
*****
Martin Pitt (pitti) wrote : | #13 |
This sounds similar to bug 1270257, but that was closed due to getting too much noise.
affects: | dbus (Ubuntu) → network-manager (Ubuntu) |
no longer affects: | systemd (Ubuntu) |
George Shuklin (george-shuklin) wrote : | #14 |
Same issue with cinnamon session.
wpa_supplicant dies:
root@x220:~# systemctl status wpa_supplicant
● wpa_supplicant.
Loaded: loaded (/lib/systemd/
Active: failed (Result: signal) since Tue 2016-05-24 18:17:46 EEST; 17h ago
Process: 1421 ExecStart=
Main PID: 1421 (code=killed, signal=KILL)
May 24 16:05:44 x220 wpa_supplicant[
May 24 16:05:44 x220 wpa_supplicant[
May 24 16:05:48 x220 wpa_supplicant[
May 24 16:05:48 x220 wpa_supplicant[
May 24 16:05:48 x220 wpa_supplicant[
May 24 16:05:49 x220 wpa_supplicant[
May 24 16:05:49 x220 wpa_supplicant[
May 24 18:17:46 x220 systemd[1]: wpa_supplicant.
May 24 18:17:46 x220 systemd[1]: wpa_supplicant.
May 24 18:17:46 x220 systemd[1]: wpa_supplicant.
Jason Robinson (jaywink) wrote : | #15 |
Seen on 16.04 with rtl8723be wifi driver, network-manager 1.2.0-0ubuntu0.
Jul 13 23:45:39 lenovo NetworkManager[
Jul 13 23:45:39 lenovo kernel: [ 406.193741] IPv6: ADDRCONF(
Jul 13 23:45:39 lenovo wpa_supplicant[
Jul 13 23:45:39 lenovo wpa_supplicant[
Jul 13 23:45:39 lenovo NetworkManager[
Jul 13 23:45:39 lenovo NetworkManager[
Jul 13 23:45:39 lenovo kernel: [ 406.242502] IPv6: ADDRCONF(
Jul 13 23:45:47 lenovo wpa_supplicant[
Jul 13 23:45:47 lenovo wpa_supplicant[
Jul 13 23:45:47 lenovo NetworkManager[
Jul 13 23:45:47 lenovo NetworkManager[
Jul 13 23:45:47 lenovo systemd[1]: Starting Load/Save RF Kill Switch Status...
Jul 13 23:45:47 lenovo systemd[1]: Started Load/Save RF Kill Switch Status.
Jul 13 23:45:47 lenovo wpa_supplicant[
Jul 13 23:45:51 lenovo NetworkManager[
Jul 13 23:45:51 lenovo kernel: [ 417.961786] IPv6: ADDRCONF(
Jul 13 23:45:51 lenovo wpa_supplicant[
Jul 13 23:45:51 lenovo wpa_supplicant[
Jul 13 23:45:51 lenovo NetworkManager[
Jul 13 23:45:51 lenovo kernel: [ 418.008598] IPv6: ADDRCONF(
Jul 13 23:45:51 lenovo NetworkManager[
Jul 13 23:45:51 lenovo wpa_supplicant[
Iiro Laiho (iiro) wrote : | #16 |
Happens sometimes, but not after every suspend, with BCM4313. It's sad to see this bug to be unfixed for so long.
Iiro Laiho (iiro) wrote : | #17 |
I discussed this thing on #ubuntu-devel. Apparently it has something to do with Broadcom WLAN chips or drivers as it seems to be unreproducible on Intel chips. Would it be possible to make Broadcom drivers unload before going to hibernate as it will help to avoid many problems?
User workaround: Create file /etc/pm/
Iiro Laiho (iiro) wrote : | #18 |
To add to the earlier comment, "brcmsmac" is the module name on my system when using the open source driver. It can also be b44, b43, b43legacy, ssb, brcmsmac or bcma, or with proprietary driver, wl.
Cavia Porcellus (caviaporcellus) wrote : | #19 |
Not sure if I'm commenting on the right bug, since I'm using Unity not XFCE, but I get this problem on two computers with Intel cards (both Intel Corporation Centrino Ultimate-N 6300). It happens maybe 1/10 times after resuming from suspend. This is on Ubuntu 16.04; there were no problems back with 14.04.
mthurston (c-mzrk-a) wrote : | #20 |
This seems similar to a bug that I am experiencing (1654730). Only 1 WiFi network is visible in network manager following resume from suspend. Running the command ``sudo iwlist scanning`` gets WiFi working again.
Does that fix this bug for you? If so, I will mark it as a duplicate.
Coomy Ted (pointy) wrote : | #21 |
Partial from logfile. Dell 5378 13 i7 KabyLake fresh re-install of Artful
Priority 3dbus:
Failed to construct signal
dbus: wpa_dbus_
(src/devices/
It's a shame that this bug has been around so long without fixes.
aleandro (aleandrodasilva) wrote : | #22 |
Bug is still present in ubuntu 18.04.
Dave Goldsbrough (daveg-k) wrote : | #23 |
I can confirm this is happening also in my recently installed 18.04 on Bell Latitude E6430
Using the logs tool I can see this
11:16:20 wpa_supplicant: dbus: fill_dict_
11:16:16 gdm-x-session: dbus-update-
11:16:02 wpa_supplicant: dbus: fill_dict_
11:16:02 wpa_supplicant: dbus: fill_dict_
11:15:58 wpa_supplicant: wlp3s0: CTRL-EVENT-
11:15:58 wpa_supplicant: wlp3s0: CTRL-EVENT-
11:15:58 wpa_supplicant: wlp3s0: Associated with 00:26:f2:29:d4:ac
11:15:58 wpa_supplicant: wlp3s0: Trying to associate with 00:26:f2:29:d4:ac (SSID='NETGEAR' freq=2447 MHz)
11:15:58 wpa_supplicant: wlp3s0: SME: Trying to authenticate with 00:26:f2:29:d4:ac (SSID='NETGEAR' freq=2447 MHz)
11:15:55 wpa_supplicant: dbus: fill_dict_
11:15:55 wpa_supplicant: dbus: Failed to construct signal
11:15:55 wpa_supplicant: dbus: wpa_dbus_
11:15:55 wpa_supplicant: dbus: fill_dict_
11:15:55 NetworkManager: <info> [1531304155.3344] supplicant: wpa_supplicant running
11:15:53 systemd: Started WPA supplicant.
11:15:52 wpa_supplicant: Successfully initialized wpa_supplicant
I am assuming that wifi is failing at boot but succeding after login. Is this a security feature or a bug?
Aluigi Teseo (pcxz) wrote : | #24 |
Same here in Desktop x64 and Raspberry pi3, Ubuntu Mate 18.04.01 ..still present.
ianwu (ianwu) wrote : | #25 |
Same here in Dell latitude 7480 Ubuntu 18.04.01 ..still present.
opik (babisayabundar) wrote : | #26 |
the bug still present in hpmini 110-3014tu on Ubuntu 18.04.01
WinEunuchs2Unix (ricklee518) wrote : | #27 |
Dell AW17R3, Skylake i7-6700HQ, nVidia GTX 970M, Thunderbolt USB-C, Ubuntu 16.04.5 LTS, Kernel 4.13-0-36-generic. Error appears with `journalctl --follow` whilst monitoring for unrelated error message tonight.
Complete log below:
$ journalctl --follow
-- Logs begin at Sat 2018-08-04 14:57:01 MDT. --
Sep 12 19:54:46 alien sudo[11861]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=
Sep 12 19:54:46 alien sudo[11861]: pam_unix(
Sep 12 19:54:46 alien sudo[11861]: pam_unix(
Sep 12 19:54:46 alien sudo[11858]: pam_unix(
Sep 12 19:55:46 alien sudo[15339]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c echo 654 | sudo tee /sys/class/
Sep 12 19:55:46 alien sudo[15339]: pam_unix(
Sep 12 19:55:46 alien sudo[15342]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=
Sep 12 19:55:46 alien sudo[15342]: pam_unix(
Sep 12 19:55:46 alien sudo[15342]: pam_unix(
Sep 12 19:55:46 alien sudo[15339]: pam_unix(
Sep 12 19:56:46 alien sudo[18777]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/sh -c echo 650 | sudo tee /sys/class/
Sep 12 19:56:46 alien sudo[18777]: pam_unix(
Sep 12 19:56:46 alien sudo[18780]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=
Sep 12 19:56:46 alien sudo[18780]: pam_unix(
Sep 12 19:56:46 alien sudo[18780]: pam_unix(
Sep 12 19:56:46 alien sudo[18777]: pam_unix(
Sep 12 19:59:00 alien wpa_supplicant[
Sep 12 19:59:00 alien wpa_supplicant[
Sep 12 20:00:01 alien CRON[30005]: pam_unix(
Sep 12 20:00:01 alien CRON[30006]: pam_unix(
Sep 12 20:00:01 alien CRON[30007]: (root) CMD (/sbin/fstrim /)
Sep 12 20:00:01 alien CRON[30008]: (root) CMD (/usr/bin/updatedb)
Sep 12 20:00:06 alien CRON[30006]: pam_unix(
Sep 12 20:00:06 alien CRON[30005]: pam_unix(
Sep 12 20:01:58 alien upowerd[1945]: (upowerd:1945): UPower-
Sep 12 20:05:00 alien wpa_supplicant[
ALinuxUser (buntulongername-new) wrote : | #28 |
Linux Mint 19. ThinkPad X1C6, on wifi.
`dbus: Failed to construct signal`, upon resumption from sleep.
ALinuxUser (buntulongername-new) wrote : | #29 |
Actually (cf. my comment above) the Manager does reconnect after sleep. However: a script of my disconnects weak networks, the idea being to allow connection to a stronger network. Yet, after the weak network is disconnected, there is no automatic connection to my stronger network (even though that network is known to the system and set to connect automatically).
I know it's bad form to ask this, but one does wonder: is any attention being paid to bugs in this area, save by those who suffer from them?
Demon (demonrx) wrote : | #30 |
This bug is still present: Using Ubuntu 16.04.6 with upgraded kernel v5.0.0-
syslog:
May 2 04:59:48 UbuntuHP wpa_supplicant[
May 2 04:59:48 UbuntuHP wpa_supplicant[
Demon (demonrx) wrote : | #31 |
Came across other possible causes/solutions:
https:/
Referencing an issue with linux's ecn setting:
default setting:
"net.ipv4.
changing it to:
"net.ipv4.
Wander Jose Rodriguez Betances (wanderjj23) wrote : | #32 |
dbus: failed to construct signal
guttermonk (guttermonk) wrote : | #33 |
Using Ubuntu 18.04 LTS on my desktop. From my journalctl -b:
wpa_supplicant[
wpa_supplicant[
wpa_supplicant[
wpa_supplicant[
journalctl useful log lines related to the wifi connection. This is NOT the full journalctl log
--------------- 757]: <info> wake requested (sleeping: yes enabled: yes) 757]: <info> waking up... 757]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] 757]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] 757]: <info> (eth0): preparing device 757]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] 757]: <info> (wlan0): preparing device 757]: <info> NetworkManager state is now DISCONNECTED 874]: dbus: wpa_dbus_ get_object_ properties: failed to get object properties: (none) none 874]: dbus: Failed to construct signal 757]: <warn> could not get interface properties: No readable properties in this interface. 757]: <info> (wlan0): supplicant interface state: starting -> ready 757]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant- available' ) [20 30 42] 757]: <warn> could not get interface properties: No readable properties in this interface. 874]: wlan0: CTRL-EVENT- SCAN-STARTED 757]: <info> Auto-activating connection 'NETGEAR-06'. 757]: <info> Activation (wlan0) starting connection 'NETGEAR-06' 757]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... 757]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started... 757]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] 757]: <info> NetworkManager state is now CONNECTING 757]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... 757]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. 757]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting... 757]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] 757]: <info> Activation (wlan0/wireless): access point 'NETGEAR-06' has security, but secrets are required.
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux kernel: r8169 0000:09:00.0 eth0: link down
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux wpa_supplicant[
apr 02 16:47:51 enrico-linux wpa_supplicant[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux NetworkManager[
apr 02 16:47:51 enrico-linux wpa_supplicant[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr 02 16:47:52 enrico-linux NetworkManager[
apr ...