mouse does not resume after waking from suspend to ram triggered by closing lid

[Ali Asad Lotia]

Binary package hint: gnome-power-manager

Dell Latitude D630
Package details:
gnome-power-manager:
  Installed: 2.29.91-0ubuntu9
  Candidate: 2.29.91-0ubuntu9
  Version table:
 *** 2.29.91-0ubuntu9 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

Release info:
Description: Ubuntu lucid (development branch)
Release: 10.04

When waking from suspend to RAM triggered by closing the lid of the machine, the mouse pointer takes 4+ minutes to return while the keyboard is responsive immediately. I had to start filing this bug-report by using Alt+F2 and opening gnome-terminal to run ubuntu-bug, which brought up the firefox window. I am running off the amd64 live desktop image burned to a 8GB USB stick. I expect the mouse to be responsive shortly after boot, around the same time as the keyboard.

ProblemType: Bug
Architecture: amd64
Date: Sun Mar 28 04:37:10 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100327)
MachineType: Dell Inc. Latitude D630
Package: gnome-power-manager 2.29.91-0ubuntu9
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: gnome-power-manager
Uname: Linux 2.6.32-17-generic x86_64
XsessionErrors:
 (polkit-gnome-authentication-agent-1:11622): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:12486): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed
dmi.bios.date: 11/24/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.asset.tag: 161910
dmi.board.name: 0WM416
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: 161910
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.

[Ali Asad Lotia (ali-asad-lotia)]

Some further testing shows that every alternate wake from suspend to RAM while running off the amd64 live image results in a blank screen at wake. Switching to the first or second virtual console works, and then going to virtual console 7 (in which the x session is running) brings back the display. The order of events is:
1. Suspend by closing lid.
2. Open lid, note problem with mouse pointer disappearing as reported above.
3. Suspend by closing lid.
4. Open lid and get a black screen.
5. Attempt to switch to different virtual console, successful.
6. Switch back to virtual console 7. Get restored X session.
7. Suspend by closing lid.
8. Open lid and have system restore to X session very fast.
9. Suspend by closing lid.
10. Open lid and get a black screen.
11. Switch to virtual console 1 or 2. Then back to 7 and return to X session.

So it appears that waking from suspend to RAM in even-numbered sessions has problems with restoring the X session and requires that you switch to a different virtual console and switch back to console 7.

I have also noticed that the problem with the mouse (reported above) only happened after the first wake from suspend to RAM.

[Overboost (overboost)]

Mouse pointer does not come up after sleep on my Thinkpad T43 running an installed Version of 10.4 which is up-to-date.

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance and sorry for the late response.

[Ali Asad Lotia (ali-asad-lotia)]

I've updated to Natty on the one laptop to which I currently have
access and haven't seen this issue. I have also installed as a VM in
Virtualbox and have not seen the problem again.
--
Ali

On Wed, Jun 22, 2011 at 20:20, Pedro Villavicencio <email address hidden> wrote:
> Thanks for the report, it has been some time without any response or
> feedback in this bug report and we are wondering if this is still an
> issue for you with the latest release of Ubuntu the Natty Narwhal, May
> you please test with that version and comment back if you're still
> having or not the issue? Please have a look at
> http://www.ubuntu.com/download to know how to install that
> version.Thanks in advance and sorry for the late response.
>
> ** Changed in: gnome-power-manager (Ubuntu)
>   Importance: Undecided => Low
>
> ** Changed in: gnome-power-manager (Ubuntu)
>       Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/550046
>
> Title:
>  mouse does not resume after waking from suspend to ram triggered by
>  closing lid
>
> Status in “gnome-power-manager” package in Ubuntu:
>  Incomplete
>
> Bug description:
>  Binary package hint: gnome-power-manager
>
>  Dell Latitude D630
>  Package details:
>  gnome-power-manager:
>    Installed: 2.29.91-0ubuntu9
>    Candidate: 2.29.91-0ubuntu9
>    Version table:
>   *** 2.29.91-0ubuntu9 0
>          500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
>          100 /var/lib/dpkg/status
>
>
>  Release info:
>  Description:  Ubuntu lucid (development branch)
>  Release:      10.04
>
>  When waking from suspend to RAM triggered by closing the lid of the
>  machine, the mouse pointer takes 4+ minutes to return while the
>  keyboard is responsive immediately. I had to start filing this bug-
>  report by using Alt+F2 and opening gnome-terminal to run ubuntu-bug,
>  which brought up the firefox window. I am running off the amd64 live
>  desktop image burned to a 8GB USB stick. I expect the mouse to be
>  responsive shortly after boot, around the same time as the keyboard.
>
>  ProblemType: Bug
>  Architecture: amd64
>  Date: Sun Mar 28 04:37:10 2010
>  DistroRelease: Ubuntu 10.04
>  ExecutablePath: /usr/bin/gnome-power-manager
>  GnomeSessionIdleInhibited: No
>  GnomeSessionInhibitors: None
>  GnomeSessionSuspendInhibited: No
>  LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100327)
>  MachineType: Dell Inc. Latitude D630
>  Package: gnome-power-manager 2.29.91-0ubuntu9
>  PccardctlIdent:
>   Socket 0:
>     no product info available
>  PccardctlStatus:
>   Socket 0:
>     no card
>  ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
>  ProcEnviron:
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
>  SourcePackage: gnome-power-manager
>  Uname: Linux 2.6.32-17-generic x86_64
>  XsessionErrors:
>   (polkit-gnome-authentication-agent-1:11622): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' f...

[Launchpad Janitor (janitor)]

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