Ubuntu
gdm package

  1. Bug #615549
  2. Comment #79

Comment 79 for bug 615549

Revision history for this message
Jamie Krug (jamie-thekrugs) wrote : Re: gdm starting too early for DRM modules to load, no video

I have some new clues on my crashes! First, Martin's changes to my gdm.conf as mentioned in comment #67 did not fix all for me, as I just had a few more crashes. What I noticed (and had a hunch this morning too), is that I believe I've primarily (if not always) had crashes occur while on battery power. This would explain the fact that I'm sometimes perfectly stable all day at the office (with AC power plugged in to my laptop) while other times it's just crash after crash.

I've also noticed that the crashes seem to occur very soon after login. The last 4-5 crashes have also all occurred just as I was opening Chrome browser.

I've also found a hint of this being battery/power related, as I found mentions of "gnome-power-manager" in a GDM log just after crash. I've attached various output and X/GDM logs. Here are a few lines from my :0-greeter.log.1 log, which has the gnome-power-manager warnings:

(gnome-power-manager:1852): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.24.1/gobject/gsignal.c:2273: signal `proxy-status' is invalid for instance `0x773250'

** (gnome-power-manager:1852): WARNING **: Either HAL or DBUS are not working!

** (gnome-power-manager:1852): WARNING **: proxy failed

** (gnome-power-manager:1852): WARNING **: failed to get Computer root object

** (gnome-power-manager:1852): WARNING **: proxy NULL!!

Martin, you'd mentioned that the crash could be delayed from boot if something using 3D opens--could this be what's happening with Chrome? Then again, if my bug is related to power management, is this a separate bug or related? Thanks again to all for any help!