ica crashed with SIGSEGV in QLocale::dayName()

[Jerry]

nothing special. other bug 745052 seems similar but so old,
maybe wrong version of Ubuntu?

I notice the local for the kernel ? is not known
and have been seeing those messages for a long while

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: italc-client 1:1.0.13-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Wed Aug 3 06:20:34 2011
ExecutablePath: /usr/bin/ica
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: ica -noshm -isdport 5800 -ivsport 5900 -role other
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xbaec25 <_ZNK7QLocale7dayNameEiNS_10FormatTypeE+293>: mov (%eax),%edx
 PC (0x00baec25) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: italc
StacktraceTop:
 QLocale::dayName(int, QLocale::FormatType) const () from /usr/lib/libQtCore.so.4
 QDate::shortDayName(int) () from /usr/lib/libQtCore.so.4
 QDateTime::toString(Qt::DateFormat) const () from /usr/lib/libQtCore.so.4
 msgHandler(QtMsgType, char const*) () from /usr/lib/italc/libitalc_core.so
 qt_message_output(QtMsgType, char const*) () from /usr/lib/libQtCore.so.4
Title: ica crashed with SIGSEGV in QLocale::dayName()
UpgradeStatus: Upgraded to oneiric on 2011-07-21 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #745052, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.