← Back to team overview

kernel-packages team mailing list archive

[Bug 570123] Re: Using xrandr with dual monitor causes garbled image

 

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

-- 
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:
  Expired

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