Comment 11 for bug 130450

I agree, to properly fix the problem it will probably require a good deal of work (I don't know, but I am assuming, I would have to know more about the whole indirect thing, is it a driver problem that things have to be done indirectly, or hardware?). But for now, could a simple patch against gnome-session work (possibly for gutsy+1, not sure if you want to add something like that that might fix one problem and create another especially since we are nearing beta) so that it won't save compiz.real (while saving running processes, check if the process it is saving is compiz.real and if it is save it as compiz instead, I don't really know how gnome-session works, but I imagine it does something similar)? Yes, it would be an ugly hack, but it would make it a much nicer experience for users ("ah, why the hell is this not working, I give up" users are not going to google something like this, it should just work, they don't care if you have to use ugly hacks to make it work, so long as it works) and could be easily dropped once it was properly fixed (something that could take years to finish). And I think that would be the easiest way, if you wanted to fix it via compiz, the only way I can really see at the moment is to merge the compiz wrapper script with compiz itself, which is not really a good idea. Thanks for explaing that though Travis, although why mark this as won't fix if it is a problem and it does affect users. I understand it will take a lot of time and effort (I think) for fixing a very small problem, but it should not just be overlooked. Ignoring a problem does not make it go away.