Propose your solution
Attachments
Duplicates
Comments
|
|
|
One thing i'd like to see would be playing a low res movie on first boot. This would be exceptionally slick and resemble other oses
|
|
madman2k
wrote on the 28 Feb 08 at 16:08
|
|
|
|
that would need a new Xorg with kernel mode-switching.
|
|
|
I believe splashy or the one used in gentoo (fbsplash?) are better then currently used one in Ubuntu. Easier to create themes, no recompilation needed and I think it supports more features as well.
It would be nice to have one screen resolution since the first boot message and no switching (at least no notice).
Currently:
bootloader - resulution X
splash - resolution Y
GDM - resolution Z
user desktop - possibly resolution Z
|
|
Oli
wrote on the 28 Feb 08 at 20:53
|
|
|
Forum thread: http://ubuntuforums.org/showthread.php?t=477426
It was generally accepted at usplash was serving a purpose that splashy (amongst other more usable, better looking bootsplash modules) could not: framebuffering.
But I don't understand how other established distributions that use splashy (et al) get around the problem and why Ubuntu devs can't simply rip out their work and plug it into Ubuntu.
At the moment it looks like they're pouring hundreds of man hours into reinventing the wheel and coming up with a substandard replacement... This time could be used on improving an established solution!
|
|
|
|
Just a note to say that hopefully users don't boot all that often compared to how much time they spend using the system. It seems like bug fixes in apps and better integrating different apps to create a coherent desktop should take precedence over bling users hopefully see no more than once a day or so.
|
|
|
|
While it's true that ideally boot sequence ought to be a rare(r) occurance, it's still the first impression. While it's true that most of the intensive effort should be done remodeling the interior, there's something to be said for having good curb appeal.
|
|
MLange
wrote on the 29 Feb 08 at 03:12
|
|
|
I would still like to see, though, as a method of telling whether the computer is actually DOING something, a list of processes it's doing, or even just the current process it's working on listen on the bottom of the screen.
IE. "Configuring Network", "Checking Filesystem", etc.
|
|
fsamuels
wrote on the 29 Feb 08 at 03:24
|
|
|
|
I would love to see a boot like Fedora. I hate that there is no indication of what is going on when your system boots. I also like how Fedora has the simple default mode but also an ability to show details and see everything that is going on. The boot obviously should not be over informative and intimidating but I think saying things like "Enabling networking" and other broad start up tasks is not too much.
|
|
smenjas
wrote on the 29 Feb 08 at 04:52
|
|
|
|
This LWN article talks about the future of X and specifically mentions flicker-free boots. Pretty exciting!
|
|
cmr
wrote on the 29 Feb 08 at 05:03
|
|
|
an uninformative boot sequence leaves a user ignorant when the boot process fails and frustrated that the machine will not tell him what is wrong.
to prioritize fixing cosmetic transitions between different phases of the boot sequence is deeply misguided.
a quality boot sequence is one that 1) brings the machine to its highest possible level of functionality when something is broken and 2) provides accurate, helpful information about problems when they do occur.
|
|
afuchs
wrote on the 29 Feb 08 at 05:38
|
|
|
|
Just noting that Gutsy's bootsplasy doesn't function properly on my laptop (1280x800).
|
|
jvin248
wrote on the 29 Feb 08 at 06:16
|
|
|
Boot sequence needs to be quick, display progress, and inform of errors.
I usually turn off as much boot gui as possible (editing grub menu). I use the text mode to gauge completion and avoid most of the mode switching events.
If a thermometer is used, have it show completion not cycle back and forth (annoying on Windows XP too).
Avoid confusing newbs on initial screen (regular text is ok here by the way) use "boot live-cd" as the default option, then "install" as it's own line (option gui or text install would be nice). Also, put a blank line between the default line and other options to visually break up the events and not force a default-booting-newb getting confused.
J
|
|
|
Never mind all the fancy graphics on boot -- it just slows the boot down. Bad idea.
BUT: if we could reduce the number of mode changes, that would make the thing look much better.
Maybe like the end title sequence for Portal ;) ?
|
|
|
My TFT panel shows after each mode change an information window for 5 seconds. It never really disappears for the first 30 seconds at this moment, blocking the visibility of everything at the middle of the screen.
Implementing this idea would be good because it would make Linux desktop seem far more polished and aesthetic. People do care about those things. A Lot.
|
|
probono
wrote on the 1 Mar 08 at 16:16
|
|
|
|
Have a look at how Fedora 8 Live CD does this... apparently they're starting X as the first thing, for displaying the boot screen...
|
|
smenjas
wrote on the 2 Mar 08 at 07:28
|
|
|
|
Doesn't look to me like this is really a duplicate of idea #37. That one deals specifically with the boot loader, whereas this deals with the whole boot sequence including mode switches.
|
|
smenjas
wrote on the 2 Mar 08 at 07:29
|
|
|
Oops! I meant:
Doesn't look to me like this is really a duplicate of idea #21. That one deals specifically with the boot loader, whereas this deals with the whole boot sequence including mode switches.
|
|
Ubuwu
wrote on the 4 Mar 08 at 20:29
|
|
|
|
Yes, this is not a duplicate. Any way to report this?
|
|
doughy
wrote on the 6 Mar 08 at 05:17
|
|
|
|
Just casting my vote for "Not a duplicate."
|
|
gedeon
wrote on the 19 Mar 08 at 16:36
|
|
|
|
FWIW, I've suggested a way to "Report wrong duplicates" (idea #5132).
|
|
|
|
We're currently working on this issue (Ubuntu Artwork team). Please post your ideas on the blog.
|
|
jeypeyy
wrote on the 11 Oct 09 at 16:15
|
|
|
|
It's being developed right now and it's a lot better in karmic.
|
Post your comment
|
Blueprint slick-boot:
