Activity log for bug #280919

Date Who What changed Old value New value Message
2008-10-09 19:42:32 Roderick B. Greening bug added bug
2008-10-09 19:46:17 Roderick B. Greening description Binary package hint: network-manager Recent updates for intrepid introduced a new version of network-manager. It has broken network-manager-kde (once again). In order to get back online, I had to manually perform a ifconfig on eth0. We are past a point where any changes should break existing compatibility. I suspect the change is ABI related, as it was in the recent past, where network-manager-kde had to be patched to make it work again. With changes to such a core component, the Kubuntu dev need to be notified, so they can determine ahead of time if any breakage may occur. Binary package hint: network-manager Recent updates for intrepid introduced a new version of network-manager. It has broken network-manager-kde (once again). In order to get back online, I had to manually perform a ifconfig on eth0.
2008-10-09 20:03:23 Scott Kitterman network-manager: status New Confirmed
2008-10-09 20:03:23 Scott Kitterman network-manager: statusexplanation Wireless works for me, but if I boot with wired only it seems problematic. Per conversation on IRC, the reporter was using a wired connection.
2008-10-09 22:37:51 Scott Kitterman network-manager: importance Undecided Medium
2008-10-09 22:37:51 Scott Kitterman network-manager: statusexplanation Wireless works for me, but if I boot with wired only it seems problematic. Per conversation on IRC, the reporter was using a wired connection.
2008-10-09 22:37:51 Scott Kitterman network-manager: milestone ubuntu-8.10
2008-10-10 10:14:57 Scott Kitterman network-manager: status Confirmed Incomplete
2008-10-10 10:14:57 Scott Kitterman network-manager: statusexplanation [19:04] <asac> ScottK: unlikely that the regression window really is the latest upload. at least if its a knetworkmanager specific issue [19:05] <asac> ScottK: read: no dbus api changes in the last upload. [19:05] <asac> ScottK: do you use a "hybrid" setup, e.g. one connection managed by ifup/ifdown and the wireless with NM? [06:08] <ScottK> asac: About NM, not on purpose I don't use a hybrid setup. Everyone who tried it (there were three of us, IIRC) saw similar issues on Kubuntu. [06:08] --> philwyett has joined this channel (n=philip@79-69-150-162.dynamic.dsl.as9105.com). [06:09] <asac> ScottK: hybrid == /etc/network/interfaces has a configuration ;) [06:10] <ScottK> asac: It says auto eth0. Does that count? [06:10] <asac> ScottK: if there is no iface eth0 ... line then it shouldnt [06:11] <ScottK> Nope [06:11] <ScottK> The only iface line I have is for lo [06:11] <asac> ScottK: please paste your route -n output when you see these packet losses [06:11] <ScottK> OK. Will do. [06:11] <asac> ScottK: i have received other complains, but couldnt reproduce here except for a hybrid setup [06:12] <asac> ScottK: for me "wired" interfaces always have a metric/prio of "1" and wireless have a metric/prio of "2" [06:12] <asac> which should tie-break the path the packages travel - assuming that both interfaces provide a route to the same net [06:13] <ScottK> OK.
2009-02-22 13:39:52 Alexander Sack network-manager: bugtargetdisplayname network-manager (Ubuntu) knetworkmanager (Ubuntu)
2009-02-22 13:39:52 Alexander Sack network-manager: bugtargetname network-manager (Ubuntu) knetworkmanager (Ubuntu)
2009-02-22 13:39:52 Alexander Sack network-manager: statusexplanation [19:04] <asac> ScottK: unlikely that the regression window really is the latest upload. at least if its a knetworkmanager specific issue [19:05] <asac> ScottK: read: no dbus api changes in the last upload. [19:05] <asac> ScottK: do you use a "hybrid" setup, e.g. one connection managed by ifup/ifdown and the wireless with NM? [06:08] <ScottK> asac: About NM, not on purpose I don't use a hybrid setup. Everyone who tried it (there were three of us, IIRC) saw similar issues on Kubuntu. [06:08] --> philwyett has joined this channel (n=philip@79-69-150-162.dynamic.dsl.as9105.com). [06:09] <asac> ScottK: hybrid == /etc/network/interfaces has a configuration ;) [06:10] <ScottK> asac: It says auto eth0. Does that count? [06:10] <asac> ScottK: if there is no iface eth0 ... line then it shouldnt [06:11] <ScottK> Nope [06:11] <ScottK> The only iface line I have is for lo [06:11] <asac> ScottK: please paste your route -n output when you see these packet losses [06:11] <ScottK> OK. Will do. [06:11] <asac> ScottK: i have received other complains, but couldnt reproduce here except for a hybrid setup [06:12] <asac> ScottK: for me "wired" interfaces always have a metric/prio of "1" and wireless have a metric/prio of "2" [06:12] <asac> which should tie-break the path the packages travel - assuming that both interfaces provide a route to the same net [06:13] <ScottK> OK.
2009-02-22 13:39:52 Alexander Sack network-manager: title Bug #280919 in network-manager (Ubuntu): "NetworkManager 0.7~~svn20081008t224042-0ubuntu1 breaks Knetworkmanager" Bug #280919 in knetworkmanager (Ubuntu): "NetworkManager 0.7~~svn20081008t224042-0ubuntu1 breaks Knetworkmanager"
2009-09-03 15:24:18 Jonathan Thomas knetworkmanager (Ubuntu): status Incomplete Won't Fix