Summary: | freetype module crashes Xserver with latest libfreetype2 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Stefan Dirsch <sndirsch> | ||||||
Component: | Build/Monolithic | Assignee: | Keith Packard <keithp> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | high | CC: | basic, dparsons, eich, mfabian | ||||||
Version: | 6.8.2 | Keywords: | patch | ||||||
Hardware: | All | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Stefan Dirsch
2005-07-31 02:55:35 UTC
Created attachment 3194 [details]
SSH key for Sami Wagiaalla
After reverting some changes in libfreetype 2.1.10 (I'll attach another patch for this) the Xserver no longer crashes (also without the Xserver patch above). Since I'm quite sure, that these changes were intentional the libfreetype patch should only be used as workaround for now. The libfreetype developers didn't comment yet. :-( Created attachment 3195 [details] [review] Patch to ensure no test shares displays across tet_fork Assigning to Keith. Previously attached patches lost in bugzilla disk death. Created attachment 3516 [details] [review] libfreetype patch Created attachment 3517 [details] [review] freetype module patch - libfreetype patch by mfabian@suse.de - freetype module patch by eich@suse.de Any plans on merging these patches? Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to. Yes, I think these patches are obsoleted by current X.Org/freetype2 versions. At least SUSE no longer uses these patches for X.Org/freetype2. |
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.