[Bug 632382] Re: Console font does not get set in Maverick

[Colin Watson]

I have unduplicated this from bug 433897, 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 this part of
it, 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.

** This bug is no longer a duplicate of bug 433897
   at boot, the font is not set by the upstart job

** Also affects: console-setup (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: console-setup (Ubuntu Quantal)
   Importance: Undecided
       Status: Confirmed

** Changed in: console-setup (Ubuntu Quantal)
   Importance: Undecided => High

** Changed in: console-setup (Ubuntu Quantal)
     Assignee: (unassigned) => Colin Watson (cjwatson)

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

** Summary changed:

- Console font does not get set in Maverick
+ Console font does not get set

-- 
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/632382

Title:
  Console font does not get set

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

Bug description:
  Binary package hint: console-setup

  Hello,

    I upgraded Lucid to Maverick beta yesterday, and since then the
  console font does not get set properly. After talking with Colin
  Watson, and looking at the console-setup udev rule file
  (/lib/udev/rules.d/85-console-setup.rules). I understand that there is
  a possible race with Plymouth. So as suggested by Colin I created the
  attached upstart job (console-font.conf) to workaround the problem,
  and it worked !

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: console-setup 1.34ubuntu15
  ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
  Uname: Linux 2.6.35-19-generic i686
  Architecture: i386
  Date: Tue Sep  7 14:36:00 2010
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en_GB:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: console-setup

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