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
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
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:
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]:
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
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:
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
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
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'
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
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:
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
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
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
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
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
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:
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]:
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
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
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
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)
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
** 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'
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:
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.
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
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
** 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
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
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
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:
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:
** 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
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
35 matches
Mail list logo
