Return to Answer

EDIT: Before doing anything below, change the NetworkManager backend from wpa_supplicant to iwd. ArchWiki reference. To prevent link rot, here's what it should be:

Install the iwd package, then configure NM appropriately:

> sudo tee /etc/NetworkManager/conf.d/wifi_backend.conf <<EOF [device] wifi.backend=iwd EOF 

Apologies beforehand, this should be a comment, but I don't have the required reputation. There are no logs of consequence, so prepare for a very generic answer, but since you've been having this issue for years, it might be something that's worth opening a bug report.

According to the ubuntu wiki, which should probably be relevant even if on another distro, you should open the debug logs for NetworkManager, and edit the logs you've just posted:

By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:

$ sudo nmcli general logging level DEBUG domains ALL # open debug logs $ sudo journalctl -f -u NetworkManager # view logs 

Afterwards . . .

I'm going to go ahead and assume you've already tried connecting with a clean Arch install.

The following scenarios are possible; we're either dealing with:

• an incomplete package (that lacks the correct optional dependencies)
• a broken package (bad patches)
• a 'blessed configuration' issue
• or very simply a clean-cut NetworkManager bug.

Have you considered connecting using the default oob (out-of-the-box) configuration of another distribution, a.k.a. does this work under Debian, Fedora (and/or their derivatives)? The closer the package is to upstream, the more reliable this check will be. You can try overriding the system install with the latest official stable release of NetworkManager if you'd rather not toy around with other distributions instead.

A. If it does work, please confirm the NetworkManager arch package is close to upstream (e.g. there are no patches applied to the package by the maintainer).

Aa. If the package isn't close to upstream, open an issue with the package maintainer. Clearly, some patch is causing issues/grievances for you. This is worth opening an issue for.

Ab. If the package is close to upstream, you are missing critical packages. I'm unaware of how optional package dependencies are resolved under Arch, but I'd start with installing the relevant package group for it (if one exists), otherwise I'd go full ham and all optional dependencies -- and go from there.

Aba. If the package is close to upstream, and you've installed all possible dependencies, yet it stil ldoesn't work, you might have to cross-reference possible optional dependencies from another distribution (whose configuration works) compared to yours. But honestly, I'd just open a detailed ticket on NetworkManagers bug tracker at this point.

B. if it isn't, refer to E.

E. Open an issue to the project bug tracker.

EDIT: Before doing anything below, try changing the NetworkManager backend from wpa_supplicant to iwd. ArchWiki reference. To prevent link rot, here's what it should be:

Install the iwd package, then configure NM appropriately:

> sudo tee /etc/NetworkManager/conf.d/wifi_backend.conf <<EOF [device] wifi.backend=iwd EOF 

Apologies beforehand, this should be a comment, but I don't have the required reputation. There are no logs of consequence, so prepare for a very generic answer, but since you've been having this issue for years, it might be something that's worth opening a bug report.

According to the ubuntu wiki, which should probably be relevant even if on another distro, you should open the debug logs for NetworkManager, and edit the logs you've just posted:

By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:

$ sudo nmcli general logging level DEBUG domains ALL # open debug logs $ sudo journalctl -f -u NetworkManager # view logs 

Afterwards . . .

I'm going to go ahead and assume you've already tried connecting with a clean Arch install.

The following scenarios are possible; we're either dealing with:

• an incomplete package (that lacks the correct optional dependencies)
• a broken package (bad patches)
• a 'blessed configuration' issue
• or very simply a clean-cut NetworkManager bug.

Have you considered connecting using the default oob (out-of-the-box) configuration of another distribution, a.k.a. does this work under Debian, Fedora (and/or their derivatives)? The closer the package is to upstream, the more reliable this check will be. You can try overriding the system install with the latest official stable release of NetworkManager if you'd rather not toy around with other distributions instead.

A. If it does work, please confirm the NetworkManager arch package is close to upstream (e.g. there are no patches applied to the package by the maintainer).

Aa. If the package isn't close to upstream, open an issue with the package maintainer. Clearly, some patch is causing issues/grievances for you. This is worth opening an issue for.

Ab. If the package is close to upstream, you are missing critical packages. I'm unaware of how optional package dependencies are resolved under Arch, but I'd start with installing the relevant package group for it (if one exists), otherwise I'd go full ham and all optional dependencies -- and go from there.

Aba. If the package is close to upstream, and you've installed all possible dependencies, yet it stil ldoesn't work, you might have to cross-reference possible optional dependencies from another distribution (whose configuration works) compared to yours. But honestly, I'd just open a detailed ticket on NetworkManagers bug tracker at this point.

B. if it isn't, refer to E.

E. Open an issue to the project bug tracker.

Apologies beforehand, this should be a comment, but I don't have the required reputation. There are no logs of consequence, so prepare for a very generic answer, but since you've been having this issue for years, it might be something that's worth opening a bug report.

According to the ubuntu wiki, which should probably be relevant even if on another distro, you should open the debug logs for NetworkManager, and edit the logs you've just posted:

By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:

$ sudo nmcli general logging level DEBUG domains ALL # open debug logs $ sudo journalctl -f -u NetworkManager # view logs 

Afterwards . . .

I'm going to go ahead and assume you've already tried connecting with a clean Arch install.

The following scenarios are possible; we're either dealing with:

• an incomplete package (that lacks the correct optional dependencies)
• a broken package (bad patches)
• a 'blessed configuration' issue
• or very simply a clean-cut NetworkManager bug.

Have you considered connecting using the default oob (out-of-the-box) configuration of another distribution, a.k.a. does this work under Debian, Fedora (and/or their derivatives)? The closer the package is to upstream, the more reliable this check will be. You can try overriding the system install with the latest official stable release of NetworkManager if you'd rather not toy around with other distributions instead.

A. If it does work, please confirm the NetworkManager arch package is close to upstream (e.g. there are no patches applied to the package by the maintainer).

Aa. If the package isn't close to upstream, open an issue with the package maintainer. Clearly, some patch is causing issues/grievances for you. This is worth opening an issue for.

Ab. If the package is close to upstream, you are missing critical packages. I'm unaware of how optional package dependencies are resolved under Arch, but I'd start with installing the relevant package group for it (if one exists), otherwise I'd go full ham and all optional dependencies -- and go from there.

Aba. If the package is close to upstream, and you've installed all possible dependencies, yet it stil ldoesn't work, you might have to cross-reference possible optional dependencies from another distribution (whose configuration works) compared to yours. But honestly, I'd just open a detailed ticket on NetworkManagers bug tracker at this point.

B. if it isn't, refer to E.

E. Open an issue to the project bug tracker.

EDIT: Before doing anything below, change the NetworkManager backend from wpa_supplicant to iwd. ArchWiki reference. To prevent link rot, here's what it should be:

Install the iwd package, then configure NM appropriately:

> sudo tee /etc/NetworkManager/conf.d/wifi_backend.conf <<EOF [device] wifi.backend=iwd EOF 

Apologies beforehand, this should be a comment, but I don't have the required reputation. There are no logs of consequence, so prepare for a very generic answer, but since you've been having this issue for years, it might be something that's worth opening a bug report.

According to the ubuntu wiki, which should probably be relevant even if on another distro, you should open the debug logs for NetworkManager, and edit the logs you've just posted:

By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:

$ sudo nmcli general logging level DEBUG domains ALL # open debug logs $ sudo journalctl -f -u NetworkManager # view logs 

Afterwards . . .

I'm going to go ahead and assume you've already tried connecting with a clean Arch install.

The following scenarios are possible; we're either dealing with:

• an incomplete package (that lacks the correct optional dependencies)
• a broken package (bad patches)
• a 'blessed configuration' issue
• or very simply a clean-cut NetworkManager bug.

Have you considered connecting using the default oob (out-of-the-box) configuration of another distribution, a.k.a. does this work under Debian, Fedora (and/or their derivatives)? The closer the package is to upstream, the more reliable this check will be. You can try overriding the system install with the latest official stable release of NetworkManager if you'd rather not toy around with other distributions instead.

A. If it does work, please confirm the NetworkManager arch package is close to upstream (e.g. there are no patches applied to the package by the maintainer).

Aa. If the package isn't close to upstream, open an issue with the package maintainer. Clearly, some patch is causing issues/grievances for you. This is worth opening an issue for.

Ab. If the package is close to upstream, you are missing critical packages. I'm unaware of how optional package dependencies are resolved under Arch, but I'd start with installing the relevant package group for it (if one exists), otherwise I'd go full ham and all optional dependencies -- and go from there.

Aba. If the package is close to upstream, and you've installed all possible dependencies, yet it stil ldoesn't work, you might have to cross-reference possible optional dependencies from another distribution (whose configuration works) compared to yours. But honestly, I'd just open a detailed ticket on NetworkManagers bug tracker at this point.

B. if it isn't, refer to E.

E. Open an issue to the project bug tracker.

Apologies beforehand, this should be a comment, but I don't have the required reputation. There are no logs of consequence, so prepare for a very generic answer, but since you've been having this issue for years, it might be something that's worth opening a bug report.

According to the ubuntu wiki, which should probably be relevant even if on another distro, you should open the debug logs for NetworkManager, and edit the logs you've just posted:

By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:

$ sudo nmcli general logging level DEBUG domains ALL # open debug logs $ sudo journalctl -f -u NetworkManager # view logs 

Afterwards . . .

I'm going to go ahead and assume you've already tried connecting with a clean Arch install; The following scenarios are possible; we're either dealing with:

• an incomplete package (that lacks the correct optional dependencies)
• a broken package (bad patches)
• a 'blessed configuration' issue
• or very simply a clean-cut NetworkManager bug.

Have you considered connecting using the default oob (out-of-the-box) configuration of another distribution, a.k.a. does this work under Debian, Fedora (and/or their derivatives)? The closer the package is to upstream, the more reliable this check will be. You can try overriding the system install with the latest official stable release of NetworkManager if you'd rather not toy around with other distributions instead.

A. If it does work, please confirm the NetworkManager arch package is close to upstream (e.g. there are no patches applied to the package by the maintainer).

Aa. If the package isn't close to upstream, open an issue with the package maintainer. Clearly, some patch is causing issues/grievances for you. This is worth opening an issue for.

Ab. If the package is close to upstream, you are missing critical packages. I'm unaware of how optional package dependencies are resolved under Arch, but I'd start with installing the relevant package group for it (if one exists), otherwise I'd go full ham and all optional dependencies -- and go from there.

Aba. If the package is close to upstream, and you've installed all possible dependencies, you might have to cross-reference possible optional dependencies from another distribution (whose configuration works) compared to yours. But honestly, I'd just open a detailed ticket on NetworkManagers bug tracker at this point.

B. if it isn't, refer to E.

E. Open an issue to the project bug tracker.

Apologies beforehand, this should be a comment, but I don't have the required reputation. There are no logs of consequence, so prepare for a very generic answer, but since you've been having this issue for years, it might be something that's worth opening a bug report.

According to the ubuntu wiki, which should probably be relevant even if on another distro, you should open the debug logs for NetworkManager, and edit the logs you've just posted:

By default, the NetworkManager log level is set to info. You can use nmcli to modify the logging level:

$ sudo nmcli general logging level DEBUG domains ALL # open debug logs $ sudo journalctl -f -u NetworkManager # view logs 

Afterwards . . .

I'm going to go ahead and assume you've already tried connecting with a clean Arch install.

The following scenarios are possible; we're either dealing with:

• an incomplete package (that lacks the correct optional dependencies)
• a broken package (bad patches)
• a 'blessed configuration' issue
• or very simply a clean-cut NetworkManager bug.

Have you considered connecting using the default oob (out-of-the-box) configuration of another distribution, a.k.a. does this work under Debian, Fedora (and/or their derivatives)? The closer the package is to upstream, the more reliable this check will be. You can try overriding the system install with the latest official stable release of NetworkManager if you'd rather not toy around with other distributions instead.

A. If it does work, please confirm the NetworkManager arch package is close to upstream (e.g. there are no patches applied to the package by the maintainer).

Aa. If the package isn't close to upstream, open an issue with the package maintainer. Clearly, some patch is causing issues/grievances for you. This is worth opening an issue for.

Ab. If the package is close to upstream, you are missing critical packages. I'm unaware of how optional package dependencies are resolved under Arch, but I'd start with installing the relevant package group for it (if one exists), otherwise I'd go full ham and all optional dependencies -- and go from there.

Aba. If the package is close to upstream, and you've installed all possible dependencies, yet it stil ldoesn't work, you might have to cross-reference possible optional dependencies from another distribution (whose configuration works) compared to yours. But honestly, I'd just open a detailed ticket on NetworkManagers bug tracker at this point.

B. if it isn't, refer to E.

E. Open an issue to the project bug tracker.