Bug 27032

Summary: some text has gone missing in googleearth
Product: xorg Reporter: fangxun <xunx.fang>
Component: Fonts/otherAssignee: fangxun <xunx.fang>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: medium CC: brian, jeremyhu, yselkowi
Version: gitKeywords: regression
Hardware: All   
OS: Linux (All)   
Whiteboard: 2011BRB_Reviewed
i915 platform: i915 features:
Attachments:
Description Flags
Screenshot showing the problem
none
Xorg log none

Description fangxun 2010-03-11 20:08:05 UTC
Created attachment 33974 [details]
Screenshot showing the problem

System Environment:
--------------------------
Arch:           x86_64
Platform:       G45
Mesa:           (7.8)54af54277a7a469ed2b9821ef6ed7ed464381f91
Xserver:        (master)f2eacb4646beb25d055de22868f93e6b24f229b6
Xf86_video_intel:(master)318aa9ed799197810e2039dbe3ec51559dcc888c
Libdrm:         (master)04fd3872ee8bd8d5e2c27740508c67c2d51dbc11
Kernel:  (master)60b341b778cc2929df16c0a504c91621b3c6a4ad


Bug detailed description:
-------------------------
Some text disappears in googleearth as shown in the attached screenshots. The version is 5.0.11733.9347. It happens on all platforms. This is regression. I will bisect this.

 
Reproduce steps:
----------------
1.xinit&
2.googleearth
Comment 1 fangxun 2010-03-11 20:09:08 UTC
Created attachment 33975 [details]
Xorg log
Comment 2 Eric Anholt 2010-03-12 15:17:38 UTC
It would be better if you didn't report until you've done the bisect.  It just means we have to set it to NEEDINFO and there's a chance of losing track of the bug report.
Comment 3 fangxun 2010-03-16 22:40:35 UTC
Bisect result:
56658fc06cb773ed20ef1b23a3fe918c0d3b36bb is first bad commit
commit 56658fc06cb773ed20ef1b23a3fe918c0d3b36bb
Author: Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
Date:   Thu Oct 15 22:40:02 2009 -0500

    Set default font path with fontutil 1.1 and fontpath.d

    Look for $sysconfdir/X11/fontpath.d and, if it exists, set it to the
    default font path as a catalogue: entry. Based on app/xfs commit
    c66a46e35ae40a23ad9acee838ab42300eddbd67.

    Otherwise, use the font-util 1.1 macros to determine the system
    fontrootdir and standard subdirectories, or let the user configure it
    and the subdirectories themselves.

    This adds a build-time (or at least an autoconf/autogen time) dependency
    on font-util, and changes the --with-fontdir argument to --with-fontrootdir.

    Signed-off-by: Yaakov Selkowitz <yselkowitz@users.sourceforge.net>
    Reviewed-by: Alan Coopersmith <alan.coopersmith-xsfywfwIY+M@public.gmane.org>
    Signed-off-by: Jon TURNEY <jon.turney@dronecode.org.uk>
Comment 4 Brian Rogers 2010-03-17 08:40:07 UTC
So it's a font problem, not a driver problem. Updating product/component.
Comment 5 meng 2011-03-07 04:38:56 UTC
This issue still happens with following commits:
-------------------------------------------------------------------
Libdrm:    (master)2.4.24-6-g3b04c73650b5e9bbcb602fdb8cea0b16ad82d0c0
Mesa:      (master)6538b5824e298eaebede2d9686c7607c44ab446
Xserver:                (master)xorg-server-1.10.0
Xf86_video_intel:       (master)2.14.901
Kernel:    (drm-intel-fixes) 91355834646328e7edc6bd25176ae44bcd7386c7
Comment 6 Jeremy Huddleston Sequoia 2011-10-06 10:34:01 UTC
There's not really much to go on here.  You need to provide more information.

What fontdir was being found before the change in font-util?  What fontdir is 
being found now?  What are the differences between them?  What font is Google 
Earth trying to use?
Comment 7 fangxun 2015-01-04 06:33:44 UTC
Jeremy, I know little about font,font-util and fontdir. Would you like to tell me how to get the information?

(In reply to Jeremy Huddleston from comment #6)
> There's not really much to go on here.  You need to provide more
> information.

What fontdir was being found before the change in font-util? 
> What fontdir is 
being found now?  What are the differences between them? 
> What font is Google 
Earth trying to use?
Comment 8 Adam Jackson 2018-07-30 15:31:11 UTC
Clearly this isn't being worked on and/or is no longer a problem.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.