answered 14 years ago
This is bug #7981, and it will hopefully be fixed in an upcoming version of Sage. If you need it fixed now, you can apply the second patch on that ticket. Use the steps 1 - 4 here if you aren't sure how to apply the patch.