Description of problem: After upgrading to MGA4 and starting acroread (9.4.2 and 9.5.x) which I need for forms filling, it shows only squares instead of letters, including menus, etc. Digging showed, that /etc/pango/i386/pango.modules is empty (while x86_64) version is not and that copying content of /etc/pango/x86_64/pango.modules to /etc/pango/i386/pango.modules and changing paths so that they would point to proper i586 place fixes this problem. As that file should be autogenerated, it seems that generator failed somehow. Version-Release number of selected component (if applicable): pango-1.36.1-1.mga4.src.rpm How reproducible: 100% (all upgraded PCs were hit) Steps to Reproduce: 1. upgrade MGA3-> MGA4 2. try to use i586 application depending on pango (acrobat reader for example) Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedCC: (none) => fundawang, olavSummary: Acrobat Reader shows squares instead of letters/numbers => Acrobat Reader shows squares instead of letters/numbers (i386/pango.modules empty)
Follow up: when updating from MGA3->MGA4, installation of libpango1.0_0-modules basically hangs with error message: (pango-querymodules-32:21395): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init() (pango-querymodules-32:21395): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed (pango-querymodules-32:21395): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>' (pango-querymodules-32:21395): GLib-GObject-CRITICAL **: g_enum_get_value: assertion `G_IS_ENUM_CLASS (enum_class)' failed (pango-querymodules-32:21395): Pango-WARNING **: Engine reported invalid script value 2 <=== (proces /usr/bin/pango-querymodules-32 --system). You have to kill this process in order to proceed which almost certainly causes reported bug.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=12898
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