To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
User hi changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
User hi changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
--- Additional comments from [EMAIL PROTECTED] Tue Feb 21 11:22:07 -0800
2006 ---
For some reason no one can reproduce the bug any more. Weird
-
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
User hi changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
--- Additional comments from [EMAIL PROTECTED] Thu Feb 16 06:37:00 -0800
2006 ---
It in On Gentoo Linux using the OpenOffice-bin. I tested it with a lexmark T620
and
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
--- Additional comments from [EMAIL PROTECTED] Thu Feb 16 08:21:24 -0800
2006 ---
Is it possible to use the crash reporter to send us the stack of the crash?
The cra
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
User mru changed the following:
What|Old value |New value
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=62111
User tesseract changed the following:
What|Old value |New value
==