Comment 9 for bug 697974

Thanks for the debugging and for the patch, but I don't think it fixes the root cause. tzmap->point_hover should already contain the point that was retrieved using e_map_get_closest_point() when the pointer moved. So if tzmap->point_hover isn't valid, we have to find out why. The questions I asked in my last comment might help understanding this.

I don't see what Compiz could be doing that makes this fail - maybe we don't get events when the pointer moves, but this would be a real failure from Compiz. Or is the crash only triggered when you click without the pointer having moved too much on the map? or when it hasn't gone out of the map once?

Also, please don't commit the fix to Natty. If we choose this patch, I'd rather push it upstream first, rather than diverging, which will create packaging work when the next release is out (this is not a problem for Maverick, though).