Package: compiz
Version: 0.2.2-1
Followup-For: Bug #427384
xserver-xorg-core 1.3 made compiz start, but with black frames around
windows instead of shadows (Intel i810).
I don't know if it's important, because I don't know what it means,
but it is also there when I start compiz with the old
hi,
upgrading xserver-xorg-core to the unstable version 2:1.3.0.0.dfsg6
everything works ok for me.
I have the same warnings than Peter, but window shadows are ok, and no
black boxes appears. Also with i810.
Regards
Diego
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: compiz
Version: 0.2.2-1
Followup-For: Bug #427384
I'm very sorry, but this was wrong. It needs a few minutes,
but now I have problems with the configuration (old libxrand2
and old xserver), too which didn't occure before.
compiz tells me
/usr/bin/compiz.real: pixmap 0x3c03875 can't be
Package: xserver-xorg
Version: 1:7.2-3
Followup-For: Bug #331435
Hello.
The last reply about this bug is fairly old. Was the cause found?
I recently upgraded many packages (including the nvidia driver).
Now, sometimes, after the session has been locked (using xlock), the mouse
pointer does not
Like Diego, after upgrading xserver-xorg-core to the unstable version
2:1.3.0.0.dfsg6 everything works ok, using the most recent Lenny
packages (libxrandr2 2:1.2.1-1).
Using i810 (Intel 945GM onboard) on a Core2 Duo.
I did witness the black or white shading problems Peter mentions earlier
Package: xterm
Version: 225-1
Severity: wishlist
It would be useful to have the ability to run a script just before
xterm is about to exit. The script should have access to the following
information in some way:
* the exit status of the subprocess if it has terminated (thus
causing xterm to
Package: compiz
Version: 0.2.2-1
Followup-For: Bug #427384
My mistake was to stick with the stable libxrandr2 while trying to
use the unstable xserver-xorg-core, please foregive the unnecessary
confusion. Everything works fine here with unstable xserver-xorg-core
now too.
--
To UNSUBSCRIBE,
Your message dated Wed, 06 Jun 2007 19:40:27 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#427384: compiz broken in lenny after libc6 upgrade
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Processing commands for [EMAIL PROTECTED]:
reassign 427384 xserver-xorg-core
Bug#427384: compiz broken in lenny after libc6 upgrade
Bug reassigned from package `compiz' to `xserver-xorg-core'.
retitle 427384 libxrandr 1.2 with xserver-xorg-core 1.1 breaks compiz
Bug#427384: compiz broken in
Package: libdrm2
Version: 2.3.0-4
Followup-For: Bug #324560
Could this be the reason that with an amd64 kernel I get this:
[drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
This card requires a new X.org DDX for 3D
Whilst it works OK with a 686 kernel?
-- System
Jason Cormie wrote:
Package: libdrm2
Version: 2.3.0-4
Followup-For: Bug #324560
Could this be the reason that with an amd64 kernel I get this:
[drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
This card requires a new X.org DDX for 3D
I don't think so. I'd say it is
Your message dated Wed, 06 Jun 2007 20:53:58 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#390271: compiz: unusable (very very slow) with r300
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Wed, 06 Jun 2007 20:57:46 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#390319: compiz: Doesnt refresh windows content
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
On Wed, Jun 6, 2007 at 20:32:30 +0200, Brice Goglin wrote:
Jason Cormie wrote:
[drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
This card requires a new X.org DDX for 3D
I don't think so. I'd say it is related to an outdated kernel and/or
Xorg for a recent board.
Brice Goglin wrote:
Jason Cormie wrote:
Package: libdrm2
Version: 2.3.0-4
Followup-For: Bug #324560
Could this be the reason that with an amd64 kernel I get this:
[drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
This card requires a new X.org DDX for 3D
I don't
Hi,
Does this crash of the Xserver when running compiz still occurs
nowadays? With latest compiz 0.5.0 and xserver-xorg-core 1.3 currently
in unstable?
thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
Did any of you guys reproduce this problem regarding missing window
borders in compiz recently? With latest compiz 0.5 and xserver-xorg-core
1.3 currently in unstable?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Hi,
Did you reproduce recently this problem with compiz refusing to replace
another window manager (KDE here)?
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Your message dated Wed, 06 Jun 2007 21:31:00 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#402545: compiz: Returning from another virtual terminal
makes a black screen
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Hi,
Do you still reproduce these rendering problems in compiz after
suspend/resume? Even with latest xserver-xorg-core 1.3, compiz 0.5 and
drivers?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi Evgeni,
Does this problem with compiz in twinview still occurs with latest
compiz 0.5, xserver-xorg-core 1.3 and nvidia drivers? Can you reproduce
with another xinerama-like extension that does not need on the nvidia
binary? Nobody else reported such a problem with a free driver, so it
might
Hi Erich,
Does this RandR problem under compiz still occurs with latest compiz
0.5, xserver-xorg-core 1.3 and xserver-xorg-video-intel 2.0 currently in
unstable? RandR 1.2 support might changed things here.
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Hi Brice,
On Mon, Jun 04, 2007 at 11:01:18PM +0200, Brice Goglin wrote:
Does this crash of the X server still happen nowadays when switching
with alt-tab between gnome-terminal and a Xv window? with latest
xserver-xorg-core and drivers?
I didn't see the bug for quiet some time, but since it
Hi,
Did you reproduce recently this problem with compiz refusing to replace
another window manager (KDE here)?
This is in my case:
$ compiz --replace
GLX_EXT_texture_from_pixmap is available with direct rendering.
/usr/bin/gtk-window-decorator: Could not acquire decoration manager
Julien Cristau wrote:
On Wed, Jun 6, 2007 at 20:32:30 +0200, Brice Goglin wrote:
Jason Cormie wrote:
[drm:radeon_do_init_cp] *ERROR* Cannot initialise DRM on this card
This card requires a new X.org DDX for 3D
I don't think so. I'd say it is related to an outdated kernel and/or
Xorg
Hi,
Do you still reproduce this problem with full-screen windows in compiz?
with latest xserver-xorg-core 1.3, compiz 0.5 and drivers?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi Enrico,
Do you still reproduce this problem with the move plugin of compiz not
preserving initiate_button setting when set to Mod4Button1? With
latest compiz 0.5 currently in unstable?
Thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Hi Brice,
On Wed, 06 Jun 2007 21:45:06 +0200 Brice Goglin wrote:
Does this problem with compiz in twinview still occurs with latest
compiz 0.5, xserver-xorg-core 1.3 and nvidia drivers? Can you reproduce
with another xinerama-like extension that does not need on the nvidia
binary? Nobody
It is impossible to UnSubscribe from this list.
Would someone please help me to get out of this nut house.
Thank you,
Jeff Stanich
Simix Reactive Solutions, LLC
http://www.simixsolutions.com
-Original Message-
From: Brice Goglin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 06,
On Wed, Jun 06, 2007 at 10:13:10PM +0200, Brice Goglin wrote:
Do you still reproduce this problem with the move plugin of compiz not
preserving initiate_button setting when set to Mod4Button1? With
latest compiz 0.5 currently in unstable?
I'm unfortunately not using compiz anymore. I'll see
I want out of your nut house, get me off of this list,
Thank you,
Jeff Stanich
Simix Reactive Solutions, LLC
http://www.simixsolutions.com
-Original Message-
From: Evgeni Golov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 06, 2007 3:17 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Radu Spineanu wrote:
Hi,
Did you reproduce recently this problem with compiz refusing to replace
another window manager (KDE here)?
This is in my case:
$ compiz --replace
GLX_EXT_texture_from_pixmap is available with direct rendering.
/usr/bin/gtk-window-decorator: Could not acquire
Your message dated Wed, 06 Jun 2007 22:43:25 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#409485: server crash when Alt-Tab switching between
gnome-terminal and Xv window
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 06 Jun 2007 22:36:02 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#407055: compiz: manages only screen 0 of a multi screen
display
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 06 Jun 2007 22:38:25 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#391228: compiz: does not work correctly with twinview
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Hi Benoit,
Do you still reproduce your problems with compiz 0.5.0 currently in
unstable? With xserver-xorg-core 1.3 and latest ATI drivers (6.6.192 is
currenlty in experimental)? To reduce speed issues, you might want to
try adding
Option XAANoOffscreenPixmaps
to the device section of your
Hi Nick,
Does this problem with xterm windows jiggling when maximized in compiz
still happens today? With compiz 0.5.0?
thanks,
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I wonder whether this bug is actually in compiz and not in
gnome-screensaver. There are some known problems with non-trivial X
config in gnome-screensaver, for instance randr-1.2 dual-head [1], which
lead to the unlock window not being displayed at all (but entering the
passwd unlocks and restores
Hi Brice,
This is in my case:
$ compiz --replace
GLX_EXT_texture_from_pixmap is available with direct rendering.
/usr/bin/gtk-window-decorator: Could not acquire decoration manager
selection on screen 0 display :0.0
/usr/bin/compiz.real: decoration: property ignored because version is
20061011
Hm...
Brice Goglin schrieb:
Friedrich Delgado Friedrichs wrote:
Package: xserver-xorg
Version: 1:7.2-3
Followup-For: Bug #326956
xserver-xorg does not matter here. This package basically contains
nothing. The actual server code is in xserver-xorg-core, which you
didn't upgrade to
Package: xserver-xorg-video-intel
Version: 2:2.0.0-4
--- Please enter the report below this line. ---
My laptop with a i915GM was suspending to ram and to disk fine with the
non-modesetting driver (i810), even if i had to use 915resolution to set
the modes, vbetool to POST the video, and press
I can confirm this bug, i915GM with xserver-xorg-video-intel 2:2.0.0-4
Was working fine with the i815 driver.
Also suspend to ram/disk doesn't work anymore now :-((
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Brice Goglin wrote:
Does this problem with xterm windows jiggling when maximized in compiz
still happens today? With compiz 0.5.0?
Nope, problem's gone.
Thanks, Brice!
Nick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Your message dated Thu, 07 Jun 2007 00:47:15 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#390198: compiz: maximize doesn't enter steady state with
windows whose sizes are multiples
has caused the attached Bug report to be marked as done.
This means that you claim that the problem
Package: xserver-xorg-video-ati
Version: 6.6.192-1
Severity: normal
The output from running LIBGL_DEBUG=VERBOSE glxinfo indicates no direct
rendering and states:
libGL error: dlopen /usr/lib/dri/r300_dri.so failed
(/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_add_dispatch)
libGL error:
On Wed, Jun 6, 2007 at 18:50:23 -0500, Adam Dane wrote:
Package: xserver-xorg-video-ati
Version: 6.6.192-1
Severity: normal
The output from running LIBGL_DEBUG=VERBOSE glxinfo indicates no direct
rendering and states:
libGL error: dlopen /usr/lib/dri/r300_dri.so failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brice Goglin wrote:
Hi,
Do you still reproduce these rendering problems in compiz after
suspend/resume? Even with latest xserver-xorg-core 1.3, compiz 0.5 and
drivers?
I'm running an up2date sid system and I unfortunately still experience the
Julien Cristau wrote:
This symbol is provided by libGL.so.1 from the libgl1-mesa-glx package,
so this error is probably caused by an installation of fglrx. Can you
check this?
Yes, that was the problem. Sorry about that.
Thanks,
Adam
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Your message dated Thu, 7 Jun 2007 03:00:04 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#427858: xserver-xorg-video-ati: no DRI: undefined symbol
_glapi_add_dispatch
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt
Brice Goglin wrote:
I wonder whether this bug is actually in compiz and not in
gnome-screensaver. There are some known problems with non-trivial X
config in gnome-screensaver, for instance randr-1.2 dual-head [1], which
lead to the unlock window not being displayed at all (but entering the
50 matches
Mail list logo
