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#32429 - [netcfg] NETWORKS=last doesn't work.

Attached to Project: Arch Linux
Opened by Jente (Unia) - Saturday, 03 November 2012, 19:41 GMT
Last edited by Jouke Witteveen (jouke) - Sunday, 04 November 2012, 21:08 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Netcfg has the option to auto-connect to the last used network upon (re)boot. However, I found out this doesn't work. When in /etc/conf.d/netcfg I have "NETWORKS=(last)" and start netcfg with the net-profiles service, I find this in my journalctl: netcfg-daemon[277]: No recorded netcfg state to restore.

I don't know if it worked with previous versions as I only just reinstalled Arch and wanted to use it since then. I think you have all the information I can deliver, but if there's more then please tell me and I'll provide.

Additional info:
* package version(s): core/netcfg 3.0-1
* config and/or log files etc.


Steps to reproduce:
Just use "NETWORKS=(last)" in /etc/conf.d/netcfg and reboot. You will find the provided error message ("netcfg-daemon[277]: No recorded netcfg state to restore") in journalctl afterwards.
This task depends upon

Closed by  Jouke Witteveen (jouke)
Sunday, 04 November 2012, 21:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  75359
Comment by Alexander F. Rødseth (xyproto) - Sunday, 04 November 2012, 16:05 GMT
netcfg is currently an orphan. Assigning to last packager. Please move this package to extra, community or unsupported if there is no interest for it. Thanks.
Comment by Jouke Witteveen (jouke) - Sunday, 04 November 2012, 17:09 GMT
Look at the git repo. I am actively maintaining netcfg.
At the moment I am a bit busy, but this will change and I have some big plans.

As for this bug: isn't the error clear? At least once you have to connect manually to a netcfg profile. Indeed, it might be a bug that this profile is not stored on shutdown in a systemd setup. I will research this later (probably just change the return value to 0 for this case). For now, it should suffice to just execute `netcfg-daemon stop` manually as root once, when a profile is connected. That way, the profile name is stored. Sequential boots should be fine.
Comment by Jente (Unia) - Sunday, 04 November 2012, 19:59 GMT
The error itself is clear, but it doesn't explain what could be done to resolve it. Nor do the manpage and the Wiki.

I will test now and report back - if it works I will also update the Wiki.

Thanks in advance.
Comment by Jente (Unia) - Sunday, 04 November 2012, 20:03 GMT
Yes, this seems to have resolved this issue.

Thanks again!

Loading...