[Bug 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot

Steve Langasek steve.langasek at canonical.com
Thu Oct 18 14:31:37 UTC 2012


dmesg shows the below output.  plymouth is clearly being stopped by
lightdm (not by /etc/init/plymouth-stop.conf), so we're not hitting a
race in the plymouth jobs.  But after stopping plymouth, lightdm hits
the problem with the X server and exits.

I think this is clearly a problem with either the kernel or with
lightdm.

[   15.801383] init: lightdm goal changed from stop to start
[   15.801430] init: lightdm state changed from waiting to starting
[   15.801559] init: plymouth-splash goal changed from stop to start
[   15.801605] init: plymouth-splash state changed from waiting to starting
[...]
[   15.803513] init: plymouth-stop goal changed from stop to start
[   15.803563] init: plymouth-stop state changed from waiting to starting
[...]
[   15.806338] init: plymouth-stop state changed from starting to pre-start
[   15.806828] init: plymouth-stop pre-start process (1133)
[...]
[   15.809173] init: plymouth-stop pre-start process (1133) exited normally
[   15.809314] init: plymouth-stop state changed from pre-start to spawned
[   15.809398] init: plymouth-stop state changed from spawned to post-start
[   15.809477] init: plymouth-stop state changed from post-start to running
[...]
[   15.811474] init: lightdm state changed from starting to pre-start
[   15.811752] init: lightdm state changed from pre-start to spawned
[   15.812406] init: lightdm main process (1136)
[   15.812499] init: lightdm state changed from spawned to post-start
[   15.812818] init: lightdm state changed from post-start to running
[...]
[   15.817462] init: plymouth-splash state changed from starting to pre-start
[   15.817511] init: plymouth-splash state changed from pre-start to spawned
[   15.820635] init: plymouth-splash main process (1146)
[   15.820690] init: plymouth-splash state changed from spawned to post-start
[   15.820908] init: plymouth-splash state changed from post-start to running
[...]
[   16.573039] init: plymouth-splash main process (1146) exited normally
[   16.573104] init: plymouth-splash goal changed from start to stop
[   16.573184] init: plymouth-splash state changed from running to stopping
[   16.573242] init: Handling stopping event
[   16.573332] init: plymouth-splash state changed from stopping to killed
[   16.573382] init: plymouth-splash state changed from killed to post-stop
[   16.573430] init: plymouth-splash state changed from post-stop to waiting
[   16.573537] init: Handling stopped event
[   16.591136] init: plymouth main process (259) exited normally
[   16.591194] init: plymouth goal changed from start to stop
[   16.591264] init: plymouth state changed from running to stopping
[...]
[   17.610321] init: lightdm main process (1136) terminated with status 1
[   17.610429] init: lightdm goal changed from start to stop
[   17.610490] init: lightdm state changed from running to stopping
[...]
[   16.591619] init: plymouth state changed from stopping to killed
[   16.591669] init: plymouth state changed from killed to post-stop
[   16.591721] init: plymouth state changed from post-stop to waiting


** Package changed: plymouth (Ubuntu Quantal) => lightdm (Ubuntu Quantal)

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

Title:
  [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on
  reboot

Status in “lightdm” package in Ubuntu:
  New
Status in “linux” package in Ubuntu:
  Confirmed
Status in “lightdm” source package in Quantal:
  New
Status in “linux” source package in Quantal:
  Confirmed

Bug description:
  Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display.
  The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly....' error message is displayed.

  The logs attached are directly from the first reboot.

  A tar file will be added with the logs after the failure.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CurrentDmesg:

  Date: Mon Oct 15 14:37:01 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00e6]
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121014)
  MachineType: Apple Inc. Macmini5,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2011
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B0F.1110201309
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.name: Macmini5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.8.4-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066883/+subscriptions




More information about the foundations-bugs mailing list