← Back to team overview

touch-packages team mailing list archive

[Bug 969489] Re: lightdm tries (and fails) to start too early?

 

It's me, again.

The N54L works now, but I don't remember the changes.

But today I failed to add SSD based EnhanceIO to several iSCSI based
Ubuntu desktops (Intel G530 and G1610). They hung up with a blank screen
and a mouse cursor in the middle. The kernel hung up, I cannot ping it.
But when I booted with text mode and then "sudo service lightdm start",
it worked for the most times and failed for several times. It seems that
lightdm or X failed if the machine STARTED TOO SOON. I tried all the
walkarounds above but no one works.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489

Title:
  lightdm tries (and fails) to start too early?

Status in Upstart:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  Sometimes lightdm comes up fine.  Other times it appears to fail.
  x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is
  what actually exists).  When I then log into console and 'start
  lightdm', it comes up fine (on :1).

  I've not had it come up ok today, so I don't know if, when it comes up
  fine, it starts on :0.  No idea if the lightdm.conf needs a change to
  'start on'clause, or if this is just a case of a bad shipped config
  file (for module 'nv').

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 13:40:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120323)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions