compiz assert failure: compiz: ../../nouveau/nouveau_pushbuf.c:273: nouveau_pushbuf_flush: Assertiva `!nouveau_pushbuf_space(chan, min)' falhou.

[Leonardo Santagada]

moving an icon in unity

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
AssertionMessage: compiz: ../../nouveau/nouveau_pushbuf.c:273: nouveau_pushbuf_flush: Assertiva `!nouveau_pushbuf_space(chan, min)' falhou.
CrashCounter: 1
Date: Tue Oct 4 10:08:07 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
ProcCmdline: compiz
Signal: 6
SourcePackage: nux
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 nouveau_pushbuf_flush () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.1
 nvfx_push_vbo () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
Title: compiz assert failure: compiz: ../../nouveau/nouveau_pushbuf.c:273: nouveau_pushbuf_flush: Assertiva `!nouveau_pushbuf_space(chan, min)' falhou.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __GI___assert_fail (assertion=0x7f2bdabd9a58 "!nouveau_pushbuf_space(chan, min)", file=<optimized out>, line=273, function=<optimized out>) at assert.c:81
 nouveau_pushbuf_flush (chan=0x20f90d0, min=0) at ../../nouveau/nouveau_pushbuf.c:273
 FIRE_RING (chan=0x20f90d0) at /usr/include/nouveau/nouveau_pushbuf.h:101
 nvfx_push_vbo (pipe=<optimized out>, info=0x7fff3164df40) at nvfx_push.c:407
 st_draw_vbo (ctx=0x217ce70, arrays=<optimized out>, prims=<optimized out>, nr_prims=1, ib=0x0, index_bounds_valid=<optimized out>, min_index=0, max_index=3) at state_tracker/st_draw.c:763

[Bryce Harrington (bryce)]

Hey santagada,

Hi, thanks for reporting this issue during the development period of
Ubuntu.

I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?

Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.