Comment 8 for bug 61535
Revision history for this message
| Matt Zimmerman (mdz) wrote Re: [Bug 61535] Re: usplash progress reporting is not very accurate for casper | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
On Mon, Oct 09, 2006 at 11:02:28AM -0000, Tollef Fog Heen wrote:
> * Matt Zimmerman
>
> | On Fri, Oct 06, 2006 at 12:31:11PM -0000, Tollef Fog Heen wrote:
> | > * Force suspend and hibernate both off, since reconfiguring
> | > gnome-power-manager kills usplash here. Fixes Malone: #61535
> | > completely.
> |
> | It's useful to be able to test suspend to RAM using the live CD. Can this
> | be fixed a different way?
>
> My guess is that it's the dmidecode call that (at least on my test
> machine) kills usplash. (By kill I mean «freeze», since what happens
> is usplash seems to stop updating the screen). If my guess is
> correct then it's non-trivial to fix since we only enable suspend for
> machines where it's supported. (AFAIK, at least. If I'm wrong, I
> could always enable it and tell people whose systems it doesn't work
> on «tough luck».)
The progress reporting on the current dailies looks good, thanks.
--
- mdz