| Summary: | Updating Mageia from 3 to 4 from DVD with online repos leaves pango.modules empty causing GTK apps display squares | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Taaki Atshe <taakine> |
| Component: | RPM Packages | Assignee: | Olav Vitters <olav> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | dmorganec, fundawang, harald, mageia, olav, olegbosis, shlomif, thierry.vignaud, yvesbrungard |
| Version: | 4 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.mageia.org/show_bug.cgi?id=12743 https://bugs.mageia.org/show_bug.cgi?id=12660 |
||
| Whiteboard: | |||
| Source RPM: | pango-1.36.1-1.mga4.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | Full log of a failed upgrade attempt | ||
|
Description
Taaki Atshe
2014-02-27 18:18:18 CET
Taaki Atshe
2014-02-27 18:27:32 CET
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=12743
Taaki Atshe
2014-02-27 18:39:04 CET
See Also:
(none) =>
https://bugs.mageia.org/show_bug.cgi?id=12660
Manuel Hiebel
2014-02-27 18:48:08 CET
Assignee:
bugsquad =>
thierry.vignaud
Taaki Atshe
2014-02-27 19:02:03 CET
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) =>
Triaged
Jani Välimaa
2015-05-21 19:30:31 CEST
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 *** Bug 12660 has been marked as a duplicate of this bug. *** 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 =>
RESOLVED |