libpango update stuck

English Install/Boot/Login
#1

i just did an update of my Tumbleweed install, and the install gets stuck during install of of libpango-1_0-0-1.34.0-2.1, when checking processes it seems like rpm calls /usr/bin/pango-querymodules-64 --update-cache which does not finish

this is the relevant process tree

 2242  2266  2266  2266 pts/0     4499 Ss     507   0:00  \_ /bin/bash
 2266  4434  4434  2266 pts/0     4499 S        0   0:00  |   \_ su -
 4434  4437  4437  2266 pts/0     4499 S        0   0:00  |       \_ -bash
 4437  4499  4499  2266 pts/0     4499 S+       0   0:29  |           \_ zypper up
 4499  4520  4499  2266 pts/0     4499 S+       0   0:00  |               \_ /usr/bin/python /usr/lib/zypp/plugins/commit/snapper.py
 4499  5460  4499  2266 pts/0     4499 S+       0   0:00  |               \_ rpm --root / --dbpath /var/lib/rpm -U --percent --force --nodeps -- /var/cache/zypp/packages/Tumbleweed/x86_64/libpango-1_0-0-1.34.0-2.1.x86_64.rpm
 5460  5461  4499  2266 pts/0     4499 S+       0   0:00  |                   \_ /bin/sh /var/tmp/rpm-tmp.6cPfmm 2
 5461  5463  4499  2266 pts/0     4499 S+       0   0:00  |                       \_ /usr/bin/pango-querymodules-64 --update-cache

after 30 minutes i killed pango-querymodules-64 after this i get this additional rpm output

Additional rpm output:

(pango-querymodules-64:5463): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()

(pango-querymodules-64:5463): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(pango-querymodules-64:5463): GLib-GObject-WARNING **: cannot retrieve class for invalid (unclassed) type `<invalid>'

(pango-querymodules-64:5463): GLib-GObject-CRITICAL **: g_enum_get_value: assertion `G_IS_ENUM_CLASS (enum_class)' failed

(pango-querymodules-64:5463): Pango-WARNING **: Engine reported invalid script value 2

warning: %post(libpango-1_0-0-1.34.0-2.1.x86_64) scriptlet failed, signal 15

after this zypper continues normally, but i keep getting multiple error outputs from packets which seem to be happen allways on packets which call of gtk-update-icon-cache

var/tmp/rpm-tmp.Ykj0dd: line 11:  7002 Segmentation fault      /usr/bin/gtk-update-icon-cache --quiet --force "/usr/share/icons/${ICON_THEME}"

(gtk-update-icon-cache:7047): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()

(gtk-update-icon-cache:7047): GLib-GObject-CRITICAL **: gtype.c:2720: You forgot to call g_type_init()

(gtk-update-icon-cache:7047): GLib-GObject-CRITICAL **: g_type_interface_add_prerequisite: assertion `G_TYPE_IS_INTERFACE (interface_type)' failed

(gtk-update-icon-cache:7047): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(gtk-update-icon-cache:7047): GLib-GObject-CRITICAL **: g_type_add_interface_static: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(gtk-update-icon-cache:7047): GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed

(gtk-update-icon-cache:7047): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed
#2

seems like there is some dependency missing. after getting some of the updates which were blocked before by zypper cause of dependencies (had to resolve a few conflicts which included downgrading a few branding and gtk2-engine packages) ‘pango-querymodules-64 --update-cache’ works now.

#3

could you give more information about what you changed. I have the same errors and I think it is related to another problem I have.
Thank you

#4

Yes, I had that problem. And login to Gnome would hang.

I tried reinstalling libpango, with the same hang.

Following a suggestion on the factory mailing list:

  • I changed the priority of the tumbleweed repos to 98 (instead of 99) - including the packman tw repo;
  • I did “zypper dup”.

Then I tried again to install libpango, and it went through without a problem. Moreover, login to Gnome then worked.

#5

I had the same issue and I fixed it with a simple

sudo zypper dup --from Tumbleweed

Afterwards I had to reinstall some packages, as I recognized the kernel installation went a little bit wrong and not all sym.links were created. Therefore I reinstalled these packages to be on the safe site.