kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Alessio Gaeta, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Changed in: linux (Ubuntu)
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/570123

Title:
  Using xrandr with dual monitor causes garbled image

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: xorg

  Almost every time I use xrandr to setup my monitors I get garbled,
  unusable desktop. The system remains perfectly working (no lockups,
  mouse pointer visible and working, desktop responsive to inputs: I
  could continue use it blindly). With some more details:

  - If I change the configuration of a monitor, I get the garbled
  desktop. Reverting to previous configuration does not work (still
  garbled). Sometimes I got an usable desktop (blindly) configuring
  monitors with very low resolutions (800x600 or 640x480).

  - The issue often occurs even doing a simple xrandr query (with CLI or
  opening the GUI).

  - If I start my laptop with the external monitor plugged, gdm starts
  fine (with low resolution on both monitors, though), gnome starts fine
  with both monitors well working at right resolution (1280x800+0+224,
  1280x1024+1280+0). Changing the configuration of a monitor triggers
  the issue.

  As a side node, things work perfectly with Fedora 13 Beta live DVD
  (apart from xorg crash when rotating a monitor at maximum resolution).
  So the issue maybe related to xorg 1.7.6 and solved in xorg 1.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: xserver-xorg 1:7.5+5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  NonfreeKernelModules: slamr
  Architecture: i386
  Date: Mon Apr 26 13:00:38 2010
  DkmsStatus:
   sl-modem, 2.9.11~20100303, 2.6.32-19-generic, i686: built 
   sl-modem, 2.9.11~20100303, 2.6.32-20-generic, i686: built 
   sl-modem, 2.9.11~20100303, 2.6.32-21-generic, i686: installed 
   sl-modem, 2.9.11~20100303, 2.6.32-17-generic, i686: built 
   sl-modem, 2.9.11~20100303, 2.6.32-18-generic, i686: built
  MachineType: TOSHIBA Satellite M30X
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=70ea592a-005a-4499-aee6-d4a664c82b4e ro radeon.agpmode=1 quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V2.00
  dmi.board.name: EAL20
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Null
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnTOSHIBA:bvrV2.00:bd11/10/2008:svnTOSHIBA:pnSatelliteM30X:pvrPSA72E-2K202WIT:rvnTOSHIBA:rnEAL20:rvrNull:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite M30X
  dmi.product.version: PSA72E-2K202WIT
  dmi.sys.vendor: TOSHIBA
  glxinfo: Error: [Errno 2] Nessun file o directory
  system:
   distro:             Ubuntu
   codename:           lucid
   architecture:       i686
   kernel:             2.6.32-21-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/570123/+subscriptions