Description of problem: When editing files with gvim, Pango-WARNING messages are output in the shell that spawned gvim. [jwboyer@vader ubi-utils]$ gvim README (gvim:17352): Pango-WARNING **: Error loading GPOS table 4097 Version-Release number of selected component (if applicable): vim-X11-7.0.035-1.1 How reproducible: Always Steps to Reproduce: 1. Open file for editing from shell 2. Scroll file 3. Actual results: Pango warnings are spit out Expected results: No pango warnings Additional info: This system has the dejavu-fonts installed.
So I'm still seeing this problem. I'm also seeing it on FC5 with dejavu-fonts installed.
This looks more like pango has a problem with dajavu fonts
(In reply to comment #2) > This looks more like pango has a problem with dajavu fonts Could be. Though gvim is the only application I've come across that spits out this warning. Now on my FC5 machine with dejavu installed: [jwboyer@zod ~]$ rpm -qa | grep dejavu dejavu-fonts-2.8.0-1.fc5 dejavu-fonts-makedefault-2.8.0-1.fc5 dejavu-fonts-experimental-2.8.0-1.fc5 [jwboyer@zod ~]$ rpm -q vim-X11 vim-X11-7.0.042-0.fc5 I still get: [jwboyer@zod ~]$ gvim cheat (gvim:16502): Pango-WARNING **: Error loading GPOS table 4097 [jwboyer@zod ~]$ (gvim:16503): Pango-WARNING **: Error loading GPOS table 4097
Oh, and: [jwboyer@zod ~]$ rpm -q pango pango-1.12.3-1
I no longer have this problem with rawhide, so it's purely a FC-5 issue now.
It's a totally harmless warning with DejavVu Sans Mono fonts. It's fixed in Pango 1.14. I've fixed that in pango-1-12 branch upstream already, but have not made a release. This can be closed as rawhide for example.
(In reply to comment #6) > It's a totally harmless warning with DejavVu Sans Mono fonts. It's fixed in > Pango 1.14. I've fixed that in pango-1-12 branch upstream already, but have not > made a release. This can be closed as rawhide for example. Would it be possible to make a release? I understand it's harmless, however it's really really annoying from a user standpoint. Or if you cannot make a release, could you provide the fix in the FC-5 branch in CVS so users can compile their own updated RPM?
I'll make a release one of these days... Leaving open.
*** Bug 207979 has been marked as a duplicate of this bug. ***