Error starting VisIt

[angelv]

Hi,

when starting VisIt (​https://wci.llnl.gov/codes/visit/), it just hangs and no windows appear.

A workaround is to start visit with the option -nowindowmetrics, which according to visit documentation "Prevents X11 from grabbing and moving a test widget used in calculating window borders. This option can be useful if VisIt hangs when displaying to an Apple X-server.". With this option, VisIt? starts under Xpra with no problems.

Ángel de Vicente

[Antoine Martin]

Thanks for reporting this, probably the same issue as #40 and #53

(may close this bug as duplicate once confirmed)

[ahuillet]

Problem confirmed with r696 and VisIt? 2.3.2 and 2.4.2.

[Antoine Martin]

let's try to get this one fixed for 0.2 too

[ahuillet]

WaitForWindowManagerToMoveWindow(testWindow);

This is the function it hangs on.

The function is:

// ****************************************************************************
//  Method:  WaitForWindowManagerToMoveWindow
//
//  Purpose:
//    Waits for the window manager to move a window
//
//  Arguments:
//    win        the window
//
//  Programmer:  Jeremy Meredith
//  Creation:    September 13, 2001
//
//  Modifications:
//    Jeremy Meredith, Fri Sep 28 14:19:19 PDT 2001
//    Removed ProcessEvents.  It sometimes caused a crash on some platforms.
//
// ****************************************************************************
void
WindowMetrics::WaitForWindowManagerToMoveWindow(QWidget *win)
{
    XFlush(QX11Info::display());
    XEvent ev;
    while (!XCheckTypedWindowEvent(QX11Info::display(), win->winId(),
                                   ConfigureNotify, &ev))
    {
        // just keep polling
    } 
    qApp->x11ProcessEvent(&ev);
}

[Antoine Martin]

It's quite possible that we are missing a ConfigureNotify somewhere, can you find in the code above what is supposed to trigger this event?
Is it just the creation of the window, or maybe a _NET_MOVERESIZE_WINDOW event? or something else?

[Antoine Martin]

ahuillet, can you post the details of what it does prior to this call?
I can't find any traces of it, it must do some X11 call prior to that if it expects us to map the window. A simple X11/C based test case would be even better.

[Antoine Martin]

Can I close this?

[ahuillet]

Please don't. Even though I didn't properly follow up on your requests the error is still there and we shouldn't forget about it.

[Antoine Martin]

13 months without activity - closing.

Likely to be solved by #212