Weird error message
Locked
Weird error message
 
|
Hi all,
I get this error message whenever I start digiKam: KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work Do you see this, too? Andi -- Using Opera's revolutionary email client: http://www.opera.com/mail/ _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On 04/10/2011 06:06 PM, Andi Clemens wrote:
> Hi all, > > I get this error message whenever I start digiKam: > KGlobal::locale::Warning your global KLocale is being recreated with a > valid main component instead of a fake component, this usually means you > tried to call i18n related functions before your main component was > created. You should not do that since it most likely will not work > > Do you see this, too? Yes, I do. I think it means we call i18n before creating KApplication, in which case we should be using ki18n or similar (used in the construction of the about data). Michael _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Weird error message
|
|
I also get this when running the testsuite.
Andi On Sun, 10 Apr 2011 19:55:32 +0200, Michael G. Hansen <[hidden email]> wrote: > On 04/10/2011 06:06 PM, Andi Clemens wrote: >> Hi all, >> >> I get this error message whenever I start digiKam: >> KGlobal::locale::Warning your global KLocale is being recreated with a >> valid main component instead of a fake component, this usually means you >> tried to call i18n related functions before your main component was >> created. You should not do that since it most likely will not work >> >> Do you see this, too? > > Yes, I do. I think it means we call i18n before creating KApplication, > in which case we should be using ki18n or similar (used in the > construction of the about data). > > Michael > > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel -- Using Opera's revolutionary email client: http://www.opera.com/mail/ _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
I cannot see it on the console. Do you have enabled a special kdebug
area for that ? Gilles Caulier 2011/4/10 Andi Clemens <[hidden email]>: > I also get this when running the testsuite. > > Andi > > > On Sun, 10 Apr 2011 19:55:32 +0200, Michael G. Hansen <[hidden email]> > wrote: > >> On 04/10/2011 06:06 PM, Andi Clemens wrote: >>> Hi all, >>> >>> I get this error message whenever I start digiKam: >>> KGlobal::locale::Warning your global KLocale is being recreated with a >>> valid main component instead of a fake component, this usually means you >>> tried to call i18n related functions before your main component was >>> created. You should not do that since it most likely will not work >>> >>> Do you see this, too? >> >> Yes, I do. I think it means we call i18n before creating KApplication, >> in which case we should be using ki18n or similar (used in the >> construction of the about data). >> >> Michael >> >> >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel > > > -- > Using Opera's revolutionary email client: http://www.opera.com/mail/ > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
Le 13/04/2011 13:25, Gilles Caulier a écrit :
> > I cannot see it on the console. Do you have enabled a special kdebug > area for that ? hello i can see it also, without any special debug enabled. the only thing is that i use gnome and not kde... -- Pierre > Gilles Caulier > > 2011/4/10 Andi Clemens <[hidden email]>: >> I also get this when running the testsuite. >> >> Andi >> >> >> On Sun, 10 Apr 2011 19:55:32 +0200, Michael G. Hansen <[hidden email]> >> wrote: >> >>> On 04/10/2011 06:06 PM, Andi Clemens wrote: >>>> Hi all, >>>> >>>> I get this error message whenever I start digiKam: >>>> KGlobal::locale::Warning your global KLocale is being recreated with a >>>> valid main component instead of a fake component, this usually means you >>>> tried to call i18n related functions before your main component was >>>> created. You should not do that since it most likely will not work >>>> >>>> Do you see this, too? >>> >>> Yes, I do. I think it means we call i18n before creating KApplication, >>> in which case we should be using ki18n or similar (used in the >>> construction of the about data). >>> >>> Michael >>> >>> >>> _______________________________________________ >>> Digikam-devel mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-devel >> >> >> -- >> Using Opera's revolutionary email client: http://www.opera.com/mail/ >> _______________________________________________ >> Digikam-devel mailing list >> [hidden email] >> https://mail.kde.org/mailman/listinfo/digikam-devel >> > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > > _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
In reply to this post by Bugzilla from andi.clemens@gmx.net
On 04/10/2011 06:06 PM, Andi Clemens wrote:
> Hi all, > > I get this error message whenever I start digiKam: > KGlobal::locale::Warning your global KLocale is being recreated with a > valid main component instead of a fake component, this usually means you > tried to call i18n related functions before your main component was > created. You should not do that since it most likely will not work > > Do you see this, too? I think I found the causes for this problem, or at least some of them, by intercepting calls to i18n, see valgrind log below. One example is this line: http://lxr.kde.org/source/extragear/graphics/digikam/utilities/advancedrename/parser/options/dateoption.cpp#46 static const QString dateFormatLinkDescr = i18nc("date format settings", "format settings"); Here, we should use ki18nc instead, but the string is used in the next line: static const QString dateFormatLink = QString("<a href='http://doc.trolltech.com/latest/qdatetime.html#toString'>%1</a>").arg(dateFormatLinkDescr); So I think we have to move it to some place which will be called after the creation of KApplication. Michael (sid-kde-46)mike@operator:/c/temp/kdebuild/digikam-sc$ valgrind --tool=memcheck ./core/tests/advancedrenametest ==27142== Memcheck, a memory error detector ==27142== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==27142== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==27142== Command: ./core/tests/advancedrenametest ==27142== **27142** 802 at 0x6E97D92: VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:4233) ==27142== by 0x6E99708: i18nc(char const*, char const*) (klocalizedstring.h:802) ==27142== by 0x70641F7: __static_initialization_and_destruction_0(int, int) (imageguidewidget.cpp:54) ==27142== by 0x7102555: ??? (in /c/temp/kdebuild/digikam-sc/lib/libdigikamcore.so.2.0.0) ==27142== by 0x6E47332: ??? (in /c/temp/kdebuild/digikam-sc/lib/libdigikamcore.so.2.0.0) unnamed app(27142)/digikam (core) i18nc: /usr/local/include/klocalizedstring.h 802 **27142** 802 at 0x6E97D92: VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:4233) ==27142== by 0x6E99708: i18nc(char const*, char const*) (klocalizedstring.h:802) ==27142== by 0x706422E: __static_initialization_and_destruction_0(int, int) (imageguidewidget.cpp:55) ==27142== by 0x7102555: ??? (in /c/temp/kdebuild/digikam-sc/lib/libdigikamcore.so.2.0.0) ==27142== by 0x6E47332: ??? (in /c/temp/kdebuild/digikam-sc/lib/libdigikamcore.so.2.0.0) unnamed app(27142)/digikam (core) i18nc: /usr/local/include/klocalizedstring.h 802 **27142** 802 at 0x423460: VALGRIND_PRINTF_BACKTRACE(char const*, ...) (valgrind.h:4233) ==27142== by 0x424656: i18nc(char const*, char const*) (klocalizedstring.h:802) ==27142== by 0x4314F6: __static_initialization_and_destruction_0(int, int) (dateoption.cpp:46) ==27142== by 0x44CD85: ??? (in /c/temp/kdebuild/digikam-sc/core/tests/advancedrenametest) ==27142== by 0x4133C2: ??? (in /c/temp/kdebuild/digikam-sc/core/tests/advancedrenametest) ==27142== by 0x7FF00047F: ??? ==27142== by 0x44CD14: __libc_csu_init (in /c/temp/kdebuild/digikam-sc/core/tests/advancedrenametest) ==27142== by 0x91EEBDF: (below main) (libc-start.c:187) unnamed app(27142)/digikam (core) i18nc: /usr/local/include/klocalizedstring.h 802 KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
|
On 04/14/2011 11:04 PM, Michael G. Hansen wrote:
> On 04/10/2011 06:06 PM, Andi Clemens wrote: >> Hi all, >> >> I get this error message whenever I start digiKam: >> KGlobal::locale::Warning your global KLocale is being recreated with a >> valid main component instead of a fake component, this usually means you >> tried to call i18n related functions before your main component was >> created. You should not do that since it most likely will not work >> >> Do you see this, too? > > I think I found the causes for this problem, or at least some of them, > by intercepting calls to i18n, see valgrind log below. For the digikam executable, I get the same output as in the previous mail, so these three cases may be all. Michael _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Re: Weird error message
|
|
In reply to this post by Michael G. Hansen
Hmm weird never seen this before, these changes were made months ago.
Need to check this at the weekends. Andi On Thu, 14 Apr 2011 23:04:25 +0200, Michael G. Hansen <[hidden email]> wrote: > I think I found the causes for this problem, or at least some of them, > by intercepting calls to i18n, see valgrind log below. One example is > this line: > > http://lxr.kde.org/source/extragear/graphics/digikam/utilities/advancedrename/parser/options/dateoption.cpp#46 > > static const QString dateFormatLinkDescr = i18nc("date format settings", > "format settings"); > > Here, we should use ki18nc instead, but the string is used in the next > line: > > static const QString dateFormatLink = > QString("<a > href='http://doc.trolltech.com/latest/qdatetime.html#toString'>%1</a>").arg(dateFormatLinkDescr); > > So I think we have to move it to some place which will be called after > the creation of KApplication. Using Opera's revolutionary email client: http://www.opera.com/mail/ _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
«
Return to digikam-devel
|
1 view|%1 views
| Free forum by Nabble | Edit this page |