349 2010-09-21 01:01:00 +0000 [QT] fotowall warns iconv failure in QIconvCodec 2013-06-21 09:21:59 +0000 1 1 7 Build System, Metadata & Runtime Meta-yocto meta-yocto 0.9 x86 Multiple RESOLVED FIXED Low minor 1.5 M2 1 qing.he net147 jessica.zhang jiajun.xu ke.yu kevin.tian net147 poky.bs.watcher poky.watcher richard.purdie sgw --- --- --- oldest_to_newest 9929 0 qing.he 2010-09-21 01:01:00 +0000 see also bug 280, bug 347, bug 347 this bug addresses the warning part of iconv failures. Since it appears to be just warning, don't block bug 280 ###### root@qemux86-64:~# DISPLAY=:0.0 fotowall QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv failed for BOM: Bad file descriptor QIconvCodec::convertFromUnicode: using Latin-1 for conversion, iconv_open failed QIconvCodec::convertToUnicode: using Latin-1 for conversion, iconv_open failed Illegal instruction ###### 15536 1 bluelightning 2011-08-17 16:43:02 +0000 Honestly I have looked at this and the message itself doesn't really mean anything based on all of the searching I have done. If we are getting actual i18n failures that is a different story. My opinion is that we should mark this as WONTFIX. 18965 2 bluelightning 2012-03-12 12:28:31 +0000 Resolving as WONTFIX as above. If we get actual i18n issues with Qt then we can reopen or file a new bug as appropriate. 33964 3 net147 2013-06-19 06:48:53 +0000 Installing eglibc-gconv-utf-16 makes the warning disappear. 33965 4 richard.purdie 2013-06-19 08:00:58 +0000 Based on that should we add am RDEPENDS to fotowall? 33967 5 bluelightning 2013-06-19 08:15:14 +0000 If this dependency is independent of locale and is added conditional on using (e)glibc, then yes; I'd use RRECOMMENDS though since it's not a hard dependency. 33968 6 net147 2013-06-19 08:21:27 +0000 This happens for every Qt application. For example, it happens for this minimal Qt application: #include <QCoreApplication> int main(int argc, char *argv[]) { QCoreApplication a(argc, argv); return 0; } 33969 7 net147 2013-06-19 08:38:50 +0000 Qt's QString class stores strings internally using UTF-16 encoding. This affects conversions between the system's local 8-bit representation and QString's UTF-16 encoding. The example, the following functions would be affected: QString::fromLocal8Bit(...) QString::toLocal8Bit(...) It would use Latin-1 encoding instead of the system's encoding for conversion. 33970 8 bluelightning 2013-06-19 09:02:49 +0000 Right, this makes sense. In which case I guess the easiest thing would be to add the dependency to the qtcore package itself in qt4.inc. 34038 9 net147 2013-06-21 09:21:59 +0000 Fixed by http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ed4a919cae7b1e03d0cb83636ce88f50a3ca1d16