System hangs at laptop lid reopening

Bug #570484 reported by registerthis@rocketmail.com
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Linux Mint
Triaged
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After closing my Dell Inspiron 6000, the system hangs or something. Whether asleep or hibernating, when reopened it only shows a flashing command prompt-like line at the top left of the screen, though no keyboard input is displayed. The only way to get around this problem is to restart the computer.

description: updated
description: updated
tags: added: crash
Revision history for this message
Clement Lefebvre (clementlefebvre) wrote :

Marking as upstream.

Changed in linuxmint:
status: New → Triaged
Revision history for this message
Peter M. Clausen (pclausen) wrote :

Looks like a duplicate of #462939

Does the dell inspiron 6000 also have an intel grafic chip ?

Revision history for this message
Vladimir Atehortúa (vladimir-atehortua) wrote :

The very exact same thing happens to me.

After suspend or hibernate (which apparently was successfull), when I wake the laptop by opening the lid (or by pressing power button), the screen is all blank except for a blue line at the top left of the screen. The system doesn't respong, Ctrl Alt F1 does not bring a CLI, the only way to get out of this is to restart the computer.

I read around that some old suspend issues were related to the compiz, so I tried disabling compiz yet nothing changed.

In my case its a dell Studio 15, with ATI Mobility Radeon 4500 graphics, ATI Catalist driver (Version 8.723.1-100408a-098580C-ATI).
I run two monitors, so perhaps this has something to do with it (the internal laptop LCD and an external LCD).

I have Linux Mint 9 Isadora, all packages fully updated as of 2010-05-27.

I'll try to post my /var/log/pm-suspend.log here

Revision history for this message
Vladimir Atehortúa (vladimir-atehortua) wrote :
Revision history for this message
Leo Arias (elopio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Leo Arias (elopio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.

Please run the following command which will attach necessary information:

apport-collect 570484
if you are using Karmic Koala (9.10) or newer, or

apport-collect -p linux-image-`uname -r` BUGNUMBER
if you are using Jaunty Jackalope (9.04).

Bear in mind that you may need to install the python-launchpadlib package from the universe repository with 'sudo apt-get install python-launchpadlib'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.

If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):

First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).

For your reference, the full description of procedures for kernel related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: kernel-power needs-kernel-logs
Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Peter M. Clausen (pclausen) wrote :

@ Leo: see apport-collect in bug #462939. I wont double post unless you say so.

Revision history for this message
Leo Arias (elopio) wrote :

@ Peter M. Clausen, I was talking to the original reporter :)
As he hasn't answered I'm going to close this issue. If bug #462939 is the same you are experiencing, then your apport collect is enough for a developer to work on that and you should just wait. If you have different symptoms you should report a different issue with "ubuntu-bug linux".

Thanks a lot.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.