Arch Linux

abd29

Member

Registered: 2015-04-29

Posts: 4

[SOLVED]restarting gnome kills wpa_supplicant

Whenever gnome shell is restarted it kills wpa_supplicant and (most of the time) does not start it again until I restart gnome once again.
This causes automatic connection problem on boot,like if I am already connected to wifi on login screen ,then as soon as I login it disconnects from wifi and connects again in around 15 secs. Here are logs of NetworkManager & wpa_supplicant ,please help in fixing same.

 
Apr 29 21:32:37 arch NetworkManager[363]: <info>  wpa_supplicant stopped
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): supplicant interface state: completed -> down
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): device state change: activated -> unavailable (reason 'supplicant-failed') [100 20 10]
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): deactivating device (reason 'supplicant-failed') [10]
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): canceled DHCP transaction, DHCP client pid 6405
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): DHCPv4 state changed bound -> done
Apr 29 21:32:37 arch NetworkManager[363]: <info>  Removing DNS information from /usr/bin/resolvconf
Apr 29 21:32:37 arch NetworkManager[363]: <info>  NetworkManager state is now CONNECTED_LOCAL
Apr 29 21:32:37 arch NetworkManager[363]: <info>  NetworkManager state is now DISCONNECTED
Apr 29 21:32:37 arch NetworkManager[363]: <info>  wpa_supplicant started
Apr 29 21:32:37 arch NetworkManager[363]: <info>  wpa_supplicant stopped
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): supplicant interface state: starting -> down
Apr 29 21:32:37 arch NetworkManager[363]: <info>  wpa_supplicant started
Apr 29 21:32:37 arch NetworkManager[363]: <info>  wpa_supplicant stopped
Apr 29 21:32:37 arch NetworkManager[363]: <info>  (wlp2s0): supplicant interface state: starting -> down
Apr 29 21:32:37 arch NetworkManager[363]: <info>  wpa_supplicant die count 3; ignoring for 10 seconds
Apr 29 21:32:37 arch NetworkManager[363]: <warn>  Unexpected error requesting supplicant properties: (4) Message did not receive a reply (timeout by message bus)
Apr 29 21:32:37 arch NetworkManager[363]: <warn>  Unexpected error requesting supplicant properties: (4) Message did not receive a reply (timeout by message bus)
Apr 29 21:32:48 arch NetworkManager[363]: <info>  wpa_supplicant die count reset 

Apr 29 22:02:03 arch wpa_supplicant[7182]: process 7182: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2681.
Apr 29 22:02:03 arch wpa_supplicant[7182]: This is normally a bug in some application using the D-Bus library.
Apr 29 22:02:03 arch wpa_supplicant[7182]: D-Bus not built with -rdynamic so unable to print a backtrace
Apr 29 22:02:03 arch systemd[1]: wpa_supplicant.service: main process exited, code=dumped, status=6/ABRT
Apr 29 22:02:03 arch systemd[1]: Unit wpa_supplicant.service entered failed state.
Apr 29 22:02:03 arch systemd[1]: wpa_supplicant.service failed.
Apr 29 22:02:03 arch systemd[1]: Starting WPA supplicant...
Apr 29 22:02:03 arch systemd-coredump[7491]: Process 7182 (wpa_supplicant) of user 0 dumped core.
Apr 29 22:02:03 arch systemd[1]: Started WPA supplicant.
Apr 29 22:02:03 arch systemd[1]: wpa_supplicant.service: main process exited, code=dumped, status=6/ABRT
Apr 29 22:02:03 arch systemd[1]: Unit wpa_supplicant.service entered failed state.
Apr 29 22:02:03 arch systemd[1]: wpa_supplicant.service failed.
Apr 29 22:02:03 arch systemd[1]: Starting WPA supplicant...
Apr 29 22:02:03 arch systemd-coredump[7539]: Process 7494 (wpa_supplicant) of user 0 dumped core.
Apr 29 22:02:03 arch systemd[1]: Started WPA supplicant.
Apr 29 22:02:03 arch systemd-coredump[7553]: Process 7542 (wpa_supplicant) of user 0 dumped core.
Apr 29 22:02:03 arch systemd[1]: wpa_supplicant.service: main process exited, code=dumped, status=6/ABRT
Apr 29 22:02:03 arch systemd[1]: Unit wpa_supplicant.service entered failed state.
Apr 29 22:02:03 arch systemd[1]: wpa_supplicant.service failed.
Apr 29 22:02:03 arch wpa_supplicant[7494]: Successfully initialized wpa_supplicant
Apr 29 22:02:03 arch wpa_supplicant[7494]: Could not read interface p2p-dev-wlp2s0 flags: No such device
Apr 29 22:02:03 arch wpa_supplicant[7494]: process 7494: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2681.
Apr 29 22:02:03 arch wpa_supplicant[7494]: This is normally a bug in some application using the D-Bus library.
Apr 29 22:02:03 arch wpa_supplicant[7494]: D-Bus not built with -rdynamic so unable to print a backtrace
Apr 29 22:02:03 arch wpa_supplicant[7542]: Successfully initialized wpa_supplicant
Apr 29 22:02:03 arch wpa_supplicant[7542]: Could not read interface p2p-dev-wlp2s0 flags: No such device
Apr 29 22:02:03 arch wpa_supplicant[7542]: process 7542: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2681.
Apr 29 22:02:03 arch wpa_supplicant[7542]: This is normally a bug in some application using the D-Bus library.
Apr 29 22:02:03 arch wpa_supplicant[7542]: D-Bus not built with -rdynamic so unable to print a backtrace

Last edited by abd29 (2015-04-30 02:27:05)

bendavis78

Member

Registered: 2014-06-21

Posts: 41

Re: [SOLVED]restarting gnome kills wpa_supplicant

I'm  seeing this same problem. wpa_supplicant fails even when I try to restart it.

Apr 29 11:51:33 chromebook wpa_supplicant[862]: Successfully initialized wpa_supplicant
Apr 29 11:51:33 chromebook systemd[1]: Started WPA supplicant.
Apr 29 11:51:33 chromebook wpa_supplicant[862]: Could not read interface p2p-dev-wlp1s0 flags: No such device
Apr 29 11:51:33 chromebook wpa_supplicant[862]: process 862: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_path (*string_p)" failed in file dbus-message.c line 2681.
Apr 29 11:51:33 chromebook wpa_supplicant[862]: This is normally a bug in some application using the D-Bus library.
Apr 29 11:51:33 chromebook wpa_supplicant[862]: D-Bus not built with -rdynamic so unable to print a backtrace
Apr 29 11:51:33 chromebook systemd-coredump[880]: Process 862 (wpa_supplicant) of user 0 dumped core.
Apr 29 11:51:33 chromebook systemd[1]: wpa_supplicant.service: main process exited, code=dumped, status=6/ABRT
Apr 29 11:51:33 chromebook systemd[1]: Unit wpa_supplicant.service entered failed state.
Apr 29 11:51:33 chromebook systemd[1]: wpa_supplicant.service failed.

Last edited by bendavis78 (2015-04-29 19:56:12)

NCordon

Member

Registered: 2015-04-29

Posts: 2

Re: [SOLVED]restarting gnome kills wpa_supplicant

The same problem is happening to me.

NCordon

Member

Registered: 2015-04-29

Posts: 2

Re: [SOLVED]restarting gnome kills wpa_supplicant

I've been giving a glimpse at /var/log/pacman.log. It seems that wpa_supplicant got upgraded for me a few days before.

I've downgraded it to its previous version (2.3-1) and everything is working just fine after reboot. Must be an error in new version.

Last edited by NCordon (2015-04-29 22:38:24)

abd29

Member

Registered: 2015-04-29

Posts: 4

Re: [SOLVED]restarting gnome kills wpa_supplicant

@Ncordon Thanks this solved the problem.
I just installed arch this sunday and used  2.4.1 only,I was thinking may be gnome/networkmanager service not configured properly.
now I think official repository has also downgraded/upgraded  wpa_supplicant to 1:2.3.1

Last edited by abd29 (2015-04-30 02:30:26)