You are not logged in.

Pages: 1

#1 2016-07-17 05:33:26

archmania
Member
Registered: 2016-07-17
Posts: 8

[SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

Hi,

I had just installed Arch during the weekend and connected to my WPA2 secured home wifi without any problem. But today when I came to work and tried to connect to the work wifi from the wifi-menu, it kept on crashing

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

I ran "systemctl status netctl@HQ.service"

`--> systemctl status netctl@HQ.service
● netctl@HQ.service - Networking for netctl profile HQ
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sun 2016-07-17 08:28:24 AST; 2min 23s ago
     Docs: man:netctl.profile(5)
  Process: 5010 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 5010 (code=exited, status=1/FAILURE)

and "journalctl -xe"

`--> journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
                                                              #35 0x00000000004151b8 main (nm-connection-editor)
                                                              #36 0x00007f501614c741 __libc_start_main (libc.so.6)
                                                              #37 0x0000000000415349 _start (nm-connection-editor)
                                                              
                                                              Stack trace of thread 3166:
                                                              #0  0x00007f501620a6cd poll (libc.so.6)
                                                              #1  0x00007f5016a37fd6 n/a (libglib-2.0.so.0)
                                                              #2  0x00007f5016a380ec g_main_context_iteration (libglib-2.0.so.0)
                                                              #3  0x00007f5016a38131 n/a (libglib-2.0.so.0)
                                                              #4  0x00007f5016a5e2b5 n/a (libglib-2.0.so.0)
                                                              #5  0x00007f50164d4484 start_thread (libpthread.so.0)
                                                              #6  0x00007f50162136dd __clone (libc.so.6)
                                                              
                                                              Stack trace of thread 3167:
                                                              #0  0x00007f501620a6cd poll (libc.so.6)
                                                              #1  0x00007f5016a37fd6 n/a (libglib-2.0.so.0)
                                                              #2  0x00007f5016a38362 g_main_loop_run (libglib-2.0.so.0)
                                                              #3  0x00007f5017033726 n/a (libgio-2.0.so.0)
                                                              #4  0x00007f5016a5e2b5 n/a (libglib-2.0.so.0)
                                                              #5  0x00007f50164d4484 start_thread (libpthread.so.0)
                                                              #6  0x00007f50162136dd __clone (libc.so.6)
-- Subject: Process 3163 (nm-connection-e) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 3163 (nm-connection-e) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and
-- should be reported to its vendor as a bug.
Jul 17 08:13:16 localhost.localdomain /usr/lib/gdm/gdm-x-session[859]: Cjs-Message: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Jul 17 08:13:56 localhost.localdomain /usr/lib/gdm/gdm-x-session[859]: Cjs-Message: JS LOG: Removing an access point that was never added

I had Googled but didn't find any solution. Please help

[UPDATE]: I had submitted a bug report #768986 for nm-connection-manager in Gnome Bugzilla  https://bugzilla.gnome.org/show_bug.cgi?id=768986 and they confirmed they fixed the bug in network-manager-applet 1.2.2

Last edited by archmania (2016-07-24 05:01:08)

Offline

#2 2016-07-17 18:18:15

Starfish
Member
From: Germany
Registered: 2015-10-21
Posts: 134

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

archmania wrote:

...when I came to work and tried to connect to the work wifi from the wifi-menu, it kept on crashing

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

So not wifi-menu was crashing, but the netctl - service you where trying to start?
Could you successfully generate a profile with wifi-menu for your work-wifi, i.e. could you at least see the SSID?
Have you set the network interface down before starting the netctl service?
Have you stopped the network service for your home wifi before starting the one for your work?

"Yesterday is history, tomorrow is a mystery, but today is a gift. That is why it is called the present." - Master Oogway

Offline

#3 2016-07-17 18:24:31

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

Thanks a lot for you reply. Below are my answers.

Starfish wrote:

So not wifi-menu was crashing, but the netctl - service you where trying to start?

I'm note sure to be honest whether it was wifi-menu or netctl. Because I can see mentions of nm-connection-editor in the traces.


Starfish wrote:

Could you successfully generate a profile with wifi-menu for your work-wifi, i.e. could you at least see the SSID?

No I couldn't generate a profile with wifi-menu for the work wifi. It always crashes.

Starfish wrote:

Have you set the network interface down before starting the netctl service?

Yes I did.

Starfish wrote:

Have you stopped the network service for your home wifi before starting the one for your work?

Yes I did.

Offline

#4 2016-07-17 18:52:38

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

The journalctl output is from nm-connection-editor so two crashing programs possibly related?

hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.

As netctl services are run as system services not user services this explains why there were no netctl related entries in the journalctl output.

localhost.localdomain

localhost is not a valid hostname see here for the issues this can cause https://bbs.archlinux.org/viewtopic.php?id=214738

Offline

#5 2016-07-17 19:03:48

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

loqs wrote:

localhost is not a valid hostname see here for the issues this can cause https://bbs.archlinux.org/viewtopic.php?id=214738

I read the link and to be honest TIL that "hostname" and "localhost" can make apps to not work correctly. Thanks for the tip, I had changed my hostname and updated my hosts file.

As for the first point, i'll add my user to the "adm" group and try tomorrow again to connect to my work wifi and provide the logs smile

Offline

#6 2016-07-17 19:59:19

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

archmania wrote:

As for the first point, i'll add my user to the "adm" group and try tomorrow again to connect to my work wifi and provide the logs smile

Another altervative would be to run journalctl under Sudo
Also the following when run with the privileges to access the system journal should provide more info than "journalctl -xe"

journalctl --unit netctl@HQ.service

Additionally if there is still an issue what is the output of

$ systemctl list-unit-files | grep enabled

Offline

#7 2016-07-18 05:13:50

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

loqs wrote:

Also the following when run with the privileges to access the system journal should provide more info than "journalctl -xe"

I came to work today and did exactly what you asked me. Please find below the logs

`--> systemctl list-unit-files | grep enabled
autovt@.service                             enabled  
dbus-org.freedesktop.NetworkManager.service enabled  
dbus-org.freedesktop.nm-dispatcher.service  enabled  
display-manager.service                     enabled  
gdm.service                                 enabled  
getty@.service                              enabled  
netctl@home.service                         enabled  
NetworkManager-dispatcher.service           enabled  
NetworkManager.service                      enabled  
plexmediaserver.service                     enabled  
remote-fs.target                            enabled 
`--> journalctl --unit netctl@HQ.service
-- Logs begin at Fri 2016-07-15 15:11:16 AST, end at Mon 2016-07-18 08:00:05 AST. --
Jul 18 07:59:21 homebase systemd[1]: Starting Networking for netctl profile HQ...
Jul 18 07:59:21 homebase network[3781]: Starting network profile 'HQ'...
Jul 18 07:59:21 homebase network[3781]: Line 5: Invalid passphrase length 0 (expected: 8..63) '"'.
Jul 18 07:59:21 homebase network[3781]: Line 5: failed to parse psk '""'.
Jul 18 07:59:21 homebase network[3781]: Line 7: failed to parse network block.
Jul 18 07:59:21 homebase network[3781]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp2s0.conf'.
Jul 18 07:59:22 homebase network[3781]: The WPA supplicant did not start for interface 'wlp2s0'
Jul 18 07:59:22 homebase network[3781]: Failed to bring the network up for profile 'HQ'
Jul 18 07:59:22 homebase systemd[1]: netctl@HQ.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 07:59:22 homebase systemd[1]: Failed to start Networking for netctl profile HQ.
Jul 18 07:59:22 homebase systemd[1]: netctl@HQ.service: Unit entered failed state.
Jul 18 07:59:22 homebase systemd[1]: netctl@HQ.service: Failed with result 'exit-code'.
`--> systemctl status netctl@HQ.service  
● netctl@HQ.service - Networking for netctl profile HQ
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Mon 2016-07-18 07:59:22 AST; 3min 15s ago
     Docs: man:netctl.profile(5)
  Process: 3781 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 3781 (code=exited, status=1/FAILURE)

Jul 18 07:59:21 homebase network[3781]: Line 5: Invalid passphrase length 0 (expected: 8..63) '"'.
Jul 18 07:59:21 homebase network[3781]: Line 5: failed to parse psk '""'.
Jul 18 07:59:21 homebase network[3781]: Line 7: failed to parse network block.
Jul 18 07:59:21 homebase network[3781]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp2s0.conf'.
Jul 18 07:59:22 homebase network[3781]: The WPA supplicant did not start for interface 'wlp2s0'
Jul 18 07:59:22 homebase network[3781]: Failed to bring the network up for profile 'HQ'
Jul 18 07:59:22 homebase systemd[1]: netctl@HQ.service: Main process exited, code=exited, status=1/FAILURE
Jul 18 07:59:22 homebase systemd[1]: Failed to start Networking for netctl profile HQ.
Jul 18 07:59:22 homebase systemd[1]: netctl@HQ.service: Unit entered failed state.
Jul 18 07:59:22 homebase systemd[1]: netctl@HQ.service: Failed with result 'exit-code'.

I noticed that I don't have a wpa_supplicant_wlp2s0.conf file from the error below

Jul 18 07:59:21 homebase network[3781]: Failed to read or parse configuration '/run/network/wpa_supplicant_wlp2s0.conf'.

 `--> sudo ls /run/network/wpa_supplicant_wlp2s0.conf
ls: cannot access '/run/network/wpa_supplicant_wlp2s0.conf': No such file or directory

Offline

#8 2016-07-18 07:07:59

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

archmania wrote:
netctl@home.service                         enabled  
NetworkManager-dispatcher.service           enabled  
NetworkManager.service                      enabled

NetworkManager and netctl are conflicting, pick one and disable the other.

Are you infected with Wetiko?

Offline

#9 2016-07-18 07:26:00

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

Head_on_a_Stick wrote:
archmania wrote:
netctl@home.service                         enabled  
NetworkManager-dispatcher.service           enabled  
NetworkManager.service                      enabled

NetworkManager and netctl are conflicting, pick one and disable the other.

I had disabled netctl and I got this segmentation fault from nm-connection-editor

-- The start-up result is done.
Jul 18 10:23:04 homebase /usr/lib/gdm/gdm-x-session[587]: Cjs-Message: JS LOG: Removing an access point that was never added
Jul 18 10:23:06 homebase kernel: nm-connection-e[2527]: segfault at 8 ip 0000000000442802 sp 00007ffd4bcef4a0 error 4 in nm-connection-editor[400000+5d000]
Jul 18 10:23:06 homebase systemd[1]: Created slice system-systemd\x2dcoredump.slice.
-- Subject: Unit system-systemd\x2dcoredump.slice has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit system-systemd\x2dcoredump.slice has finished starting up.
-- 
-- The start-up result is done.
Jul 18 10:23:06 homebase systemd[1]: Started Process Core Dump (PID 2591/UID 0).
-- Subject: Unit systemd-coredump@0-2591-0.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-coredump@0-2591-0.service has finished starting up.
-- 
-- The start-up result is done.
Jul 18 10:23:07 homebase systemd-coredump[2592]: Process 2527 (nm-connection-e) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 2527:
                                                 #0  0x0000000000442802 n/a (nm-connection-editor)
                                                 #1  0x0000000000440cc7 eap_method_validate (nm-connection-editor)
                                                 #2  0x000000000043d70f ws_802_1x_validate (nm-connection-editor)
                                                 #3  0x000000000043ce9e wireless_security_validate (nm-connection-editor)
                                                 #4  0x00000000004206d2 n/a (nm-connection-editor)
                                                 #5  0x000000000041aa1a ce_page_validate (nm-connection-editor)
                                                 #6  0x0000000000415b3b n/a (nm-connection-editor)
                                                 #7  0x00007fc9c212a1d4 n/a (libgobject-2.0.so.0)
                                                 #8  0x00007fc9c214490d g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #9  0x00007fc9c2144fff g_signal_emit (libgobject-2.0.so.0)
                                                 #10 0x00007fc9c2129fa5 g_closure_invoke (libgobject-2.0.so.0)
                                                 #11 0x00007fc9c213bfb2 n/a (libgobject-2.0.so.0)
                                                 #12 0x00007fc9c2144c1c g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #13 0x00007fc9c21454ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                 #14 0x00007fc9c2ed9e69 n/a (libgtk-3.so.0)
                                                 #15 0x00007fc9c2edcd25 n/a (libgtk-3.so.0)
                                                 #15 0x00007fc9c2edcd25 n/a (libgtk-3.so.0)
                                                 #16 0x00007fc9c2129fa5 g_closure_invoke (libgobject-2.0.so.0)
                                                 #17 0x00007fc9c213c3ad n/a (libgobject-2.0.so.0)
                                                 #18 0x00007fc9c2144c1c g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #19 0x00007fc9c21454ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                 #20 0x00007fc9c2ed7855 n/a (libgtk-3.so.0)
                                                 #21 0x00007fc9c2ee04c4 n/a (libgtk-3.so.0)
                                                 #22 0x00007fc9c212ca14 g_cclosure_marshal_VOID__STRINGv (libgobject-2.0.so.0)
                                                 #23 0x00007fc9c212a1d4 n/a (libgobject-2.0.so.0)
                                                 #24 0x00007fc9c214490d g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #25 0x00007fc9c21454ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                 #26 0x00007fc9c212ca14 g_cclosure_marshal_VOID__STRINGv (libgobject-2.0.so.0)
                                                 #27 0x00007fc9c212a1d4 n/a (libgobject-2.0.so.0)
                                                 #28 0x00007fc9c214490d g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #29 0x00007fc9c21454ab g_signal_emit_by_name (libgobject-2.0.so.0)
                                                 #30 0x00007fc9c2f400e1 n/a (libgtk-3.so.0)
                                                 #31 0x00007fc9c2f410b5 n/a (libgtk-3.so.0)
                                                 #32 0x00007fc9c2f43263 n/a (libgtk-3.so.0)
                                                 #33 0x00007fc9c2edc74c n/a (libgtk-3.so.0)
                                                 #34 0x00007fc9c2f62821 n/a (libgtk-3.so.0)
                                                 #35 0x00007fc9c212a122 n/a (libgobject-2.0.so.0)
                                                 #36 0x00007fc9c21443e1 g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #37 0x00007fc9c2144fff g_signal_emit (libgobject-2.0.so.0)
                                                 #38 0x00007fc9c30a47bc n/a (libgtk-3.so.0)
                                                 #39 0x00007fc9c30c493b gtk_window_propagate_key_event (libgtk-3.so.0)
                                                 #40 0x00007fc9c30c83ab n/a (libgtk-3.so.0)
                                                 #41 0x00007fc9c2f62821 n/a (libgtk-3.so.0)
                                                 #42 0x00007fc9c212a1d4 n/a (libgobject-2.0.so.0)
                                                 #43 0x00007fc9c21443e1 g_signal_emit_valist (libgobject-2.0.so.0)
                                                 #44 0x00007fc9c2144fff g_signal_emit (libgobject-2.0.so.0)
                                                 #45 0x00007fc9c30a47bc n/a (libgtk-3.so.0)
                                                 #46 0x00007fc9c2f5fa89 n/a (libgtk-3.so.0)
                                                 #47 0x00007fc9c2f618d2 gtk_main_do_event (libgtk-3.so.0)
                                                 #48 0x00007fc9c2a98735 n/a (libgdk-3.so.0)
                                                 #49 0x00007fc9c2ac56a2 n/a (libgdk-3.so.0)
                                                 #50 0x00007fc9c1e54dd7 g_main_context_dispatch (libglib-2.0.so.0)
                                                 #51 0x00007fc9c1e55040 n/a (libglib-2.0.so.0)
                                                 #52 0x00007fc9c1e55362 g_main_loop_run (libglib-2.0.so.0)
                                                 #53 0x00000000004151b8 main (nm-connection-editor)
                                                 #54 0x00007fc9c1569741 __libc_start_main (libc.so.6)
                                                 #55 0x0000000000415349 _start (nm-connection-editor)
                                                 
                                                 Stack trace of thread 2529:
                                                 #0  0x00007fc9c16276cd poll (libc.so.6)
                                                 #1  0x00007fc9c1e54fd6 n/a (libglib-2.0.so.0)
                                                 #2  0x00007fc9c1e55362 g_main_loop_run (libglib-2.0.so.0)
                                                 #3  0x00007fc9c2450726 n/a (libgio-2.0.so.0)
                                                 #4  0x00007fc9c1e7b2b5 n/a (libglib-2.0.so.0)
                                                 #5  0x00007fc9c18f1484 start_thread (libpthread.so.0)
                                                 #6  0x00007fc9c16306dd __clone (libc.so.6)
                                                 
                                                 Stack trace of thread 2528:
                                                 #0  0x00007fc9c16276cd poll (libc.so.6)
                                                 #1  0x00007fc9c1e54fd6 n/a (libglib-2.0.so.0)
                                                 #2  0x00007fc9c1e550ec g_main_context_iteration (libglib-2.0.so.0)
                                                 #3  0x00007fc9c1e55131 n/a (libglib-2.0.so.0)
                                                 #4  0x00007fc9c1e7b2b5 n/a (libglib-2.0.so.0)
                                                 #5  0x00007fc9c18f1484 start_thread (libpthread.so.0)
                                                 #6  0x00007fc9c16306dd __clone (libc.so.6)
                                                 
                                                 Stack trace of thread 2590:
                                                 #0  0x00007fc9c162c269 syscall (libc.so.6)
                                                 #1  0x00007fc9c1e992aa g_cond_wait_until (libglib-2.0.so.0)
                                                 #2  0x00007fc9c1e29a19 n/a (libglib-2.0.so.0)
                                                 #3  0x00007fc9c1e2a03c g_async_queue_timeout_pop (libglib-2.0.so.0)
                                                 #4  0x00007fc9c1e7bd7d n/a (libglib-2.0.so.0)
                                                 #5  0x00007fc9c1e7b2b5 n/a (libglib-2.0.so.0)
                                                 #6  0x00007fc9c18f1484 start_thread (libpthread.so.0)
                                                 #7  0x00007fc9c16306dd __clone (libc.so.6)
-- Subject: Process 2527 (nm-connection-e) dumped core
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Process 2527 (nm-connection-e) crashed and dumped core.
-- 
-- This usually indicates a programming error in the crashing program and

Offline

#10 2016-07-18 11:45:42

Starfish
Member
From: Germany
Registered: 2015-10-21
Posts: 134

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

archmania wrote:
Starfish wrote:

Could you successfully generate a profile with wifi-menu for your work-wifi, i.e. could you at least see the SSID?

No I couldn't generate a profile with wifi-menu for the work wifi. It always crashes.

Try this:

iw dev <name of network_interface> scan | grep SSID

This way you can find out whether you can see the network at all.

"Yesterday is history, tomorrow is a mystery, but today is a gift. That is why it is called the present." - Master Oogway

Offline

#11 2016-07-18 12:46:35

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

Starfish wrote:

Try this:

iw dev <name of network_interface> scan | grep SSID

This way you can find out whether you can see the network at all.

I saw this after I went back home. I'll try it tomorrow.

Thing is, I can see the work SSID in the wifi-menu and when I press enter on it wifi-menu fails and exits with the below error

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

I checked /etc/netctl/HQ and found the below profile. It's incorrect profile tho because the wifi is WPA2 Enterprise.

Description='Automatically generated profile by wifi-menu'
Interface=wlp2s0
Connection=wireless
Security=wpa
ESSID=HQ
IP=dhcp

Offline

#12 2016-07-18 14:17:46

Starfish
Member
From: Germany
Registered: 2015-10-21
Posts: 134

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

If its only wifi-menu thats bothering you, you can make the config file for netctl by hand as I explained in the 7th post of the following thread:
https://bbs.archlinux.org/viewtopic.php?id=206695
If that doesnt help either, I'm out of suggestions.

"Yesterday is history, tomorrow is a mystery, but today is a gift. That is why it is called the present." - Master Oogway

Offline

#13 2016-07-18 16:34:11

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,791

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

Um,  NetworkManager has a bunch of userspace tools for controlling and configuring it.  HINT: wifi-menu is NOT one of them.

wifi-menu will invoke netctl which will conflict with Networkmanager. Don't do that.  Use one of these

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#14 2016-07-19 20:15:23

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

archmania wrote:

I had disabled netctl and I got this segmentation fault from nm-connection-editor

Perhaps there is a problem with that program, have you tried downgrading it?
https://wiki.archlinux.org/index.php/Downgrading

Can you connect manually?
https://wiki.archlinux.org/index.php/Wi … nual_setup

Post any error messages here in full please.

Are you infected with Wetiko?

Offline

#15 2016-07-20 09:05:22

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

Thank you guys all for your support. I had managed to solve it. I gave up on nm-connection-editor and its segmentation fault whenever I try to configure a WPA2 Enterprise network.

I managed to connect to my WPA2 Enterprise wifi using wpa_supplicant only. Below are the steps that I took

`--> cat /etc/wpa_supplicant/wpa_supplicant_wlp2s0.conf 
ctrl_interface=/var/run/wpa_supplicant 
fast_reauth=1 
network={ 
        scan_ssid=1 
        ssid="HQ" 
        key_mgmt=WPA-EAP 
        eap=PEAP 
        identity="DOMAIN\username" 
        phase1="peaplabel=auto peapver=0 " 
        phase2="auth=MSCHAPV2" 
        password="superstrongpassword" 
}
sudo wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf

I'll try to submit a bug report for the NetworkManager segmentation fault, I just don't know where to start lol

Offline

#16 2016-07-24 05:01:19

archmania
Member
Registered: 2016-07-17
Posts: 8

Re: [SOLVED] wifi-menu& NetworkManager crash connecting to WPA2 Enterprise

I had submitted a bug report #768986 for nm-connection-manager in Gnome Bugzilla  https://bugzilla.gnome.org/show_bug.cgi?id=768986 and they confirmed they fixed the bug in network-manager-applet 1.2.2

Offline

Pages: 1

Board footer

Powered by FluxBB