To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=47285
------- Additional comments from [EMAIL PROTECTED] Mon Apr 25 07:27:02 -0700 2005 ------- > dvo: I am neither crazy, nor do I close issue just to avoid having to deal > with > them. I certainly resent if anyone suggests differently, and I have no idea > how > I might have deserved that. Closing INVALID is what you did. The issue is NOT invalid as it does not meet the criteria I quoted. > On the matter itself: There are a number of different problems cumulated in > this > issue. 1) The original report, which has a stack trace and a screenshot to > back > it up, but no information on how to reproduce it. 2) The .doc document > attached, > which reproducably crashed on .doc export. 3) And 'stackID 168334', which > lists >130 reported stack traces (including the one in this mail). If you needed more info then you should have asked. > On 3: These stack traces are wildly different problems. Apparently due to a > bug > in the stack trace report mechanism (which is itself a P2, but that doesn't > help > with the existing traces), different stack traces may be invalidly thrown > together under special circumstances. That unfortunately doesn't leave me > anything to work with. I have been told by qa that I should just close this. > As a side note, it also removes justification for the current issue priority, > since that was raised based on the notion of massive amount of stack traces. So what you are saying is that you are triaging this issue. > On 2: This is a duplicate to another issue, which is already fixed. No it is not. 47013 dealt with the MSO output filter. This is about saving in native odt format. > Which leaves 1. The problem here is that I can't find the problem with only > the > single stack trace (plus screen shot). Sometimes, a stack trace is sufficient > to > find the problem, sometimes it is not. In this case, it is not. As I have no > other information on the problem, I can't really do anything about it. The standard procedure for this case is to close the issue, as far as I know. > grsingleton, if you want to me fix the problem, you will have to help me along > and supply some additional information. Preferably some way to reproduce the > problem. As it stands now, there is not much I can do. There is no magic; I > can > only work with what I have, and right now that is plainly insufficient. Whatever. I can see that failure to save is not a priority with QA. Sobeit. > As for the issue status: To the best of my knowledge, INVALID is the suitable > status if there is insufficient information to fix an issue. If not, I'll be > perfectly happy to choose a different tag. I do not believe this could be. THat is not what is stated in the quote I provided. You may interpret as you choose. Since you haven't bothered to ask for more info and have closed the issue. I would suggest WONTFIX as a better choice under the circumstances as you have stated you cannot fix and you do not want to pursue the issue. At this point in time I will not waste my time anymore and accept that this is not a priorty and that closing the issue is more important than asking for more information. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
