[SOLVED] netctl issues & wifi-menu doesn't detect handmade profiles

Leafy Greens · 2018-09-06 23:26:24

I'm trying to connect to my college's wifi, which uses WPA2 Enterprise, which wifi-menu seems to be unable to auto-generate a profile for. I think that I've put together a functional profile for netctl to use, but when I tried to select it from wifi-menu's dialog (as I'm in the habit of doing), it didn't detect that the profile was present.
I then tried to start it manually with

 sudo netctl start [profile]

but that returned the error

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

I then tried to use the same command to connect to my apartment building's wifi, and got the same error. However, I am still able to use the apartment wifi if I use wifi-menu (which is how I'm able to post this).

I've tried googlng around, but couldn't find any record of anyone having similar problems. Can anyone point me in the right direction to fix this?

Here's the output of systemctl status netctl@[profile].service:

● netctl@[profile].service - Networking for netctl profile [profile]
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2018-09-06 19:02:01 EDT; 27s ago
     Docs: man:netctl.profile(5)
  Process: 24637 ExecStart=/usr/lib/netctl/network start [profile] (code=exited, status=1/FAILURE)
 Main PID: 24637 (code=exited, status=1/FAILURE)

And here's the output of journalctl -xe

-- The start-up result is RESULT.
Sep 03 20:43:20 fern at-spi-bus-launcher[709]: dbus-daemon[714]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=614 comm="/usr/bin/telegram-desktop -session 10>
Sep 03 20:43:20 fern at-spi-bus-launcher[709]: dbus-daemon[714]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 03 20:43:20 fern at-spi-bus-launcher[709]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Sep 03 20:43:20 fern dbus-daemon[460]: [session uid=1000 pid=460] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.4' (uid=1000 pid=485 com>
Sep 03 20:43:20 fern systemd[403]: Starting Bluetooth OBEX service...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr: XRandR::setConfig
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr: Requested screen size is QSize(1600, 900)
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr: Needed CRTCs:  1
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr: Actions to perform:
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr:         Primary Output: false
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr:         Change Screen Size: false
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr:         Disable outputs: false
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr:         Change outputs: false
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr:         Enable outputs: false
Sep 03 20:43:20 fern kscreen_backend_launcher[668]: kscreen.xrandr: XRandR::setConfig done!
Sep 03 20:43:21 fern obexd[719]: OBEX daemon 5.50
Sep 03 20:43:21 fern dbus-daemon[460]: [session uid=1000 pid=460] Successfully activated service 'org.bluez.obex'
Sep 03 20:43:21 fern systemd[403]: Started Bluetooth OBEX service.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 03 20:43:23 fern dbus-daemon[460]: [session uid=1000 pid=460] Activating service name='org.freedesktop.Notifications' requested by ':1.39' (uid=1000 pid=614 comm="/usr/bin/telegram-desktop -se>
Sep 03 20:43:26 fern dbus-daemon[460]: [session uid=1000 pid=460] Successfully activated service 'org.freedesktop.Notifications'
Sep 03 20:43:26 fern dbus-daemon[460]: [session uid=1000 pid=460] Activating service name='org.kde.kuiserver' requested by ':1.20' (uid=1000 pid=554 comm="/usr/bin/plasmashell ")
Sep 03 20:43:26 fern dbus-daemon[460]: [session uid=1000 pid=460] Successfully activated service 'org.kde.kuiserver'
Sep 06 13:17:23 fern kcheckpass[9926]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Sep 06 13:17:23 fern kcheckpass[9926]: pam_tally(kde:auth): Error opening /var/log/faillog for read
Sep 06 13:17:23 fern kcheckpass[9926]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Sep 06 13:17:23 fern kcheckpass[9926]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Sep 06 13:21:57 fern dbus-daemon[460]: [session uid=1000 pid=460] Activating service name='org.gnome.GConf' requested by ':1.50' (uid=1000 pid=23620 comm="/usr/bin/palemoon ")
Sep 06 13:21:57 fern dbus-daemon[460]: [session uid=1000 pid=460] Successfully activated service 'org.gnome.GConf'
Sep 06 19:01:54 fern kcheckpass[24408]: pam_tally(kde:auth): Error opening /var/log/faillog for update
Sep 06 19:01:54 fern kcheckpass[24408]: pam_tally(kde:auth): Error opening /var/log/faillog for read
Sep 06 19:01:55 fern kcheckpass[24408]: pam_tally(kde:setcred): Error opening /var/log/faillog for update
Sep 06 19:01:55 fern kcheckpass[24408]: pam_tally(kde:setcred): Error opening /var/log/faillog for update

Last edited by Leafy Greens (2018-09-10 20:43:57)

Leafy Greens · 2018-09-10 20:43:40

I might have found a solution. I found this thread with a similar error message, and after using

# chmod +s /usr/lib/kcheckpass

I can run netctl start commands without error.

The other issue with wifi-menu may or may not be solved; I'll test it tomorrow. Marking as solved for now, will reopen if needed.

Arch Linux

#1 2018-09-06 23:26:24

[SOLVED] netctl issues & wifi-menu doesn't detect handmade profiles

#2 2018-09-10 20:43:40

Re: [SOLVED] netctl issues & wifi-menu doesn't detect handmade profiles

Board footer