[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#517127: marked as done (compiz does not run on display 1.0 (but on 0.0))



Your message dated Wed, 25 Feb 2009 21:27:13 +0100
with message-id <1235593633.4029.92.camel@radis.liafa.jussieu.fr>
and subject line Re: Bug#517127: compiz does not run on display 1.0 (but on 0.0)
has caused the Debian Bug report #517127,
regarding compiz does not run on display 1.0 (but on 0.0)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
517127: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517127
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: compiz
Version: 0.7.6-7
Severity: normal

Hello,

I have configured gdm to start 2 xservers.
They set DISPLAY to :0.0 and :1.0

When I try to start compiz in a terminal on display :1.0, it delivers the following:

compiz --replace  &
[1] 5831
juergen@acer-ilzleite:~$ Checking for Xgl: not present.
Detected PCI ID for VGA: 01:00.0 0300: 1002:5b60 (prog-if 00 [VGA controller])
Checking for texture_from_pixmap: present.
Checking for non power of two support: present.
Checking for Composite extension: present.
Comparing resolution (1280x1024) to maximum 3D texture size (2048): Passed.
Checking for nVidia: not present.
Checking for FBConfig: present.
Checking for Xgl: not present.
Starting gtk-window-decorator
/usr/bin/compiz.real (core) - Fatal: No GLXFBConfig for default depth, this isn't going to work.
/usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
/usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :1.0


The stange thing is, that compiz works on the other display.


Greetings
	Juergen


-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages compiz depends on:
ii  compiz-core                   0.7.6-7    OpenGL window and compositing mana
ii  compiz-gnome                  0.7.6-7    OpenGL window and compositing mana
ii  compiz-gtk                    0.7.6-7    OpenGL window and compositing mana
ii  compiz-plugins                0.7.6-7    OpenGL window and compositing mana

compiz recommends no packages.

Versions of packages compiz suggests:
ii  compizconfig-settings-manager 0.7.6-3    Compizconfig Settings Manager

-- no debconf information



--- End Message ---
--- Begin Message ---
On Wed, 2009-02-25 at 21:01 +0100, Juergen Kosel wrote:
> I have configured gdm to start 2 xservers.
> They set DISPLAY to :0.0 and :1.0
> 
> When I try to start compiz in a terminal on display :1.0, it delivers the following:
> 
> compiz --replace  &
> [1] 5831
> juergen@acer-ilzleite:~$ Checking for Xgl: not present.
> Detected PCI ID for VGA: 01:00.0 0300: 1002:5b60 (prog-if 00 [VGA controller])
> Checking for texture_from_pixmap: present.
> Checking for non power of two support: present.
> Checking for Composite extension: present.
> Comparing resolution (1280x1024) to maximum 3D texture size (2048): Passed.
> Checking for nVidia: not present.
> Checking for FBConfig: present.
> Checking for Xgl: not present.
> Starting gtk-window-decorator
> /usr/bin/compiz.real (core) - Fatal: No GLXFBConfig for default depth, this isn't going to work.
> /usr/bin/compiz.real (core) - Error: Failed to manage screen: 0
> /usr/bin/compiz.real (core) - Fatal: No manageable screens found on display :1.0
> 
DRI (accelerated 3d rendering) only works on one X server.  This isn't a
bug in compiz, but a well-known limitation in the DRI architecture.
Might get fixed with dri2.

Cheers,
Julien


--- End Message ---

Reply to: