To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=78383
User hdu 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=78383
User pl 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=78383
User hdu 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=78383
User pl 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=78383
Issue #|78383
Summary|Can we actually print the XError on catching it
Component|gsl
Version|current
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=78383
--- Additional comments from [EMAIL PROTECTED] Wed Jun 13 12:35:11 +
2007 ---
Created an attachment (id=45874)
just print the XError if we catch one
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=78383
User pl 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=78383
--- Additional comments from [EMAIL PROTECTED] Wed Jun 13 20:06:21 +
2007 ---
It's the default for gnome applications to spit out the XError if they encounter
