console-setup messes up usplash and vice versa

Bug #60483 reported by Michael Biebl on 2006-09-14
6
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Medium
Colin Watson

Bug Description

If I boot without the splash option, console-setup works as expected and configures the keymap and font correctly.
If I boot with the splash option and remove /etc/rcS.d/S49console-setup, usplash works fine.
If I boot with the splash option and console-setup enabled, usplash freezes half way through the boot process. The last message I can see is
 "Setting up console font and keymap..."
Afterwards I get distorted colors in the bottom half of the screen (see attached screenshot) until X is started.
The font and keymap is *not* properly setup.
If I switch to Alt+F1 and run setupcon, everything is fine. After switching to X and back again to Alt+F1, the console is reset (easily noticeable, because I set up console-setup to use terminus, and I get the bold standard font again).

All in all, usplash and console-setup do not play well together very nicely. This bug is maybe related to #60129

Michael Biebl (mbiebl) wrote :
Michael Biebl (mbiebl) wrote :

 cat /etc/usplash.conf
# Usplash configuration file
xres=1680
yres=1050

Colin Watson (cjwatson) wrote :

The next version of usplash will run setupcon --force when quitting usplash at the end of the boot process, which will help.

Michael Biebl (mbiebl) wrote :

/etc/init.d/console-setup should check, if usplash is running and if so not call setupcon in /etc/rcS.d/S49setupcon.

Matt Zimmerman (mdz) on 2006-09-20
Changed in console-setup:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Colin Watson (cjwatson) wrote :

console-setup (1.7ubuntu10) edgy; urgency=low

  * console-setup Depends: perl; something in ckbcomp is causing perl to
    'use utf8' implicitly, and some of the necessary modules aren't in
    perl-base (closes: Malone #60203).
  * Allow preseeding of console-setup/modelcode, console-setup/layoutcode,
    console-setup/variantcode, console-setup/optionscode, and
    console-setup/fontsize.
  * Don't set up the console font at boot time if usplash is running, since
    that seems to trigger a kernel bug that corrupts the usplash display
    (closes: Malone #60483).

 -- Colin Watson <email address hidden> Thu, 21 Sep 2006 01:01:54 +0100

Changed in console-setup:
status: Confirmed → Fix Released
assignee: nobody → kamion
Michael Biebl (mbiebl) wrote :

Dunno how to reopen this bug report, but there is a regression in feisty:

I'm running console-setup 1.13ubuntu3 and the bug has reappeared.

Matthias Urlichs (smurf) wrote :

(Almost) the same thing happens if you create a new feisty installation using (e.g.) debootstrap.

The reason for this problem appears to be that the postinst script unconditionally runs

    setupcon --force --save

at the end. This messes up the X display. Switching to text mode and back into X cures the display anomaly, but ...

Why is that call there, anyway? It definitely doesn't belong into a postinst!

Matthias Urlichs (smurf) wrote :

re-opening -- regression in Feisty

Changed in console-setup:
status: Fix Released → Confirmed
Matt Zimmerman (mdz) wrote :

Matthias, the issue you describe is recorded by bug 73955

Changed in console-setup:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments