https://qa.mandrakesoft.com/show_bug.cgi?id=1146
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|premature network |premature network
|configuration |configuration
------- Additional Comments From [EMAIL PROTECTED] 2003-01-31 23:45 -------
This is a problem, but I'm not sure it's responsible for the hang. In today's
cooker, the only hang I get is the one described by someone in the list, i.e.
when the package install gets down to about 10-20 seconds to go, whatever
package is being installed (it varies) stops with its progress bar at 100% for
minutes at a time.
However, when the Summary display comes up, Network shows configured as "lan",
which is misleading because it has NOT been successfully configured, and if you
try to configure it again, you get a warning that it has already been configured
and can be left as is, which is incorrect, since the configuration is set to
dhcp and my network is not using dhcp.
There is one new Network twist today that wasn't there yesterday: if I configure
anyway and select autodetection, it autodetects and displays "ethernet cards
detected", but the "lan" selection is not selected (this is on the display
listing different connection hardware like modem, etc.), giving the impression
that autodetect couldn't find the card.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
description:
Today's cooker seems to be deciding that it needs the network before it's been
configured from the Network tab of the Summary page. It assumes DHCP, and
installs dhcpcd-client, and then appears to hang. The hang is because it is
timing out looking for a DHCP server, and there is none. The hang eventually
times out, but when I actually get the Summary dialog and go to configure the
network, it tells me that the network was already configured and I can leave it
as is.
It doesn't seem to realize that it never managed to connect with DHCP, and it
shouldn't be trying it anyway.
