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’
Pango-WARNING **: failed to choose a font, expect ugly output. engine-type=‘PangoRenderFc’, script=‘latin’
Pango-WARNING **: failed to choose a font, expect ugly output. engine-type=‘PangoRenderFc’, script=‘common’
how to fix this please, i want not have at boot after later menu grub2 when all services loading systemd start:
welcome to OpenSuse 12.2 (Mantis) x86:x64
lsb_service ok
udev ok
the message warning pango is up before welcome to opensuse Mantis
I posted about the same problem in the general install-boot-login forum. I have not found a solution yet, but it might be prudent to follow that forum also:
The bug should not have prevented booting as far as I know, unless we are talking about two different problems. It only affected text displays in the plymouth bootsplash. My problem was that the text prompt for entering my luks password on the plymouth screen was nothing but small boxes and no text. That is what pango was complaining about when it said that output would be ugly. It was not able to find the modules with the preconfigured fonts. pango is a tool used for displaying text, so pango errors should not prevent booting. I use grub rather than grub2, but I would think that either would be fine.
install: cannot stat ‘/etc/pango/pango64.modules’: No such file or directory
In a terminal as root or su, run: pango-querymodules-64 >/etc/pango/pango64.modules and then run mkinitrd again. That error should disappear.
Cant find any pango64 packages so im guessing this is the cause of the problem as to how to fix it im thinking rolling the kernel version back?
There is no pango64 package. If you have all of the “libpango” packages, then the solver would have chosen the 64 bit versions. It turns out that the problem was not with pango anyway.
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. If your machine(s) still fail to boot, then there is apparently a second problem.
In a terminal as root or su, run: pango-querymodules-64 >/etc/pango/pango64.modules and then run mkinitrd again.
Except i didnt run mkinitrd the first time so i tried doing that and no luck.
My system wasnt booting i was getting past the black splash screen with the white opensuse logo (complete with white dots floating around it since this problem started) to the Pango error then it stopped. I could only get the system working using failsafe mode.
Luckily i could still log in via ssh to do all the repo stuff and run commands so that is how i am running these.
So i tried your next suggestion followed by a zypper dup ( adding the oddball repo):
#zypper dupWarning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
The following packages are going to be upgraded:
cups cups-client cups-libs cups-libs-32bit kernel-desktop libply2 libply-boot-client2 libply-splash-core2 libply-splash-graphics2 plymouth plymouth-plugin-label
plymouth-plugin-script plymouth-scripts
The following packages are going to change vendor:
kernel-desktop openSUSE -> obs://build.opensuse.org/openSUSE:Tumbleweed
libply2 openSUSE -> obs://build.opensuse.org/home:oddball33
libply-boot-client2 openSUSE -> obs://build.opensuse.org/home:oddball33
libply-splash-core2 openSUSE -> obs://build.opensuse.org/home:oddball33
libply-splash-graphics2 openSUSE -> obs://build.opensuse.org/home:oddball33
plymouth openSUSE -> obs://build.opensuse.org/home:oddball33
plymouth-plugin-label openSUSE -> obs://build.opensuse.org/home:oddball33
plymouth-plugin-script openSUSE -> obs://build.opensuse.org/home:oddball33
plymouth-scripts openSUSE -> obs://build.opensuse.org/home:oddball33
13 packages to upgrade, 9 to change vendor.
After a reboot i am now presented with a differant error:
libpng error: Not a PNG file
systemd-fsck[523]: /dev/sda3: clean, 7187/8331264 file, 4673749/33303296 blocks
so now i need to try and work out what happened and fix this however thanks for the link and information in your post it has been very useful.
Well i cant this working again tried everything i can find, think its time to wipe and start again :’(
Seems like such a shame as ive zypper dup’d this box for as long as i can remember through the last 5 versions of opensuse i think and this is the first time it has stopped working.
I can boot into failsafe and use the system with really bad graphical effects but maybe its just time to start again.
The only other thing i can think of trying is adding the factory repositories and seeing if that can fix it but i think with the time available i might just start again.
Hope other people experiencing this problem have better luck.
Em 18-12-2012 12:56, purevw escreveu:
>
> [snip]
>
> 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’
> (http://tinyurl.com/brxghm6) 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. If your machine(s) still
> fail to boot, then there is apparently a second problem.
>
>
This solved my longtime problem with pango. Thank you for the suggestion.
Actually, I would use “zypper refresh” followed by “zypper up”. “Zypper dup” is a complete distribution upgrade, as in 12.1 to 12.2. That’s the reason for the warning about repositories. You shouldn’t mix repositories of different distros. If you run Tumbleweed, all or most of the 12.2 repositories should be disable, or you could end up with a mess of mis-matched packages. Good instructions concerning Tumbleweed can be found here: Portal:Tumbleweed - openSUSE Wiki
I only ever had one set of repositories active, since tumbleweed came about it was those repositories only, in trying to fix this i added the oddball one then disabled them all and swapped to factory still the same issue.
As i was unable to fix it or find a solution i’m going back to 12.2 fresh install for now as i actually need the machine to be working again and have no more time to mess around with this problem, i was hoping to find the cause as this could effect other users if not fixed.