[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
dbus: failed to construct signal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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" ** Bug watch added: github.com/systemd/systemd/issues #9748 https://github.com/systemd/systemd/issues/9748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
This bug is still present: Using Ubuntu 16.04.6 with upgraded kernel v5.0.0-05-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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Linux Mint 19. ThinkPad X1C6, on wifi. `dbus: Failed to construct signal`, upon resumption from sleep. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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/pci:00/: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: failed to get object properties: (org.freedesktop.DBus.Error.Failed) failed to parse RSN IE Sep 12 20:05:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal Sep 12 20:15:01 alien CRON[18052]: pam_unix(cron:session): session opened for user root by (uid=0) Sep 12 20:15:01 alien CRON[18053]: (root) CMD (/usr/bin/updatedb) Sep 12 20:15:06 alien CRON[18052]: pam_unix(cron:session): session closed for user root Sep 12 20:17: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 20:17:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal Sep 12 20:17:01 alien CRON[24974]: pam_unix(cron:session): session opened for user root by (uid=0) Sep 12 20:17:01 alien CRON[24975]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Sep 12 20:17:01 alien CRON[24974]: pam_unix(cron:session): session closed for user root Sep 12 20:23: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 20:23:00 alien wpa_supplicant[1399]: dbus: Failed to construct signal Sep 12 20:28:33 alien upowerd[1945]: (upowerd:1945): UPower-Linux-WARNING **: treating change event as add on /sys/devices/pci:00/: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:30:01 alien CRON[6024]: pam_unix(cron:session): session opened for user root by (uid=0) Sep 12 20:30:01 alien CRON[6025]: (root) CMD (/usr/bin/updatedb) Sep 12 20:30:06 alien CRON[6024]: pam_unix(cron:session): session closed for user root -- You received this bug notification because you are a member of Ubunt
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
the bug still present in hpmini 110-3014tu on Ubuntu 18.04.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Same here in Dell latitude 7480 Ubuntu 18.04.01 ..still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Same here in Desktop x64 and Raspberry pi3, Ubuntu Mate 18.04.01 ..still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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: [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? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Bug is still present in ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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 '' failed It's a shame that this bug has been around so long without fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Happens sometimes, but not after every suspend, with BCM4313. It's sad to see this bug to be unfixed for so long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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]: [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]: [1468442739.9209] device (wlp4s0): supplicant interface state: starting -> ready Jul 13 23:45:39 lenovo NetworkManager[2544]: [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]: [1468442747.0170] manager: WiFi now disabled by radio killswitch Jul 13 23:45:47 lenovo NetworkManager[2544]: [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]: [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]: [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]: [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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
This sounds similar to bug 1270257, but that was closed due to getting too much noise. ** Package changed: dbus (Ubuntu) => network-manager (Ubuntu) ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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[]: WiFi hardware radio set disabled Jul 16 07:36:33 devx64 NetworkManager[]: (wlan0): device state change: disconnected -> unavailable (reason 'none') [30 20 0] Jul 16 07:36:33 devx64 NetworkManager[]: (wlan0): deactivating device (reason 'none') [0] Jul 16 07:36:33 devx64 NetworkManager[]: WiFi now disabled by radio killswitch Jul 16 07:37:02 devx64 NetworkManager[]: WiFi hardware radio set enabled Jul 16 07:37:02 devx64 NetworkManager[]: 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[]: could not get interface properties: No readable properties in this interface. Jul 16 07:37:02 devx64 NetworkManager[]: (wlan0): supplicant interface state: starting -> ready Jul 16 07:37:02 devx64 NetworkManager[]: (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [ Jul 16 07:37:02 devx64 NetworkManager[]: could not get interface properties: No readable properties in this interface. * -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Does this on Xubuntu 15.04 also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Update: Using upstart instead of systemd made no difference: wired 802.1x still gets that failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Thank you very much Plurtu. There will be a fix for the problem or we must always use upstart? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
I get this same dbus error but it does not prevent wifi from successfully reconnecting after sleep when testing with "systemctl suspend". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
** Changed in: dbus (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
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]: wake requested (sleeping: yes enabled: yes) apr 02 16:47:51 enrico-linux NetworkManager[757]: waking up... apr 02 16:47:51 enrico-linux NetworkManager[757]: (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] apr 02 16:47:51 enrico-linux NetworkManager[757]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] apr 02 16:47:51 enrico-linux NetworkManager[757]: (eth0): preparing device apr 02 16:47:51 enrico-linux NetworkManager[757]: (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] apr 02 16:47:51 enrico-linux kernel: r8169 :09:00.0 eth0: link down apr 02 16:47:51 enrico-linux NetworkManager[757]: (wlan0): preparing device apr 02 16:47:51 enrico-linux NetworkManager[757]: 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]: could not get interface properties: No readable properties in this interface. apr 02 16:47:51 enrico-linux NetworkManager[757]: (wlan0): supplicant interface state: starting -> ready apr 02 16:47:51 enrico-linux NetworkManager[757]: (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] apr 02 16:47:51 enrico-linux NetworkManager[757]: 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]: Auto-activating connection 'NETGEAR-06'. apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) starting connection 'NETGEAR-06' apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... apr 02 16:47:52 enrico-linux NetworkManager[757]: (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] apr 02 16:47:52 enrico-linux NetworkManager[757]: NetworkManager state is now CONNECTING apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... apr 02 16:47:52 enrico-linux NetworkManager[757]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0/wireless): access point 'NETGEAR-06' has security, but secrets are required. apr 02 16:47:52 enrico-linux NetworkManager[757]: (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. apr 02 16:47:52 enrico-linux NetworkManager[757]: (wlan0): supplicant interface state: ready -> inactive apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... apr 02 16:47:52 enrico-linux NetworkManager[757]: (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... apr 02 16:47:52 enrico-linux NetworkManager[757]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0/wireless): connection 'NETGEAR-06' has security, and secrets exist. No new secrets needed. apr 02 16:47:52 enrico-linux NetworkManager[757]: Config: added 'ssid' value 'NETGEAR-06' apr 02 16:47:52 enrico-linux NetworkManager[757]: Config: added 'scan_ssid' value '1' apr 02 16:47:52 enrico-linux NetworkManager[757]: Config: added 'key_mgmt' value 'WPA-PSK' apr 02 16:47:52 enrico-linux NetworkManager[757]: Config: added 'auth_alg' value 'OPEN' apr 02 16:47:52 enrico-linux NetworkManager[757]: Config: added 'psk' value '' apr 02 16:47:52 enrico-linux NetworkManager[757]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. apr 02 16:47:52 enrico-li
