Can't connect to a specific WiFi network

Cottand · 2016-10-28 17:50:40

Hi, I'm sorry if I didn't post this on the right section, this issue looks so weird to me that I can't tell if it's a laptop issue, a networking one, or if I'm just too much of a newbie to solve it on my own.

The problem is I can't connect to a specific WiFi network on my laptop. I've tried 2 different networks and they seem to work as expected. When I try to connect, NetworkManager crashes after a few seconds (around 2) and then it seems to restart on its own and try to reconnect again and it crashes again and so on. Now the weird part is that it also happens with another arch install on a completely different laptop (also with NetworkManager and in the same WiFi network). I've tried using a USB WiFi adapter but that doesn't seem to change much. Android devices and Windows computers seem not to have any problems whatsoever either. I'll be honest, I'm clueless about this. Ethernet also works fine.

Any kind of help is welcome and thanks in advance.

onslow77 · 2016-10-28 19:17:36

Hello!

I suggest you do a manual setup first: The Arch Wireless Wiki writes: "Whatever is your choice, you should try to connect using the manual method first. This will help you understand the different steps that are required and troubleshoot possible problems."

Regards
Martin

seth · 2016-10-28 19:31:22

It might be helpful to know sth. about the troublesome spot, eg "iwlist scanning" results.
You might also want to check whether that's just a bug in NM by stopping it and try to connet using wifi-menu or deep down, try https://wiki.archlinux.org/index.php/WPA_supplicant to debug it

Sorry, too many things at the same time ;-)

Last edited by seth (2016-10-28 19:33:25)

Cottand · 2016-10-28 21:24:15

seth wrote:

It might be helpful to know sth. about the troublesome spot, eg "iwlist scanning" results.

Sure here is the output:

wlp8s0    Scan completed :
          Cell 01 - Address: F8:63:94:B4:ED:03
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=70/70  Signal level=-30 dBm  
                    Encryption key:on
                    ESSID:"DCotta_House"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s
                    Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=00000004a5bee642
                    Extra: Last beacon: 2010ms ago
                    IE: Unknown: 000C44436F7474615F486F757365
                    IE: Unknown: 010882848B960C121824
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 32043048606C
                    IE: Unknown: 2D1A6C1817FFFF000000000000000000000000000000000000000000
                    IE: Unknown: 3D160B000000000000000000000000000000000000000000
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: DD1E00904C336C1817FFFF000000000000000000000000000000000000000000
                    IE: Unknown: DD1A00904C340B000000000000000000000000000000000000000000
                    IE: Unknown: DD0600E04C020160

seth wrote:

You might also want to check whether that's just a bug in NM by stopping it and try to connet using wifi-menu or deep down, try https://wiki.archlinux.org/index.php/WPA_supplicant to debug it

onslow77 wrote:

I suggest you do a manual setup first: The Arch Wireless Wiki

Ok as both of you suggested I've followed the steps obediently but for some reason I got

<3>CTRL-EVENT-SCAN-STARTED 
<3>CTRL-EVENT-SCAN-RESULTS 
<3>CTRL-EVENT-NETWORK-NOT-FOUND

Which is weird but dunno if I did it wrong or something or if it's indeed related to my issue. Any ideas? Thanks for the help so far!

EDIT: I aslo attempted connecting using wifi-menu and netctl unsuccesfully, here's some output code in case it's relevant:

$  sudo netctl start wlp8s0-DCotta_House

Job for netctl@wlp8s0\x2dDCotta_House.service failed because the control process exited with error code.
See "systemctl status "netctl@wlp8s0\\x2dDCotta_House.service"" and "journalctl -xe" for details.

$  journalctl -xe

-- Subject: Unit netctl@wlp8s0\x2dDCotta_House.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp8s0\x2dDCotta_House.service has begun starting up.
Oct 28 23:37:39 localhost network[18445]: Starting network profile 'wlp8s0-DCotta_House'...
Oct 28 23:37:39 localhost network[18445]: The interface of network profile 'wlp8s0-DCotta_House' is already up
Oct 28 23:37:39 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Main process exited, code=exited, status=1/FAILURE
Oct 28 23:37:39 localhost systemd[1]: Failed to start Networking for netctl profile wlp8s0-DCotta_House.
-- Subject: Unit netctl@wlp8s0\x2dDCotta_House.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp8s0\x2dDCotta_House.service has failed.
-- 
-- The result is failed.
Oct 28 23:37:39 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Unit entered failed state.
Oct 28 23:37:39 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Failed with result 'exit-code'.
Oct 28 23:37:39 localhost sudo[18438]: pam_unix(sudo:session): session closed for user root
Oct 28 23:37:50 localhost gnome-terminal-[12720]: gdkcursor-wayland.c:170: Unable to load blank_cursor from the cursor theme
Oct 28 23:37:50 localhost gnome-terminal-[12720]: gdkcursor-wayland.c:170: Unable to load blank_cursor from the cursor theme
Oct 28 23:37:52 localhost sudo[18453]:  cottand : TTY=pts/1 ; PWD=/home/cottand ; USER=root ; COMMAND=/usr/bin/netctl start wlp8s0-DCotta_House
Oct 28 23:37:52 localhost sudo[18453]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 28 23:37:52 localhost systemd[1]: Starting Networking for netctl profile wlp8s0-DCotta_House...
-- Subject: Unit netctl@wlp8s0\x2dDCotta_House.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp8s0\x2dDCotta_House.service has begun starting up.
Oct 28 23:37:52 localhost network[18460]: Starting network profile 'wlp8s0-DCotta_House'...
Oct 28 23:37:52 localhost network[18460]: The interface of network profile 'wlp8s0-DCotta_House' is already up
Oct 28 23:37:52 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Main process exited, code=exited, status=1/FAILURE
Oct 28 23:37:52 localhost systemd[1]: Failed to start Networking for netctl profile wlp8s0-DCotta_House.
-- Subject: Unit netctl@wlp8s0\x2dDCotta_House.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp8s0\x2dDCotta_House.service has failed.
-- 
-- The result is failed.
Oct 28 23:37:52 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Unit entered failed state.
Oct 28 23:37:52 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Failed with result 'exit-code'.
Oct 28 23:37:52 localhost sudo[18453]: pam_unix(sudo:session): session closed for user root

It says "already up"? I'm pretty sure I stopped NM though...

Last edited by Cottand (2016-10-28 21:46:03)

seth · 2016-10-28 21:48:31

networkmanager service still running?
If the AP supports WPA2, you should use that (configure it there - and if things then magically start to work, i'll present a theory on why ;-)

sudo systemctl list-units | grep -i net

Last edited by seth (2016-10-28 21:50:26)

Cottand · 2016-10-28 21:59:57

Ok so some failed instance of netctl was up, I rebooted, definitely stopped NM and I got a different error:

$  sudo netctl start wlp8s0-DCotta_House

Job for netctl@wlp8s0\x2dDCotta_House.service failed because the control process exited with error code.
See "systemctl status "netctl@wlp8s0\\x2dDCotta_House.service"" and "journalctl -xe" for details.

$ journalctl -xe

-- Unit system-netctl.slice has finished starting up.
-- 
-- The start-up result is done.
Oct 28 23:56:32 localhost systemd[1]: Starting Networking for netctl profile wlp8s0-DCotta_House...
-- Subject: Unit netctl@wlp8s0\x2dDCotta_House.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp8s0\x2dDCotta_House.service has begun starting up.
Oct 28 23:56:33 localhost network[2639]: Starting network profile 'wlp8s0-DCotta_House'...
Oct 28 23:56:38 localhost network[2639]: Failed to bring the network up for profile 'wlp8s0-DCotta_House'
Oct 28 23:56:38 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Main process exited, code=exited, status=1/FAILURE
Oct 28 23:56:38 localhost systemd[1]: Failed to start Networking for netctl profile wlp8s0-DCotta_House.
-- Subject: Unit netctl@wlp8s0\x2dDCotta_House.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@wlp8s0\x2dDCotta_House.service has failed.
-- 
-- The result is failed.
Oct 28 23:56:38 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Unit entered failed state.
Oct 28 23:56:38 localhost systemd[1]: netctl@wlp8s0\x2dDCotta_House.service: Failed with result 'exit-code'.
Oct 28 23:56:38 localhost sudo[2632]: pam_unix(sudo:session): session closed for user root

EDIT: Ok I finally managed. I successfully connected with netctl by "forgetting" the network on NM, after that sudo netctl start wlp8s0-DCotta_House worked like a charm. I guess I sort of needed to erase the NM profile to enable the netctl one? Honestly? No idea. But it does prove that, as you said, it's a NM bug. It just doesn't like my network.

So is it possible to fix it? Or do I just swap NM for something else? If so, with what? I'd love to be able to keep managing my networks from the gnome applet/extension....

Last edited by Cottand (2016-10-28 23:11:44)

seth · 2016-10-29 06:47:24

Smells more as if NM was still running ;-)

There're some gnome shell extensions which let you switch between known netctl profiles and there's https://github.com/codywd/NetGUI (where I don't know whether it's still supported) and qnetctl and netctl-gui in AUR (but those are Qt tools)

To figure why networkmanager fails, have a close look at the profile and the settings, notably reg. the authorization (if you can, force it to use WPA1 + TKIP)

Cottand · 2016-10-29 10:44:51

seth wrote:

Smells more as if NM was still running ;-)

xD not a chance I had disabled the service and rebooted, then stopped it again just in case, and it didn't show up in

sudo systemctl list-units | grep -i net

so no idea.

Yes I think I'd rather fix whatever the issue is. I also noticed NM also crashes when I connect through ethernet (weird? it seemed to work just fine when I 1st tried it)

seth wrote:

To figure why networkmanager fails, have a close look at the profile and the settings, notably reg. the authorization (if you can, force it to use WPA1 + TKIP)

I don't know how to force NM to use WPA1 + TKIP, but I have tried changing the WiFi encryption to WPA2 and WPA1/WPA2 and still no success, but since ethernet also seems to be crashing I don't think it's a security settings problem. Here are my current WiFi settings:

Security Mode : Auto (WPA or WPA2) (Here I mway choose between WPA only; WPA2 only; WPA or WPA2(current); and WEP. I have tried them all but WEP)

WPA Encryption : TKIPS+AES

WPA Mode : Auto (WPA or WOA2)-PSK 

Group Key Update Interval : 0

EDIT: I also tried connecting through a live installer (Antergos') and exact same issue with both WiFi and ethernet.

Last edited by Cottand (2016-10-29 11:10:42)

seth · 2016-10-29 14:02:29

If and when networkmanager *crashes* (like "segfaults") you should gdb attach to it and dump a backtrace to know why this happens.

----
The four major network handlers are netctl, wicd, networkmanager and systemd-network.
I'd personally always go with netctl and iff you "only" (foremost) want to manage known networks, netctl can auto-pick the best available anyway. The only "drawback" is maybe that there's no "GUI" to add networks (except for wifi-menu, technically curses is a GUI as well

Cottand · 2016-10-29 17:14:46

seth wrote:

If and when networkmanager *crashes* (like "segfaults") you should gdb attach to it and dump a backtrace to know why this happens.

I don't know how to do that. I'll look through a few guides and I'll report back as soon as I figure it out ^^' thanks for the help though, I'll consider switching to one of the alternatives you suggested!

seth · 2016-10-29 18:28:04

Another thing that could be relevant is your hostname - maybe there's a conflict with the routers dhcp table?

loqs · 2016-10-29 18:34:07

Oct 28 23:56:38 localhost

Installation_guide#Hostname

Cottand · 2016-10-29 20:05:37

loqs wrote:

Oct 28 23:56:38 localhost
Installation_guide#Hostname

I had indeed forgotten to "Consider adding a matching entry to hosts", but after doing it and rebooting, still no changes =(.

seth wrote:

Another thing that could be relevant is your hostname - maybe there's a conflict with the routers dhcp table?

Changed and still nothing :/ but it must have something to do with the dchp table since ethernet isn't working either. But as I said, the issue is still there on an Antergos build on another computer and netctl does work, so maybe I have to mess with some router setting? I already tried reseting it but no luck.

I didn't manage to debug NetworkManager. I can get as far as "run" but then gdb immediately the proccess is reported as "exited normally". Other commands will return "the process is not being run" even though I can see it running on the gnome interface.

seth · 2016-10-29 20:12:45

You need to "hostnamectl set-hostname foobar", editing /etc/hosts won't do.

Notice: "localhost" is not a good choice. NM often breaks the system for that.

(While the weird thing is that only one network seems to be troublesome)

Last edited by seth (2016-10-29 20:14:14)

loqs · 2016-10-29 20:16:09

Cottand wrote:

I had indeed forgotten to "Consider adding a matching entry to hosts", but after doing it and rebooting, still no changes .

You mean the systems /etc/hosts did not already have entries for localhost?

$ cat /etc/hosts 
#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost
::1		localhost.localdomain	localhost

Or do you mean the systems hostname is set to a valid value but all the command outputs you have posted are incorrectly showing it as localhost

man 1 hostnamectl wrote:

If a static hostname is set, and is valid
(something other than localhost), then the transient hostname is not
used.

Cottand · 2016-10-29 22:55:28

seth wrote:

You need to "hostnamectl set-hostname foobar", editing /etc/hosts won't do.
Notice: "localhost" is not a good choice. NM often breaks the system for that.
(While the weird thing is that only one network seems to be troublesome)

Ok done. Besides, the other laptop and the Antergos live installer do not have localhost as their hostname and weee, they work.

loqs wrote:

You mean the systems /etc/hosts did not already have entries for localhost?

$ cat /etc/hosts 
#
# /etc/hosts: static lookup table for host names
#

#<ip-address>	<hostname.domain.org>	<hostname>
127.0.0.1	localhost.localdomain	localhost
::1		localhost.localdomain	localhost

Thats was there, I was missing:

127.0.1.1	Arabella.localdomain	Arabella

(which is now the last line and where Arabella is my new hostname)
This bit I don't understand though:

loqs wrote:

Or do you mean the systems hostname is set to a valid value but all the command outputs you have posted are incorrectly showing it as localhost
man 1 hostnamectl wrote:
If a static hostname is set, and is valid
(something other than localhost), then the transient hostname is not
used.

EDIT: as I described in the 1st post, NM doesn't crash immediately, it takes around 2 seconds for it do so. I ran "iwconfig" and the output indicated that an IP address had been assigned to the computer. So my guess is that the DCHP server works just fine?

Last edited by Cottand (2016-10-29 23:25:43)

loqs · 2016-10-30 00:01:53

Every crash of NetworkManager should have generated a core dump
Core_dump#Examining_a_core_dump
You will need to install gdb if it is not already installed.
Please post the backtrace from the coredump generated by the last crash of NetworkManager.
Would also recommend you try the Wireless_network_configuration#Manual_setup
Make sure all network management services are stopped before starting on manual configuration
If the result of

$ ip link

shows the interface is up this a good indicator a network management service brought the interface up and multiple services managing the same device can cause unpredictable behavior.

Cottand · 2016-10-30 09:22:47

Ok here's the core dump:

cottand@Arabella~  coredumpctl info 12452

           PID: 12452 (NetworkManager)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 6 (ABRT)
     Timestamp: Sun 2016-10-30 01:20:55 CEST (9h ago)
  Command Line: /usr/bin/NetworkManager --no-daemon
    Executable: /usr/bin/NetworkManager
 Control Group: /system.slice/NetworkManager.service
          Unit: NetworkManager.service
         Slice: system.slice
       Boot ID: 3d0ea89ac55e4b149f8348d50b1432ea
    Machine ID: 63234608a6e44d9abdc254644fe77c0e
      Hostname: Arabella
      Coredump: /var/lib/systemd/coredump/core.NetworkManager.0.3d0ea89ac55e4b149f8348d50b1432ea.12452.
       Message: Process 12452 (NetworkManager) of user 0 dumped core.
                
                Stack trace of thread 12452:
                #0  0x00007f823ffcc04f raise (libc.so.6)
                #1  0x00007f823ffcd47a abort (libc.so.6)
                #2  0x00007f82407c92a5 g_assertion_message (libglib-2.0.so.0)
                #3  0x00007f82407c9632 g_assertion_message_cmpnum (libglib-2.0.so.0)
                #4  0x0000000000470f1c nm_dhcp_client_set_state (NetworkManager)
                #5  0x000000000044ac52 n/a (NetworkManager)
                #6  0x0000000000570733 n/a (NetworkManager)
                #7  0x0000000000576eaa n/a (NetworkManager)
                #8  0x0000000000578644 n/a (NetworkManager)
                #9  0x00000000005610dd n/a (NetworkManager)
                #10 0x00007f82407a2587 g_main_context_dispatch (libglib-2.0.so.0)
                #11 0x00007f82407a27f0 n/a (libglib-2.0.so.0)
                #12 0x00007f82407a2b12 g_main_loop_run (libglib-2.0.so.0)
                #13 0x0000000000436e34 n/a (NetworkManager)
                #14 0x00007f823ffb9291 __libc_start_main (libc.so.6)
                #15 0x00000000004374ba n/a (NetworkManager)
                
                Stack trace of thread 12455:
                #0  0x00007f824007848d poll (libc.so.6)
                #1  0x00007f82407a2786 n/a (libglib-2.0.so.0)
                #2  0x00007f82407a2b12 g_main_loop_run (libglib-2.0.so.0)
                #3  0x00007f8240d88316 n/a (libgio-2.0.so.0)
                #4  0x00007f82407ca0d5 n/a (libglib-2.0.so.0)
                #5  0x00007f824033e454 start_thread (libpthread.so.0)
                #6  0x00007f82400817df __clone (libc.so.6)
                
                Stack trace of thread 12453:
                #0  0x00007f824007848d poll (libc.so.6)
                #1  0x00007f82407a2786 n/a (libglib-2.0.so.0)
                #2  0x00007f82407a289c g_main_context_iteration (libglib-2.0.so.0)
                #3  0x00007f82407a28e1 n/a (libglib-2.0.so.0)
                #4  0x00007f82407ca0d5 n/a (libglib-2.0.so.0)
                #5  0x00007f824033e454 start_thread (libpthread.so.0)
                #6  0x00007f82400817df __clone (libc.so.6)
                
                Stack trace of thread 12454:
                #0  0x00007f824007cf19 syscall (libc.so.6)
                #1  0x00007f82407e803a g_cond_wait_until (libglib-2.0.so.0)
                #2  0x00007f8240776e89 n/a (libglib-2.0.so.0)
                #3  0x00007f82407caaa6 n/a (libglib-2.0.so.0)
                #4  0x00007f82407ca0d5 n/a (libglib-2.0.so.0)
                #5  0x00007f824033e454 start_thread (libpthread.so.0)
                #6  0x00007f82400817df __clone (libc.so.6)
lines 38-60/

And here's the gdb backtrace. I followed these instructions as suggested Core_dump#Examining_a_core_dump though I can't say I understand any of it.

Reading symbols from /usr/bin/NetworkManager...(no debugging symbols found)...done.
[New LWP 12452]
[New LWP 12455]
[New LWP 12453]
[New LWP 12454]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/NetworkManager --no-daemon'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f823ffcc04f in raise () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7f8242b4e580 (LWP 12452))]
(gdb) bt
#0  0x00007f823ffcc04f in raise () at /usr/lib/libc.so.6
#1  0x00007f823ffcd47a in abort () at /usr/lib/libc.so.6
#2  0x00007f82407c92a5 in g_assertion_message () at /usr/lib/libglib-2.0.so.0
#3  0x00007f82407c9632 in g_assertion_message_cmpnum () at /usr/lib/libglib-2.0.so.0
#4  0x0000000000470f1c in nm_dhcp_client_set_state ()
#5  0x000000000044ac52 in  ()
#6  0x0000000000570733 in  ()
#7  0x0000000000576eaa in  ()
#8  0x0000000000578644 in  ()
#9  0x00000000005610dd in  ()
#10 0x00007f82407a2587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#11 0x00007f82407a27f0 in  () at /usr/lib/libglib-2.0.so.0
#12 0x00007f82407a2b12 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#13 0x0000000000436e34 in  ()
#14 0x00007f823ffb9291 in __libc_start_main () at /usr/lib/libc.so.6
#15 0x00000000004374ba in  ()

loqs · 2016-10-30 11:11:59

#3  0x00007f82407c9632 in g_assertion_message_cmpnum () at /usr/lib/libglib-2.0.so.0
#4  0x0000000000470f1c in nm_dhcp_client_set_state ()

https://cgit.freedesktop.org/NetworkMan … ent.c#n300
https://bugs.archlinux.org/task/50788

Cottand · 2016-10-30 11:37:22

loqs wrote:

#3  0x00007f82407c9632 in g_assertion_message_cmpnum () at /usr/lib/libglib-2.0.so.0
#4  0x0000000000470f1c in nm_dhcp_client_set_state ()
https://cgit.freedesktop.org/NetworkMan … ent.c#n300
https://bugs.archlinux.org/task/50788

Thanks but please be less brief. So this is a known NM bug? Is the solution just downgrading? And what about the code?

loqs · 2016-10-30 11:49:39

Cottand wrote:

So this is a known NM bug?

It has a bug report in the arch bugtracker but given that it appears to be a bug in the code rather than a packing issue it really should be reported upstream.

Cottand wrote:

Is the solution just downgrading?

Partial_upgrades_are_unsupported
So I can not really recommend that. I would suggest using an alternative solution to manage the connection until the issue is resolved.

Cottand wrote:

And what about the code?

The code line was referencing the line that I think matches entries three and four of the backtrace.

Cottand · 2016-10-30 12:03:54

loqs wrote:

Cottand wrote:
So this is a known NM bug?
It has a bug report in the arch bugtracker but given that it appears to be a bug in the code rather than a packing issue it really should be reported upstream.
Cottand wrote:
Is the solution just downgrading?
Partial_upgrades_are_unsupported
So I can not really recommend that. I would suggest using an alternative solution to manage the connection until the issue is resolved.
Cottand wrote:
And what about the code?
The code line was referencing the line that I think matches entries three and four of the backtrace.

Ok I understand. Thanks a lot for the clarification and all the help! Greatly appreciated. I hope the bug will be fixed sometime soon upstream.

seth · 2016-10-30 12:09:14

Cottand wrote:

I hope the bug will be fixed sometime soon upstream.

Use netctl ;-)

For clarification on my side, the bug also occurs with a proper hostname?
(Since the assert is somewhat in the area where NM messes around with hostnames for dhcp announcements)

Cottand · 2016-10-30 12:26:01

seth wrote:

For clarification on my side, the bug also occurs with a proper hostname?

Yes, absolutely. I had attempted connection on several machines with different hostnames.

By the way, I honestly don't know how much of a workaround this is but I just installed the package dhclient and well it magically worked. No crashing anymore. I have no idea why.

ronw · 2016-10-30 16:37:37

Cottand wrote:

By the way, I honestly don't know how much of a workaround this is but I just installed the package dhclient and well it magically worked. No crashing anymore. I have no idea why.

Maybe this:

"It has functionality for basic DHCP support. For full featured DHCP and if you require IPv6 support, dhclient integrates it."

https://wiki.archlinux.org/index.php/Ne … stallation

Arch Linux

#1 2016-10-28 17:50:40

Can't connect to a specific WiFi network

#2 2016-10-28 19:17:36

Re: Can't connect to a specific WiFi network

#3 2016-10-28 19:31:22

Re: Can't connect to a specific WiFi network

#4 2016-10-28 21:24:15

Re: Can't connect to a specific WiFi network

#5 2016-10-28 21:48:31

Re: Can't connect to a specific WiFi network

#6 2016-10-28 21:59:57

Re: Can't connect to a specific WiFi network

#7 2016-10-29 06:47:24

Re: Can't connect to a specific WiFi network

#8 2016-10-29 10:44:51

Re: Can't connect to a specific WiFi network

#9 2016-10-29 14:02:29

Re: Can't connect to a specific WiFi network

#10 2016-10-29 17:14:46

Re: Can't connect to a specific WiFi network

#11 2016-10-29 18:28:04

Re: Can't connect to a specific WiFi network

#12 2016-10-29 18:34:07

Re: Can't connect to a specific WiFi network

#13 2016-10-29 20:05:37

Re: Can't connect to a specific WiFi network

#14 2016-10-29 20:12:45

Re: Can't connect to a specific WiFi network

#15 2016-10-29 20:16:09

Re: Can't connect to a specific WiFi network

#16 2016-10-29 22:55:28

Re: Can't connect to a specific WiFi network

#17 2016-10-30 00:01:53

Re: Can't connect to a specific WiFi network

#18 2016-10-30 09:22:47

Re: Can't connect to a specific WiFi network

#19 2016-10-30 11:11:59

Re: Can't connect to a specific WiFi network

#20 2016-10-30 11:37:22

Re: Can't connect to a specific WiFi network

#21 2016-10-30 11:49:39

Re: Can't connect to a specific WiFi network

#22 2016-10-30 12:03:54

Re: Can't connect to a specific WiFi network

#23 2016-10-30 12:09:14

Re: Can't connect to a specific WiFi network

#24 2016-10-30 12:26:01

Re: Can't connect to a specific WiFi network

#25 2016-10-30 16:37:37

Re: Can't connect to a specific WiFi network

Board footer