usplash timeout should be extended to cope with slow DHCP

Bug #21617 reported by Jamie Hamshere
8
Affects Status Importance Assigned to Milestone
netbase (Ubuntu)
Fix Released
Medium
Martin Pitt

Bug Description

When waiting to receive an IP address from a router via DHCP, sometimes usplash
reverts to the old white-on-black boot-up style if not assigned an address
quickly enough.

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

I have a similar problem, but I have an static IP address instead a dynamic one
via DHCP. I think usplash reverts to old-style when the startup process goes to
"setting the console font", but I'm not sure; it's only a theory. :/

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #1)
> I have a similar problem, but I have an static IP address instead a dynamic one
> via DHCP. I think usplash reverts to old-style when the startup process goes to
> "setting the console font", but I'm not sure; it's only a theory. :/

The original report is about a timeout (the default is 15 seconds, so if DHCP
takes longer than that, usplash will exit). The fix is to extend the usplash
timeout while ifup is running.

Your report sounds more like bug #21479

Revision history for this message
Martin Pitt (pitti) wrote :

(In reply to comment #2)

> Your report sounds more like bug #21479

That should be #15344, I guess.

Revision history for this message
Martin Pitt (pitti) wrote :

 netbase (4.21ubuntu3) breezy; urgency=low
 .
   * debian/netbase.init: Temporarily increase usplash timeout to 120 seconds
     to cope with slop DHCP server responses. (Ubuntu #15394)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.