Massive corruption of video memory when changing panel orientation

[QB89Dragon]

Binary package hint: gnome-panel

To reproduce this bug, go to system monitor and kill an applet linked using bonobo to the gnome panel, so that the 'do you want to reload' dialog pops up. Leave the dialog where it is, open the properties for the panel and change the orientation around from up, down, left, right. You need to be using compiz for this to work, but watch the spectacular corruption of all the video buffers for every window so that glitching goes all over the whole screen. I did this twice in a row and it crashed compiz.

Ubuntu jaunty, nvidia restricted geforce 9400gt, google gadgets running at the time. No other open-gl or wine applications had been run since the computer booted. No other activities that may have contributed to this issue.

[Sebastien Bacher (seb128)]

the issue is either a compiz or a video driver one, nobody else is getting similar effects and the video buffer being corrupted is not an user software issue

[QB89Dragon (hughescih)]

You're an unbeliever!
Behold with thine own eyes
http://qb89.deviantart.com/art/Spectacular-linux-crash-130557255

Sebastien Bacher wrote:
> the issue is either a compiz or a video driver one, nobody else is
> getting similar effects and the video buffer being corrupted is not an
> user software issue
>
> ** Package changed: gnome-panel (Ubuntu) => ubuntu
>
>

[QB89Dragon (hughescih)]

Here's the whole kaboodle of crash screenshots.

Sebastien Bacher wrote:
> the issue is either a compiz or a video driver one, nobody else is
> getting similar effects and the video buffer being corrupted is not an
> user software issue
>
> ** Package changed: gnome-panel (Ubuntu) => ubuntu
>
>

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!