ReimarBauer

@matrss maybe I have the timeouts catched.

It looks like when I disable start of the mscolab server, the WMS tests succeeds ``` FAILED tests/_test_msui/test_mscolab_save_merge_points.py::Test_Save_Merge_Points::test_save_merge_points - pytestqt.exceptions.TimeoutError: waitUntil timed out in 5000 milliseconds FAILED tests/_test_msui/test_mscolab.py::Test_Mscolab::test_upload_and_fetch_profile_image - pytestqt.exceptions.TimeoutError:...

## OS14 ``` FAILED tests/_test_msui/test_topview.py::Test_TopViewWMS::test_server_getmap - pytestqt.exceptions.TimeoutError: Signal image_displayed() not emitted after 5000 ms ====== 1 failed, 564 passed, 16 skipped, 40 warnings in 716.87s (0:11:56) ====== ``` ## OS13...

We have still many ``` Original exception was: Error in sys.excepthook: ```

> We have still many > > ``` > Original exception was: > Error in sys.excepthook: > ``` that is likly because of https://github.com/Open-MSS/MSS/blob/develop/mslib/utils/qt.py#L435

The MBP can run tests, when there is no problem in

fixing the excepthook output can be done separatly. I have currently no idea how that gets in.

a bunch of changes improved the situation. Maybe redone later.

**Original comment by Joern Ungermann (Bitbucket: [joernu76](https://bitbucket.org/joernu76), GitHub: [joernu76](https://github.com/joernu76)).** ---------------------------------------- Practically, this requires quite some changes on both the frontend and the server. The OWS protocol addition of MSS does...

**Original comment by Reimar Bauer (Bitbucket: [ReimarBauer](https://bitbucket.org/ReimarBauer), GitHub: [ReimarBauer](https://github.com/ReimarBauer)).** ---------------------------------------- I see only changes on the frontend in mpl_qtwidget. I don't see changes on serverside, because by the options entries...