I upgraded to kernel-3.6.9-14-default this morning and now, Plymouth displays boxes instead of text. If I manually run mkinitrd, I get:
Kernel image: /boot/vmlinuz-3.6.9-14-default
Initrd image: /boot/initrd-3.6.9-14-default
KMS drivers: fglrx
install: cannot stat ‘/etc/pango/pango64.modules’: No such file or directory
Root device: /dev/system/root (mounted on / as reiserfs)
Resume device: /dev/system/swap
I can verify that “pango.modules” does not exist.
I found an article concerning a pango bug in SuSE studio, but running the suggested script did not fix the problem. My pango, mkinitrd, and plymouth are the newest available that I could find. I “force updated” all of them to no avail. I also uninstalled the proprietary fglrx driver, just to make sure that was not the problem.
I would appreciate any suggestions. If it should be filed as a bug, what package should I file the bug against?
I noticed some pango errors in the boot messages just after a whack of updates two days ago on 12.2 (non-tumbleweed). Plymouth stopped working for me ages ago (still not exactly certain the exact cause), so I can’t say anything else is wrong since applying those same updates. However, I haven’t had time to investigate the pango issue (other then a cursory glance at http://forums.gentoo.org/viewtopic-t-688659-highlight-32bit+pango.html which seemed similar)
I apologize for the late response. It seems that instant e-mail notifications concerning posts fail to send at times.
I run openSUSE 12.2 but upgrade from Tumbleweed when updates are released.
I saw that someone suggested that I run: pango64-query modules. I did that and the modules (64 bit) are in the correct place at /etc/pango/ (they were there before the command). One thing I notice about the error is that it complains about not finding pango.modules, as opposed to pango64.modules. I run X_64 architecture, so I’m not sure if this is a bug or if plymouth requires 32 bit packages.
I noticed that the most recent update to plymouth had something to do with an architecture correction. I reverted to an older version, but to no avail.
For now, I’ll check the bug report mentioned here and see what other information I can gather.
On 12/17/2012 04:36 PM, purevw wrote:
> I run openSUSE 12.2 but upgrade from Tumbleweed when updates are
> released.
no, you run Tumbleweed…
yes, a it is (today) based on 12.2, but it is not 12.2, it is 12.2+
you could say you run something between openSUSE 12.2 and openSUSE 12.3,
but that could whatever you wanted to pull in out of factory, whereas
Tumbleweed is not only a lot shorter to type, but it is also a specific
and known product.
when you ask for help here and do not say you are running Tumbleweed you
absolutely take the chance of getting a straight 12.2 answer which can
harm your system.
I should probably note that my plymouth and pango packages are from the “current floating update” repositories, rather than tumbleweed. Tumbleweed has some, but not all pango packages and no plymouth packages. I felt it better to get all from the same source. I use tumbleweed for kernel and KDE updates more than anything else.
The kernel-default version originally posted is outdated also. I am running kernel-default-3.6.10
I found my solution. In a Novell forum, I got help from one of the plymouth developers. I had to add: Index of /repositories/home:/oddball33:/plymouth/openSUSE_Tumbleweed to my repository list and upgrade all plymouth related packages to his versions. The solver failed to upgrade plymouth-scripts to his version, which still caused failure. When I manually added it from his repository, all was well again. He planned to modify the dependencies, so that failure should not occur again.
Once you get the correct packages, you must run mkinitrd to build everything into the initrd before you reboot.
