Gaussian blur distorted when screen rotated

[Bogdan Butnaru]

Binary package hint: compiz

Hello! I'm running up-to-date Jaunty/amd64, on a self-built desktop with an NVidia GeForce 9600 video card, running the NVIDIA GLX Module 180.37. (I've got 180.44-0ubuntu1 installed, but haven't rebooted yet, I'll do that and update the report.)

Using CCSM I've activated Alpha Blur for all windows, using the Gaussian filter with radius 7 and strength 0.2603 (just some random value that looked good).

This works correctly until I rotate my screen (I've got a pivot monitor). I do the rotation with nVidia's tool, after enabling RandR with option "RandRRotation" "True" in my xorg.conf

On rotated screens, the blur is horizontally distorted (it seems at least some component is stretched). I assume the screen ratio is implicitly represented, perhaps as the size of an intermediary texture, and isn't updated on rotations.

This happens the same if the initial state is landscape or portrait: the state the screen was in when Compiz was started is correct, and 90°-rotated states are distorted. If Compiz is restarted with the screen rotated, than that rotation state becomes correct and its rotations become distorted.

[Edit:] I've attached screenshots with the two cases. The correct one was done in portrait orientation, the incorrect one in landscape. The window and the icons below are the same, but the wallpaper does not follow the screen rotation so it's different between the two states.

Let me know if you need any more info.

[Mirco Müller (macslow)]

Hm... I had that once too, but not triggered by rotating the screen. It just happened. I think it is a bug in the blur plugin. Right now I can only suggest a workaround that helped me fix the issue. Disable and re-enable the blur plugin (e.g. via ccsm). I have not encountered that more than twice sofar.

[Bogdan Butnaru (bogdanb)]

Still going on in Natty. (Also, I’m confirming Mirco’s work-around: if the blur plugin is re-initialized, it displays correctly until the screen rotation changes again.)

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Sorry for the stagnace of this very well-reported bug, Bogdan. Is this still reproducible for newer versions of Compiz/Ubuntu?

[Bogdan Butnaru (bogdanb)]

I'm sorry, Chauncellor, I mostly stopped using Ubuntu some time around the 12.4 release, and I switched to KDE a few months ago. I'm pretty sure I had all sorts of trouble with the blur plugin in the versions of Compiz included with Mint Linux, both the Ubuntu-derived one and LMDE, though at least the latter is probably irrelevant.

Meta questions:

BTW, Launchpad tells me I have reported around fifty still-open bugs, though I've seen at least one that was closed for Ubuntu but is shown open because it's linked to debbugs and status tracking didn't work right or something. AFAIK they're all at least this one's age. Should I close them all on principle, just to get it off of the triage guys, or would that just cause more work if I mess something up or someone else is still watching for a solution?

Also, normal etiquette says I should answer to these questions---I imagine I'll get them for most of those bugs during the next few months or years, since the ID of this bug is less half that of the newest one---but since my answer is pretty much "no idea, really", would it be less work for you if I ignore them and let them to (presumably) expire or something?

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Hi, Bogdan, thanks for replying.

If you or another person can't confirm this then the bug will sit and auto-expire until someone comes along and provides info. So no worries if you don't get to it.

[Launchpad Janitor (janitor)]

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for Compiz Core because there has been no activity for 60 days.]