To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=112746
                 Issue #|112746
                 Summary|framework/qa/unoapi fwk.ModuleManager failure (X11 Bad
                        |Window)
               Component|framework
                 Version|current
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|code
             Assigned to|mba
             Reported by|sb





------- Additional comments from s...@openoffice.org Mon Jun 28 09:11:36 +0000 
2010 -------
At least
<http://termite.services.openoffice.org/buildbot/builders/RedFlag/builds/411> on
CWS sb127, effectively being latest re/DEV300_next towards DEV300_m84 with
subsequenttests enabled, repeatedly fails on that buildbot in
framework/qa/unoapi with the below log (and soffice apparently terminates upon
the X11 error, so all following tests in framework/qa/unoapi stumble over
DisposedExceptions):

---8<---
[...]
5: LOG> statusChanged(): PASSED.OK
5: ***** State for
fwk.MacrosMenuController::com::sun::star::frame::XStatusListener ******
5: Whole interface: PASSED.OK
5:
***************************************************************************************
5: ***** State for fwk.MacrosMenuController ******
5: Whole component: PASSED.OK
5: ***********************************************
5: Creating: fwk.ModuleManager
5: LOG> Log started 25.05.2010 - 20:57:38
5: LOG> creating a text document
5: LOG> creating a web document
5: LOG> creating a global document
5: The program 'soffice' received an X Window System error.
5: This probably reflects a bug in the program.
5: The error was 'BadWindow (invalid Window parameter)'.
5:   (Details: serial 169 error_code 3 request_code 2 minor_code 0)
5:   (Note to programmers: normally, X errors are reported asynchronously;
5:    that is, you will receive the error a while after causing it.
5:    To debug your program, run it with the --sync command line
5:    option to change this behavior. You can then get a meaningful
5:    backtrace from your debugger if you break on the gdk_x_error() function.)
5: Exception while getting Environment java.io.EOFException
5: com.sun.star.lang.DisposedException: java.io.EOFException
5:      at
com.sun.star.lib.uno.bridges.java_remote.java_remote_bridge$MessageDispatcher.run(java_remote_bridge.java:158)
[...]
---8<---

---------------------------------------------------------------------
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

Reply via email to