|
SATO GUI sometimes doesn't show icons depending upon how the system
booted first time and configured itself. This happens because some
postinsts fail while do_rootfs becasue qemu usermode is not supported
for AMD:
NOTE: The postinstall intercept hook 'update_gio_module_cache' could
not be executed due to missing qemu usermode support...
NOTE: If an image is being built, the postinstalls for the following
packages will be postponed for first boot: gconf glib-networking
libglib-2.0-0
NOTE: The postinstall intercept hook 'update_font_cache' could not
be executed due to missing qemu usermode support...
NOTE: If an image is being built, the postinstalls for the following
packages will be postponed for first boot: liberation-fonts
NOTE: The postinstall intercept hook 'update_pixbuf_cache' could not
be executed due to missing qemu usermode support...
NOTE: If an image is being built, the postinstalls for the following
packages will be postponed for first boot: libgdk-pixbuf-2.0-loader-gif
libgdk-pixbuf-2.0-loader-jpeg libgdk-pixbuf-2.0-loader-png
libgdk-pixbuf-2.0-loader-xpm
These failing postinsts are deferred for execution on first boot.
Now, the way debian package-management is implemented in yocto, it does
not handle some corner cases where these postinsts might fail even on
first boot - resulting in many pkgs being not configured:
Errors were encountered while processing:
libglib-2.0-0
glib-networking
libgdk-pixbuf-2.0-loader-jpeg
libgdk-pixbuf-2.0-loader-png
matchbox-keyboard-im
libgdk-pixbuf-2.0-loader-gif
libgdk-pixbuf-2.0-loader-xpm
gconf
As a result, sato gui fails to show icons and fonts properly...
This adds a service that attempts to reconfigure the pkgs (before the
graphics load up after basic system init on first boot) that had
failed postinsts. Service then disables itself and never runs again.
That fixes the issues with SATO GUI.
INTAMDDET-2758
Signed-off-by: Arsalan H. Awan <Arsalan_Awan@mentor.com>
|
Zhaolong Zhang
Arsalan H. Awan