Propose your solution
Attachments
Duplicates
Comments
Biornus
(Idea reviewer)
wrote on the 18 Nov 08 at 21:01
|
|
|
It works great and until Plymouth gets implemented I see no reason why not to make it like this.
Maybe it should work as normal the first couple of boots so it has time to learn how to progress smoothly from the start?
|
|
retj
wrote on the 18 Nov 08 at 21:01
|
|
|
|
Does it work with any Usplash Theme?
|
|
volanin
wrote on the 18 Nov 08 at 21:07
|
|
|
> 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!
|
|
gmatht
wrote on the 19 Nov 08 at 01:20
|
|
|
"If Ubuntu decides to check for errors, the progress bar will fill up in 30 seconds and stay filled until Gnome starts."
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.
|
|
retj
wrote on the 19 Nov 08 at 05:44
|
|
|
|
I use Kubuntu, how can i make it work with it?
|
|
volanin
wrote on the 19 Nov 08 at 06:47
|
|
|
> 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!
|
|
steve196
wrote on the 19 Nov 08 at 10:11
|
|
|
-1
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.
|
|
Dazed_75
wrote on the 19 Nov 08 at 19:20
|
|
|
An absolutely horrible idea. Even worse than the default -quiet option while booting. A time based movement does not indicate progress in any way, shape or form as it simply indicates that interrupts are funtioning and the time based update is working. A machine with a real problem might well sit for 24 hours looking like it was doing something but not doing anything real.
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.
|
|
volanin
wrote on the 19 Nov 08 at 23:10
|
|
|
> 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!
|
|
|
|
Perhaps a time based and a non-time based bar should be displayable
|
|
volanin
wrote on the 20 Nov 08 at 16:21
|
|
|
That's...
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!
|
|
probono
wrote on the 20 Nov 08 at 17:14
|
|
|
|
Plymouth first, then think about this...
|
|
Otacon87
wrote on the 21 Nov 08 at 08:02
|
|
|
Tested it:
> 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!
|
|
_alex_
wrote on the 21 Nov 08 at 19:06
|
|
|
|
Love the idea. Installed and testing now! Keep up the great work.
|
|
Warbo
wrote on the 25 Nov 08 at 02:28
|
|
|
Hmm... I think the jumping progress bar and the time dependence could be seen as different issues. The jumpiness could be smoothed out by staying one step behind in the progress bar, and smoothly moving to the current step.
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.
|
|
Baggers
wrote on the 25 Nov 08 at 23:19
|
|
|
Works brilliantly on my PC, surprising how different the 'feel' is.
+1
|
|
motumboe
wrote on the 26 Nov 08 at 08:46
|
|
|
Volanin,
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.
|
|
|
I'd love to see this as an option at the very least... unfortunately it hasnt worked on either of the computers i've installed it on... just get text output instead. so...
+0 for now!
|
|
DJ_Peng
wrote on the 14 Dec 08 at 17:37
|
|
|
-1
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).
|
|
ktulu77
wrote on the 15 Dec 08 at 20:26
|
|
|
very good work !
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.
|
|
|
|
usplash is going to be replaced with plymouth in jaunty
|
|
borsook
wrote on the 17 Dec 08 at 23:59
|
|
|
|
@graingert - no, in Jaunty +1 i.e. 9.10
|
Post your comment
|
Blueprint usplash-smooth:
Ubuntuforums.org thread #985390
