Changing monitor resolution causes screen corruption
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6+4ubuntu3
Uname: Linux 3.0.0-rc3+ i686
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
DRM.card0.VGA.1:
status: connected
enabled: enabled
dpms: On
modes: 1024x768 800x600 800x600 848x480 640x480
edid-base64:
Date: Fri Jun 24 08:56:26 2011
DistUpgraded: Log time: 2011-06-18 15:45:11.515970
DistroCodename: natty
DistroVariant: ubuntu
GraphicsCard: nVidia Corporation Device [10de:016f] (rev a1) (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: OEM OEM
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
Renderer: Unknown
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to natty on 2011-06-18 (5 days ago)
dmi.bios.date: 09/28/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: SY-I5G31-L V2.0
dmi.board.vendor: soyo
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: OEM
dmi.product.
dmi.sys.vendor: OEM
version.compiz: compiz 1:0.9.4+
version.libdrm2: libdrm2 2.4.26+
version.
version.
version.
version.
version.
version.
version.
affects: | xorg (Ubuntu) → xorg-server (Ubuntu) |
Hey jukarimov,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in the new release and you think it's worth backporting
the fix, please indicate that. Or if having the fix in the new release
is good enough, feel free to close out the bug (or let us know and we'll
close it.)
If it's not solved, leave the bug report open. I can't promise we'll
get to it (we get way more bugs filed than we can usually get to), but
your testing and feedback can help out if and when we do.