To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=113898
------- Additional comments from sbo...@openoffice.org Tue Aug 24 12:07:27 +0000 2010 ------- I just wanted to comment that investigating further I've found that on GNOME preferences I'd support for assistive technologies active, even when I didn't use any of them, but deactivating them took away the crashes even on the not patched builds. Perhaps that's why no one could reproduce this problem, but again, it didn't happen with 3.2.1, so something must have changed on code related to accessibility features and its integration with GNOME. Checking for that NULL pointer solved the crash problem, but I'm wondering if that pointer it's not supposed to be NULL when you really have activated accessibility tools, and it being NULL on 3.3.0 means that the support for accessibility features in OOo 3.3 is broken and will not work at all. Is out there anybody that can check accessibility features on the OOO330 branch? I have no idea how are they supposed to work, to try myself. --------------------------------------------------------------------- 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...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
