I do also *not* have this problem (and have not 'fixed' it myself) using 11.10. So I suppose it is fixed somewhere along the route?
I do also *not* have this problem (and have not 'fixed' it myself) using 11.10. So I suppose it is fixed somewhere along the route?