Doesn't reconnect to wired network and shows incorrectly that it did

Bug #1099914 reported by Martin Dluhos
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
New
Undecided
David Paleino

Bug Description

I had a working ethernet connection and when I disconnected wicd correctly showed 'Not connected'. When plugged in my ethernet cord again, wicd showed 'Connected to wired network (IP: 192.168.0.201)' even though it actually did not reestablish the connection.

More importantly wicd never reestablished the wired connection.

distro: Arch Linux 3.6.11
wicd version: 1.7.2.4-5

This is what was printed in the log after I reconnected:

2013/01/15 11:24:29 :: GetCurrentNetworkID: Returning -1, current network not
found
2013/01/15 11:24:29 :: Reading wired profile wired-default
2013/01/15 11:24:29 :: found ip in configuration None
2013/01/15 11:24:29 :: found broadcast in configuration None
2013/01/15 11:24:29 :: found netmask in configuration None
2013/01/15 11:24:29 :: found gateway in configuration None
2013/01/15 11:24:29 :: found search_domain in configuration None
2013/01/15 11:24:29 :: found dns_domain in configuration None
2013/01/15 11:24:29 :: found dns1 in configuration None
2013/01/15 11:24:29 :: found dns2 in configuration None
2013/01/15 11:24:29 :: found dns3 in configuration None
2013/01/15 11:24:29 :: found beforescript in configuration None
2013/01/15 11:24:29 :: found afterscript in configuration None
2013/01/15 11:24:29 :: found predisconnectscript in configuration None
2013/01/15 11:24:29 :: found postdisconnectscript in configuration None
2013/01/15 11:24:29 :: found encryption_enabled in configuration None
2013/01/15 11:24:29 :: found default in configuration True
2013/01/15 11:24:29 :: found dhcphostname in configuration turing
2013/01/15 11:24:29 :: found lastused in configuration True

description: updated
summary: - Shows incorrectly that autoconnected to wired network
+ Doesn't reconnect to wired network and shows incorrectly that it did
Revision history for this message
David Paleino (dpaleino) wrote :

Unfortunately, the log you provided isn't sufficient.

Please provide the log taken this way:

1) let wicd connect to the wired network
2) mark in the log the time it finished connecting (it should have a series of "ifconfig eth0", or similar, each ~3s)
3) unplug the cable (and mark it in the log)
4) re-plug the cable (and mark it)
5) wait maximum 10 seconds

Then, attach the log taken this way to this report. When I say "mark in the log", I mean: add a clearly visible line, so that I understand what you did in that moment (something like: "======= PLUGGED CABLE ========"). Unfortunately, I don't have a wired network to test this behaviour at the moment, so I need your help to debug this.

Kindly,
David

Changed in wicd:
assignee: nobody → David Paleino (dpaleino)
Revision history for this message
Martin Dluhos (ub71a5bwcb7kuu1-martin-b69y0hv8hgzdev3) wrote :

I followed the steps and I am attaching the log. Hope this helps. Let me know if you need more info.

Thanks,
Martin

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.