Activity log for bug #324233

Date Who What changed Old value New value Message
2009-02-02 09:56:06 tpurch bug added bug
2009-02-02 15:12:34 tpurch title kubuntu 8.10 - Network Manager 0.7 replaces resolv.conf kubuntu 8.10 - Network Manager 0.7 - DHCP/resolvconf Problem
2009-03-16 14:36:57 Mackenzie Morgan knetworkmanager (Ubuntu): status New Confirmed
2009-03-16 14:36:57 Mackenzie Morgan knetworkmanager (Ubuntu): statusexplanation Confirming as still existing on Jaunty.
2009-03-16 17:07:20 Mackenzie Morgan knetworkmanager (Ubuntu): bugtargetdisplayname knetworkmanager (Ubuntu) network-manager (Ubuntu)
2009-03-16 17:07:20 Mackenzie Morgan knetworkmanager (Ubuntu): bugtargetname knetworkmanager (Ubuntu) network-manager (Ubuntu)
2009-03-16 17:07:20 Mackenzie Morgan knetworkmanager (Ubuntu): statusexplanation Confirming as still existing on Jaunty.
2009-03-16 17:07:20 Mackenzie Morgan knetworkmanager (Ubuntu): title Bug #324233 in knetworkmanager (Ubuntu): "kubuntu 8.10 - Network Manager 0.7 - DHCP/resolvconf Problem" Bug #324233 in network-manager (Ubuntu): "kubuntu 8.10 - Network Manager 0.7 - DHCP/resolvconf Problem"
2009-04-21 23:23:48 Alexander Sack network-manager (Ubuntu): importance Undecided Medium
2009-04-21 23:23:48 Alexander Sack network-manager (Ubuntu): status Confirmed Triaged
2009-04-21 23:23:48 Alexander Sack network-manager (Ubuntu): assignee Alexander Sack (asac)
2009-04-21 23:26:19 Alexander Sack summary kubuntu 8.10 - Network Manager 0.7 - DHCP/resolvconf Problem Network Manager 0.7 doesn't use resolvconf on shutdown if it didn't use it on startup - this causes /etc/resolv.conf link to be wiped on shutdown
2009-04-21 23:27:30 Alexander Sack summary Network Manager 0.7 doesn't use resolvconf on shutdown if it didn't use it on startup - this causes /etc/resolv.conf link to be wiped on shutdown Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it didn't use it to add that information - this causes /etc/resolv.conf link to be wiped on shutdown and makes migrating a running system to resolvconf tricky
2009-04-21 23:29:26 Alexander Sack summary Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it didn't use it to add that information - this causes /etc/resolv.conf link to be wiped on shutdown and makes migrating a running system to resolvconf tricky Network Manager 0.7 doesn't use resolvconf to remove nameserver info if it didn't use resolvconf for adding its nameserver info - wipes /etc/resolv.conf link
2009-05-27 15:30:19 TuxInvader attachment added If /etc/resolv.conf is a symlink, then follow it. http://launchpadlibrarian.net/27207466/nm-follow-symlink-patch.txt
2009-05-27 15:33:55 TuxInvader attachment added Ignore resolv.conf symlink http://launchpadlibrarian.net/27207535/nm-ignore-symlink.txt
2009-10-12 15:54:31 Alexander Sack network-manager (Ubuntu): status Triaged In Progress
2009-10-12 16:00:07 Alexander Sack attachment added lp324233.patch http://launchpadlibrarian.net/33523413/lp324233.patch
2010-02-11 06:09:46 Hernando Torque removed subscriber Hernando Torque
2010-07-08 07:52:24 Christian Rueb bug added subscriber Christian Rueb
2010-08-25 17:19:25 peteradleralberti bug added subscriber Ikkeetnavn
2010-12-26 16:00:56 Paul Smith bug added subscriber Paul Smith
2011-01-04 05:01:41 Jose Bernardo bug added subscriber Jose Bernardo
2011-01-07 10:37:38 Martin Pitt network-manager (Ubuntu): assignee Alexander Sack (asac)
2011-01-07 10:37:43 Martin Pitt network-manager (Ubuntu): status In Progress Triaged
2011-02-23 15:36:16 Khai Dinh removed subscriber Khai Dinh
2011-12-03 09:57:14 Thomas Hood attachment added nm-correct-resolvconf-handling.patch https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/324233/+attachment/2617538/+files/nm-correct-resolvconf-handling.patch
2012-06-22 09:30:50 Thomas Hood network-manager (Ubuntu): status Triaged Fix Released