monitor remains blank after quick close/open lid cycle

Bug #82463 reported by Bogdan Butnaru
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: acpi-support

Hi! I have a Dell Latitude D620 laptop. It has some kind of Intel 9** graphics and a widescreen monitor. I have set it to turn off the screen when I close the lid instead of suspending, because I routinely leave the laptop do stuff for long times.

This works well usually. The screen turns off when I close the lid, the computer visibly works a bit afterwards (swapping; presumably it does something to the X session) and when I open the lid it works a bit again, wakes up in text-mode (you can see a cursor there, and the resolution is clearly not native; this is annoying and should probably be fixed, but it's not a problem), then turns to graphics mode and asks for my password. (Sometimes the screen is blank until I move the mouse or press a key; I think it's the screensaver that's the cause, I set it to just blank the screen.)

Now the problem: if I close the lid and then I open it _quickly_, which means approximately before the swapping stops, the screen remains turned off. As far as I can remember, closing the lid and opening it ten or so seconds later fixes this, but it's really annoying. I also had (some time ago) problems with the laptop freezing when woken-up, and it's easy to confuse the two.

Please let me know any information you might need (and how to get it) to diagnose this.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Bogdan, please update the bug report with the output of

uname -a

Also, please run the following commands and attach their output to the report, one attachment per command:

sudo lspci -vv

sudo lspci -vvn

sudo dmidecode

Please be sure to attach as there will be a lot of output. Also please be sure to run with sudo, as these commands require root access to get to the required information.

It may also be useful to run

lshal -m

close the lid, get back to your session, then attach the output of the command.

Thanks!

Changed in acpi-support:
status: Unconfirmed → Needs Info
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

Damn it, each time I post a bug report I forget to say what linux I use...

OK, here they come:

bogdanb@bogdanb-d620:~$ uname -a
Linux bogdanb-d620 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

(By the way, this shouldn't matter, but I used to use the -lowlatency kernel too, with the same results.)

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

'lshal -m' doesn't output anything, even with sudo. I tried "lshal --monitor" and it works:

First, I started the monitor, I closed the lid, counted to ten, then I opened it. (Incidentally, gnome-screensaver refuses to unlock the screen, but this is unrelated, I think, because they often happen separately.)

$ sudo lshal --monitor
Start monitoring devicelist:
-------------------------------------------------
acpi_LID property button.state.value = true
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12421 (0x3085)
acpi_LID property button.state.value = false
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12420 (0x3084)

*******************
Then I restarted 'ls-hal --monitor', I closed the lid and re-opened it immediately; it remained blank. I counted to ten and then again closed and opened it immediately. The second time it turned on.

$ sudo lshal --monitor

Start monitoring devicelist:
-------------------------------------------------
acpi_LID condition ButtonPressed = lid
acpi_LID condition ButtonPressed = lid
acpi_LID property button.state.value = true
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12419 (0x3083)
acpi_LID property button.state.value = false
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12420 (0x3084)

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

And of course, I forgot again. This is on Ubuntu Feisty.

Revision history for this message
Peter Whittaker (pwwnow) wrote :

Confirmed based on availability of requested logs.

Changed in acpi-support:
status: Needs Info → Confirmed
Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
Revision history for this message
Ben Collins (ben-collins) wrote :

Confirmed bugs need to be assigned to ubuntu-kernel-team.

Changed in linux-source-2.6.20:
assignee: timg-tpi → ubuntu-kernel-team
importance: Undecided → Medium
Revision history for this message
unggnu (unggnu) wrote :

Could you please recheck it with Gutsy Final Live CD? In Gutsy i810 driver is deprecated and intel driver is used instead. Maybe this fixes the problem too.

Changed in linux-source-2.6.20:
status: Confirmed → Incomplete
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

I can't seem to reproduce this on Gutsy.

However, there is another difference that might be related: When I entered this bug report, I had the computer set-up to lock the screen when I closed the lid. I can't figure out how to do this now, the only equivalent setting in the power manager is to blank the screen, and apparently this doesn't lock the screen.

The fact that the screen-saver was enabled (to lock the screen) when the lid was closed _might_ have been related to the problem.

Revision history for this message
unggnu (unggnu) wrote :

I am closing this bug because it seems to be fixed in Gutsy. Feel free to open it again if the issue still happens with Gutsy Gibbon.

@Bogdan Butnaru
Lock settings can be changed with gconf-editor (run with alt + f2 or in console) under apps/gnome-power-manager/lock .

Changed in linux-source-2.6.20:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.