Usplash switches to text when running fsck and won't switch back

[Martin Böhm]

In my Kubuntu Edgy RC machine, the usplash switches to console mode when running "fsck", even when it doesn't do anything more than just quick checking all partitions (no scan, no errors found). This bug occurs only on my laptop which contains a FAT32 partition, too.

[Jens (jens-launchpad-net)]

Hi,

I have exactly the same problem. I have two machines, laptop with dapper (and no FAT partitions) and a workstation (also no FAT partitions). On the laptop it doesn't do this, on the workstation it does.

The workstation also has two "//smb-server/share " style CIFS mounts in the /etc/fstab - might this be related to the problem?

If I switch auto-check during boot off (last column in fstab 2 -> 0) the bootsplash stays. So something in reiserfsck triggers usplash to change back to text mode.

But what? And how do I find out?

Jens

[Jens (jens-launchpad-net)]

See Bug 38303 - usplash goes into text mode if it does not see any activity for 15 seconds (by default). I guess this is configurable somewhere ... I just don't know where.

[Motin (motin)]

Thanks for taking the time to report this bug. In order to proceed, we need some more information from anyone who experiences this problem:
 * Is there less or more than 15 seconds of inactivity prevalent before the switch to textmode?
 * What are the contents of /etc/fstab for the system(s) experiencing this issue?

(Btw, this is not a duplicate of #38303 since #38303 is only applicable when complete scans/checks are performed)

[Adolfo González Blázquez (infinito)]

This happens when the system does the fscking after mounting partitions, I mean that fsck that is always done. In my system there's no noticable inactivity before the switch.

My fstab is:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0

# /dev/sda3
UUID=6042b87d-09b3-488e-a4db-474d6dbb8572 / ext3 defaults,errors=remount-ro 0 1

# /dev/sda1
UUID=988456928456732C /media/sda1 ntfs defaults,user,noauto,umask=007,gid=46 0 1

# /dev/sda5
UUID=46D4-801B /media/sda5 vfat defaults,user,utf8,umask=007,gid=46 0 1

# /dev/sda2
UUID=5a60178e-801d-4bbc-aac2-cab8e9221f56 none swap sw 0 0

# cdrom
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0

[Adolfo González Blázquez (infinito)]

This seems to be fixed in my system now with latest updates.

[Saivann Carignan (oxmosys)]

This bug is now fixed in the latest Hardy alpha release. usplash now shows directly fsck outputs without switching to the console. Thanks to everybody who contributed to this bug report.

[Adolfo González Blázquez (infinito)]

Well, I'm using right now Hardy Beta (up to date) and this bug is still affecting me, with same fstab as above.
Is there any command is should run to get this fixed?

[Saivann Carignan (oxmosys)]

Adolfo González Blázquez : Since this bug is fixed for most of people, can you give more informations about your issue? Does this happens everytime fsck starts? Does this happens during fsck checkup or it happens before/after? Also do you have specific messages from fsck, error or warning messages?

[Adolfo González Blázquez (infinito)]

Well, in my case usplash gets killed when a message about dosfsck appears on screen (i have a vfat partition mounted automatically on boot).

/etc/fstab line is:
# /dev/sda5
UUID=47E8-3D46 /media/Data vfat defaults,users,utf8,umask=000,gid=46 0 1

fsck doesn't run, just says something like "partition clean", i mean, is not the long check...

[Adolfo González Blázquez (infinito)]

BTW, setting the "fs_passno" to 0 on fstab, fixes the problem. But i still think this is a bug doesn't it? As with fs_passno 1 or 2 usplash dissapears on dosfsck...

[Adolfo González Blázquez (infinito)]

It seems this was reported and (by mistake?) rejected (#49965)

[Saivann Carignan (oxmosys)]

Re-opened bug 49965, please add a comment to say that you confirm this bug. Thanks for your contribution!

[Khorne (szczygiel-piotr)]

I have this issue since Jaunty. Now I'm using Karmic alpha and it still happens.

Some time ago I reported a bug #364194 so I marked it as a duplicate of this one. See this bug for more info.

[Alex EviL (alex--evil)]

ubuntu jaunty amd64

confirm that bug too, splash dissapears at fsck, in my case it's reiserfs partition. No errors prints in text. There is small pause (3-5 sec) in text output of fsck for my big reiserfs partition, so I guess splash thinks that something bad happens.

Then full fsck check happens - each 30 days or so - splash display messages correctly, it didn't dissapear before complete boot, like in usual routine fsck checks.