To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=99029
------- Additional comments from nicklevin...@openoffice.org Fri Feb 13 08:06:20 +0000 2009 ------- I've emailed a file for testing (to cmc & cc: mru). It's not confidential, but, until or unless we understand more, it should be considered dangerous to existing data, so I emailed it compressed and I don't want to put it on an open site. However, you may post it if you conclude that it's not a danger or that only reasonably cautious people who will take responsibility for fixing their own computer systems will handle it. Here's a replication procedure: 1. Decompress the file. (I believe it's safe while in its compressed state.) 2. Open in gedit or, probably, any text editor. 3. Open Calc and Writer in OOo 3.0.1. 4. Select all in the gedit file. 5. Copy from gedit. 6. Paste into Writer. 7. Page up to the top and then back down. Within a handful of seconds, the screen will freeze. Page Up, Page Down, and scrolling will fail. The insertion point won't move. No menus will open except the service menu in the title bar. If you use the service menu to move the file to another workspace, it will move but only the titlebar will be visible. Alt-F4 will produce a Force Quit alert. If you okay Force Quit, all of OOo will disappear. Two new facts: --- The encoding, according to an email service, is base64. --- This long string is not identical to the string that was originally discussed, yet the effect is the same. That it's not the same string is due to my having made a new (nonconfidential) spreadsheet (available on request), with different content, and emailing it to an address that wouldn't likely exist, causing an immediate bounce, in which the bounce message included this very long string evidently generated from the spreadsheet file. --- I was able to restart OOo during the same Linux login session, which is an improvement from the experience in my first post above. Thus, something in what I did the first time had the additional effect of preventing program restart without an intervening login, but maybe solving the narrower problem will moot the restart one. Thanks again. -- Nick --------------------------------------------------------------------- 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: issues-unsubscr...@framework.openoffice.org For additional commands, e-mail: issues-h...@framework.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
