To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102735
------- Additional comments from h...@openoffice.org Tue Jul 7 08:48:02 +0000 2009 ------- @gantim: Thank you very much for the reportids! Since the POS-tooling doesn't work today I analyzed them manually. It looks like a specific NSMenu event is not handled at all. The crash-reporter doesn't send not enough data to identify which message that would be. There is a trick to get this info though: If an application was started from the command line OSX usually prints the details about a failed message to stderr. So here is the next quest for all users that are affected by the problem: - open the Terminal application - go into the OpenOffice.org.app directory (use the "cd" command to change the directory) - type "./Contents/MacOS/soffice.bin -writer" into the terminal then press enter - make it crash with typing => in the terminal there should be some details about the crash, please provide them here --------------------------------------------------------------------- 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
