http://brainstorm.ubuntu.com/item/15741/
Although this works ok, the progress effect is very ugly because the bar moves in huge increments and then stops for an undetermined time until it moves again. Besides not being beautiful, this provides no information to the user about the time remaining for the boot or shutdown process.

I suggest that the usplash progressbar be time-based, pretty much like the progressbar in MacOSX.

Since the booting and shutdown times do not change drastically from session to session, we could save the time the computer spent to boot and to shutdown, and use it to guide the progressbar the next time. This would provide a beautiful and smooth animation of the progressbar, and an accurate remaining time, increasing the usability.

This can be already implemented using the current usplash code without modifications whatsoever, and a working solution is already available.

Please check it here:
http://gnome-look.org/content/show.php?content=93386

Ubuntu PPA:
https://launchpad.net/~usplash-smooth/+archive

Ubuntu WIKI:
https://wiki.ubuntu.com/UsplashSmooth


[591 votes] Solution #1: Auto-generated solution of idea #15741


[-5 votes] Solution #2: Same as Solution One, but Different


[16 votes] Solution #3: Just wait for Plymouth


]]> en-us Tue, 18 Nov 2008 19:23:54 +0000 Wed, 17 Dec 2008 23:59:55 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/15741/
Maybe it should work as normal the first couple of boots so it has time to learn how to progress smoothly from the start?]]> Tue, 18 Nov 2008 21:01:20 +0000 Tue, 18 Nov 2008 21:01:45 +0000 It works great and until Plymouth gets implemented
> I see no reason why not to make it like this.

Sure thing!
This is absolutely no competition for Plymouth.
I, for one, really want to see Plymouth in Jaunty!
This is just a small improvement step for the technology we already use right now!

> Does it work with any Usplash Theme?

Yes, but not directly.
The themes would need small modifications.
There is a very good documentation on how to do this in the package.
Just ask your theme maintainer to release a smooth version!]]> Tue, 18 Nov 2008 21:07:50 +0000
In other words this gives the user less info about delays to the boot process. Personally I prefer the progress bar the way it is. A possible compromise is to time each individual step and stop the progress bar moving if a step takes to long. Really if fsck occurs we should inform the user that the bootup will take longer than usual, and show progress of the fsck. Fortunately the fsck time is going to be greatly less under ext4 thought.]]> Wed, 19 Nov 2008 01:20:58 +0000 Wed, 19 Nov 2008 05:44:41 +0000 In other words this gives the user less info about delays to the boot process.
> Personally I prefer the progress bar the way it is.

In the current implementation, the progressbar stays still while
the filesystem check is being performed. This is also not ideal.
I plan to fix this in the next version.
Stay tuned!

> I use Kubuntu, how can i make it work with it?

This works in kubuntu as well.
But the kubuntu usplash theme has not been adapted yet.
This is a good suggestion, I will also include this in the next version!]]> Wed, 19 Nov 2008 06:47:10 +0000 The purpose of a progress bar is to see, if progress is made or if something is stuck. Something that just moves from left to right in 30 seconds does not provide any information.
But i think, the bar could be replaced by two or three lines of text output at the bottom of the screen, so if it stands still, you get an idea, why.]]> Wed, 19 Nov 2008 10:11:20 +0000
On the other hand, making it time based and removing the quiet option is acceptable. Since I always remove the quiet option and get actual information, I don't really care. But for those people who do not, the time based option is no more useful than simply putting up a static graphic. In other words, it can do actual harm by keeping the user from having ANY idea something is wrong.]]> Wed, 19 Nov 2008 19:20:10 +0000 The purpose of a progress bar is to see, if progress is
> made or if something is stuck. Something that just moves
> from left to right in 30 seconds does not provide any
> information.

> A machine with a real problem might well sit for 24 hours
> looking like it was doing something but not doing anything
> real.

Usplash already has a timeout mechanism in place, pretty
much like a watchdog. If the initialization scripts do
not reset this mechanism from time to time, usplash
finishes itself and the command line is displayed,
so you can check the status of the boot process.
The default timeout is 15 seconds.

In the majority of the cases, the boot is without problems.
For the cases where we have a problem, the mechanism above
kicks in.


> But i think, the bar could be replaced by two or three
> lines of text output at the bottom of the screen,
> so if it stands still, you get an idea, why.

> On the other hand, making it time based and removing the
> quiet option is acceptable. Since I always remove the
> quiet option and get actual information.

The text output is STILL AVAILABLE.
You can remove the quiet option to see the initialization
status, and programs like fsck can still report the progress
to the user. A time-based progressbar won't do all this harm!

In version 0.4 (real soon now), the time-based progressbar
ALREADY WAITS FOR FSCK TO FINISH, while the progress text
is displayed as usual.

And in future versions, the progressbar will wait for user
input also, like encryption passwords, and continue as
normal after that.

Things are progressing fast.
Please keep telling me your thoughts.
And let's see where this whole thing will end!]]> Wed, 19 Nov 2008 23:10:11 +0000 Thu, 20 Nov 2008 15:47:24 +0000 That's an interesting idea!
This is completely theme-based, and depends solely on the theme artist.
I am planning on creating a uplash-smooth themes pack.
Be sure that I'll look into this idea!]]> Thu, 20 Nov 2008 16:21:38 +0000 Thu, 20 Nov 2008 17:14:53 +0000 > First boot EXTREMELY INACCURATE (obviously hasn't got any "referral time"
> Second boot ACCURACY TO 99%

It's sure, if you get an error this bar could be a problem!

We need an hybrid solution!]]> Fri, 21 Nov 2008 08:02:30 +0000 Fri, 21 Nov 2008 19:06:00 +0000
Instead of timing the bootup and providing a total progress based on that, it should be possible to time each process (using something like bootchart) and dividing the progress bar up into differently sized chunks to represent the time they take. It still wouldn't be ideal, since handling the last process would take a few experiments to determine the most natural progression, but it would be an improvement at least.]]> Tue, 25 Nov 2008 02:28:07 +0000 +1]]> Tue, 25 Nov 2008 23:19:25 +0000 you're definitely right.
I think that the current progress, with its glitches and breaks and steps inspires doubt and incertainty.

We have to remember that this is not a certified measure tool. So I think that the progress bar should be smoothed out so the user gets more calm, and happy. ]]> Wed, 26 Nov 2008 08:46:01 +0000 +0 for now!]]> Mon, 08 Dec 2008 03:05:28 +0000 Sat, 13 Dec 2008 08:14:02 +0000
I'd much rather get a little more information on what's going on than a timed splash. The current way lets me know things are in fact happening (or not).]]> Sun, 14 Dec 2008 17:37:39 +0000 I have tried your deb and the startup bar is very smooth !
And I had no problem when the check dist occured.

With this, we know exactly when the system will be ready, and then the startup seems quicker because the bar is always moving on with the same speed.

It will be nice if it is integrated with the next ubuntu release.]]> Mon, 15 Dec 2008 20:26:26 +0000 Wed, 17 Dec 2008 12:13:33 +0000 Wed, 17 Dec 2008 23:59:55 +0000