Bug 146908

Summary: Unable to start X session after the update of fontconfig
Product: [openSUSE] SUSE Linux 10.1 Reporter: Petr Mladek <pmladek>
Component: X11 ApplicationsAssignee: Mike Fabian <mfabian>
Status: RESOLVED FIXED QA Contact: Stefan Dirsch <sndirsch>
Severity: Major    
Priority: P5 - None    
Version: Beta 2   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: The problematic font cache that causes the crash
A log with the error messages. It is generated using the tool "script".

Description Petr Mladek 2006-01-31 11:12:09 UTC
I am running 10.1-beta2 on x86_64. I updated fontconfig from STABLE to investigate the bug #146181. This morning, I was unable to start any xsession until I removed the old ~/.fonts.cache-2.
 
The new fontconfig has this latest changelog entry:
--- cut ---
$# rpm -q -changelog fontconfig-2.3.93.20060127-2 | head -n5
* Fri Jan 27 2006 - mfabian@suse.de
- check return values of FcCacheReadString () to fix endless loop.
  See:
  http://lists.freedesktop.org/archives/fontconfig/2006-January/001959.html
--- cut ---

I'll attach the problematic .fonts.cache-2 and the error log. I am able to reproduce the crash after I put the broken .fonts.cache-2 back.

I am not sure if it helps. Note that the problematic .fonts.cache-2 might be generated using 32-bit fontconfig because I started 32-bit OOo on the system. And, yes, I updated the 32-bit fontconfig as well:

--- cut ---
$# rpm -qa | grep fontconfig
fontconfig-devel-2.3.93.20060127-2
fontconfig-devel-32bit-2.3.93.20060127-2
fontconfig-32bit-2.3.93.20060127-2
fontconfig-2.3.93.20060127-2
--- cut ---

Also note that I had to restart the X-session because my system freezed when a colleague tested a game on my system. So, the .fonts.cache-2 migh be broken because of this.
Comment 1 Petr Mladek 2006-01-31 11:14:17 UTC
Created attachment 65829 [details]
The problematic font cache that causes the crash
Comment 2 Petr Mladek 2006-01-31 11:17:40 UTC
Created attachment 65830 [details]
A log with the error messages. It is generated using the tool "script".

I get a similar crash also when I try to start KDE.
Comment 3 Mike Fabian 2006-01-31 19:25:39 UTC
I think this is already fixed by the checkin with the following
changelog:
-------------------------------------------------------------------
Mon Jan 30 20:47:05 CET 2006 - mfabian@suse.de

- destroy-completely-broken-cache-files-in-home-directory.patch:
  when no string at all can be read from a ~/.fonts.cache-2 file
  or if such a file does not start with FC_GLOBAL_MAGIC_COOKIE,
  something is badly wrong and the file should be destroyed.

-------------------------------------------------------------------
Comment 4 Mike Fabian 2006-01-31 19:27:14 UTC
Your ~/.fonts.cache-2 file didn't start with the string "GLOBAL"
(which is the value of FC_GLOBAL_MAGIC_COOKIE).

Fontconfig now deletes ~/.fonts.cache-2 files which do not
start with "GLOBAL".
Comment 5 Mike Fabian 2006-01-31 19:34:31 UTC
You an try the mbuild job magellan-mfabian-85.

Closing as FIXED.