← Back to team overview

kernel-packages team mailing list archive

[Bug 1522472] Re: Black screen on boot after updating Trusty


Kayleigh, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1522472

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: xorg-server (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Black screen on boot after updating Trusty

Status in linux package in Ubuntu:

Bug description:
  Current release: Ubuntu 14.04.3 LTS
  Current version: v3.
  Expected behavior: System boots to GUI showing chromium-browser
  What happened: Booted to black screen

  After updating my linux kernel from v3. to v3., my
  system does not boot into the GUI properly anymore. X11 starts up and
  I have confirmed that I can interact with the screen that should be
  there via keyboard (using chromium logs, I can confirm that I can open
  new tabs with CTRL+T), but the screen is completely black. If I
  restart nodm, X11 restarts and comes up as it should. If I simply
  switch to the vivid kernel (v3. on the same system the
  problem goes away and the system boots properly every time, as well as
  the system working fine until I update just the linux-generic package.

  Other possibly useful information:
  - Every time the system boots to a black screen, plymouth does not appear while booting nor can I TTY switch to it after booting (instead the TTY it should be on is a black screen with a blinking cursor), which is opposite of the behavior observed when the system boots properly.
  - Attached Xorg.0.log (produced from a bad boot).

To manage notifications about this bug go to: