To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=56877
Issue #:|56877
Summary:|buggy fonts cause segfault - crash
Component:|Word processor
Version:|OOo 2.0
Platform:|PC
URL:|
OS/Version:|Linux
Status:|UNCONFIRMED
Status whiteboard:|
Keywords:|
Resolution:|
Issue type:|DEFECT
Priority:|P2
Subcomponent:|code
Assigned to:|mru
Reported by:|racran
------- Additional comments from [EMAIL PROTECTED] Fri Oct 28 07:08:10 -0700
2005 -------
Actually, this causes the whole suite to crash/not start, but I suspect it's
related to #54214. (and since there's no nice place to report general crashes,
here it lands) The Font Trouble Shooting Guide asked that an issue be filed
whenever bad fonts are found.
Symptom: OO 2.0 crashes on startup with a doc recovery screen and an
'unexpected error'. Splash progress bar gets to about 1/4.
Note this happened on the few 680m builds I tried - though at the time I was
probably running an earlier X (4.3 probably). I'm filing this under 2.0, as I
don't recall which m680 releases I tried. (Seems I do recall 680m87, and
something in the m70's range)
I'll attach one of the buggy fonts below.
Note, I do not use xfontserver - though I did at one time, briefly. From the
output below one might think that fontserver is active, but I assure you it's
not, now it's just in X's font path.
The buggy fonts probably came from corel's wp 2k for linux, wp personal for
linux (the freebie), off the net somewhere, some maybe even from a windows box..
this box has been around a long time and I have no real idea where exactly
they're from.
Used a different method to find the buggy fonts than in the font trouble guide:
Might be worth including in docs, as it's perhaps more to the point.
strace /opt/openoffice.org2.0/program/soffice.bin -norestore 2>&1 | grep
-B 50 "egment"
access("/usr/X11R6/lib/X11/fonts/server/Zhu601bi.pfb", R_OK) = 0
access("/usr/X11R6/lib/X11/fonts/server/Zhu601bi.afm", R_OK) = 0
open("/usr/X11R6/lib/X11/fonts/server/Zhu601bi.afm", O_RDONLY) = 19
fstat(19, {st_mode=S_IFREG|0444, st_size=28844, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x41aa9000
read(19, "StartFontMetrics 3.0\r\nComment Co"..., 4096) = 4096
read(19, "d ; B 19 -14 605 750 ;\r\nC 101 ; "..., 4096) = 4096
read(19, "; WX 597 ; N Atilde ; B -77 -2 5"..., 4096) = 4096
read(19, "llemotleft -21\r\nKPX A guilsingll"..., 4096) = 4096
read(19, "PX W A -38\r\nKPX W quoteleft 29\r\n"..., 4096) = 4096
read(19, "llemotleft Lslash -28\r\nKPX guill"..., 4096) = 4096
read(19, "mandbls quotedblright -61\r\nKPX g"..., 4096) = 4096
read(19, "\nCC yacute 2 ; PCC y 0 0 ; PCC a"..., 4096) = 172
close(19) = 0
munmap(0x41aa9000, 4096) = 0
--- SIGSEGV (Segmentation fault) ---
The fix: remove the font:
mkdir /root/fonts-argh
mv /usr/X11R6/lib/X11/fonts/server/Zhu* /root/fonts-argh
Then ran mkfontscale and mkfontdir again on that directory (don't think
mkfontscale is necessary, but it can't hurt AFAIK)
mkfontscale usr/X11R6/lib/X11/fonts/server
mkfontdir usr/X11R6/lib/X11/fonts/server
OO started up just fine after this, fonts listed fine in the dropdown.
To reproduce: probably just invert the fix with the attached font..
About this box:
2.4.31
X 4.4.0
libc 2.2.4
gcc 3.3.1 (minorly hacked) used to build tons of stuff from tarball/srpm,
particularly libraries (i.e. glibc) that OO may depend on.. this box does all
the builds for the lan, and other than the kernel, is reasonably up to date.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
