This cannot be usefully handled as a driver bug; the hardware is perfectly capable of running at that resoluton. The driver cannot know that you're going to try to use a GL compositor that doesn't handle running at resolutions greater than the maximum GL texture size.
This is either a compiz bug or a unity bug. Didn't compiz grow support for running at > max_gl_texture_size this cycle? That would be slower (I'm not sure how much slower) but shouldn't fail. There might be mesa bugs causing that to be slower than it has to be, but that doesn't seem to be this bug.
This cannot be usefully handled as a driver bug; the hardware is perfectly capable of running at that resoluton. The driver cannot know that you're going to try to use a GL compositor that doesn't handle running at resolutions greater than the maximum GL texture size.
This is either a compiz bug or a unity bug. Didn't compiz grow support for running at > max_gl_texture_size this cycle? That would be slower (I'm not sure how much slower) but shouldn't fail. There might be mesa bugs causing that to be slower than it has to be, but that doesn't seem to be this bug.