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:
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 (Ubuntu)
Status: Confirmed = Incomplete
--
monitor remains blank after quick close/open lid
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
Confirmed bugs need to be assigned to ubuntu-kernel-team.
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = Medium
Assignee: Tim Gardner = Ubuntu Kernel Team
--
monitor remains blank after quick close/open lid cycle
https://launchpad.net/bugs/82463
--
ubuntu-bugs
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Tim Gardner
--
monitor remains blank after quick close/open lid cycle
https://launchpad.net/bugs/82463
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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
Damn it, each time I post a bug report I forget to say what linux I
use...
OK, here they come:
[EMAIL PROTECTED]:~$ 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,
** Attachment added: Output of sudo lspci -vvn
http://librarian.launchpad.net/6423817/lspci-vvn.txt
--
monitor remains blank after quick close/open lid cycle
https://launchpad.net/bugs/82463
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: Output of sudo dmidecode
http://librarian.launchpad.net/6423818/dmidecode.txt
--
monitor remains blank after quick close/open lid cycle
https://launchpad.net/bugs/82463
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
And of course, I forgot again. This is on Ubuntu Feisty.
--
monitor remains blank after quick close/open lid cycle
https://launchpad.net/bugs/82463
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
'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
Confirmed based on availability of requested logs.
** Changed in: acpi-support (Ubuntu)
Sourcepackagename: acpi-support = linux-source-2.6.20
Status: Needs Info = Confirmed
--
monitor remains blank after quick close/open lid cycle
https://launchpad.net/bugs/82463
--
ubuntu-bugs mailing
12 matches
Mail list logo
