Comment # 1 on bug 1044747 from Dirk Weber

I think I found the cause: the functionality seems not to be implemented yet
and the missing UTMInputHandler causes the crash:

in the Tumbleweed source marble-15.08.3/src/lib/marble/LatLonEdit.cpp:
...
void LatLonEdit::setNotation(GeoDataCoordinates::Notation notation)
{
    delete d->m_inputHandler;
    d->m_inputHandler = 0;

    switch (notation) {
    case GeoDataCoordinates::Decimal:
        d->m_inputHandler = new DecimalInputHandler(d);
        break;
    case GeoDataCoordinates::DMS:
        d->m_inputHandler = new DMSInputHandler(d);
        break;
    case GeoDataCoordinates::DM:
        d->m_inputHandler = new DMInputHandler(d);
        break;
    case GeoDataCoordinates::UTM:
        /** @todo implement */
        break;
    case GeoDataCoordinates::Astro:
        /** @todo implement */
        break;
    }

    d->m_notation = notation;
    d->m_inputHandler->setupUi();
    d->m_inputHandler->setupMinMax(d->m_dimension);
    d->m_inputHandler->setValue(d->m_value);
}
...
in the current marble git repository the only difference is that a Q_ASSERT at
the end of LatLonEdit::setNotation() checks whether d->m_inputHandler is
assigned a value != 0:

...
    if (d->m_inputHandler) {
        d->m_notation = notation;
        d->m_inputHandler->setupUi();
        d->m_inputHandler->setupMinMax(d->m_dimension);
        d->m_inputHandler->setValue(d->m_value);
    } else {
        Q_ASSERT(false && "Support for this notation has not been implemented
yet");
    }
}
...