[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
I`m running Ubuntu 12.04 updated till today (09 may 2014 ) and aswell Debian Testing with KDE updated and I have the same trouble the network is not working after a 30 o 45 minutes; I can not restart the network so if I wanna have the network running well I must restart the machine and the modem. Syslog: May 9 16:44:10 pcdebian kernel: [ 2071.820186] via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... May 9 16:44:20 pcdebian kernel: [ 2081.820185] via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... May 9 17:00:16 pcdebian kernel: [ 3037.820197] via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... Kern.log: May 6 12:35:48 pcdebian kernel: [ 1383.808509] via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... May 6 13:26:54 pcdebian kernel: [0.822714] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker May 6 13:26:54 pcdebian kernel: [0.823126] via-rhine :00:12.0 eth0: VIA Rhine II at 0x1f200, 00:19:db:a0:d6:13, IRQ 23 May 6 13:26:54 pcdebian kernel: [0.823905] via-rhine :00:12.0 eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1 May 6 13:37:07 pcdebian kernel: [ 625.820368] via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... May 6 13:37:17 pcdebian kernel: [ 635.820197] via-rhine :00:12.0 eth0: Transmit timed out, status 1003, PHY status 786d, resetting... Ubuntu kern.log May 5 19:28:54 caralu74 kernel: [ 451.136479] device eth0 left promiscuous mode May 5 19:29:01 caralu74 kernel: [ 458.572040] device eth0 entered promiscuous mode May 5 19:36:50 caralu74 kernel: [ 926.820645] via-rhine :00:12.0: eth0: Transmit timed out, status 1003, PHY status 786d, resetting... May 5 19:36:50 caralu74 kernel: [ 926.821393] via-rhine :00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 May 5 19:36:54 caralu74 kernel: [ 930.820180] via-rhine :00:12.0: eth0: Transmit timed out, status 1003, PHY status 786d, resetting... May 9 16:00:02 caralu74 kernel: [ 5408.820181] via-rhine :00:12.0: eth0: Transmit timed out, status 1003, PHY status 786d, resetting... ## And this could be useful: May 6 16:13:53 caralu74 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 May 6 16:13:58 caralu74 NetworkManager[1568]: (eth0): DHCPv4 request timed out. May 6 16:13:58 caralu74 NetworkManager[1568]: (eth0): canceled DHCP transaction, DHCP client pid 2876 May 6 16:13:58 caralu74 NetworkManager[1568]: Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... May 6 16:13:58 caralu74 NetworkManager[1568]: Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) started... May 6 16:13:58 caralu74 NetworkManager[1568]: (eth0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5] May 6 16:13:58 caralu74 NetworkManager[1568]: Activation (eth0) failed. May 6 16:13:58 caralu74 NetworkManager[1568]: Activation (eth0) Stage 4 of 5 (IPv4 Configure Timeout) complete. May 6 16:13:58 caralu74 NetworkManager[1568]: (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0] May 6 16:13:58 caralu74 NetworkManager[1568]: (eth0): deactivating device (reason 'none') [0] May 6 16:13:58 caralu74 avahi-daemon[1468]: Withdrawing address record for fe80::219:dbff:fea0:d613 on eth0. May 6 16:13:58 caralu74 avahi-daemon[1468]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::219:dbff:fea0:d613. May 6 16:13:58 caralu74 avahi-daemon[1468]: Interface eth0.IPv6 no longer relevant for mDNS. May 6 16:14:00 caralu74 avahi-daemon[1468]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::219:dbff:fea0:d613. May 6 16:14:00 caralu74 avahi-daemon[1468]: New relevant interface eth0.IPv6 for mDNS. May 6 16:14:00 caralu74 avahi-daemon[1468]: Registering new address record for fe80::219:dbff:fea0:d613 on eth0.*. May 6 16:14:01 caralu74 NetworkManager[1568]: Auto-activating connection 'Conexión cableada 1'. May 6 16:14:01 caralu74 NetworkManager[1568]: Activation (eth0) starting connection 'Conexión cableada 1' May 6 16:14:01 caralu74 NetworkManager[1568]: (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0] May 6 16:14:01 caralu74 NetworkManager[1568]: Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... May 6 16:14:01 caralu74 NetworkManager[1568]: Activation (eth0) Stage 1 of 5 (Device Prepare) started... May 6 16:14:01 caralu74 NetworkManager[1568]: Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... May 6 16:14:01 caralu74 NetworkManager[1568]: Activation (eth0) Stage 1 of 5 (Device Prepare) complete. May 6 16:14:01 caralu74 NetworkManager[1568]: Activation (eth0) Stage 2 of 5 (Device Configure) starting... May 6 16:14:01
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
This is a network manager bug, as it affects a Gentoo system of mine running Gnome. The problem is that Network Manager "helpfully" sets the hostname, which confuses a lot of programs. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
> most likely a kde admin or ifupdown issue. There are many, many confirmations under Gnome. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
not a network manager bug. most likely a kde admin or ifupdown issue. ** Changed in: ubuntu Sourcepackagename: network-manager => None ** Tags added: needs-reassignment -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
I can confirm this bug in Hardy-Gnome. If a domain is added to the hostname in /etc/hosts, sudo does not work any more. In Gutsy that did not matter; sudo still worked even if a domain name was added: 172.0.0.1 localhost [hostname].[domain] I think, the problem is not, how the domain name has been added. It is rather how /etc/hosts is parsed. A simple workaround to edit /etc/hosts without rebooting in recovery mode (as described above) is to open an administration terminal from the main menue. This is possible without any sudo command and does still work. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
ArbitraryConstant: I'm not disagreeing with you - I think this should have been two bugs myself (unless the backend is in some way shared between KDE and GNOME) but we shall see. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
Perhaps, but as I said if the same symptoms are caused by two different bugs then it is certainly not appropriate to mark reports of this issue in Gnome as duplicates of this bug, which is what has happened to date. If this bug is to be transferred to KDE, then revive 208947 or tell me to re-file it. It's as simple as that. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
The problem is that under GNOME it is not network-manager that sets static configurations - it is gnome-system-tools... The question is whether the KDE equivalent uses the same backend. Either way I doubt network-manager is the right place for this bug... -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
> There is at least one comment reporting a problem on GNOME, which is surely a different bug and should be filed separately No need. I submitted 208947 with Gnome, and it was marked as a duplicate of this bug. Given identical corruption of /etc/hosts under similar circumstances, that's probably correct. If 208947 is a different bug, then it's not a duplicate. Since the symptoms are identical, it should also be given a "high" priority. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
The bug actually occurred in KDE3, not KDE4. Setting to network-manager since it affects Gnome as well as KDE. ** Changed in: network-manager (Ubuntu) Sourcepackagename: meta-kde4 => network-manager -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
Actually Matt, the bug took place while using KDE3...I ran into the bug while assigning the machine a static ip, which is the first thing I do after installing any OS. So I hadn't even gotten to the process of installing the KDE4 packages when KDE3's network manager hosed my system. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
I was the other Ubuntu (Gnome) poster. gmcalp's description is _exactly_ what happened to me. I'm surprised anyone has any problems reproducing it: it seems to happen 100% of the time and recipe is very simple. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
I can also confirm that it isn't just KDE that is having this problem. I just ran into it today using network-anager under GNOME. How it happened for me was to switch from 'roaming' to use DHCP... I too am getting the "sudo: unable to resolve host geoff-laptop" error when trying to sudo. I am using the LTS Hardy release. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
This bug, as originally reported, affects the KDE 4 Remix of Kubuntu, not the 8.04 release itself. Moving to kde4 for further analysis and reassignment, as it seems unlikely to be a network-manager problem. There is at least one comment reporting a problem on GNOME, which is surely a different bug and should be filed separately. ** Changed in: meta-kde4 (Ubuntu) Sourcepackagename: network-manager => meta-kde4 Assignee: Alexander Sack (asac) => (unassigned) -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
It's not just "manual configuration" that causes this failure. I had this exact thing happen to me when I tried to reconfigure my network interface via the System -> Administration -> Network tool. I disabled roaming mode and enabled DHCP... and NetworkManager whacked my /etc/hosts file so that I could no longer use sudo. See bug 214360 -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
Agreed. The problem should be fixed at the source instead of putting a band-aid on the symptoms as they appear. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
The interaction with sudo is a very inconvenient, very visible symptom. Without getting into whether or not it's desirable for sudo to do the gethostbyname() lookup, we can say for certain that it is never the correct behavior for a configuration GUI used by the user to produce an incorrect /etc/hosts file. If gethostbyname() were removed from sudo, we would still have a broken /etc/hosts file, and there would still be bugs resulting from that. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
At least parts of the problem are releated to: https://bugs.edge.launchpad.net/ubuntu/+source/sudo/+bug/32906 -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
** Changed in: network-manager (Ubuntu) Assignee: dlgandalf (gandalf-die-laterne) => Alexander Sack (asac) -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
This happens with KDE and Gnome, so it is probably a network-manager backend issue. ** Changed in: network-manager (Ubuntu) Sourcepackagename: kdeadmin => network-manager -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
The problem occurred for me on gnome. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
kubuntu doesn't use gnome admin tools, reassigning to kde ** Changed in: kdeadmin (Ubuntu) Sourcepackagename: gnome-system-tools => kdeadmin -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdeadmin in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
Wait! I think this is in the wrong package which is why no-one is looking at it. Attempting a punt to gnome-system-tools ... ** Changed in: gnome-system-tools (Ubuntu) Sourcepackagename: network-manager => gnome-system-tools -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
I, too, confirm this bug. It worked fine in Gutsy; and the network manager edits the /etc/hosts file so that the first two lines look like: 172.0.0.1 localhost [hostname].[domain] 172.0.1.1 [hostname].[domain] The second ".[domain]" should not be added; this is the part the messes with sudo. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
I ran into this after changing the hostname of a Hardy machine (dist- upgraded yesterday) with KNetworkManager. The /etc/hosts file did not contain the new hostname after this and because of this sudo refused working from then on. One needs to boot into recovery mode or with a live CD to fix this problem by correcting /etc/hosts. -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
Well, since I didn't set the root password, the only way for me to use su was through sudo. But thanks for confirming this...glad to know I'm not crazy. dlgandalf wrote: > this bug is real, I ran into it many times now. > Btw, can someone tell me if it is necessary for the hosts file to have the > rule > > 127.0.0.1 localhost > > with the emphasis on the name between '<>' > > btw Mr Peoples you can still use 'su' -command, you don't have to do a > recovery mode > > ** Changed in: network-manager (Ubuntu) > Assignee: (unassigned) => dlgandalf (gandalf-die-laterne) >Status: New => Confirmed > > -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185209] Re: [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure
this bug is real, I ran into it many times now. Btw, can someone tell me if it is necessary for the hosts file to have the rule 127.0.0.1 localhost with the emphasis on the name between '<>' btw Mr Peoples you can still use 'su' -command, you don't have to do a recovery mode ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => dlgandalf (gandalf-die-laterne) Status: New => Confirmed -- [hardy] Manually Configuring Network Causes Massive, Unreversable, Failure https://bugs.launchpad.net/bugs/185209 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
