Bug#756847: wpasupplicant: systemd wpa_supplicant.service wrong behavior on target isolate
Package: wpasupplicant Followup-For: Bug #756847 Dear Maintainer, It seems that systemd is not working properly when it switches from rescue mode to another target: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693522 It is not a wpasupplicant package issue. Best -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756847: wpasupplicant: systemd wpa_supplicant.service wrong behavior on target isolate
Package: wpasupplicant Version: 1.1-1 Severity: normal Dear Maintainer, I switched from sysvinit to systemd in Debian Jessie. I created a personalized systemd target similar to graphical.target, just adding some Conflicts directives in order to stop some daemons (mysql and apache2). When I switch from graphical.target to personalized.target and vice-versa (using systemctl isolate name.target), everything works fine, except that WiFi connection in Gnome3 Network Manager drops and then restart. Syslog reports that it is wpa_supplicant.service that stops and then restarts. I think that it is not a desiderable behaviour of wpa_supplicant.service, unless it is explicitly stopped by a target. I tried to edit wpa_supplicant.service configuration: 1) I created a wpa_supplicant.service.d directory in /etc/systemd/system 2) I edited a personalized.conf file in it, in which I added the following 2 lines: [Unit] IgnoreOnIsolate=true 3) Then I restarted daemons and reloaded wpa_supplicant.service 4) systemd-delta reports that wpa_supplicant.service has been EXTENDED 5) switching from graphical.target to my personalize.target works fine, Wifi connection is not stopped. 6) errors happens when I switch to rescue.target and then back to graphical or personalized targets: - rescue shell is not closed - gnome3 doesn't load properly (just shows desktop image, but no login window) - I need to force a reboot - I suspect that it is an issue related to DBus (I am not an expert.) Do you think it is possible to fix wpa_supplicant.service ? thanks -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wpasupplicant depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.2 ii libc6 2.19-7 ii libdbus-1-3 1.8.6-1 ii libnl-3-200 3.2.24-2 ii libnl-genl-3-200 3.2.24-2 ii libpcsclite1 1.8.11-3 ii libreadline6 6.3-6 ii libssl1.0.0 1.0.1h-3 ii lsb-base 4.1+Debian13 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl none pn wpaguinone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756847: [pkg-wpa-devel] Bug#756847: wpasupplicant: systemd wpa_supplicant.service wrong behavior on target isolate
Control: tags -1 moreinfo Control: tags -1 help Hi On Saturday 02 August 2014, debianizzato wrote: Package: wpasupplicant Version: 1.1-1 Severity: normal Dear Maintainer, I switched from sysvinit to systemd in Debian Jessie. I created a personalized systemd target similar to graphical.target, just adding some Conflicts directives in order to stop some daemons (mysql and apache2). When I switch from graphical.target to personalized.target and vice-versa (using systemctl isolate name.target), everything works fine, except that WiFi connection in Gnome3 Network Manager drops and then restart. Syslog reports that it is wpa_supplicant.service that stops and then restarts. I think that it is not a desiderable behaviour of wpa_supplicant.service, unless it is explicitly stopped by a target. I tried to edit wpa_supplicant.service configuration: 1) I created a wpa_supplicant.service.d directory in /etc/systemd/system 2) I edited a personalized.conf file in it, in which I added the following 2 lines: [Unit] IgnoreOnIsolate=true 3) Then I restarted daemons and reloaded wpa_supplicant.service 4) systemd-delta reports that wpa_supplicant.service has been EXTENDED 5) switching from graphical.target to my personalize.target works fine, Wifi connection is not stopped. 6) errors happens when I switch to rescue.target and then back to graphical or personalized targets: - rescue shell is not closed - gnome3 doesn't load properly (just shows desktop image, but no login window) - I need to force a reboot - I suspect that it is an issue related to DBus (I am not an expert.) Do you think it is possible to fix wpa_supplicant.service ? thanks [...] $ cat /lib/systemd/system/wpa_supplicant.service [Unit] Description=WPA supplicant [Service] Type=dbus BusName=fi.epitest.hostap.WPASupplicant ExecStart=/sbin/wpa_supplicant -u -s -O /run/wpa_supplicant [Install] WantedBy=multi-user.target Alias=dbus-fi.epitest.hostap.WPASupplicant.service These are the full contents of said systemd unit, which looks sensible to me. I guess what happens in your case is not really wpasupplicant restarting, but the frontend driving it triggering the connection reset via DBUS, which could be the case of network-manager interacting with the graphical.target. Are you using network-manager - and if you do, are your wlan connections configured as system connections or user connections, the later are (afaik) bound to your logind console session and may stop (or restart) if you log out. Configuring these as system connections might provide further data points. Alternatively you could test what happens with different frontends for wpasupplicant, in particular the native ifupdown integration - which should be excempt from these problems. As these advanced aspects of systemd customisations are still rather new to me, I would suggest to solicit assistance from the systemd maintainers. Regards Stefan Lippers-Hollmann signature.asc Description: This is a digitally signed message part.
