Comment 18 for bug 1038573

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Yes, that's the expected "resolution", and what we try to do via evolution --force-shutdown but perhaps unsuccessfully.

I re-ran the upgrade on metal and managed to get the error that is the most likely cause of the unreadable text (in any application, since any already-running application runs the risk of showing unreadable dialogs):

(evolution-alarm-notify:1708): Pango-CRITICAL **: No modules found:
No builtin or dynamically loaded modules were found.
PangoFc will not work correctly.
This probably means there was an error in the creation of:
  '/etc/pango/pango.modules'
You should create this file by running:
  pango-querymodules > '/etc/pango/pango.modules'

(evolution-alarm-notify:1708): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='latin'

(evolution-alarm-notify:1708): Pango-WARNING **: failed to choose a font, expect ugly output. engine-type='PangoRenderFc', script='common'

Indeed, libpango1.0-common happily removes /etc/pango/pango.modules after the upgrade:

libpango1.0-common.postinst:# until version 1.14.5-1, we generated a /etc/pango/pango.modules
libpango1.0-common.postinst: echo "I: Purging /etc/pango/pango.modules" >&2
libpango1.0-common.postinst: rm -f /etc/pango/pango.modules