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!
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!
FS#9145 - wicd + wired behaves strange
Attached to Project:
Arch Linux
Opened by Erwin Van de Velde (evdvelde) - Thursday, 10 January 2008, 09:23 GMT
Last edited by Varun Acharya (ganja_guru) - Friday, 11 January 2008, 12:39 GMT
Opened by Erwin Van de Velde (evdvelde) - Thursday, 10 January 2008, 09:23 GMT
Last edited by Varun Acharya (ganja_guru) - Friday, 11 January 2008, 12:39 GMT
|
DetailsDescription:
When starting my computer, wicd does not connect automatically to the wired network. If wireless is available, it connects correctly to the wireless network. When manually connecting to the wired network (clicking in the wicd gui), the wicd gui and tray icon say "Not connected" although the connection is up. Additional info: * package version(s) wicd 1.4.1-2 |
This task depends upon
Closed by Varun Acharya (ganja_guru)
Friday, 11 January 2008, 12:39 GMT
Reason for closing: Fixed
Additional comments about closing: wicd-1.4.1-4 now in extra
Friday, 11 January 2008, 12:39 GMT
Reason for closing: Fixed
Additional comments about closing: wicd-1.4.1-4 now in extra
Comment by Erwin Van de Velde (evdvelde) -
Friday, 11 January 2008, 09:44 GMT
I found the problem: wicd requires ethtool for this and ethtool is not listed as dependency, please update.
Comment by Varun Acharya (ganja_guru) -
Friday, 11 January 2008, 12:38 GMT
Thanks, fixed.