display turns off after login when on battery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-nouveau (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xorg
Hello. I have a Sony Vaio computer with Ubuntu Maverick Meerkat. It is equipped with special keys ("Sony Vaio keys") one of which is "Display off" and which is functionning correctly and turning off backlight of display when pressed.
The problem emerges when I'm on battery. Just after the login screen, the backlight is turned off, just like when I press the "display off" button and I cannot turn it on back.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-
Architecture: i386
DRM.card0.
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1920x1080 1920x1080 1680x1050 1400x1050 1280x1024 1280x960 1152x864 1024x768 800x600 640x480 720x400 640x400 640x350
edid-base64:
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Thu Dec 9 14:31:26 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Sony Corporation VPCF12Z1E
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=fr_FR.utf8
SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
dmi.bios.date: 05/31/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1110Y6
dmi.board.
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: VPCF12Z1E
dmi.product.
dmi.sys.vendor: Sony Corporation
glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-
affects: | xorg (Ubuntu) → xserver-xorg-video-nouveau (Ubuntu) |
Hey montag42,
Hi, have you had a chance to test if this bug is still present in natty?
If it does (and if you're the original reporter), please boot into natty
and run the command:
apport-collect <bug-number>
which will update the bug with fresh logs and tag the bug as affecting
natty. (It is best to run this right after reproducing the problem.)