No, it's not working. It still presents the same behavior. For instance, right now I booted the laptop unplugged from power. After one hour of working, I plugged it and the display stopped going to sleep.
I'm running a clean installation of Maverick. I was also looking at the changelog document of the latest version of the gnome-power-manager package and I didn't see any information about a correction of this problem, so it would be expectable that it could continue to exist in Maverick. This problem exists since gnome-power-manager stopped using HAL. I will continue to use Xfce power manager as it is much more reliable and stable. By the way, Xfce power manager is still using HAL. >From what I could read from other users it may also be a problem restricted to computers with intel graphics. But I cannot confirm this. Again, I'd like to emphasize the following message that I can see when running gnome power manager with verbose mode: "lid is closed, so we are ignoring ->NORMAL state changes" And, obviously, the lid is NOT closed. And, the following is what is showed when the laptop display should, supposedly go off, when I move the mouse. TI:17:14:54 TH:0x887c8b8 FI:gpm-tray-icon.c FN:gpm_tray_icon_add_device,261 - adding device /org/freedesktop/UPower/devices/battery_BAT0 TI:17:14:58 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_set_mode,108 - Doing a state transition: blank TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_idletime_reset_cb,391 - idletime reset TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_evaluate,187 - session_idle=0, idle_inhibited=0, suspend_inhibited=0, x_idle=0 TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_set_mode,108 - Doing a state transition: normal TI:17:15:03 TH:0x887c8b8 FI:gpm-manager.c FN:gpm_manager_idle_changed_cb,804 - lid is closed, so we are ignoring ->NORMAL state changes TI:17:15:03 TH:0x887c8b8 FI:gpm-idle.c FN:gpm_idle_evaluate,192 - X not idle -- Gnome Power Manager fails to put display to sleep https://bugs.launchpad.net/bugs/431146 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
