Boot stops after "checking battery state..."

Bug #824140 reported by danizmax
122
This bug affects 24 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

It's actually a duplicate of bug #577477, but in Ubuntu 11.10 Alpha

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gdm 3.0.4-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic-pae 3.0.1
Uname: Linux 3.0.0-8-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Aug 10 21:16:55 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm
UpgradeStatus: Upgraded to oneiric on 2011-08-10 (0 days ago)

Revision history for this message
danizmax (danizmax) wrote :
Revision history for this message
Joschi Poschi (joschiposchi) wrote :

gdm was already replaced by lightdm in the current Alpha

affects: gdm (Ubuntu) → lightdm (Ubuntu)
Revision history for this message
Joschi Poschi (joschiposchi) wrote :

I did a fresh install of Oneiric Alpha 3 in the VBox, updated via Update Manager and rebooted as desired. After that I run into that bug.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue doesn't really seem a lightdm one, do you still get it? does it happen using gdm?

Changed in lightdm (Ubuntu):
importance: Undecided → Low
Revision history for this message
henry adler (anachoret) wrote :

i have this issue with both gdm and lightdm.

Revision history for this message
danizmax (danizmax) wrote :

My problem is actually nvidia driver, thats why it stoppes at "Checking battery state"...
My nvidia driver doesnt work, therefore X can't start and that is no login manager.

Revision history for this message
danizmax (danizmax) wrote :

I have found the right duplicate of this bug - 816635... the nvidia kernel module is never build therefore X can not start.

Revision history for this message
Joschi Poschi (joschiposchi) wrote :

This definetely not solely related to nvidia driver problems as I have this issue on a Virtual Machine (strangely only on my Ubuntu laptop and not on my Windows computer at work) and on a persistent USB installation.

Revision history for this message
danizmax (danizmax) wrote :

You are right, it was fixed for me after last update. Now it shows, just login as it suppose to.

Revision history for this message
Tory (tory-andrew-law) wrote :

I uninstalled Virtual Box guest additions which fixed the issue.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I have this problem with ubuntu natty since the -10 kernel update.

Ubuntu boots ok with 2.6.38-9 but not with -10

Revision history for this message
Leo Iannacone (l3on) wrote :

I had same problem and I fixed it with:

sudo apt-get purge lightdm
sudo apt-get install ubuntu-desktop

Revision history for this message
sergey.degtyar (sergey-degtyar) wrote :

Leo Iannacone (l3on)
Thanks man! What default x-manager chose in ubuntu-desktop?

Revision history for this message
webguy (ubuntu-seremeth) wrote :

I have run into this several time since upgrading to Oneiric and each time it requires me to reinstall nvidia-current and nvidia-173. It's extremely frustrating as this is a laptop I use as my primary work system. It's a lenovo w510 with:

01:00.0 VGA compatible controller: nVidia Corporation GT216 [Quadro FX 880M] (rev a2)

running 11.10 64bit.

Here's hoping someone can find this and crush it fast.

If I can help debug this issue, please let me know.

Revision history for this message
pobbel (p-burne) wrote :

I have been able to get this going by installing nvidia-current.
For some reason it broke again however this time I could run lightdm from command line after boot.
I got sick of doing this every boot, so I started fresh again. The following output is from a fresh install prior to installing nvidia-current drivers.

Fresh 11.10 (32bit) install on Dell Precision M6500 (64bit).
Boot stops after "Checking battery state".
Ctrl+Alt+F1 then startx

X.Org X Server 1.10.4
Release Date: 2011-08-19
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-29-server i686 Ubuntu
Current Operating System: Linux hostname 3.0.0-12-generic-pae #20-Ubuntu SMP Fri OCT 7 16:37:17 UTC 2011 i686
Kernel command line: BOOT_MAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID-ba00a000-7b9f-40a8-a72b-18674f486639 ro quiet splash vt.handoff=7
Build Date: 29 September 2011 12:48:48AM
xorg-server 2:1.10.4-1ubuntu4
Current version of pixman: 0.22.2 ...

...
(EE) Failed to load module "nv" (module does not exist, 0)
FATAL: Module nvidia_173 not found.
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screens(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Let me know if I can provide any more info. Still looking for a solid fix.

Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

I fixed it by REMOVING every nvidia* on my ubuntu, and installing the official proprietary driver FWIW

Revision history for this message
Edward (edwardtisdale-2004) wrote :

Same problem on Precise (12.04) alpha, kernel 3.2.0.7.7

Revision history for this message
Adam Niedling (krychek) wrote :

I have the same problem with Ubuntu 11.10 and an nVidia 540M. It doesn't always happen tho.

Revision history for this message
Adam Niedling (krychek) wrote :

When this is happening for me I do the following:

1. Press ctrl+alt+f1 and log in
2. sudo restart lightdm

The GUI will start.

Revision history for this message
ski (skibrianski) wrote :

I've tried every trick in the book for this, read every bug report I can find. The *only* thing that reliably works is to install gdm ( I don't count restart lightdm on vty1 as a solution). What a bummer.

Revision history for this message
ski (skibrianski) wrote :

Either install gdm or run unity-2d with nouveau, that is.

Revision history for this message
ski (skibrianski) wrote :

why on earth is this bug characterized as low priority?

Revision history for this message
Sebastien Bacher (seb128) wrote :

it's low priority because the bug is not useful to be worked, it mixes different issues from different users who have similar bugs, it doesn't seem a lightdm bug at all in fact but rather a video driver, session issue

Revision history for this message
Humphrey van Polanen Petel (hpvpp) wrote :

I had this (or a similar) problem and fell back on a previous release. From time to time I checked if the problem was still there and this morning it was gone. I assume some update or other must have fixed it.

Revision history for this message
JensOtto (jos-ideatore) wrote :

I got the same problem upgrading from 11.10 to 12.04.
The upgrade went apperently well, but the final boot into the newly upgraded v. 12.04 fail with this same problem.
I needed a working machine badly, so me final decision was to go with a fresh installation (deling all my stuff!) and that worked -- I don't have this problem any more.
I'm running on a Lenovo IdeaPad U260 (Intel i3 Core, 4 Gb RAM, Graphics Adapter: Intel Graphics Media Accelerator (GMA) HD Graphics)
And 12.04 (precise) 32-bit , Linux 3.2.0-24-generic-pae, GNOME 3.4.1

Revision history for this message
Balázs Úr (urbalazs) wrote :
Download full text (3.8 KiB)

I've installed Kubuntu 12.10. It works perfectly, but after upgrading and restarting the boot stops on at "Checkink battery state [OK]".

My video card:
product: K8M800/K8N800/K8N800A [S3 UniChrome Pro]
vendor: VIA Technologies, Inc.

The problem is this package:
xserver-xorg-video-openchrome_1%3a0.3.0+0-0ubuntu1_i386.deb

Workaround:
apt-get remove xserver-xorg-video-openchrome

The X.org.log is:
[ 295.815] Loading extension GLX
[ 295.815] (==) Matched openchrome as autoconfigured driver 0
[ 295.815] (==) Matched vesa as autoconfigured driver 1
[ 295.815] (==) Matched modesetting as autoconfigured driver 2
[ 295.815] (==) Matched fbdev as autoconfigured driver 3
[ 295.815] (==) Assigned the driver to the xf86ConfigLayout
[ 295.815] (II) LoadModule: "openchrome"
[ 295.815] (WW) Warning, couldn't open module openchrome
[ 295.815] (II) UnloadModule: "openchrome"
[ 295.815] (II) Unloading openchrome
[ 295.815] (EE) Failed to load module "openchrome" (module does not exist, 0)
[ 295.815] (II) LoadModule: "vesa"
[ 295.816] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 295.816] (II) Module vesa: vendor="X.Org Foundation"
[ 295.817] compiled for 1.12.99.902, module version = 2.3.2
[ 295.817] Module class: X.Org Video Driver
[ 295.817] ABI class: X.Org Video Driver, version 13.0
[ 295.817] (II) LoadModule: "modesetting"
[ 295.817] (WW) Warning, couldn't open module modesetting
[ 295.817] (II) UnloadModule: "modesetting"
[ 295.817] (II) Unloading modesetting
[ 295.817] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 295.817] (II) LoadModule: "fbdev"
[ 295.818] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 295.818] (II) Module fbdev: vendor="X.Org Foundation"
[ 295.818] compiled for 1.12.99.902, module version = 0.4.3
[ 295.818] Module class: X.Org Video Driver
[ 295.818] ABI class: X.Org Video Driver, version 13.0
[ 295.818] (==) Matched openchrome as autoconfigured driver 0
[ 295.818] (==) Matched vesa as autoconfigured driver 1
[ 295.818] (==) Matched modesetting as autoconfigured driver 2
[ 295.818] (==) Matched fbdev as autoconfigured driver 3
[ 295.818] (==) Assigned the driver to the xf86ConfigLayout
[ 295.818] (II) LoadModule: "openchrome"
[ 295.819] (WW) Warning, couldn't open module openchrome
[ 295.819] (II) UnloadModule: "openchrome"
[ 295.819] (II) Unloading openchrome
[ 295.819] (EE) Failed to load module "openchrome" (module does not exist, 0)
[ 295.819] (II) LoadModule: "vesa"
[ 295.824] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 295.824] (II) Module vesa: vendor="X.Org Foundation"
[ 295.824] compiled for 1.12.99.902, module version = 2.3.2
[ 295.824] Module class: X.Org Video Driver
[ 295.824] ABI class: X.Org Video Driver, version 13.0
[ 295.824] (II) UnloadModule: "vesa"
[ 295.824] (II) Unloading vesa
[ 295.824] (II) Failed to load module "vesa" (already loaded, 0)
[ 295.824] (II) LoadModule: "modesetting"
[ 295.824] (WW) Warning, couldn't open module modesetting
[ 295.824] (II) UnloadModule: "modesetting"
[ 295.824] (II) Unloading modesetting
[ 295.825] (EE) Faile...

Read more...

Revision history for this message
Adam Niedling (krychek) wrote :

I don't have this issue anymore in 12.04.

Revision history for this message
Ads20000 (ads20000) wrote :

I have this issue in raring (in VirtualBox). I assume is a bug in the actual project because raring should have the most recent package...

Changed in lightdm:
status: New → Confirmed
Revision history for this message
Arnaud Thevenet (aeromousse) wrote :

I have this bug on Ubuntu 13.04 fresh installation, although I did not have it in 12.10.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Closing assumed fixed.

no longer affects: lightdm
Changed in lightdm (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.