Bug 793400

"Actual Results:  
/usr/lib64/pango/1.8.0/modules/pango-basic-fc.so cannot be found"

This is still a remnant from before reinstalling pango. This now obviously just fails to find the module described in the mkinitrd. I wonder, however, if this points towards the problem, i.e. that mkinitrd expects pango modules version 1.8.0, whereas pango only supplies version 1.6.0.

# pango-querymodules-64 > /etc/pango/pango64.modules
#mkinitrd

Kernel image: /boot/vmlinuz-3.6.9-14-desktop
Initrd image: /boot/initrd-3.6.9-14-desktop
KMS drivers: i915
Root device: /dev/system/root (mounted on / as ext4)
Resume device: /dev/system/swap
enabling LUKS support for /dev/disk/by-id/ata-HITACHI_HTS725050A7E630_TF1501Y9GE2YMF-part2 (cr_ata-HITACHI_HTS725050A7E630_TF1501Y9GE2YMF-part2)
Kernel Modules: thermal_sys thermal processor fan dm-mod dm-snapshot dm-crypt scsi_dh scsi_dh_rdac scsi_dh_hp_sw scsi_dh_alua scsi_dh_emc video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj linear arc4 sha256_generic cryptd aes-x86_64 ablk_helper aesni-intel ghash-clmulni-intel crc32c-intel
Features: acpi dm kms plymouth block usb lvm2 luks resume.userspace resume.kernel



Source: http://web.archiveorange.com/archive...YBJcEoCYHDyIFz

(In reply to comment #2)
> # pango-querymodules-64 > /etc/pango/pango64.modules
> #mkinitrd

mkinitrd runs without trouble afterwards, however, plymouth still doesn't show fonts (upon unlocking lvm/LUKS). However, I can't seem to find relevant error messages in either dmesg, /var/log/boot* etc.

sh-4.2$ ls -la /etc/pango/
total 32
drwxr-xr-x   2 root root  4096 Dec  9 01:45 .
drwxr-xr-x 158 root root 12288 Dec  9 14:49 ..
-rw-r--r--   1 root root  1533 Dec  9 01:45 pango64.modules
-rw-r--r--   1 root root 11446 Jul 16 16:40 pangox.aliases

sh-4.2$ ls -la /usr/lib64/pango/*
/usr/lib64/pango/1.6.0:
total 12
drwxr-xr-x 2 root root 4096 Dec  8 02:15 .
drwxr-xr-x 4 root root 4096 Dec  8 02:15 ..
-rw-r--r-- 1 root root 3512 Dec  7 15:39 modules.cache

/usr/lib64/pango/1.8.0:
total 16
drwxr-xr-x 3 root root 4096 Dec  8 02:15 .
drwxr-xr-x 4 root root 4096 Dec  8 02:15 ..
drwxr-xr-x 2 root root 4096 Dec  8 02:15 modules
-rw-r--r-- 1 root root 1532 Dec  8 02:15 modules.cache

please fix this bug pango-querymodules-64 > /etc/pango/pango64.modules

please not send you to tumbleweed packages with bugs! i want tumbleweed very stable and usability without ridiculus bugs how this.Thanks for listen me

before send to tumbleweed the packages news from factory you test well the packages and control if have bug please!

I can verify that I have the same problem. The cryptsetup prompt is in "squareeze" as I have heard it called. The plymouth graphics work perfectly. Only text rendering is affected. My particular machine wants me to run pango-query-modules, rather than the 64 bit version of the command for some reason. My architecture is 64 bit. I noticed that the most recent plymouth patch mentions something about fixing an architecture problem in it's descrition. Is it possible that this "fix" broke other packages?

This problem does not manifest on my laptop, which is locked with Kernel 3.4.* because newer kernels seem to break the performance of the Radeon X700 graphics card in that machine. Apparently this problem is limited to the newer kernels? I run kernel-default if it would make any difference. 

I would add that I find the last comments less than helpful in a bug reporting forum. Tumbleweed is "considered" stable, but "bug free" software does not exist, as there is no possible way for developers to test every possible hardware / software combinations before release. It is also impossible for them to control how many possibly incompatible repository combinations people have on their machines. 

Also, I would consider this as a minor bug rather than major, as it is fairly obvious to the computer owner what the black text box on the plymouth screen is there for. 

I very much appreciate everyone's patience and hard work.

Please do not reassign randomly. This is a bug in either the plymouth mkinitrd scripts or in pango, not in mkinitrd itself.

With the original openSUSE 12.2, we had the pango installation in /usr/lib64/pango/1.6.0, but the pango update in Tumbleweed broke this. A fix for plymouth was already submitted to Factory about 1 month ago. 

I will create a request to Tumbleweed with the proper update on the 12.2 package in order to generate issues with the /usr move that is further in Factory than in Tumbleweed.

I have just created SR#145690 to openSUSE:Tumbleweed with an updated plymouth package which would resolve this issue with pango

This is an autogenerated message for OBS integration:
This bug (793400) was mentioned in
https://build.opensuse.org/request/show/145690 Tumbleweed / plymouth

I installed what I think are the packages you mentioned. They were listed under Tumbleweed "show unstable". Here is the description from Yast:

[QUOTE]
- fix path to systemd-tty-ask-password-agent for newer systemd
- create the pid file again during boot, the existence of this is
  a condition for systemd-ask-password-plymouth.service. A proper
  fix might look different but that get's it going again.
[/QUOTE]

Everything installed without error, but still no text in Plymouth. 

My case may be unusual because the error I get is that Pango is looking for pango.modules rather than pango64.modules   I'll attach a screen shot if I'm able. 

All my packages, including the recently downloaded git packages are 64 bit. 
I can verify that /etc/pango/pango64.modules exists in both the root filesystem (which pango can't access because the luks partition hasn't been unlocked when plymouth starts), and also inside the initrd. 

Does anyone know of a reason why pango would require 32 bit files on a 64 bit system? Everything worked until about a week ago, after an update. 

Here is my setup-plymouth.sh file:
[code]
#!/bin/bash
#
#%stage: setup
#%depends: start

# We don't need to copy the binaries since boot-plymouth.sh does that for us

[ -z "$tmp_mnt" ] && exit 1

THEME=$(plymouth-set-default-theme)

PLUGIN_PATH=$(plymouth --get-splash-plugin-path)

MODULE=$(grep "ModuleName *= *" /usr/share/plymouth/themes/${THEME}/${THEME}.plymouth | sed 's/ModuleName *= *//')

if [ ! -f "$PLUGIN_PATH/${MODULE}.so" ]; then
	echo "The default plymouth plugin ($MODULE) doesn't exist." > /dev/stderr
	exit 1
fi

FILES="/usr/share/plymouth/themes/text/text.plymouth \
	/usr/share/plymouth/themes/details/details.plymouth \
	/usr/share/plymouth/plymouthd.defaults \
	/usr/share/plymouth/themes/${THEME}/* \
	/etc/plymouth/plymouthd.conf \
       /usr/share/fonts/uni/unifont.pcf.gz /etc/os-release \
       /etc/fonts/fonts.conf \
       /etc/fonts/conf.d/69-unifont.conf \
       /etc/fonts/conf.avail/69-unifont.conf "

PLUGINS="${PLUGIN_PATH}/details.so \
	${PLUGIN_PATH}/text.so \
	${PLUGIN_PATH}/label.so \
	${PLUGIN_PATH}/${MODULE}.so \
	${PLUGIN_PATH}/renderers/drm.so \
	${PLUGIN_PATH}/renderers/frame-buffer.so"

for file in $FILES; do
	install -D $file $tmp_mnt/$file
done

for plugin in $PLUGINS; do
	mkdir -p $tmp_mnt/$(dirname $plugin)
	cp_bin $plugin $tmp_mnt/$plugin
done

_libdir=`rpm --eval '%{_lib}'`
if [ "$_libdir" == "lib64" ];
  then
     _pangodir=`pango-querymodules-64 | grep ModulesPath | awk '{print $4}'`
     _pangomod="/etc/pango/pango64.modules"
     pangobasicfc="${_pangodir}/pango-basic-fc.so"
  else
     _pangodir=`pango-querymodules | grep ModulesPath | awk '{print $4}'`
     _pangomod="/etc/pango/pango.modules"
     pangobasicfc="${_pangodir}/pango-basic-fc.so"
fi
install -D ${_pangomod} $tmp_mnt/${_pangomod}
install -D ${pangobasicfc} $tmp_mnt/${pangobasicfc}
mkdir -p $tmp_mnt/var/cache/fontconfig
[/code]
and my boot-plymouth.sh file:
[code]
#!/bin/bash
#%stage: boot
#%depends: start udev kms
#%programs: /usr/bin/plymouth /usr/sbin/plymouthd

enable_plymouth=1
for o in $(cat /proc/cmdline) ; do
  case "$o" in
	shell*|plymouth.enable=0*|rd.plymouth=0*)
		enable_plymouth=0
		break
		;;
  esac
done
if [ "$enable_plymouth" = "1" ]; then
  mkdir --mode 755 /run/plymouth

  /usr/sbin/plymouthd --attach-to-session --pid-file /run/plymouth/pid

  plymouth show-splash
fi
[/code]

Created attachment 517438 [details]
Screen shot of pango error

When plymouth started and there was still no text displayed, I hit "Esc" and took this photo of my screen.

Reopened

@Ronnie,

The script shown in Comment #12 is not the standard setup-plymouth.sh script that is supplied with the package. Did you change it before or after you got the error ?

I haven't changed it, neither before nor after. I simply copied and pasted it into the post from /lib/mkinitrd/scripts. 
Is it possible that an update failed to modify or replace it? 

I checked my installation and found that for whatever reason, plymouth-scripts was not updated to your git version. Perhaps the dependencies didn't specifically require the git package?

I installed the git package of plymouth-scripts, and the differences that I see are:

/etc/fonts/conf.avail/69-unifont.conf " is removed

 then
     _pangodir=`pango-querymodules-64 | grep ModulesPath | awk '{print $4}'`
     _pangomod="/etc/pango/pango64.modules"
     pangobasicfc="${_pangodir}/pango-basic-fc.so"
  else
     _pangodir=`pango-querymodules | grep ModulesPath | awk '{print $4}'`
     _pangomod="/etc/pango/pango.modules"
     pangobasicfc="${_pangodir}/pango-basic-fc.so"

is changed to:

then
     _pangodir=`pango-querymodules-64 | grep ModulesPath | awk '{print $4}'`
     pango-querymodules-64 > $tmp_mnt/etc/pango/pango.modules
     pangobasicfc="${_pangodir}/pango-basic-fc.so"
  else
     _pangodir=`pango-querymodules | grep ModulesPath | awk '{print $4}'`
     pango-querymodules > $tmp_mnt/etc/pango/pango.modules
     pangobasicfc="${_pangodir}/pango-basic-fc.so"

install -D ${_pangomod} $tmp_mnt/${_pangomod}  is added

I'll run mkinitrd and try it. If you see any more errors, please point them out and I'll try to rectify the problem.

Hi Ronnie,

Please let me know if this resolved your issue. I will validate the dependency on the right package in the meantime before I will request the update for Tumbleweed.

Thanks

Yes, problem solved. Apparently there was just a mix-up of packages. Thanks for the help. I'll mark it as resolved / upstream. If that is not correct, please make the necessary corrections. Thanks again.

This is an autogenerated message for OBS integration:
This bug (793400) was mentioned in
https://build.opensuse.org/request/show/145764 Factory / plymouth