[Bug 433897] Re: at boot, the font is not set by the upstart job

[Colin Watson]

I have unduplicated this from bug 632382, based on the implicit
assertion in https://code.launchpad.net/~abone/ubuntu/precise/console-
setup/fix-433897/+merge/118886 that these are separate bugs.  I suspect
that in fact many people's problems will be fixed just by the part of it
that nominally fixes bug 632382, but I wanted to make some effort to
separate them out for further analysis.  Here's the comment I made on
the merge proposal:

  After some thought, I agree that this Upstart job is the right thing
to add, and I'm going to apply this to quantal.  Thanks!

  I am much less convinced by the proposal to remove OPTION=FRAMEBUFFER
(and still less by the proposal to force FRAMEBUFFER=y when splash is
enabled; I agree with Oliver on that).  I also don't think that creating
a separate option for it is the right answer.  If the framebuffer isn't
enabled for some other reason, then the console-setup script should not
need to run in the initramfs at all (except in the case of a panic,
which is handled); the fact that this shouldn't be needed is what
OPTION=FRAMEBUFFER expresses.  It should be sufficient for the
corresponding code to run from udev rules and Upstart jobs.

  Therefore, if the udev rules and Upstart jobs aren't working properly
when there is no framebuffer code in the initramfs, that is what needs
to be debugged.  I believe this ought to be possible without running
console-setup code in the initramfs.

For the time being, I'm moving this bug to quantal-updates to indicate
that I'm not going to attempt to fix whatever part of this bug may
relate to OPTION=FRAMEBUFFER et al for 12.10, and not until I have a
better explanation of what's going on there.

** Changed in: console-setup (Ubuntu Quantal)
    Milestone: ubuntu-12.10 => quantal-updates

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/433897

Title:
  at boot, the font is not set by the upstart job

Status in “console-setup” package in Ubuntu:
  Confirmed
Status in “console-setup” source package in Precise:
  Confirmed
Status in “console-setup” source package in Quantal:
  Confirmed

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  Since the Karmic transition away from init.d scripts to upstart services has started, the font is no longer set at bootup. This results in unreadable user prompts, whenever applications output non-ascii characters to screen and it also affects graphic box characters used by ncurses, such as for debconf dialogs.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep 21 12:51:40 2009
  DistroRelease: Ubuntu 9.10
  Package: console-setup 1.34ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fi_FI.UTF-8
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: console-setup
  Uname: Linux 2.6.31-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/433897/+subscriptions