Issue 101735

Summary: OOo 3.1.0 Calc (Stable) Error Copying Custom Styles Between Templates
Product: Calc Reporter: robelsman <robelsman>
Component: programmingAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, rb.henschel, tj
Version: OOo 3.1 RC2Keywords: oooqa
Target Milestone: ---   
Hardware: Other   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
Default spreadsheet template with custom templates to copy elsewhere
Calc spreadsheet template as target for copying custom templates none

Description robelsman 2009-05-10 21:33:42 UTC
Error Copying Styles from Template to Template in Calc Template Management 
Dialog Box

Platform:  Intel Pentium 4, 256MB RAM

OpenOffice Version:  3.1.0 (English language install without JRE) Stable 
Release, downloaded 8 May 2009

Operating System:  Windows XP SP3

JAVA Runtime Environment :  Sun Microsystems, Inc. 6.0.130


I am encountering a repeatable error in OpenOffice 3.1.0 Calc (stable English 
version) while trying to copy styles from one template to another in the 
Template Management box.  While the copying operation seems to go successfully 
at first, closing the Template Management box causes the display of an error 
message, described below.  Closing that error message box opens another error 
message box, described below, and a program crash.


Preliminary:  Import two spreadsheet templates, one of which has custom styles 
defined. Exit program.

1. Start the OpenOffice program.
2. At the "Welcome to" screen, choose Templates.
3. Select Organize... at the bottom of the dialog box.
4. In the Template Management dialog box, select Templates in both the left and 
the right selection boxes.
5. Double-click the template with custom styles in the left box.
6. Double-click Styles in the left box.
7. Double-click the other template in the right box.
8. Double-click Styles in the right box.
9. Hold down the Ctrl key and use the mouse to copy all the custom styles from 
the left box to the right box.
10. Click the Close button
11. Note the error message:  "Error saving template Checking Account Register".
12. Click OK.
13. Note the error message from Microsoft Visual C++ Runtime Library:  "Runtime 
Error!  Program:  C:\Program Files\ 3\program\soffice.bin.  This 
application has requested the Runtime to terminate it in an unusual way.  
Please contact the application's support team for more information."
14. Note the program closes without opening the crash report 
Comment 1 robelsman 2009-05-10 21:49:32 UTC
Created attachment 62149 [details]
Default spreadsheet template with custom templates to copy elsewhere
Comment 2 robelsman 2009-05-10 21:51:13 UTC
Created attachment 62150 [details]
Calc spreadsheet template as target for copying custom templates
Comment 3 Regina Henschel 2009-05-11 21:44:08 UTC
I get the same crash. It makes no difference whether you use 'Template' in the
welcome screen or in the file menu.
Comment 4 T. J. Frazier 2009-09-04 00:19:12 UTC
(3.1.1, WVHP) Also happens in Writer, trying to copy (Ctrl+drag) a custom
character style from a document to its template, in the File > Templates >
Organize... dialog. Copying one style is sufficient to show the error, on Close.
Suggest component change.--/tj/
Comment 5 T. J. Frazier 2009-09-05 00:53:04 UTC
Further testing in Writer shows that styles can be copied from document to
document, and from template to document, without problems. Only copying a style
into a template (from a document or another template) causes the crash.

A quick way to make a simple template, for testing, is to save a blank document
as a template: Quickstarter > Text Document, or File > New > Text Document,
followed by File > Templates > Save... which leads to a SaveAs-type dialog.

*Crash*: This bug produces a 100% reproducible crash, but no error report. The
recovery process recovers everything but the theoretically-modified template.
The dialog says to press Next for the Error Report, but pressing Next goes
straight to the recovered document. If this is a problem, rather than policy, I
will file another issue on that, if you want.

I suggest Framework component, and keyword "crash".