wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'

Bug #1439771 reported by Enrico
272
This bug affects 57 people
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-generic x86_64
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)

Revision history for this message
Enrico (enricobe) wrote :
Revision history for this message
Enrico (enricobe) wrote :
Download full text (9.8 KiB)

journalctl useful log lines related to the wifi connection. This is NOT the full journalctl log

---------------
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> wake requested (sleeping: yes enabled: yes)
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> waking up...
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (eth0): preparing device
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
apr 02 16:47:51 enrico-linux kernel: r8169 0000:09:00.0 eth0: link down
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (wlan0): preparing device
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> NetworkManager state is now DISCONNECTED
apr 02 16:47:51 enrico-linux wpa_supplicant[874]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
apr 02 16:47:51 enrico-linux wpa_supplicant[874]: dbus: Failed to construct signal
apr 02 16:47:51 enrico-linux NetworkManager[757]: <warn> could not get interface properties: No readable properties in this interface.
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (wlan0): supplicant interface state: starting -> ready
apr 02 16:47:51 enrico-linux NetworkManager[757]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
apr 02 16:47:51 enrico-linux NetworkManager[757]: <warn> could not get interface properties: No readable properties in this interface.
apr 02 16:47:51 enrico-linux wpa_supplicant[874]: wlan0: CTRL-EVENT-SCAN-STARTED
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Auto-activating connection 'NETGEAR-06'.
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0) starting connection 'NETGEAR-06'
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> NetworkManager state is now CONNECTING
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
apr 02 16:47:52 enrico-linux NetworkManager[757]: <info> Activation (wlan0/wireless): access point 'NETGEAR-06' has security, but secrets are required.
apr ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
Changed in dbus (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Plurtu (plurtu) wrote :

I get this same dbus error but it does not prevent wifi from successfully reconnecting after sleep when testing with "systemctl suspend".

Revision history for this message
Plurtu (plurtu) wrote :

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.

https://wiki.ubuntu.com/SystemdForUpstartUsers

Revision history for this message
Enrico (enricobe) wrote :

Thank you very much Plurtu.
There will be a fix for the problem or we must always use upstart?

Revision history for this message
Jonathan Byrne (jonathan-yamame) wrote :

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.

Revision history for this message
Jonathan Byrne (jonathan-yamame) wrote :

Update: Using upstart instead of systemd made no difference: wired 802.1x still gets that failure.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Changed in systemd (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Denilson Sá (denilsonsa) wrote :

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-manager.

I have not tried too many variations, though; but I hope this helps reproducing the issue.

Revision history for this message
dumpstar (dumpstar) wrote :

Does this on Xubuntu 15.04 also.

Revision history for this message
Vindicator (vindicator) wrote :

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.service" (which was still active and running) brought back the wifi functionality.

$ journalctl -xe
*****
Jul 16 07:36:33 devx64 wpa_supplicant[1346]: rfkill: WLAN soft blocked
Jul 16 07:36:33 devx64 NetworkManager[1111]: <info> WiFi hardware radio set disabled
Jul 16 07:36:33 devx64 NetworkManager[1111]: <info> (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0]
Jul 16 07:36:33 devx64 NetworkManager[1111]: <info> (wlan0): deactivating device (reason 'none') [0]
Jul 16 07:36:33 devx64 NetworkManager[1111]: <info> WiFi now disabled by radio killswitch
Jul 16 07:37:02 devx64 NetworkManager[1111]: <info> WiFi hardware radio set enabled
Jul 16 07:37:02 devx64 NetworkManager[1111]: <info> WiFi now enabled by radio killswitch
Jul 16 07:37:02 devx64 wpa_supplicant[1346]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jul 16 07:37:02 devx64 wpa_supplicant[1346]: dbus: Failed to construct signal
Jul 16 07:37:02 devx64 NetworkManager[1111]: <warn> could not get interface properties: No readable properties in this interface.
Jul 16 07:37:02 devx64 NetworkManager[1111]: <info> (wlan0): supplicant interface state: starting -> ready
Jul 16 07:37:02 devx64 NetworkManager[1111]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [
Jul 16 07:37:02 devx64 NetworkManager[1111]: <warn> could not get interface properties: No readable properties in this interface.
*****

Revision history for this message
Martin Pitt (pitti) wrote :

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)
Revision history for this message
George Shuklin (george-shuklin) wrote :

Same issue with cinnamon session.

wpa_supplicant dies:

root@x220:~# systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled; vendor preset: enabled)
   Active: failed (Result: signal) since Tue 2016-05-24 18:17:46 EEST; 17h ago
  Process: 1421 ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant (code=killed, signal=KILL)
 Main PID: 1421 (code=killed, signal=KILL)
May 24 16:05:44 x220 wpa_supplicant[1421]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
May 24 16:05:44 x220 wpa_supplicant[1421]: dbus: Failed to construct signal
May 24 16:05:48 x220 wpa_supplicant[1421]: wlan0: SME: Trying to authenticate with 04:18:d6:13:ff:90 (SSID='A' freq=5240 MHz)
May 24 16:05:48 x220 wpa_supplicant[1421]: wlan0: Trying to associate with 04:18:d6:13:ff:90 (SSID='A' freq=5240 MHz)
May 24 16:05:48 x220 wpa_supplicant[1421]: wlan0: Associated with 04:18:d6:13:ff:90
May 24 16:05:49 x220 wpa_supplicant[1421]: wlan0: WPA: Key negotiation completed with 04:18:d6:13:ff:90 [PTK=CCMP GTK=CCMP]
May 24 16:05:49 x220 wpa_supplicant[1421]: wlan0: CTRL-EVENT-CONNECTED - Connection to 04:18:d6:13:ff:90 completed [id=0 id_str=]
May 24 18:17:46 x220 systemd[1]: wpa_supplicant.service: Main process exited, code=killed, status=9/KILL
May 24 18:17:46 x220 systemd[1]: wpa_supplicant.service: Unit entered failed state.
May 24 18:17:46 x220 systemd[1]: wpa_supplicant.service: Failed with result 'signal'.

Revision history for this message
Jason Robinson (jaywink) wrote :

Seen on 16.04 with rtl8723be wifi driver, network-manager 1.2.0-0ubuntu0.16.04.2. Happens no suspend/resume AND flight mode toggle. Worked around the suspend problem by making systemd restart network-manager service after suspend, which restores network connections.

Jul 13 23:45:39 lenovo NetworkManager[2544]: <info> [1468442739.4325] manager: WiFi now enabled by radio killswitch
Jul 13 23:45:39 lenovo kernel: [ 406.193741] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Jul 13 23:45:39 lenovo wpa_supplicant[1101]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jul 13 23:45:39 lenovo wpa_supplicant[1101]: dbus: Failed to construct signal
Jul 13 23:45:39 lenovo NetworkManager[2544]: <info> [1468442739.9209] device (wlp4s0): supplicant interface state: starting -> ready
Jul 13 23:45:39 lenovo NetworkManager[2544]: <info> [1468442739.9210] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 13 23:45:39 lenovo kernel: [ 406.242502] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Jul 13 23:45:47 lenovo wpa_supplicant[1101]: rfkill: WLAN soft blocked
Jul 13 23:45:47 lenovo wpa_supplicant[1101]: rfkill: WLAN soft blocked
Jul 13 23:45:47 lenovo NetworkManager[2544]: <info> [1468442747.0170] manager: WiFi now disabled by radio killswitch
Jul 13 23:45:47 lenovo NetworkManager[2544]: <info> [1468442747.0173] device (wlp4s0): state change: disconnected -> unavailable (reason 'none') [30 20 0]
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[1101]: nl80211: deinit ifname=wlp4s0 disabled_11b_rates=0
Jul 13 23:45:51 lenovo NetworkManager[2544]: <info> [1468442751.1801] manager: WiFi now enabled by radio killswitch
Jul 13 23:45:51 lenovo kernel: [ 417.961786] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Jul 13 23:45:51 lenovo wpa_supplicant[1101]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jul 13 23:45:51 lenovo wpa_supplicant[1101]: dbus: Failed to construct signal
Jul 13 23:45:51 lenovo NetworkManager[2544]: <info> [1468442751.6681] device (wlp4s0): supplicant interface state: starting -> ready
Jul 13 23:45:51 lenovo kernel: [ 418.008598] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
Jul 13 23:45:51 lenovo NetworkManager[2544]: <info> [1468442751.6683] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Jul 13 23:45:51 lenovo wpa_supplicant[1101]: rfkill: WLAN soft blocked

Revision history for this message
Iiro Laiho (iiro) wrote :

Happens sometimes, but not after every suspend, with BCM4313. It's sad to see this bug to be unfixed for so long.

Revision history for this message
Iiro Laiho (iiro) wrote :

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/config.d/unload_module and put "SUSPEND_MODULES="brcmsmac" into it.

Revision history for this message
Iiro Laiho (iiro) wrote :

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.

Revision history for this message
Cavia Porcellus (caviaporcellus) wrote :

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.

Revision history for this message
mthurston (c-mzrk-a) wrote :

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.

Revision history for this message
Coomy Ted (pointy) wrote :

Partial from logfile. Dell 5378 13 i7 KabyLake fresh re-install of Artful

Priority 3dbus:

Failed to construct signal

dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
(src/devices/nm-device.c:1452)): assertion '<dropped>' failed

It's a shame that this bug has been around so long without fixes.

Revision history for this message
aleandro (aleandrodasilva) wrote :

Bug is still present in ubuntu 18.04.

Revision history for this message
Dave Goldsbrough (daveg-k) wrote :

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_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
11:16:16 gdm-x-session: dbus-update-activation-environment: setting WINDOWPATH=2
11:16:02 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
11:16:02 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
11:15:58 wpa_supplicant: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
11:15:58 wpa_supplicant: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 00:26:f2:29:d4:ac completed [id=0 id_str=]
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_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
11:15:55 wpa_supplicant: dbus: Failed to construct signal
11:15:55 wpa_supplicant: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
11:15:55 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
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?

Revision history for this message
Aluigi Teseo (pcxz) wrote :

Same here in Desktop x64 and Raspberry pi3, Ubuntu Mate 18.04.01 ..still present.

Revision history for this message
ianwu (ianwu) wrote :

Same here in Dell latitude 7480 Ubuntu 18.04.01 ..still present.

Revision history for this message
opik (babisayabundar) wrote :

the bug still present in hpmini 110-3014tu on Ubuntu 18.04.01

Revision history for this message
WinEunuchs2Unix (ricklee518) wrote :
Download full text (4.8 KiB)

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=/usr/bin/tee /sys/class/backlight/intel_backlight/brightness
Sep 12 19:54:46 alien sudo[11861]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 12 19:54:46 alien sudo[11861]: pam_unix(sudo:session): session closed for user root
Sep 12 19:54:46 alien sudo[11858]: pam_unix(sudo:session): session closed for user root
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/backlight/intel_backlight/brightness
Sep 12 19:55:46 alien sudo[15339]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 12 19:55:46 alien sudo[15342]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/tee /sys/class/backlight/intel_backlight/brightness
Sep 12 19:55:46 alien sudo[15342]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 12 19:55:46 alien sudo[15342]: pam_unix(sudo:session): session closed for user root
Sep 12 19:55:46 alien sudo[15339]: pam_unix(sudo:session): session closed for user root
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/backlight/intel_backlight/brightness
Sep 12 19:56:46 alien sudo[18777]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 12 19:56:46 alien sudo[18780]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/tee /sys/class/backlight/intel_backlight/brightness
Sep 12 19:56:46 alien sudo[18780]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 12 19:56:46 alien sudo[18780]: pam_unix(sudo:session): session closed for user root
Sep 12 19:56:46 alien sudo[18777]: pam_unix(sudo:session): session closed for user root
Sep 12 19:59:00 alien wpa_supplicant[1399]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE
Sep 12 19:59:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal
Sep 12 20:00:01 alien CRON[30005]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 12 20:00:01 alien CRON[30006]: pam_unix(cron:session): session opened for user root by (uid=0)
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(cron:session): session closed for user root
Sep 12 20:00:06 alien CRON[30005]: pam_unix(cron:session): session closed for user root
Sep 12 20:01:58 alien upowerd[1945]: (upowerd:1945): UPower-Linux-WARNING **: treating change event as add on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.2/0003:046D:C52B.0005/0003:046D:2010.0009/power_supply/hidpp_battery_3
Sep 12 20:05:00 alien wpa_supplicant[1399]: dbus: wpa_dbus_get_object_properties: fail...

Read more...

Revision history for this message
ALinuxUser (buntulongername-new) wrote :

Linux Mint 19. ThinkPad X1C6, on wifi.

`dbus: Failed to construct signal`, upon resumption from sleep.

Revision history for this message
ALinuxUser (buntulongername-new) wrote :

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?

Revision history for this message
Demon (demonrx) wrote :

This bug is still present: Using Ubuntu 16.04.6 with upgraded kernel v5.0.0-050000-generic

syslog:

May 2 04:59:48 UbuntuHP wpa_supplicant[1879]: dbus: wpa_dbus_get_object_properties: failed to get
                object properties: (none) none

May 2 04:59:48 UbuntuHP wpa_supplicant[1879]: dbus: Failed to construct signal

Revision history for this message
Demon (demonrx) wrote :

Came across other possible causes/solutions:

https://www.linuxquestions.org/questions/linux-networking-3/wifi-drops-in-and-out-when-on-campus-and-at-home-4175642548/

https://github.com/systemd/systemd/issues/9748

Referencing an issue with linux's ecn setting:

default setting:
"net.ipv4.tcp_ecn=2"

changing it to:
"net.ipv4.tcp_ecn=0"

Revision history for this message
Wander Jose Rodriguez Betances (wanderjj23) wrote :

dbus: failed to construct signal

Revision history for this message
guttermonk (guttermonk) wrote :

Using Ubuntu 18.04 LTS on my desktop. From my journalctl -b:

wpa_supplicant[6756]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=
wpa_supplicant[6756]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
wpa_supplicant[6756]: dbus: Failed to construct signal
wpa_supplicant[6756]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.