On our current testing desktops (running feisty) it seems to work.
--
Network connection failed after booting (Dapper 6.0.6)
https://bugs.launchpad.net/bugs/54911
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Thank you, I'm marking this as fixed.
** Changed in: dhcp3 (Ubuntu)
Status: Incomplete = Fix Released
--
Network connection failed after booting (Dapper 6.0.6)
https://bugs.launchpad.net/bugs/54911
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Do you still have this issue with the latest stable release of Ubuntu ?
** Changed in: dhcp3 (Ubuntu)
Importance: Undecided = Medium
Status: New = Incomplete
--
Network connection failed after booting (Dapper 6.0.6)
https://bugs.launchpad.net/bugs/54911
You received this bug
** Changed in: dhcp3 (Ubuntu)
Assignee: Philip Paquette = (unassigned)
Status: Needs Info = Unconfirmed
--
Network connection failed after booting (Dapper 6.0.6)
https://bugs.launchpad.net/bugs/54911
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Setting package to dhcp3, so this bug gets out of the list of bugs without a
package.
Can you confirm this bug still happens in edgy/feisty?
You seem to say the bug is fixed, should I close it then or is it just a
workaround?
Thanks.
** Changed in: dhcp3 (Ubuntu)
Sourcepackagename: None = dhcp3
This problem is dhcp3-client related. Setting a fixed ip-address in
/etc/network/interfaces is a workaround, and installing pump fixes the problem,
allowing me to use dhcp with these network controllers.
Is pump the default in edgy/festy by any chance, because dhcp-client has been
causing so
Pretty much default:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
--
This is still a problem, at least for me. I've bought 2 new Dell desktop
machines to test, so hopefully they can replace our old custom-built
desktop machines. These machines are Dell optiplexes 745 with a broadcom
onboard network (exact type unknown atm, uses the tg3 driver)
However, with our
Could you please add the contents of your '/etc/network/interfaces'
file? Thanks in advance.
--
Network connection failed after booting (Dapper 6.0.6)
https://launchpad.net/bugs/54911
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Based on your comment EdSpraDo regarding your updating to Edgy I would
like to close this bug as we won't be able to get the information we
need about Dapper.
eswar - are you still using dapper and is this an issue for you?
--
Network connection failed after booting (Dapper 6.0.6)
I have recently updated to UBUNTU 6.10 and in this version the bug is not
present.
But in UBUNTU 6.0.6 LTS it was still an issue.
Regards
2007/3/20, Brian Murray [EMAIL PROTECTED]:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while
Thanks for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any
activity in it recently. We were wondering is this still an issue for
you? Thanks in advance.
** Changed in: Ubuntu
Assignee: (unassigned) = Brian
This happens with my Toshiba Satellite A80-154 laptop too. It has
Marvell Yukon 88e8086 Fast ethernet controller. Moreover, i connect my
system in office lan, so it has a static IP. And in many posts people
mostly complain about DHCP and the network problems occur because of the
DHCP. But
** Tags added: dapper ethernet
** Tags removed: 6.06
--
Network connection failed after booting (Dapper 6.0.6)
https://launchpad.net/bugs/54911
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
14 matches
Mail list logo
