Boot messages show before xsplash kicks in

[Jono Bacon]

Binary package hint: upstart

When booting in Karmic I still see many boot messages before xsplash kicks in. These include:

fsck from util-linux-ng 2.16
/dev/sda1: clean 279342/14712832 files, 29086625/58821989 blocks (check in 3 mounts)
 * Setting preliminary keymap...
 * Starting AppArmour profiles
Skipping profile in /etc/apparmour.d/disable: usr.bin.firefox-3.5

 * Setting up console font and keymap
 * Starting OpenBSD Secure Shell server sshd

I also sometimes see this message:

 * Starting database server couchdb

after the ssh server has started.

ProblemType: Bug
Architecture: i386
Date: Mon Sep 28 12:03:00 2009
DistroRelease: Ubuntu 9.10
Package: upstart 0.6.3-5
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: upstart
Uname: Linux 2.6.31-11-generic i686

[Aaron Haviland (aaron-haviland)]

I can confirm this behaviour (installed alpha 6, and upgraded to current package set on 9/27/09).

[Robbie Williamson (robbiew)]

Anything we can do here to get xsplash up faster? Or is this just an issue of overly "chatty" system apps/daemons that we need to quiet somehow?

[Yunkwan (chanyunkwan0217)]

Also messages show up when it is shutting down. Only sometimes can I see the black background with white ubuntu glowing logo show up.

[Harry (harry33)]

After usplash update of 29th September (0.5.39) I always see usplash (the new white logo) when shutting down.
Just as it should be.
But as usplash has been disabled during boot, we of course see messages rolling.
Usplash used to hide them before.

[Arun (akarun)]

Same problem here. I upgraded ubuntu from 9.04
Is it possible that the issues are related to grub. A fresh installation uses grub2

[Sebastian (sebastianhaselbeck)]

same issue, also with USB errors and whatnot....

is there anything i can do just to have this fixed manually until the bugfix is out through updates?

[Robbie Williamson (robbiew)]

@Sebastian: What do you mean by "fixed"? Fixing the error causing the message or hiding the messages? People are welcome to enable usplash at boot by running the following 3 commands:
  sudo -i
  echo USPLASH=y > /etc/initramfs-tools/conf.d/usplash.conf
  update-initramfs -u

[Robbie Williamson (robbiew)]

@Arun: you can convert to grub2 by running: sudo upgrade-from-grub-legacy

[Claus Frein (cfrein)]

I see similar messages and some more. Alpha-6 updated today to karmic-beta (20091002). Output of vt1 is attached.

[Jack Leigh (leighman)]

I get similar, the most notable is starting and stopping firestarter which occurs at boot and shutdown

[Robbie Williamson (robbiew)]

I think I have a quick fix for the NON-kernel related messages...but not sure if it's the RIGHT fix:

1) sudo vi /etc/default/grub
2) Add "console=tty6" to GRUB_CMDLINE_LINUX_DEFAULT:
     "quiet splash console=tty6"
3) save and quit
4) sudo update-grub

This will redirect console messages to tty6 (Ctrl-Alt-F6), instead of tty1. Can folks try this and let me know if it helps at all? Thanks

[sheldonross (ross-sheldon)]

fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
/dev/sda3: clean 279342/14712832 files, 29086625/58821989 blocks (check in 3 mounts)
/dev/sda6: clean 279342/14712832 files, 29086625/58821989 blocks (check in 3 mounts)
 * Setting preliminary keymap...
 * Starting AppArmour profiles
Skipping profile in /etc/apparmour.d/disable: usr.bin.firefox-3.5

 * Setting up console font and keymap
 * Starting database server couchdb

This is more like mine, (i just copied messages from first post though), but I have a seperate home partition which fsck reports, and I don't have openssh-server installed which is likely the case with the first poster.

This is as a fresh install of 9.10 beta alongside a windows partition.

I have autologin enabled and it takes ~50 seconds to startup with no disk activity. Kinda disappointing seeing as how I have a reasonably fast machine (e6750 core2duo, newer 1 TB hd, 8800gts,4gb). Definitely speedier than 9.04 though. Oh well, hopes this helps.

[sheldonross (ross-sheldon)]

Oh yeah, this is AMD64, and I also never see the white ubuntu logo on shutdown.

[Robbie Williamson (robbiew)]

@sheldonross: With regard to the shutdown logo, what type of graphics card do you have?

Also, could you install bootchart and send the .png file in /var/log/bootchart after you reboot *twice* (the first reboot profiles with sreadahead). That may help us see if there's something unexpected going on for you.

Oh, and add the line to /etc/default/grub that I mentioned in comment #13...that should help with the messages.

[Vincent DAVY (vincentdavy)]

Hi everybody,

I am using kubuntu 9.10 beta, and I have the same error messages at boot.
Usplash had been disabled I don't know why so I can't see kubuntu loading progress bar.
I created the usplash config file in the initramfs to enable usplash, made the new initram and rebooted my pc and saw the boot splash working.

I hope usplash will be reactivated for kubuntu users as well gnome people.

Thanks

[Charlie Halford (soupmonster)]

Hi, I'm getting this too, while running Karmic through VirtualBox. Will try the tty redirection.

[Charlie Halford (soupmonster)]

The solution in #13 works well, though in my case a kernel message (I think relating to the fact I'm running it inside VirtualBox), is still showing just before xplash loads. Also, on shutdown, I still get a flicker of messages before usplash takes over.

[Anders Sjöström (anders-sjostrom)]

I have made a clean install of the 9.10 beta on my Acer Aspire One 110L, and I also get similar messages. They flash for 0.5 to 1 second, but in combination with https://bugs.launchpad.net/bugs/413419 that also flashed me, this is a bit too much overall blinking.

My messages transcribed from a bury photo:

fsck from util-linux-ng 2.16
/dev/sda1: clean, 126871/468640 files, 620951/1871564 blocks
 * Starting init crypto disks...
 * cryptswap1 (starting)
init: upstart-udev-bridge main process (442) terminated with status 1
init: upstart-udev-bridge main process ended, respawning
 * Starting early crypto disks... [ OK ]
 * Starting remaining crypto disks [ OK ]
 * Starting AppArmor profiles
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox-3.5
 * cryptswap1 (started)... [ OK ]
                                                                                                                     [ OK ]
 * Starting Kernel Oops catching service kerneloops

(The crypto messages are due to my encrypted home directory. The udev-bridge main process termination message I haven't investigated yet).

[Aurelien Naldi (aurelien.naldi)]

I also noticed this when usplash was removed. It is ugly and indeed a regression from the usplah era but I didn't care... until fsck was triggered.

With usplash we had progress status ans a "skip" option. Now we are back to a cryptic text message without and a system which seems stuck as the old text progress bar is also gone.

Do you have any plan to mitigate this, or at least to add a "... to skip" message and the old progress bar?

[Jack Leigh (leighman)]

I also see the flash of terminal between desktop and shutdown

[Anders Sjöström (anders-sjostrom)]

With the latest package upgrades I no longer see the above messages on the screen.
It would appear that the fix in #13 has been deployed, as I can find them on one of the ttys (shift+alt+f?).

Anyway it is an improvement.

[sheldonross (ross-sheldon)]

Ok, the shutdown graphic appears to be displaying now. I still see several messages before xsplash shows up though.

I've attached a bootchart as of a couple a minutes ago with everything up to date.

[Claus Frein (cfrein)]

After latest updates i still get these messages on the screen, they appear ca. 15 seconds after grub-prompt. Grafix appear at about 7 seconds later, which means the screen is more or less black for about 27 seconds. The whole systems boots in about 1:05 minutes.

Please see attachement for bootchart.

(Just to get a comparison: a windows 7 boots in about 25 seconds on the same pc to the login-prompt.)

[hewbert (josh-hewbert)]

I'm experiencing this as well. I'm using Grub 1 (not a fresh install)..

After selecting the kernel to boot, the screen goes black for a few seconds, then on to the above messages (fsck [clean] and a few others.. then finally xsplash). It does indeed seem like a regression from the behavior in Jaunty - a completely quiet startup. Is this expected behavior? I'm willing to submit whatever logs are needed if it can help.

[Robbie Williamson (robbiew)]

@hewbert: FYI, you can convert to grub2 by running:
   >sudo upgrade-from-grub-legacy

[hewbert (josh-hewbert)]

@Robbie Williamson:
Thanks. Actually, I did convert to grub2 after posting, fwiw ;)

[Anders Sjöström (anders-sjostrom)]

I take back what I wrote in #23. It seems I was fooled by the big variations in how long time the messages are shown (estimate 0.1-1.5 second).

Anyway, I have a fresh install which should mean grub2.

[Robbie Williamson (robbiew)]

@Claus: could you copy and paste the output of the following command:
  > dpkg -l | grep couch
  > dpkg -l | grep xulrunner

Your bootchart has some crazy stuff going on with couchdb and xulrunner.

[Claus Frein (cfrein)]

@Robbie: Sure, no problem:

$ dpkg -l | grep couch
ii couchdb 0.10.0~svn818859-0ubuntu1 RESTful document oriented database, system D
ii couchdb-bin 0.10.0~svn818859-0ubuntu1 RESTful document oriented database, programs
ii desktopcouch 0.4.2-0ubuntu1 A Desktop CouchDB instance
ii evolution-couchdb 0.3.0-0ubuntu2 Evolution support for CouchDB databases
ii libcouchdb-glib-1.0-1 0.5.1-0ubuntu1 GLib-based API for CouchDB
ii python-couchdb 0.6-1 library for working with Apache CouchDB
ii python-desktopcouch 0.4.2-0ubuntu1 Python Desktop CouchDB
ii python-desktopcouch-records 0.4.2-0ubuntu1 Desktop CouchDB Records API

$ dpkg -l | grep xulrunner
ii xulrunner-1.9.1 1.9.1.3+build1+nobinonly-0ubuntu4 XUL + XPCOM application runner
ii xulrunner-1.9.1-gnome-support 1.9.1.3+build1+nobinonly-0ubuntu4 Support for GNOME in xulrunner-1.9.1 applica

[Lance Stuetzle (lancestu-gmail)]

Fresh install Karmic beta- updated for today.
Get the following boot messages:
Sdb assuming drive cache: write through
fsk (3x)
setting prelim keymap
starting AppArmour profiles
setting up console font
running DKMS auto install service for kernel
nvidia (185.18.36)
starting kernel Oops caching service
starting cups
Pulse Audio configured for per:user sessions
enabled additional executable binary formats
checking battery state
Ubuntu Karmic (dev branch) tty1

[Fabian A. Scherschel (fabsh)]

I completely agree with what Adrian Glaubitz has posted on the dupe Bug 443282:

The text is just *ugly* and it's a huge step backwards compared to Jaunty IMHO ! That reminds me of my days with SuSE Linux 5.3 with kernel 2.0.38 and not the current version of Ubuntu as of fall 2009. People will complain about this. If I want to have text boot messages, I turn splash screens off manually, but the default boot design should be neat and all graphically. If you can't use KMS for whatever reason, then you should have stayed with usplash.

I suggest blanking the screen completely during boot. I hope to see KMS-based splash screens in 10.04, though.

Adrian

[pasta (pasta-bolognese)]

see the errors that it display during the boot in the attached file

[Kai Jauch (kaijauch)]

@Robbie in #13: This is how boot looks on a Dell Latitude E6400 (TOSHIBA MK1652GSX hdd):

Booting with usplash enabled:
   http://www.youtube.com/watch?v=y028WaypT_c
Bootchart:
   http://img4.imageshack.us/img4/9678/tezrakarmic200910075.png

Booting with usplash enabled and console set to tty6:
   http://www.youtube.com/watch?v=KuGK5ZvgDso
Bootchart:
   http://img143.imageshack.us/img143/2030/tezrakarmic200910076.png

With usplash enabled and console=tty6 you see a blinking cursor for a few seconds when usplash is exiting (because GDM takes a while to start X), but no other messages.

[Kai Jauch (kaijauch)]

Bah, wrong file for the first bootchart, it is actually this one: http://img7.imageshack.us/img7/2641/tezrakarmic200910073.png

[Arun (akarun)]

The second one wasn't too bad.
Slightly unrelated question.. why are the boot times so high? Its pretty high even for me.. around 1min +

[Robbie Williamson (robbiew)]

See bug 432089: performs poorly on slow HDD

[sheldonross (ross-sheldon)]

http://www.tomshardware.com/reviews/green-terabyte-1tb,2078-2.html

My HD isn't especially slow, but if that's the explanation, I guess I'll buy it.

[Matthew J. Ballard (sapphiretiger)]

I get get messages about it, upstart-udev-bridge respawning, AES-NI not being detected and padlock sha being missing.

I blacklisted padlock related stuff since I'm not using VIA-anything which seemed to remove the message about the module being missing, but the other two still show up. Ugly (and not as snappy) boot indeed.

[Matthew J. Ballard (sapphiretiger)]

Hm, the frustration from regressions in boot-experience introduced by *me* on one of *my own installs* spilled over here. Sorry about that. Anywho...

Reinstalled upstart and udev related packages:

udev, libudev0 (147~-5)
upstart (0.6.3-7)

upstart-udev-bridge respawning messages seem to have disappeared. Still no joy with AES-NI. Still get a bit of text (other than AES-NI, its all various "starting" messages) and a few seconds delay before xsplash kicks in and will even sit at a visible console login for a second before it does on occasion. Removed as much as I could (couchdb and co. included) with no visible change. Apparmor doesn't mention a thing about firefox now, though. Hm..

[Binoy (mailbinoyv)]

I am seeing some usb messages and if my external hdd is connected some messages for sdb. Please check the attached screenshot

[Leandro (leandromartinez98)]

The expected behaviour is to see the small white ubuntu logo on boot or not?

I think there is a confusion here for the less technical people like me about what
is Xplash and what is the small white ubuntu logo, and should we expect from the boot
(appart from not seen text, of course). It would be nice to indicate exactly what is
that developers are expecting the boot to behave, so that we can know exactly
what is a problem or not. For example, I see about 20 seconds of a blinking cursor
before Xplash. Should I see that at all?

[Kai Jauch (kaijauch)]

@Robbie in #13:
While adding console=tty6 to GRUB_CMDLINE_LINUX_DEFAULT does indeed hide any non-kernel messages, it also hides the emergency shell one gets if a manual fsck is necessary. usplash leaves you on tty1 when it exits, but the emergency shell is waiting for you on tty6.

[Leandro (leandromartinez98)]

Now, in desktop (I will post the apport-collect data in what follows), I get the following messages
before xplash on boot:

---------------------------------------------------
fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
/dev/sda1: clean, 236191/1221600 files, 1992474/4883752 blocks
/dev/sda3: clean, 63622/8298496 files, 21444107/33188281 blocks
init: rpc_pipefs pre-start process (871) terminated with status 1
init: idmapd pre-start process (879) terminated with status 1
init: rpc_pipefs pre-start process (900) terminated with status 1
init: gssd pre-start process (901) terminated with status 1
 * Setting preliminary keymap...
 * Stopping NTP server ntpd
 * Preparing restricted drivers...
 * Starting AppArmor profiles
 * Setting up console font and keymap...
 * Starting OpenBSD Secure Shell server sshd
 * Running DKMS auto installation service for kernel 2.6.31-12-generic
 * fglrx (8.660)...
   ...done.
 * vboxdrv (3.0.6)...
   ...done.
 * vboxnetadp (3.0.6)...
   ...done.
---------------------------------------------------

Does reporting this helps anything at this point?

[Leandro (leandromartinez98)]

Well apport didn't send any data. Here is the dmesg:

[flowerdealer (pixelcowboy79)]

Its fixed for me after updates this morning, booting still feels a bit slow
and there are some glitches and flickering, otherwise its fine.

On Fri, Oct 9, 2009 at 7:28 AM, Leandro <email address hidden> wrote:

> Well apport didn't send any data. Here is the dmesg:
>
>
> ** Attachment added: "Dmesg of the desktop of Leandro."
> http://launchpadlibrarian.net/33354195/dmesg_leandro.log
>
> --
> Boot messages show before xsplash kicks in
> https://bugs.launchpad.net/bugs/438335
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Ubuntu: Confirmed
> Status in The Karmic Koala: Confirmed
>
> Bug description:
> Binary package hint: upstart
>
> When booting in Karmic I still see many boot messages before xsplash kicks
> in. These include:
>
> fsck from util-linux-ng 2.16
> /dev/sda1: clean 279342/14712832 files, 29086625/58821989 blocks (check in
> 3 mounts)
> * Setting preliminary keymap...
> * Starting AppArmour profiles
> Skipping profile in /etc/apparmour.d/disable: usr.bin.firefox-3.5
>
> * Setting up console font and keymap
> * Starting OpenBSD Secure Shell server sshd
>
> I also sometimes see this message:
>
> * Starting database server couchdb
>
> after the ssh server has started.
>
> ProblemType: Bug
> Architecture: i386
> Date: Mon Sep 28 12:03:00 2009
> DistroRelease: Ubuntu 9.10
> Package: upstart 0.6.3-5
> ProcEnviron:
> LANGUAGE=en_US.UTF-8
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> SourcePackage: upstart
> Uname: Linux 2.6.31-11-generic i686
>

[Fabian A. Scherschel (fabsh)]

With the lastest updates this morning on Xubuntu I now get:

"Grub loading" -> usplash -> blank screen -> xsplash -> GDM

So I'll consider this fixed for me. Thanks to everyone involved in fixing this!

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

I haven't had a chance to update yet today, but if you're seeing USplash
and then XSplash in the same boot, shouldn't that be considered a bug?

[Leandro (leandromartinez98)]

Same as Fabian for me in the desktop I just reported (I applied now the updates from the main server, the
brazilian server was a little bit outdated).

The total boot time is 47 seconds in this desktop until GDM. (no automatic login).

The blank screen takes a little too long, and in my case is not totally blank, it actually
displays a blue pixeled bar, xplash starting a little bit early or usplash starting a little
bit latter would be better.

Thanks everyone for the fixes!

[Fabian A. Scherschel (fabsh)]

@Jeremy: No, since the alternative is ugly CLI messages at the moment...

[flowerdealer (pixelcowboy79)]

Exactly the same as Leandro for me in Kubuntu.

On Fri, Oct 9, 2009 at 8:52 AM, Fabian A. Scherschel <email address hidden>wrote:

> @Jeremy: No, since the alternative is ugly CLI messages at the moment...
>
> --
> Boot messages show before xsplash kicks in
> https://bugs.launchpad.net/bugs/438335
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Ubuntu: Confirmed
> Status in The Karmic Koala: Confirmed
>
> Bug description:
> Binary package hint: upstart
>
> When booting in Karmic I still see many boot messages before xsplash kicks
> in. These include:
>
> fsck from util-linux-ng 2.16
> /dev/sda1: clean 279342/14712832 files, 29086625/58821989 blocks (check in
> 3 mounts)
> * Setting preliminary keymap...
> * Starting AppArmour profiles
> Skipping profile in /etc/apparmour.d/disable: usr.bin.firefox-3.5
>
> * Setting up console font and keymap
> * Starting OpenBSD Secure Shell server sshd
>
> I also sometimes see this message:
>
> * Starting database server couchdb
>
> after the ssh server has started.
>
> ProblemType: Bug
> Architecture: i386
> Date: Mon Sep 28 12:03:00 2009
> DistroRelease: Ubuntu 9.10
> Package: upstart 0.6.3-5
> ProcEnviron:
> LANGUAGE=en_US.UTF-8
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> SourcePackage: upstart
> Uname: Linux 2.6.31-11-generic i686
>

[Robbie Williamson (robbiew)]

Everyone,

We've made some improvements. If you've done the console=tty6 or USPLASH=y workarounds, please rever those. Then, do an 'sudo apt-get update' and then 'sudo update-manager'. We are also working with the kernel team to handle the kernel console chatter at boot.

[Rachel Greenham (rachel-strangenoises)]

Confirmed; on my netbook now I just get flashing (VGA) cursor after grub's menu has disappeared, then usplash, then a few seconds of flashing cursor again (framebuffer) then xsplash. Not perfect, but getting better... :-)

Total boot time from pressing return in the grub menu to the unr desktop ready for use, about 50sec.

[Robbie Williamson (robbiew)]

On Fri, 2009-10-09 at 14:31 +0000, Rachel Greenham wrote:
> Confirmed; on my netbook now I just get flashing (VGA) cursor after
> grub's menu has disappeared, then usplash, then a few seconds of
> flashing cursor again (framebuffer) then xsplash. Not perfect, but
> getting better... :-)
>
> Total boot time from pressing return in the grub menu to the unr desktop
> ready for use, about 50sec.
>
Thanks for the feedback. We may be able to reduce the time between
usplash and xsplash with some gdm hacking. Just as an FYI, UNR has it's
own issues around boot performance, separate from the standard Desktop,
that we can hopefully plan to focus on in 10.04.

--
Robbie Williamson <email address hidden>
Ubuntu

[Colin Watson (cjwatson)]

We may be able to shorten the time between usplash and xsplash. Given current technology, we can't get it down to zero, so some flicker will still be visible for now. The same goes for X->usplash on shutdown, although that time is probably as short as it will get for Karmic.

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

Perhaps you can just make the USplash a plain black screen so no one
notices it?

> -------- Original Message --------
> Subject: [Bug 438335] Re: Boot messages show before xsplash kicks in
> From: Colin Watson <email address hidden>
> Date: Fri, October 09, 2009 10:52 am
> To: <email address hidden>
>
>
> We may be able to shorten the time between usplash and xsplash. Given
> current technology, we can't get it down to zero, so some flicker will
> still be visible for now. The same goes for X->usplash on shutdown,
> although that time is probably as short as it will get for Karmic.
>
> --
> Boot messages show before xsplash kicks in
> https://bugs.launchpad.net/bugs/438335
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.

[Robbie Williamson (robbiew)]

On Fri, 2009-10-09 at 15:05 +0000, Jeremy LaCroix wrote:
> Perhaps you can just make the USplash a plain black screen so no one
> notices it?
>
I thought about that, but I think the problem with that approach is that
for machines where it takes awhile for X to come up, users may think
their machine is hung b/c they see nothing to indicate that it has
loaded.

--
Robbie Williamson <email address hidden>
Ubuntu

[Jeremy LaCroix (jlacroix82-deactivatedaccount)]

Static Kubuntu/Ubuntu/Xubuntu/Edubuntu logo with no animation then?
(Maybe even with please wait... on the bottom)

> -------- Original Message --------
> Subject: RE: [Bug 438335] Re: Boot messages show before xsplash kicks
> in
> From: Robbie Williamson <email address hidden>
> Date: Fri, October 09, 2009 11:25 am
> To: <email address hidden>
>
>
> On Fri, 2009-10-09 at 15:05 +0000, Jeremy LaCroix wrote:
> > Perhaps you can just make the USplash a plain black screen so no one
> > notices it?
> >
> I thought about that, but I think the problem with that approach is that
> for machines where it takes awhile for X to come up, users may think
> their machine is hung b/c they see nothing to indicate that it has
> loaded.
>
> --
> Robbie Williamson <email address hidden>
> Ubuntu
>
> --
> Boot messages show before xsplash kicks in
> https://bugs.launchpad.net/bugs/438335
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.

[Rachel Greenham (rachel-strangenoises)]

I'm happy with it; as long as it's not there too long, think of it as
analogeous to the grey apple you get at the start of the Apple boot process.

Of course they're *way* ahead. That apple is the *first* thing you see
after power-on (unless you have rEFIt or something installed), and it
segues pretty gracefully to the blue desktop...

Jeremy LaCroix wrote:
> Static Kubuntu/Ubuntu/Xubuntu/Edubuntu logo with no animation then?
> (Maybe even with please wait... on the bottom)
>
>
>> -------- Original Message --------
>> Subject: RE: [Bug 438335] Re: Boot messages show before xsplash kicks
>> in
>> From: Robbie Williamson <email address hidden>
>> Date: Fri, October 09, 2009 11:25 am
>> To: <email address hidden>
>>
>>
>> On Fri, 2009-10-09 at 15:05 +0000, Jeremy LaCroix wrote:
>>
>>> Perhaps you can just make the USplash a plain black screen so no one
>>> notices it?
>>>
>>>
>> I thought about that, but I think the problem with that approach is that
>> for machines where it takes awhile for X to come up, users may think
>> their machine is hung b/c they see nothing to indicate that it has
>> loaded.
>>
>> --
>> Robbie Williamson <email address hidden>
>> Ubuntu
>>
>> --
>> Boot messages show before xsplash kicks in
>> https://bugs.launchpad.net/bugs/438335
>> You received this bug notification because you are a direct subscriber
>> of a duplicate bug.
>>
>
>

[John Paul Adrian Glaubitz (glaubitz)]

I would consider this as a temporary solution for now. Once kernel-based mode setting (KMS) is working for most cards, one should switch to kms here. It provides the smoothest possible boot experience. Once the video-mode is switched into the proper one directly after grub, there won't be any mode-switches anymore and gdm can even fade-in into the text console during boot. That looks awesome. Fedora has incorporated plymouth with kms already and it worked with both all the ATI and Intel cards I tested. Nvidia is work-in-progress.

@Rachel:

You probably could have something like this on the PC as well if you use "coreboot" as a BIOS-replacement. I guess coreboot together with KMS could provide the smoothest boot-experience ever and it would be highly customizable, one thing that you'll never get on a Mac.

Adrian

[Leandro (leandromartinez98)]

  By the way, the usplash on shutdown now, instead of the very simple and elegant ubuntu
logo, it shows the ubuntu logo surrounded by an horrible grey line, and with a small grey
circle in the middle. I suppose this was added to differenciate it from the boot ubuntu logo,
but it is uglier now. If you want to differenciate it from boot, I suggest changing a little
bit its color, to a fade brown, for example.

[flowerdealer (pixelcowboy79)]

Same here, and boot times are 50 seconds plus, when with jaunty it was
around 20 seconds.

On Fri, Oct 9, 2009 at 3:35 PM, Leandro <email address hidden> wrote:

>
> By the way, the usplash on shutdown now, instead of the very simple and
> elegant ubuntu
> logo, it shows the ubuntu logo surrounded by an horrible grey line, and
> with a small grey
> circle in the middle. I suppose this was added to differenciate it from the
> boot ubuntu logo,
> but it is uglier now. If you want to differenciate it from boot, I suggest
> changing a little
> bit its color, to a fade brown, for example.
>
> --
> Boot messages show before xsplash kicks in
> https://bugs.launchpad.net/bugs/438335
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Ubuntu: Confirmed
> Status in The Karmic Koala: Confirmed
>
> Bug description:
> Binary package hint: upstart
>
> When booting in Karmic I still see many boot messages before xsplash kicks
> in. These include:
>
> fsck from util-linux-ng 2.16
> /dev/sda1: clean 279342/14712832 files, 29086625/58821989 blocks (check in
> 3 mounts)
> * Setting preliminary keymap...
> * Starting AppArmour profiles
> Skipping profile in /etc/apparmour.d/disable: usr.bin.firefox-3.5
>
> * Setting up console font and keymap
> * Starting OpenBSD Secure Shell server sshd
>
> I also sometimes see this message:
>
> * Starting database server couchdb
>
> after the ssh server has started.
>
> ProblemType: Bug
> Architecture: i386
> Date: Mon Sep 28 12:03:00 2009
> DistroRelease: Ubuntu 9.10
> Package: upstart 0.6.3-5
> ProcEnviron:
> LANGUAGE=en_US.UTF-8
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
> SourcePackage: upstart
> Uname: Linux 2.6.31-11-generic i686
>

[andbelo (andbelo)]

I would like to add a note about another message that is showing up after the white ubuntu logo and the xsplash. I installed using a desktop alternate CD with full encryption.

As expected I'm asked for the passphrase with the white ubuntu logo. After that I see a black screen with the messages about the unlock of the internal hard-drives, then I see the xsplash.

The message follows:

key slot 0 unlocked.
Command successful.
File descriptor 3 left open
  4 logical volume(s) in volume group "laptop" now active

[sebastian-s (sebastian-s)]

Hi,
I had these three on three machines I ran the Beta CD on:

 * Starting init crypto disks... [ OK ]
 * Starting early crypto disks... [ OK ]
 * Starting remaining crypto disks [ OK ]

One of the machines (a notebook) booted without problems on the two desktops the investigation is on going :-)

[stef.baly (stef-baly)]

I've almost the same problem. Error message on screen.
Anyway even if it's seams to be OK, a professional OS should display such kind of message !

[Sean Fitzpatrick (sean-fitzpatrick)]

I think a problem I noticed today is related to this - I'd like to confirm before making a new entry:
I've had 9.10 beta running long enough that today it booted with the routine check of the filesystem.
This takes place while still at the black screen with the fuzzy Ubuntu logo (which probably is not meant to be fuzzy but I haven't found a screen resolution that works). Anyway, instead of a graphical progress dialog, like in 9.04, there is just a bunch of scrolling text on the bottom half of the screen. Functionally it's not a problem, but it's definitely not very pleasant-looking.

[David Stansby (dstansby-deactivatedaccount)]

I think Alan Pope filed a bug that sounds similar to what you've described Sean. It's bug 457496

[Sean Fitzpatrick (sean-fitzpatrick)]

Thanks - that report is exactly what I observed; my searches on google this morning failed to turn it up!

[Id2ndR (id2ndr)]

A friend of mine still get about 5 lines of messages in VT that appears between usplash and xsplash. I haven't try console=tty6 for this computer.

Is there other personn with this issue ? I saw about 6 computers with karmic and there are 2 which still display these lines:
- the one of a friend (with proprietary nvidia). It seems that usplash crashed when X was loading nvidia modules.
- my laptop (with intel KMS) bug I don't have any idea of the cause.

[Robbie Williamson (robbiew)]

On Tue, 2009-11-03 at 23:32 +0000, Id2ndR wrote:
> A friend of mine still get about 5 lines of messages in VT that appears
> between usplash and xsplash. I haven't try console=tty6 for this
> computer.
>
> Is there other personn with this issue ? I saw about 6 computers with karmic and there are 2 which still display these lines:
> - the one of a friend (with proprietary nvidia). It seems that usplash crashed when X was loading nvidia modules.
> - my laptop (with intel KMS) bug I don't have any idea of the cause.
>

Shouldn't need "console=tty6" anymore. The "quiet" kernel option
combined with changes to usplash /should/ be squelching most messages.
However, there is an allowance for messages underneath the black and
white usplash logo for things like fsck messages and such. What are the
5 lines your friend is seeing?

--
Robbie Williamson twitter/identi.ca: undacuvabrutha
Ubuntu Foundations & Security Team Manager robbiew[irc.freenode.net]
http://wiki.ubuntu.com <email address hidden>

"You can't be lucky all the time, but you can be smart everyday"
 -Mos Def

"Arrogance is thinking you are better than everyone else, while
Confidence is knowing no one else is better than you." -Me ;)

[Tristan Tarrant (tristan-tarrant-gmail)]

The only two lines of text I get now are produced by usplash I guess. They are about failing to set a resolution of 1152x864 and falling back to 1024x768 (my LCD has a native resolution of 1440x900).

[Claus Frein (cfrein)]

The same message appears on my computer (cannot set to 1152x864, setting to 1024x768).

After starting of gdm, the screen-resolution seems to switch between this settings at least two times.

[Andreas Schildbach (schildbach)]

I still see the occasional textual login prompt between usplash and xsplash.

[Robbie Williamson (robbiew)]

Tristan/Claus: can one of you open a separate bug for this issue? You can simply type "ubuntu-bug usplash" in a terminal and it should do the rest for you. Then subscribe me to it (LP ID is robbie.w).

[Robbie Williamson (robbiew)]

The issues from the original reporter have been addressed. Anyone seeing more messages should open a separate bug against usplash. I would like to note that briefly seeing a login prompt between usplash and xsplash, while a bit ugly, is unfortunately expected in Karmic. We will be cleaning up the boot screen transitions in Lucid.

[Id2ndR (id2ndr)]

Robbie Williamson: I create new bug for the trouble of my friend: https://bugs.launchpad.net/bugs/474720. I just subcribed you to this bug.

I'll create a new bug for my laptop as you explain to Tristan and Claus: I encounter exactly the same bug as them.

[T. Dalbo (tdalbo)]

I have the same showings that Andreas has, with the brief textual login. It's definitely still usable, but not as smooth as Fedora or (dare I say it) Windows.