Comment 3 for bug 176512

Revision history for this message
Emmet Hikory (persia) wrote :

Thanks for collecting the information. This has been fixed upstream in the newer releases (I'm not sure which of 2+0.13 or 2.4.0), and will be included in the next release. As it is a cosmetic issue that does not either cause data loss or a significant regression in functionality, it will not likely be considered for a stable release update.