>> emerge wicd >> /etc/init.d/wicd start wicd | * Starting wicd daemon ... wicd |sed: can't read /etc/wicd/wired-settings.conf: No such file or directory The ebuild should create an empty/default wired-settings.conf to stop this error. If a wicd run is required to create this, then this should either be performed automatically in the ebuild, or mentioned in einfo. Reproducible: Always
(In reply to comment #0) > >> emerge wicd > >> /etc/init.d/wicd start > wicd | * Starting wicd daemon ... > wicd |sed: can't read /etc/wicd/wired-settings.conf: No such file or > directory Never seen this error before. > The ebuild should create an empty/default wired-settings.conf to stop this > error. The caveat of this approach is that an etc-update/dispatch-conf will try to overwrite the populated conf file with a null file. That may or may not be ok. > If a wicd run is required to create this, then this should either be > performed automatically in the ebuild, or mentioned in einfo. Are you interested in investigating the proper resolution here?
>> emerge -C wicd >> mv /etc/wicd /etc/wicd-old >> emerge wicd >> /etc/init.d/wicd start wicd | * Starting wicd daemon ... wicd |sed: can't read /etc/wicd/wired-settings.conf: No such file or directory I can replicate with the above. Have attached a simple patch to the init script to check for wired-settings before running sed.
Created attachment 245689 [details, diff] patch to check before running sed
(In reply to comment #3) > Created an attachment (id=245689) [details] > patch to check before running sed > ah, yes. I forgot about that. Thanks.
assigning to new maintainer.
*** Bug 359073 has been marked as a duplicate of this bug. ***
Fixed in 1.7.1_beta2-r3. Thanks for reporting. Closing.
