Doesnt respect date display format

[Emil Beli]

Binary package hint: thunderbird

Linux, no matter ubuntu or openSUSE (I have both). Doesn't respect date format, neither from system setting nor from LC_TIME. If my system is English US, with modified regional settings to display date DD/MM/YYYY, it always displays MM/DD/YYYY no matter of other variables.
Very very bad. Make a format setting inside thunderbird, or make it respect what I put to my system

ProblemType: Bug
Architecture: i386
Date: Wed Sep 3 09:43:39 2008
Dependencies:

DistroRelease: Ubuntu 7.10
NonfreeKernelModules: vmnet vmmon nvidia
Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list]
PackageArchitecture: all
SourcePackage: thunderbird
Uname: Linux dskdclick02 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

[Ray Chidley (rchidley)]

I found this link useful and it worked for me:-

http://ubuntuforums.org/showthread.php?t=193916

In my case was I required %Y-%m-%d

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.04). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 264324, and any other logs that are relevant for this particular issue.

[Przemek K. (azrael)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".
If you decide to reopen this bug, it would help us a lot if you could test the current Ubuntu development version (10.10) and check if this bug is still relevant.
Thanks again!