(I've filed said issue as bug #162397)
--
usplash progress reporting is not very accurate for casper
https://bugs.launchpad.net/bugs/61535
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@lis
On Wed, Mar 28, 2007 at 05:34:10PM -, Michael wrote:
> I don't know if this quite fits in here, but I will add it anyway.
> Currently, during boot of an installed system, the first part of the
> bootsplash is very slow to start moving, and a new user might think
> their machine has frozen. Som
I don't know if this quite fits in here, but I will add it anyway.
Currently, during boot of an installed system, the first part of the
bootsplash is very slow to start moving, and a new user might think
their machine has frozen. Some sort of indication (anything moving on
the screen would do real
On Mon, Oct 09, 2006 at 11:02:28AM -, Tollef Fog Heen wrote:
> * Matt Zimmerman
>
> | On Fri, Oct 06, 2006 at 12:31:11PM -, Tollef Fog Heen wrote:
> | >* Force suspend and hibernate both off, since reconfiguring
> | > gnome-power-manager kills usplash here. Fixes Malone: #61535
>
* Matt Zimmerman
| On Fri, Oct 06, 2006 at 12:31:11PM -, 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 usin
On Fri, Oct 06, 2006 at 12:31:11PM -, 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 fi
* Force suspend and hibernate both off, since reconfiguring
gnome-power-manager kills usplash here. Fixes Malone: #61535
completely.
** Changed in: casper (Ubuntu)
Status: In Progress => Fix Released
--
usplash progress reporting is not very accurate for casper
https://laun
Marking as in-progress since this is hopefully-fixed but might need a
bit more work.
** Changed in: casper (Ubuntu)
Status: Confirmed => In Progress
--
usplash progress reporting is not very accurate for casper
https://launchpad.net/bugs/61535
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Latest upload:
casper (1.71) edgy; urgency=low
* Use TEXT-URGENT in shutdown script to make sure we display the "please
remove disc and press enter" text. Malone: #61533
* Increase usplash timeout since "TIMEOUT 0" no longer means "spin
forever".
* Don't move-mount all the squashfs
On di, 2006-09-26 at 18:18 +, Matt Zimmerman wrote:
> Looking at it, it doesn't seem very accurate for a number of other
> configurations as well. I think the approach used for ticking the
> progress bar in initramfs isn't adequate and this needs a rethink.
> Please look into this in detail af
Looking at it, it doesn't seem very accurate for a number of other
configurations as well. I think the approach used for ticking the
progress bar in initramfs isn't adequate and this needs a rethink.
Please look into this in detail after beta.
** Changed in: casper (Ubuntu)
Target: ubuntu-
** Changed in: casper (Ubuntu)
Assignee: (unassigned) => Tollef Fog Heen
--
usplash progress reporting is not very accurate for casper
https://launchpad.net/bugs/61535
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug 40029 has been marked a duplicate of this bug
--
usplash progress reporting is not very accurate for casper
https://launchpad.net/bugs/61535
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
13 matches
Mail list logo
