After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 682962 - Automatic reconnect after suspend not working with cloned MAC address
Automatic reconnect after suspend not working with cloned MAC address
Status: RESOLVED DUPLICATE of bug 673334
Product: NetworkManager
Classification: Platform
Component: nm-connection-editor
0.9.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Depends on:
Blocks:
 
 
Reported: 2012-08-29 17:09 UTC by aman
Modified: 2012-09-11 13:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
/var/log/messages relevant output (17.09 KB, text/plain)
2012-09-07 16:40 UTC, aman 		Details

Description aman 2012-08-29 17:09:53 UTC 
If a cloned MAC address is being used for the default wired network, once you suspend the laptop and resume it should automatically reconnect. However, it doesn't and after some time shows connection failed. Then the only way to make it reconnect is to unplug the cable and plug it back in.
Comment 1 aman 2012-09-07 16:33:34 UTC 
NetworkManager version used is 0.9.4.0-9.git20120521.fc17
Ethernet driver is atl1c
Comment 2 aman 2012-09-07 16:40:27 UTC 
Created attachment 223774 [details]
/var/log/messages relevant output
Comment 3 Jiri Klimes 2012-09-11 13:19:25 UTC 
Thanks for reporting it.
I guess this is a duplicate of bug 673334, caused by a race condition in carrier changes.

I noticed a problem with upowerd in the log. This is very likely unrelated to this bug, but consider to file a bug against UPower if you still see it and can provide some context:
Sep  7 19:23:57 kitkat upowerd[826]: (upowerd:826): GLib-CRITICAL **: g_ascii_strcasecmp: assertion `s1 != NULL' failed

*** This bug has been marked as a duplicate of bug 673334 ***