← Back to team overview

compiz team mailing list archive

[Bug 428769] Re: compiz starts with a blank screen on a 2048x1152 monitor

 

Hmm, well the upstreamed bug is closed as believed fixed.  Maybe you
should reopen it and elaborate on the remaining problem?

Meanwhile, your recommendation to make compiz not start up if it detects
this situation is a good one, I'll forward this to the compiz team.

** Package changed: xserver-xorg-video-intel (Ubuntu) => compiz (Ubuntu)

** Changed in: compiz (Ubuntu)
       Status: Confirmed => New

** Summary changed:

- compiz starts with a blank screen on a 2048x1152 monitor
+ compiz starts with a blank screen on a 2048x1152 monitor due to hw limit with textures > 2048

** Description changed:

+ [Problem]
+ When using dual-head or other situation where the screen has an X or Y dimension larger than (or maybe equal to) the max texture size, the hardware is unable to cope.
+ 
+ A patch that supposedly fixes this was introduced in mesa 7.7 but it
+ seems the issue persists.  It's a tough thing to fix in X and unlikely
+ to get patched with lucid, so as a workaround it's suggested that compiz
+ should check if the current resolution has a dimension equal to or
+ larger than the max texture size, and not start up in this case.
+ 
+ [Original Report]
  Binary package hint: xserver-xorg-video-intel
  
  I have an intel Atom motherboard with a 945 graphics chip
  
  00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ
  Integrated Graphics Controller (rev 02)
  
  the max texture size is 2048 and I have a Samsung 2048x1152 monitor.
  Works just fine with compiz in Jaunty but in Karmic I get a black (or
  sometimes corrupted) screen except for the column of the first pixel
  1x1152. The mouse cursor looks fine over all the screen and I can see in
  the first pixel that the panels and so on are there. It is as if there
  is a big black overlay sitting on top of the other 2047x1152 pixels. The
  first test Compiz does is compare the screen resolution to see if it
  less than or equal to the max texture size. Mine is equal, and should
  work. I can do alt+F2 and type metacity --replace to get back to a 2d
  window manager.
  
  ProblemType: Bug
  Architecture: i386
  Date: Sun Sep 13 09:25:49 2009
  DistroRelease: Ubuntu 9.10
  Package: xserver-xorg-video-intel 2:2.8.1-1ubuntu1
  PccardctlIdent:
-  
+ 
  PccardctlStatus:
-  
+ 
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=24d62e43-8f3d-4021-90f3-eb189cd294e3 ro quiet splash
  ProcEnviron:
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.30-generic
  RelatedPackageVersions:
-  xserver-xorg 1:7.4+3ubuntu5
-  libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
-  libdrm2 2.4.13-1ubuntu1
-  xserver-xorg-video-intel 2:2.8.1-1ubuntu1
-  xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
+  xserver-xorg 1:7.4+3ubuntu5
+  libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu3
+  libdrm2 2.4.13-1ubuntu1
+  xserver-xorg-video-intel 2:2.8.1-1ubuntu1
+  xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Uname: Linux 2.6.31-10-generic i686
  XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
  dmi.bios.date: 06/19/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LF94510J.86A.0067.2008.0619.1959
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D945GCLF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE27042-305
  dmi.chassis.type: 2
  dmi.modalias: dmi:bvnIntelCorp.:bvrLF94510J.86A.0067.2008.0619.1959:bd06/19/2008:svn:pn:pvr:rvnIntelCorporation:rnD945GCLF:rvrAAE27042-305:cvn:ct2:cvr:
  fglrx: Not loaded
  system:
-  distro:             Ubuntu
-  architecture:       i686kernel:             2.6.31-10-generic
+  distro:             Ubuntu
+  architecture:       i686kernel:             2.6.31-10-generic

-- 
compiz starts with a blank screen on a 2048x1152 monitor due to hw limit with textures > 2048
https://bugs.launchpad.net/bugs/428769
You received this bug notification because you are a member of compiz
packagers, which is subscribed to compiz in ubuntu.