VERY slow boot, no battery icon in panel

Bug #582570 reported by doobydave
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: gnome-power-manager

Occurs in both 9.10 and 10.04 though with slightly different behaviour (64-bit editions). I haven't tried the 32-bit editions, but this definitely wasn't a problem in 8.04 x64
In 10.04 a dialog box appears after password-entry relating to the stuck process.

4+ min boot time, no battery icon in gnome panel and the brightness keys do not function.
Machine is an Acer 5685.

No extra info, but several other people reporting similar thing here http://www.uluga.ubuntuforums.org/showthread.php?t=1338256 - most with Acers.

ProblemType: Bug
Architecture: amd64
Date: Tue May 18 23:49:44 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-manager
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.28.1-0ubuntu1.3
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-21-generic x86_64
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 Cannot stat file /proc/3112/fd/44: Stale NFS file handle
                      USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3128 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd2500000 irq 47'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,10250000,00100002 HDA:14f12bfa,1025007f,00090000'
   Controls : 24
   Simple ctrls : 14
DistroRelease: Ubuntu 10.10
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Acer Aspire 5680
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Regression: Yes
RelatedPackageVersions: linux-firmware 1.38
Reproducible: Yes
Tags: maverick regression-potential needs-upstream-testing
Uname: Linux 2.6.35-22-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/25/2006
dmi.bios.vendor: Acer
dmi.bios.version: V3.01
dmi.board.name: Grapevine
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.asset.tag: ��������������������
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV3.01:bd10/25/2006:svnAcer:pnAspire5680:pvrV3.01:rvnAcer:rnGrapevine:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5680
dmi.product.version: V3.01
dmi.sys.vendor: Acer

Revision history for this message
doobydave (dooby-dave) wrote :
Revision history for this message
doobydave (dooby-dave) wrote :

Hi, Forgive me, I may have jumped the gun somewhat.

In 8.04 x64 I get a webcam configuration error. My laptop has a revolving webcam, and I suspect this has a loose connection, as the login screen and login happen much quicker if I fiddle with the camera.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GNOME Power Manager is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
doobydave (dooby-dave) wrote :

Hi. Just double checking that this request is relevant and non-bot generated.
Clearly there is some sort of 'bug' in the way that the OS is handling my specific faulty hardware - previous versions of ubuntu and windows boot normally even if the webcam hasn't initialised properly - but whether the gnome-power-manager is responsible for this, I could not say.

Revision history for this message
xteejx (xteejx) wrote :

That is a generated response but Pedro is not a bot and afaik does not use one, but treats each bug individually. Can you test this with Ubuntu 10.10 please, either installed or Live CD. This could be a kernel related ACPI problem, so from within 10.10 please run "apport-collect -p linux 582570" and this will grab a lot more info that we can look through. Thank you.

Changed in gnome-power-manager (Ubuntu):
importance: Undecided → Medium
Revision history for this message
xteejx (xteejx) wrote :

I'm also wondering why your gnome-power-bugreport.txt attachment shows "Distro version: squeeze/sid". If you are using Debian you should report this to them, not us. Although if you are using Ubuntu, then it looks like I've found another bug :)

Revision history for this message
doobydave (dooby-dave) wrote :

OK, downloading 10.10 now.
Strange about the Debian reference - I can assure you that it is indeed Ubuntu I am using.

Revision history for this message
xteejx (xteejx) wrote :

No problem at all. You shouldn't need to install 10.10, so you can run it from Live CD for the purposes of this bug report. Of course this will be slower to boot anyway, but it will give you some indication of whether this appears fixed or not, and if the ACPI stuff (battery, brightness controls, etc) work or not.

Revision history for this message
doobydave (dooby-dave) wrote : AcpiTables.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
doobydave (dooby-dave) wrote : AlsaDevices.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : AplayDevices.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : ArecordDevices.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : BootDmesg.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : Card0.Codecs.codec.1.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : CurrentDmesg.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : IwConfig.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : Lspci.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : Lsusb.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : PciMultimedia.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : ProcInterrupts.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : ProcModules.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : RfKill.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : UdevDb.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : UdevLog.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote : WifiSyslog.txt

apport information

Revision history for this message
doobydave (dooby-dave) wrote :

Hi. The issue seemed to not occur this time.
Very rarely was I able to boot the previous versions properly without fiddling with the rotating webcam. I will try again to verify the issue has been resolved and I didn't merely experience a lucky boot..

Some of the questions I answered during the process seem a little irrelevant given that the bug now no longer seems to exist.

Let me know if I can be of any further help.

Revision history for this message
doobydave (dooby-dave) wrote :

Hi again. Sorry to complicate things, but thought I should mention this.

On trying again, I let the liveCD do it's thing with the new automatic hidden boot menu (previously, I had activated the boot menu and selected the 'live' option).
The new graphical menu appeared with the two choices, 'Try' and 'Install'. On clicking 'Try', the mouse cursor changed to the busy one and the machine appeared to do nothing else. Eventually, I hit Ctrl-Shft-F1 and rebooted from the command line.

Is it worth trying to do the apport from this state or could this be entirely unrelated?

Revision history for this message
xteejx (xteejx) wrote :

Things like webcams not working, etc should be filed separately. In fact, each issue should be filed separately for ease and to avoid confusion. If you think they are related you can always say in the other bug report something like "this could be related to bug 582570" or something along those lines.
For some reason the 10.10 Live CD also hangs for me first time around, but a reboot fixes it, so it's nothing to worry about and is not related (or unlikely to be).
So from what I gather in comment #29, the system appeared to boot fine? If you could try a few times, from a cold state (i.e. power down completely, plug on/off), and from a reboot that would give a better overall 'feel' for if it is fixed or not, but this does sound promising. :)

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Expired
Revision history for this message
doobydave (dooby-dave) wrote :

Um, the webcam fault is hardware related. Are you sure you'd like me to make a separate report?

Basically, there seems to be a fifty-fifty chance of a smooth boot. On good days everything is fine, on bad days, the gnome-power-manager app take 100+ seconds to appear after request and the machine will not successfully go into standby.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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