Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34926 - [evolution] crashes on polish locale
Attached to Project:
Arch Linux
Opened by Samuel Magiera (samuelm) - Wednesday, 24 April 2013, 06:15 GMT
Last edited by Jan de Groot (JGC) - Monday, 13 May 2013, 15:27 GMT
Opened by Samuel Magiera (samuelm) - Wednesday, 24 April 2013, 06:15 GMT
Last edited by Jan de Groot (JGC) - Monday, 13 May 2013, 15:27 GMT
|
DetailsDescription:
Evolution crashes with this error: GLib-GObject-CRITICAL **: g_param_spec_internal: assertion `!(flags & G_PARAM_STATIC_NAME) || is_canonical (name)' failed. When started with LC_ALL=C, all seems to work ok. My system locale is set to Polish. The bug is mentioned in this forum thread:https://bbs.archlinux.org/viewtopic.php?pid=1263148. Also gnome online accounts are affected by this - when adding account with Google, Facebook or Windows Live, it crashes. evolution version 3.8.1-1 gnome-online-accounts 3.8.1-1 Steps to reproduce: Set locale to polish In online accounts click add, choose Google/start evolution |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 13 May 2013, 15:27 GMT
Reason for closing: Fixed
Additional comments about closing: webkitgtk3 2.0.2-1.
Monday, 13 May 2013, 15:27 GMT
Reason for closing: Fixed
Additional comments about closing: webkitgtk3 2.0.2-1.
Temporary fix: su -c 'rm -f /usr/share/locale/pl/LC_MESSAGES/WebKitGTK-3.0.mo'
Permanent fix: Stab the face of whoever authored the 386th line of Source/WebKit/gtk/webkit/webkitviewportattributes.cpp in WebKit source code. (It erroneously marks a string for translation, which the overzealous and unsuspecting translator picked up.)
This bug has been there since the beginning, it was just waiting for someone to translate it and trigger the bug...
Reported this upstream, a patch was issued. https://bugs.webkit.org/show_bug.cgi?id=115484