Sleep does not work after upgrading to 12.04. Just black screen or wallpaper and movable mouse cursor after opening the laptop lid.

Bug #977135 reported by Lazy
54
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Linux
Incomplete
High
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

As the summary says, the sleep does not work anymore. The screen either stays black or the wallpaper can be seen with the mouse cursor, but nothing else shows up. I can change to a different console with ctrl+alt+f1 after opening the lid and reboot the machine from there.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,mousepoll,place,gnomecompat,vpswitch,resize,snap,grid,move,session,imgpng,regex,wall,animation,unitymtgrabhandles,workarounds,expo,fade,ezoom,scale,unityshell]
Date: Mon Apr 9 13:18:41 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: Upgraded to precise on 2012-04-09 (0 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: eero 2092 F.... pulseaudio
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=4781407c-5a66-493a-9dd5-2e5c8318d775
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: LENOVO 4290W4H
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-17-generic root=/dev/mapper/Mercurius-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
SourcePackage: linux
StagingDrivers: mei
Tags: precise staging precise staging
Uname: Linux 3.0.0-17-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-04-09 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/07/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET50WW (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4290W4H
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET50WW(1.20):bd07/07/2011:svnLENOVO:pn4290W4H:pvrThinkPadX220:rvnLENOVO:rn4290W4H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4290W4H
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

This seems to be a kernel problem instead of a Unity problem. I tested suspending with an older 3.0.0-17 kernel and it works as expected.

affects: unity (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 977135

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : AcpiTables.txt

apport information

tags: added: apport-collected staging
description: updated
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : AlsaDevices.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : AplayDevices.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : ArecordDevices.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : BootDmesg.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : CRDA.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Card0.Amixer.info.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Card29.Amixer.info.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Card29.Amixer.values.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : IwConfig.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Lspci.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : Lsusb.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : PciMultimedia.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : ProcModules.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : PulseList.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : RfKill.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : UdevDb.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : UdevLog.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote : WifiSyslog.txt

apport information

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

Seems like apport-collect isn't working properly.

~$ apport-collect 977135
The authorization page:
 (https://launchpad.net/+authorize-token?oauth_token=xxxxxxxxxxxxxxx&allow_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Press any key to continue or wait (5) seconds...
Waiting to hear from Launchpad about your decision...
No packages found matching linux.
ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 718, in add_hooks_info
    symb['add_info'](self, ui)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 37, in add_info
    match_error_messages(report)
  File "/usr/share/apport/general-hooks/ubuntu.py", line 121, in match_error_messages
    if report['ProblemType'] == 'Package':
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'
Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 493, in <lambda>
    GLib.idle_add(lambda: self.collect_info(on_finished=self.ui_update_view))
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 861, in collect_info
    icthread.exc_raise()
  File "/usr/lib/python2.7/dist-packages/apport/REThread.py", line 34, in run
    self._retval = self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 111, in thread_collect_info
    if report['ProblemType'] == 'Crash' and \
  File "/usr/lib/python2.7/UserDict.py", line 23, in __getitem__
    raise KeyError(key)
KeyError: 'ProblemType'

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-22.35)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-22.35
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc2-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-upstream-testing
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-23.36)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-23.36
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

How about reading these bug reports from time to time instead of marking them automatically incomplete all the time?

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

I just installed the latest package updates that were available and now the suspending with kernel version 3.4.0-030400rc2-generic seems to be working. This problem is probably some weird combination with kernel version and some other packages.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you boot back into the latest precise kernel and see if the bug still exists there?

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

WLAN seems to be broken in the newest Precise kernel so I can't really test it right now.

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

Suspending with 3.2.0-23 kernel also works.

Changed in linux:
importance: Unknown → High
status: Unknown → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does the latest kernel fix the original issue reported in this bug? If so, please mark this bug as "Fix Released". It would be best to open a new bug for any new issues your are now seeing.

Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

I wouldn't say that the latest kernel fixed this issue. Suspending didn't work with 3.2.0-23 or 3.4.0-030400rc2 earlier. Only 3.0 kernel worked at that point. When I upgraded the packages mentioned in the history.log file attached earlier the suspending started to work with these kernels. It seems to me that this issue is a combination with kernel version and some other packages.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Please ignore my last comment. I see there is already an upstream bug open.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

possibly related bug is bug 966744.

Changed in linux:
status: Confirmed → Incomplete
Revision history for this message
Lazy (ubuntu-bugs-oittaa) wrote :

The new 3.2.0-24 is also a broken kernel. Blank screen comes up every time after suspending.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Indeed, this is a dupe of bug 966744. I'm going to mark this one as a duplicate because the other one has many more people and a slightly more thorough description. I'll update the useful info from this report onto the other one. Thank you for your report!

To post a comment you must log in.