Bug 456884 - OOo writer crash with Word document
Summary: OOo writer crash with Word document
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-07-28 13:26 UTC by Horst H. von Brand
Modified: 2008-08-03 16:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-08-03 16:34:58 UTC
Type: ---

Attachments (Terms of Use)
The crash report from oowriter (9.85 KB, application/octet-stream)
2008-07-28 13:26 UTC, Horst H. von Brand
no flags Details

Description Horst H. von Brand 2008-07-28 13:26:40 UTC
Description of problem:
I tried to edit a Word document (can't attach it, it isn't for public eyes), and
oowriter froze, had to kill it.

Version-Release number of selected component (if applicable):

How reproducible:
Dunno, happened once (I rarely use OOo).

Steps to Reproduce:
Actual results:
Crash, report attached (couldn't it write out a file instead of opening a stupid
window out of which to scrape the report?)

Expected results:

Additional info:

Comment 1 Horst H. von Brand 2008-07-28 13:26:40 UTC
Created attachment 312774 [details]
The crash report from oowriter

Comment 2 Caolan McNamara 2008-07-28 15:29:33 UTC
That's a very interesting crash in the fontconfig stuff, does it crash if you
open it again ? I'd be very interested in getting it by mail because I can't see
any way a word doc should trigger a crash in that code, I'd expect it to crash
always or never when starting up

Comment 3 Horst H. von Brand 2008-07-28 17:21:15 UTC
Nope, OOo recovered the (original?) document only, and didn't crash again.

I might have been updating stuff concurrently to the first crash...

Comment 4 Caolan McNamara 2008-07-29 08:26:17 UTC
The updating would make most sense than the .doc as a trigger, i.e.

Application::MergeSystemSettings triggered by a "setting changed" signal
delivered to OOo.

So it would be interesting if we could figure out what got upgraded/installed
while OOo was running that triggered the crash. Any chance that you remember
roughly the time that the crash occurred, (presumably close to the time you
logged this) and grep out the yum: lines from /var/log/messages around that
time, e.g. grep "yum:" /var/log/messages. And maybe we can see if it was
fontconfig or gtk upgrading (or a theme maybe) which triggers this scenario.

Comment 5 Caolan McNamara 2008-08-03 16:34:58 UTC
I'm pretty sure that it was the process of updating something like the theme, or gtk2 or cairo while OOo was running that triggered this problem rather than the specific document. Unfortunately I don't know how to reproduce it. 

With luck it was a specific rawhide-only once-off sort of problem. (fat chance)

Note You need to log in before you can comment on or make changes to this bug.