Bug 34007 - googleearth crashes the X server again
Summary: googleearth crashes the X server again
Status: RESOLVED DUPLICATE of bug 31501
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xorg (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-07 13:49 UTC by aceman
Modified: 2011-04-30 05:03 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Log with crash. (32.90 KB, text/plain)
2011-02-07 13:49 UTC, aceman 		no flags Details
View All

Description aceman 2011-02-07 13:49:05 UTC 
Created attachment 43048 [details]
Log with crash.

Starting googleearth 5.2.1.1588 always crashes the X server. This started to happen when I upgraded from X.org 1.7.7 to 1.9.3 (slackware). It did not happen in 1.7.7. However, it also happened in older versions like 1.4. This is a regression.

I am using kernel 2.6.36.3, ati-driver 6.14.0, mesa 7.10 on Radeon HD 4350 (RV710).

The X.org.log with the crash is attached.
Comment 1 Michel Dänzer 2011-02-09 01:44:55 UTC 
Looks like this could be a duplicate of bug 32462.
Comment 2 aceman 2011-02-09 11:00:13 UTC 
I am not sure. I do not have reference to doListFontsWithInfo in my backtrace. And I am using 32bit system not 64bit. However, if bug 31501 is related, I also use the font server (xfs).
Comment 3 aceman 2011-02-19 08:25:00 UTC 
This does happen even when Option "NoAccel" "true" is set in xorg.conf.
Comment 4 aceman 2011-04-13 11:31:53 UTC 
After removing xfs from the FontPath, the X server no longer crashes and googleearth work fine.

This is similar to bug 36060. What can be done to fix the underlying problem?
Comment 5 aceman 2011-04-30 05:03:34 UTC 
Marking as dupe for now.

*** This bug has been marked as a duplicate of bug 31501 ***

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.