Description of problem: Updating Mageia x86_64 from 3 to 4 causes certain applications including MCC display squares instead of text. Example screenshots: http://storage5.static.itmages.ru/i/14/0226/h_1393439391_5948346_596c70130b.png http://storage9.static.itmages.ru/i/14/0226/h_1393439390_1227735_00a542021a.png http://storage6.static.itmages.ru/i/14/0226/h_1393437099_2448654_652f1d09ca.png The problem is related to lib64pango1.0_0-modules: after update from DVD enabling online sources: lib64pango1.0_0-modules-1.32.5-3.mga3 is not removed, File /etc/pango/x86_64/pango.modules is empty Version-Release number of selected component (if applicable): 1.36.1-1.mga4 and 1.32.5-3.mga3 How reproducible: Problem first appeared in real machine and was reproduced using mirror.yandex.ru as mirror in VirtualBox. i586 might be affected too. Steps to Reproduce: 1. Install Mageia 3 x86_64 (use locale ru_RU.UTF-8, but probably not necessary) 2. Update everything from internet 3. Reboot from Mageia 4 x86_64 DVD 4. Start system upgrade enabling online repositories 5. Upgrade hangs on this stage: http://storage6.static.itmages.ru/i/14/0226/h_1393433544_6224633_febe238106.png 6. Press reset and start update again, this time not using online repos 7. Reboot to the updated system 8. Update everything with urpmi --auto-update 9. Start Mageia Control Center, gedit or most of others Gtk application You see squares instead of letters. Possible workaround: Run this command as root after update: /usr/bin/pango-querymodules-64 --system > /etc/pango/x86_64/pango.modules Reproducible: Steps to Reproduce:
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=12743
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=12660
Assignee: bugsquad => thierry.vignaud
*** Bug 12660 has been marked as a duplicate of this bug. ***
CC: (none) => harald
Hardware: x86_64 => All
Created attachment 5112 [details] Full log of a failed upgrade attempt Seems like my problem is caused by the same error. I've tried to upgrade using urpmi commands and got the following: 44/215: pango ######################################################################################################### 45/215: lib64pango1.0_0 ######################################################################################################### 46/215: lib64pango1.0_0-modules ######################################################################################################### 47/215: libpango1.0_0 ######################################################################################################### 48/215: libpango1.0_0-modules ######################################################################################################### (pango-querymodules-32:4811): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init() (pango-querymodules-32:4811): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed (pango-querymodules-32:4811): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>' (pango-querymodules-32:4811): GLib-GObject-CRITICAL **: g_enum_get_value: assertion `G_IS_ENUM_CLASS (enum_class)' failed (pango-querymodules-32:4811): Pango-WARNING **: Engine reported invalid script value 2 ^CпÑедÑпÑеждение: %post(libpango1.0_0-modules-1.36.1-1.mga4.i586) scriptlet failed, signal 2 The process hanged so I had to interrupt it with Ctrl-C. It looks like the problem is somewhere in post-install script that tries to perform and fails due to missing some components. Probably versioned dependency could solve the problem but I don't know which one. And I've noticed that on x86_64 urpmi tries to upgrade 32-bit version of pango *before* 32-bit version of glib. The full log of upgrade attempt is attached. Some lines are in russian as I had not expected any serious troubles and not used LC_ALL=C. Sorry.
CC: (none) => olegbosis
As the pango package has no dedicated packagers, adding those who worked on it in the past in CC. To packagers: this is an upgrade issue from Mageia 3 to Mageia 4 with updates media on.
Keywords: (none) => TriagedCC: (none) => dmorganec, fundawang, jani.valimaa, mageia, olav, shlomif, thierry.vignaudComponent: Installer => RPM PackagesAssignee: thierry.vignaud => bugsquad
CC: jani.valimaa => (none)
What is the status of this bug for Mageia 5? Is it needed to add in the errata?
CC: (none) => yves.brungard_mageia
(In reply to papoteur from comment #4) > What is the status of this bug for Mageia 5? > Is it needed to add in the errata? I didn't encounter this bug in upgrades from Mageia 4 to Mageia 5.
If you don't see it when upgrading from mga3 to mga4, that means it depends on the package set. There's probably a missing requires. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740483 On the other hand, if this only happened with old versions of glib we could close it as OLD
Assignee: bugsquad => olav
We did not get new reports about similar upgrade issues from Mageia 4 to Mageia 5, so I guess we can close this one as OLD since Mageia 4 reached EOL.
Status: NEW => RESOLVEDResolution: (none) => OLD