Activity log for bug #148606
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2007-10-03 16:14:41 | Nick Moffitt | bug | added bug | ||
2007-10-03 16:14:50 | Nick Moffitt | bug | added subscriber The Canonical Sysadmins | ||
2007-10-05 06:58:28 | Pharao | gnome-system-tools: status | New | Confirmed | |
2007-10-11 10:08:19 | Sebastien Bacher | gnome-system-tools: importance | Undecided | Low | |
2007-10-11 10:08:19 | Sebastien Bacher | gnome-system-tools: assignee | desktop-bugs | ||
2007-10-11 10:08:19 | Sebastien Bacher | gnome-system-tools: status | Confirmed | Triaged | |
2007-10-11 10:08:42 | Sebastien Bacher | bug | assigned to gst | ||
2007-10-12 11:40:49 | Bug Watch Updater | gst: status | Unknown | New | |
2008-01-25 11:05:38 | Bug Watch Updater | gst: status | New | Invalid | |
2008-10-07 23:13:19 | Alexander Sack | network-manager: status | Triaged | Fix Released | |
2008-10-07 23:13:19 | Alexander Sack | network-manager: statusexplanation | upstream comment "gnome-system-tools just modifies the interface configuration file(s) and runs ifup immediately on it in this case. I faced myself this problem a few times some time ago when testing gnome-system-tools/NetworkManager cooperation code, I found out I could reproduce it through command line too, and that everything worked as expected if NM wasn't active. My conclusion was that NM is not releasing properly the interface, so I'm moving this bug there." reassigning the bug | NM 0.7 does supports static IP setups properly now in 0.7. I think this bug is fixed. | |
2010-09-16 08:50:12 | Bug Watch Updater | gst: status | Invalid | Unknown | |
2010-09-16 08:50:12 | Bug Watch Updater | gst: importance | Unknown | Medium |