wpa supplicant problems

krischan941 · 2019-04-14 00:58:08

Hello,

I was tinkering around with some Desktop Environments (installed Gnome and Plasma) and stucked with Plasma/KDE. Problem is that I'm not able to connect via wifi anymore. Cable without problems.

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:90:f5:ed:b8:a2 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether 12:c9:13:2b:7c:a2 brd ff:ff:ff:ff:ff:ff

wpa_supplicant.service - WPA supplicant
   Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2019-04-14 02:43:54 CEST; 4min 39s ago
 Main PID: 668 (wpa_supplicant)
    Tasks: 1 (limit: 4915)
   Memory: 7.2M
   CGroup: /system.slice/wpa_supplicant.service
           └─668 /usr/bin/wpa_supplicant -u

Apr 14 02:45:07 krischanStudios wpa_supplicant[668]: Line 0: Invalid passphrase character
Apr 14 02:45:07 krischanStudios wpa_supplicant[668]: wlp3s0: Reject scan trigger since one is already pending
Apr 14 02:45:08 krischanStudios wpa_supplicant[668]: Line 0: Invalid passphrase character
Apr 14 02:45:09 krischanStudios wpa_supplicant[668]: wlp3s0: Reject scan trigger since one is already pending
Apr 14 02:45:09 krischanStudios wpa_supplicant[668]: Line 0: Invalid passphrase character
Apr 14 02:45:10 krischanStudios wpa_supplicant[668]: wlp3s0: Reject scan trigger since one is already pending
Apr 14 02:45:11 krischanStudios wpa_supplicant[668]: Line 0: Invalid passphrase character
Apr 14 02:45:11 krischanStudios wpa_supplicant[668]: wlp3s0: Reject scan trigger since one is already pending
Apr 14 02:48:15 krischanStudios wpa_supplicant[668]: Line 0: Invalid passphrase character
Apr 14 02:48:15 krischanStudios wpa_supplicant[668]: wlp3s0: Reject scan trigger since one is already pending

Thanks in advance

Trilby · 2019-04-14 02:51:07

As you installed and likely enabled network manager and/or other tools, those are most likely interfering. This is the most common cause of networking issues on these forums.

The most common steps to diagnose / solve such problems is to check what services are running / enabled, disable all of them, then follow the manual connection steps in the wiki to determine if/where there is a problem.

krischan941 · 2019-04-15 01:14:16

Okay. I purged all other DEs and their configs. I checked my services and when I want to enable dhcpcd for my wifi device with "systemctl start dhcpcd@wlp3s0" I get the following:

systemctl status dhcpcd@wlp3s0.service
   dhcpcd@wlp3s0.service - dhcpcd on wlp3s0
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd@.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2019-04-15 02:51:44 CEST; 25s ago
  Process: 2454 ExecStart=/usr/bin/dhcpcd -q -w wlp3s0 (code=exited, status=1/FAILURE)

Apr 15 02:51:14 krischanStudios systemd[1]: Starting dhcpcd on wlp3s0...
Apr 15 02:51:14 krischanStudios dhcpcd[2454]: wlp3s0: waiting for carrier
Apr 15 02:51:44 krischanStudios dhcpcd[2454]: timed out
Apr 15 02:51:44 krischanStudios dhcpcd[2454]: timed out
Apr 15 02:51:44 krischanStudios systemd[1]: dhcpcd@wlp3s0.service: Control process exited, code=exited, status=1/FAILURE
Apr 15 02:51:44 krischanStudios dhcpcd[2454]: dhcpcd exited
Apr 15 02:51:44 krischanStudios systemd[1]: dhcpcd@wlp3s0.service: Failed with result 'exit-code'.
Apr 15 02:51:44 krischanStudios systemd[1]: Failed to start dhcpcd on wlp3s0.

journalctl -xe:

A start job for unit dhcpcd@wlp3s0.service has begun execution.
-- 
-- The job identifier is 1579.
Apr 15 03:01:31 krischanStudios dhcpcd[2758]: wlp3s0: waiting for carrier
Apr 15 03:01:35 krischanStudios plasmashell[1205]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12427, resource id: 88080391, major code: 142 (Unknown), minor code: 3
Apr 15 03:01:38 krischanStudios plasmashell[1205]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12511, resource id: 88080391, major code: 142 (Unknown), minor code: 3
Apr 15 03:01:46 krischanStudios dbus-daemon[783]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.8' (uid=0 pid=793 comm="/usr/bin/NetworkManager --no-daemon ")
Apr 15 03:01:46 krischanStudios dbus-daemon[783]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Apr 15 03:01:47 krischanStudios plasmashell[1205]: qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 12659, resource id: 69206032, major code: 142 (Unknown), minor code: 3
Apr 15 03:02:02 krischanStudios dhcpcd[2758]: timed out
Apr 15 03:02:02 krischanStudios dhcpcd[2758]: timed out
Apr 15 03:02:02 krischanStudios systemd[1]: dhcpcd@wlp3s0.service: Control process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- An ExecStart= process belonging to unit dhcpcd@wlp3s0.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Apr 15 03:02:02 krischanStudios dhcpcd[2758]: dhcpcd exited
Apr 15 03:02:02 krischanStudios systemd[1]: dhcpcd@wlp3s0.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- The unit dhcpcd@wlp3s0.service has entered the 'failed' state with result 'exit-code'.
Apr 15 03:02:02 krischanStudios systemd[1]: Failed to start dhcpcd on wlp3s0.
-- Subject: A start job for unit dhcpcd@wlp3s0.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- A start job for unit dhcpcd@wlp3s0.service has finished with a failure.
-- 
-- The job identifier is 1579 and the job result is failed.
Apr 15 03:02:02 krischanStudios audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp3s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 15 03:02:02 krischanStudios kernel: audit: type=1130 audit(1555290122.003:61): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=dhcpcd@wlp3s0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 15 03:02:02 krischanStudios sudo[2755]: pam_unix(sudo:session): session closed for user root

I don't know what else I can do. Thanks

Last edited by krischan941 (2019-04-15 01:15:54)

Head_on_a_Stick · 2019-04-15 06:24:20

krischan941 wrote:

I checked my services

How?

Please share your method and results.

I would use

systemctl list-unit-files --state=enabled

Or perhaps

ls -lR /etc/systemd/system

seth · 2019-04-15 06:42:50

Also w/o a hook, dhcpcd won't require wpa_supplicant, thus you got no carrier.
https://wiki.archlinux.org/index.php/Dhcpcd#Hooks

Please post a complete "sudo journal -b"…

krischan941 · 2019-04-16 02:42:35

Okay, my goal is to be able to connect wifi via networkmanager in Plasma. What I did so far:

disableing any network-services.

reading https://wiki.archlinux.org/index.php/NetworkManager

activating "NetworkManager.service" and "wp_supplicnt.service". My output of

Head_on_a_Stick wrote:

"systemctl list-uni-files --state=enabled"

is now:

UNIT FILE                                  STATE  
org.cups.cupsd.path                        enabled
autovt@.service                            enabled
avahi-daemon.service                       enabled
bluetooth.service                          enabled
dbus-fi.w1.wpa_supplicant1.service         enabled
dbus-org.bluez.service                     enabled
dbus-org.freedesktop.Avahi.service         enabled
dbus-org.freedesktop.ModemManager1.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
dbus-org.freedesktop.thermald.service      enabled
dbus-org.freedesktop.timesync1.service     enabled
display-manager.service                    enabled
getty@.service                             enabled
haveged.service                            enabled
lightdm.service                            enabled
ModemManager.service                       enabled
NetworkManager-dispatcher.service          enabled
NetworkManager-wait-online.service         enabled
NetworkManager.service                     enabled
org.cups.cupsd.service                     enabled
systemd-timesyncd.service                  enabled
thermald.service                           enabled
wpa_supplicant.service                     enabled
avahi-daemon.socket                        enabled
org.cups.cupsd.socket                      enabled
remote-fs.target                           enabled

seth wrote:

Please post a complete "sudo journal -b"…

don't know this command, If you refer to something else I don't get it, sorry.

Thanks for your help.

Trilby · 2019-04-16 02:58:45

Ok, so instead of deactivating all network services, you activated a couple more, and instead of trying to connect manually, you tried a different automatic service. I'm glad my advice was so well employed.

krischan941 · 2019-04-16 03:21:27

Ok sorry to not follow it to the end and being inaccurate. Can you tell me from my last post which services I all have to disable, which are all network services? And can you please give me a description or wiki link how to connect manually? I have to connect to an WPA2 encrypted one. Thank you

Brocellous · 2019-04-16 04:55:07

@Trilby was probably expecting you to keep those services disabled and follow the steps described in https://wiki.archlinux.org/index.php/WPA_supplicant for example, to connect using wpa_supplicant.

If you're unfamiliar, you certainly don't need to enable anything to connect to your wifi, enabling services is just a convenient way to start things automatically for you, which of course is an inconvenience when you are troubleshooting and would like to know what is going wrong. I would recommend reading and following the steps in the wiki above with your other networking software stopped to help you see what steps are required for your machine to associate and authenticate with an AP, and what software like NetworkManager does for you on top of that. If you cannot identify what running software may be related, try using "pacman -Qo " to determine which package owns the service file or executable you are interested in and reading about it on the wiki.

For my money though, your enabled units post shows "NetworkManager.service", "wpa_supplicant.service", and "dbus-fi.w1.wpa_supplicant1.service" all enabled. Doesn't that sound suspicious? Especially after the initial error complains "wlp3s0: Reject scan trigger since one is already pending"?

If I'm not mistaken, you don't need wpa_supplicant.service enabled to use it with NetworkManager, NetworkManager will bus-activate wpa_supplicant on it on its own unless configured otherwise.
'dbus-fi.w1.wpa_supplicant1.service' exists so other applications (like NetworkManager) can bus-activate wpa_supplicant conveniently. I don't think you want that enabled either.

I expect if you disable these services and reboot, your issue will be fixed. But still I recommend trying to connect manually, then, when your issue is fixed, you of course can enable NetworkManager.service again so that your wifi connects automatically when you log in.

Trilby · 2019-04-16 12:21:31

Hmm, there used to be a wonderful manual connection section in the wireless networking page on the wiki. It seems it was removed. Here it is in a nutshell:

1. Check the output of `ip a`. If there is no wireless interface listed, you may need to install a driver for your hardware.

2. Establish a connection, for secure networks, this would mean using wpa_supplicant. There are other tools for open networks, but as wpa_supplicant connects to those as well, I'd just use it for everything:
https://wiki.archlinux.org/index.php/WP … ant#Manual

3. Get an IP address. Running 'dhcpcd' on the wireless interface is a good default choice for this (there are other options like dhclient, or setting a static IP and route, but start with dhcpcd).

All of this should be done manually - e.g., by running the commands from a terminal and observing their output (and reporting it back here). This way you can pinpoint which step is failing. All of this should also be done without any automated services trying to control your connection. Having multiple services competing for control of networking is the most common source of problems and is almost certainly what is happening here. So stop and disable all systemd services related to networking ... *all* of them.

Head_on_a_Stick · 2019-04-16 18:23:09

krischan941 wrote:

reading https://wiki.archlinux.org/index.php/NetworkManager
activating "NetworkManager.service" and "wp_supplicnt.service".

At no point in that guide does it suggest that wpa_supplicant.service be enabled, Brocellous is right to say that is not needed.

krischan941 wrote:

seth wrote:
Please post a complete "sudo journal -b"…
don't know this command

You don't need to know it, just run the suggested command and post the output.

Trilby wrote:

stop and disable all systemd services related to networking

No need to disable stuff when testing, stopping them is sufficient.

But I do agree that wpa_supplicant.service needs to be disabled for NetworkManager to work.

EDIT: typo.

Last edited by Head_on_a_Stick (2019-04-16 18:23:42)

seth · 2019-04-16 18:34:09

"sudo journalctl -b" would probably work better, though ;-)

Head_on_a_Stick · 2019-04-16 18:35:33

D'oh! I didn't even notice that...

seth · 2019-04-16 18:42:51

Neither did I - this kind of thread is kinda prone to be addressed w/ "diminished attention" and that causes this kind of mistakes - esp. in the early morning
(I had actually already forgotton about this thread - and I also didn't get any mail about it)

@Trilby
https://wiki.archlinux.org/index.php?ti … management
https://wiki.archlinux.org/index.php/Ta … nt_rewrite

Trilby · 2019-04-16 23:54:02

Head_on_a_Stick wrote:

No need to disable stuff when testing, stopping them is sufficient.

In theory, this is true. But in practice I've seen people stop services, try something else, then reboot (as some think rebooting is a good troubleshooting step) and then they report back that the manual steps don't work. I prefer to have the person in need of assistance stop and disable all those services.

Beyond that, if they only stop them, then get one method working, then reboot, all those enabled and conflicting services will come right back and the problem will return. Starting with a clean slate really is important to getting networking working.

krischan941 · 2019-04-24 10:20:56

Sorry people for my late response.
Some new things has emerged...

I tried to connect with my kde/plasma-problem-laptop-system to some other wifi-network... with success! (why haven't I earlier...) I was able to connect to network of my brother, parents and my Android-hotspot... all automatically by Networkmanager... but I'm still unable to connect to my home-network with this system (still same errors). But I'm able to connect to my home-network via wifi with another Laptop and my smartphone... strange...
Don't know whether it is better to open a new topic because now this seems to be a completely different problem, isn't it?

Last edited by krischan941 (2019-04-24 11:01:21)

krischan941 · 2019-04-24 10:26:01

Before doing that would it be still meaningful to connect manually to my home network? Thanks people

Trilby · 2019-04-24 11:55:56

To make any headway here, we still need information. You have been provided with detailed instructions on how to gather that information. Specific information incluing error messages or command output is no less vital to the diagnostic process today than it was 10 days ago.

But given these new symptoms, the systemctl output from your first post taken at face value seems to be the most parsimonious: you are not entering (have not entered) the correct password for your home network. Of course actually following the advice that has been repeatedly given in this thread would conclusively determine whether or not this hypothesis is correct.

If you provide the exact commands and output from the manual connection steps I suspect a solution will be found in short order. If you'd rather continue speculating and have us speculating, then my next hypothesis would be unicorn interference in your home: buy unicorn repellant.

Last edited by Trilby (2019-04-24 11:58:16)

Arch Linux

#1 2019-04-14 00:58:08

wpa supplicant problems

#2 2019-04-14 02:51:07

Re: wpa supplicant problems

#3 2019-04-15 01:14:16

Re: wpa supplicant problems

#4 2019-04-15 06:24:20

Re: wpa supplicant problems

#5 2019-04-15 06:42:50

Re: wpa supplicant problems

#6 2019-04-16 02:42:35

Re: wpa supplicant problems

#7 2019-04-16 02:58:45

Re: wpa supplicant problems

#8 2019-04-16 03:21:27

Re: wpa supplicant problems

#9 2019-04-16 04:55:07

Re: wpa supplicant problems

#10 2019-04-16 12:21:31

Re: wpa supplicant problems

#11 2019-04-16 18:23:09

Re: wpa supplicant problems

#12 2019-04-16 18:34:09

Re: wpa supplicant problems

#13 2019-04-16 18:35:33

Re: wpa supplicant problems

#14 2019-04-16 18:42:51

Re: wpa supplicant problems

#15 2019-04-16 23:54:02

Re: wpa supplicant problems

#16 2019-04-24 10:20:56

Re: wpa supplicant problems

#17 2019-04-24 10:26:01

Re: wpa supplicant problems

#18 2019-04-24 11:55:56

Re: wpa supplicant problems

Board footer