Bug 1304068

Summary: wpa_supplicant.service is started even if no wireless network is present
Product: [Fedora] Fedora Reporter: Christian Stadelmann <fedora>
Component: wpa_supplicantAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: blueowl, dcbw, lkundrak
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-05 22:05:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Christian Stadelmann 2016-02-02 19:25:06 UTC 
Description of problem:
No matter whether a wireless network is present and thus no matter whether wpa_supplicant is needed, it will always be started on boot. We don't need unnecessary code running.

Version-Release number of selected component (if applicable):
wpa_supplicant-2.4-7.fc23.x86_64
systemd-222-14.fc23.x86_64

How reproducible:
always, see .service file
Comment 1 Blueowl 2017-11-01 13:20:14 UTC 
Do you still see the behaviour in Fedora 26?

Tips:
* disable wpa_supplicant service
* wpa_supplicant service can be activated via D-Bus even if it is disabled.
  NetworkManager starts wpa_supplicant when it is needed. Note that
  wpa_supplicant is not only used for Wi-Fi, but also for 802.1X, that can
  be used even for Ethernet.
* look at the journal when/how wpa_supplicant was started
Comment 2 Christian Stadelmann 2017-11-05 22:05:52 UTC 
I'm on a wireless network now, so the situation has changed.

(In reply to Blueowl from comment #1)
> Tips:
> […]
> * wpa_supplicant service can be activated via D-Bus even if it is disabled.
>   NetworkManager starts wpa_supplicant when it is needed. Note that
>   wpa_supplicant is not only used for Wi-Fi, but also for 802.1X, that can
>   be used even for Ethernet.

Looks like that was the explanation I did not expect. Thanks!