While korganizer itself shows in catalan, the reminder daemon shows all messages in english. It's a regression, since in mageia 3 it was correctly localized. Reproducible: Steps to Reproduce:
and with the version in 4.12 in testing ?
Mmmh, now the reminder seems to be localized (at least the caption is), but korganizer segfaults when I try to start it. I updated with sudo urpmi --media "updates testing" korganizer kde-l10n-ca which pulled the following dependencies Per complir les dependències, s'instal·laran els paquets següents: Paquet Versió Versió Arq (suport «Core Updates Testing») akregator 4.12.5 1.mga4 x86_64 kaddressbook 4.12.5 1.mga4 x86_64 kalarm 4.12.5 1.mga4 x86_64 kde-l10n-ca 4.12.5 1.mga4 noarch kdepim4-core 4.12.5 1.mga4 x86_64 kdepim4-kresources 4.12.5 1.mga4 x86_64 kjots 4.12.5 1.mga4 x86_64 kleopatra 4.12.5 1.mga4 x86_64 kmail 4.12.5 1.mga4 x86_64 kmailcvt 4.12.5 1.mga4 x86_64 knode 4.12.5 1.mga4 x86_64 knotes 4.12.5 1.mga4 x86_64 kontact 4.12.5 1.mga4 x86_64 korganizer 4.12.5 1.mga4 x86_64 ksendemail 4.12.5 1.mga4 x86_64 ktimetracker 4.12.5 1.mga4 x86_64 lib64folderarchive4 4.12.5 1.mga4 x86_64 lib64grantleetheme4 4.12.5 1.mga4 x86_64 lib64grantleethemeeditor4 4.12.5 1.mga4 x86_64 lib64kaddressbookgrantlee4 4.12.5 1.mga4 x86_64 lib64knotesprivate4 4.12.5 1.mga4 x86_64 perhaps I should update more packages, but in that case why didn't urpmi pull all necessary packages? After sending this comment I'll close the session and start again to see if it fixes things.
Nope, it still segfaults. I tried to update kdelibs4-core but it still segfaults. It seems I'll have to update the updates testing media and update the whole shebang.
~430 updates later korganizer starts and korgac is localized. I still think the first urpmi command should have pulled all required libraries.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD