[Mono-bugs] [Bug 51355][Maj] New - Latest freetype-2.1.5-0.ximian.5.1 caused desktop to fail

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by miguel@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=51355

--- shadow/51355	2004-02-01 20:08:39.000000000 -0500
+++ shadow/51355.tmp.13674	2004-02-01 20:08:39.000000000 -0500
@@ -0,0 +1,70 @@
+Bug#: 51355
+Product: Ximian Desktop 2
+Version: unspecified
+OS: unknown
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: Unknown
+Priority: Major
+Component: Miscellaneous
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: gerald@geraldthewes.org               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Latest freetype-2.1.5-0.ximian.5.1 caused desktop to fail
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+
+This morning, the Mono channel suggsted I upgrade 
+freetype on a Red Hat 8.0 system:
+
+reetype-devel-2.1.5-0.ximian.5.1
+freetype-2.1.5-0.ximian.5.1
+
+Soon afterwards I tried to start OpenOffice writer 1.0.x
+and it failed to start with an Unknown reference to
+FT_xxxxx  (I did not write the exact function down).
+
+Thinking, maybe the latest freetype upgrade had something to do,
+I closed all my apps and logged out.
+
+The gdm based login screen froze, never displaying the
+login prompt.
+
+I rebooted, and same problem. Did not find any log entry
+explaining the problem in /var/logs.
+The gdm process seemed to consumme a lot of CPU according to
+top (noticed it because my laptop fan went on).
+
+Anyway, now convinced freetype was the culprit, I removed
+the recently upgraded one and re-installed
+
+freetype-2.1.3-6.i386
+
+My desktop is working again.
+
+Look at RedCarpet again, it seems its the latest Mono release
+that caused RedCarpet to want to upgrade freetype.
+
+Something looks wrong (at least on my Red Hat 8.0 system)
+
+Steps to reproduce the problem:
+1. 
+2. 
+3. 
+
+Actual Results:
+
+
+Expected Results:
+
+
+How often does this happen? 
+
+
+Additional Information: