Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48919 - [networkmanager] No Wifi connectivity

Attached to Project: Arch Linux
Opened by Peter (protake) - Wednesday, 13 April 2016, 07:51 GMT
Last edited by Jan Alexander Steffens (heftig) - Friday, 02 September 2016, 08:05 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

This isn't a particular useful bug report, sorry, but with the latest Network Manager, my Wifi doesn't show up anymore in Gnome and there's no connectivity. downgrading to 1.0.12 fixes this. I have an Intel AC 7265.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Friday, 02 September 2016, 08:05 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Friday, 15 April 2016, 15:08 GMT
We really do need more information. As you said, this is pretty useless as-is. Logs?
Comment by Matthew Wardrop (mister.wardrop) - Sunday, 17 April 2016, 02:35 GMT
I'm also hit by this bug, as are many others. (see: https://bbs.archlinux.org/viewtopic.php?id=210868). Looks like it might be related to devices which use out-of-tree firmware.
Comment by Matthew Wardrop (mister.wardrop) - Sunday, 17 April 2016, 03:12 GMT
I should note though, that I can restart NetworkManager.service, and everything works great. Perhaps the issue pertains to the order in which the service is run? Happy to provide logs if you point out which ones you would like.
Comment by Greg (misiunt) - Sunday, 17 April 2016, 11:20 GMT
this bug report seems to be a duplicate of  FS#48815 .
Comment by Matthew Wardrop (mister.wardrop) - Sunday, 17 April 2016, 20:20 GMT
Looks like it to me also. :).
Comment by Lukas Erlacher (luketheduke) - Monday, 30 May 2016, 10:54 GMT
One failure mode (there appear to be several) of NetworkManager 1.2.x is that it uses its "internal" dhcp implementation by default that seems to fail in a lot of cases.

IMO the NetworkManager package should ship a NetworkManager.conf file with the dhcp option set to dhclient (and a dependency on dhclient).
Comment by Lars Hupel (larsrh) - Monday, 30 May 2016, 11:54 GMT
I second Lukas' proposal. The switch from 'dhclient' to 'internal' broke my setup too.
Comment by Jan Alexander Steffens (heftig) - Monday, 30 May 2016, 12:33 GMT
If you find a bug in the internal DHCP client, please report it at https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager&component=IP+and+DNS+config .
Comment by Lars Hupel (larsrh) - Monday, 30 May 2016, 12:37 GMT
Upstream already acknowledges that the 'internal' DHCP implementation is incomplete, which is why the default is still 'dhclient' (see the relevant man page). However, the config file shipped with Arch changes the default to 'internal'. All I'm suggesting is to leave the upstream default as it is.

EDIT: To clarify, upstream default is to use 'dhclient' only if it's installed, then fallback to 'internal'.
Comment by Xaver (xaver) - Thursday, 25 August 2016, 17:01 GMT
No Wifi connection in 1.4.0-1 in testing.
Comment by Viktor Vasilyev (vitamin1980) - Friday, 26 August 2016, 19:47 GMT
No Wifi connection in 1.4.0-1 in testing too
Comment by Xaver (xaver) - Friday, 02 September 2016, 07:22 GMT
1.4.1 resolves the wifi issue.
Looks like the API to plasma-nm is a little bit broken (connection works, but no stored passwords or states like setup or wifi strength) - i know thats a new issue

Loading...