[Bug 1046957] Re: "error during filesystem" turns off monitor, never comes back on

Bryce Harrington 1046957 at bugs.launchpad.net
Fri Sep 14 20:37:37 UTC 2012

That's actually prior to when X actually gets started up.

** Package changed: xorg (Ubuntu) => plymouth (Ubuntu)

You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.

  "error during filesystem" turns off monitor, never comes back on

Status in “plymouth” package in Ubuntu:

Bug description:
  I've noticed that my monitor turns off at some point halfway during
  booting.  I ignored the problem, since they always turned back on
  until now.

  With 12.10 my monitor wasn't turnning back on.  Eventually i managed to get it turned back on with these steps, (nothing else worked) 
  1. switch to the console ctrl+alt+f1 and turn off the monitor
  2. turn on the monitor
  3. switch back to the error with ctrl+alt+f7

  at which point i realized had an error during booting.  it looked much
  like this error:

  it had this message "serious errors were found while checking the disk
  drive for /" which I later fixed by installing xfsprogs

  but the actual problem is that my monitor is getting put in suspend
  mode or "can't display this" mode  and never comes back on to display
  the error.  This is a problem, because there is no indication of
  anything bug a blank screen.  It's a HDMI monitor.

  I'm using an ATI 5750 card with a hanspree HF259H monitor.  Should be
  able to reproduce with any error on the splash screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu4
  Architecture: amd64
  Date: Thu Sep  6 13:36:09 2012
  InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.1)
   PATH=(custom, no user)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

More information about the foundations-bugs mailing list