FS#75797 - netctl missing depends for wifi-menu: dialog, dhcpcd

Attached to Project: Arch Linux
Opened by Erik Johnson (EkriirkE) - Sunday, 04 September 2022, 08:53 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 September 2022, 22:35 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 6.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
The wifi-menu script from netctl requires dialog and dhcpcd to be installed, which should be shown/installed as dependencies in pacman

Steps to Reproduce:
Install bare system with netctl, dont have dhcpcd or dialog installed. Run wifi-menu
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 04 September 2022, 22:35 GMT
Reason for closing:  Not a bug
Additional comments about closing:  I agree with @Scimmia. optdepends covers this and is appropriate here.
Comment by Doug Newgard (Scimmia) - Sunday, 04 September 2022, 11:35 GMT
dhclient (optional) - for DHCP support (or dhcpcd)
dhcpcd (optional) - for DHCP support (or dhclient)
dialog (optional) - for the menu based wifi assistant

Doesn't look like they're missing to me. If you ignore what pacman tells you, you're going to have problems.
Comment by Erik Johnson (EkriirkE) - Sunday, 04 September 2022, 18:13 GMT
It doesn't make sense to me to install a distinct utility (and not an option to an existing one) that is completely broken unless you manually install depends.

At the very least update the note for dhcpcd that it is also required wifi-menu, which will silently fail without it.
Comment by Doug Newgard (Scimmia) - Sunday, 04 September 2022, 18:50 GMT
you didn't install a distinct wifi-menu package, you installed netctl. wifi-menu is an optional part of it, so the deps are optional.

wifi-menu doesn't fail silently without dhcpcd (or dhclient), it just doesn't use dhcp, as the description says.
Comment by Erik Johnson (EkriirkE) - Sunday, 04 September 2022, 19:34 GMT
wifi-menu does fail silently. Per dmesg, the interface is "deauthenicating ... by local choice" when wifi-menu closes abruptly to a blank screen, and I can't even manually assign an ip and route because the interface is "dead" -- deauthenticated. The logs complain about dhcpcd just before this. Once dhcpcd was installed everything worked smoothly. This tells me it is a required component just as much as dialog.

Loading...