Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Image fields in report designer badly broken | ||
---|---|---|---|
Product: | Base | Reporter: | ingenstans |
Component: | code | Assignee: | dbaneedsconfirm <needsconfirm> |
Status: | CLOSED DUPLICATE | QA Contact: | issues@dba <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues |
Version: | recent-trunk | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Windows 2000 | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
ingenstans
2007-08-10 08:47:14 UTC
reduce prio to p2 -> data lost http://qa.openoffice.org/issue_handling/basic_rules.html#one_per_issue Sorry, Andrew, there are good reasons for this policy. Bugs with different manifestations are most likely different bugs to be fixed/handled by different people, which cannot be captured by one single IssueZilla record. Also, I cannot reproduce the problems you describe with OOG680m2. I do not doubt you encounter them, but it seems you're doing something different than me. That's why I *love* bug docs - small documents showing the problem. It abstracts from all those implicit assumptions which we all usually do. So, could you please attach a document showing the problem? (I could, however, reproduce two other problems when I tried reproducing this, both seemingly related to image fields. Going to name the numbers here once I submitted them.) new issues encountered: issue 80924, issue 80925 Frank, I'm sorry if I was angry when I filed this report. We're all indebted for your efforts over the years. I would file a bugdoc but the original database was quite large, and in any case corrupted. I had been trying to make a database for my wife's embroideries, with thumbnails of quite detailed jpegs of her work. The attempt to print out a report came after she had a quite unrelated crash and lost almost everything in the file. I couldn't file a bug report about that one because I wasn't there at the time, and her account wasn't coherent. In any case, her HSQL file was truncated from several megabytes to 500k and only the backups were recoverable. These were what wouldn't print. I will look to see if any have been preserved ... OK. I have a 15MB odb file on the backup server. What should I do with it? It's too big to attach here, but I can put it somewhere you can reach by FTP if you would like. I have since switched the backend to MySQL, which ought to be more stable, but she won't touch it, believing now that nothing will work reliably... I didn't read you as being angry, no problem here. I just pointed out that the bug report was not ... ideal for further processing. If you can put up the file somewhere, and send me the link by mail, I could have a look. We still need to strip it down so we have a version to be attached here (QA plus other involved engineers need to reproduce the issue, too), but I'm willing to invest some time into this. If necessary, we should replace the content with dummy data before doing so, of course. as agreed with Frank *** This issue has been marked as a duplicate of 81126 *** as agreed with Frank close duplicate |