backtrace pgadmin3 wx3.0 assertion error when saving query to file

Hi PGadmin folks,

We've run into an issue with Pgadmin3 - version 1.20.0 (pgadmin3
1.20.0-1.pgdg70+1 amd64) on our debian wheezy (7.8) system.

Whenever we try to run query and save to file we get an (non-fatal) assert
error backtrace.

If we ignore the error the output gets stored successfully in the path
specified.

--

ASSERT INFO:

/usr/include/wx-3.0/wx/strvararg.h(456): assert "(argtype &
(wxFormatStringSpecifier<T>::value)) == argtype" failed in
wxArgNormalizer(): format specifier doesn't match argument type

BACKTRACE:

[1] wxString wxString::Format<long>(wxFormatString const&, long)

[2] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&,
wxEvent&) const

[3] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&)

[4] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)

[5] wxEvtHandler::TryHereOnly(wxEvent&)

[6] wxEvtHandler::DoTryChain(wxEvent&)

[7] wxEvtHandler::ProcessEvent(wxEvent&)

[8] wxEvtHandler::ProcessPendingEvents()

[9] wxAppConsoleBase::ProcessPendingEvents()

[10] wxApp::DoIdle()

[11] g_main_context_dispatch

[12] g_main_loop_run

[13] gtk_main

[14] wxGUIEventLoop::DoRun()

[15] wxEventLoopBase::Run()

[16] wxAppConsoleBase::MainLoop()

[17] wxEntry(int&, wchar_t**)

[18] __libc_start_main

--

The system is up to date with all packages and releases and all packages
were installed via apt.

The wxWidgets version and configure options used (if compiled from source)

ii wx-common 3.0.2-1.wheezy amd64
wxWidgets Cross-platform C++ GUI toolkit (common support files)

ii wx3.0-headers 3.0.2-1.wheezy amd64
wxWidgets Cross-platform C++ GUI toolkit (header files)

ii wx3.0-i18n 3.0.2-1.wheezy all
wxWidgets Cross-platform C++ GUI toolkit (i18n support)

The PostgreSQL version and configure options used (if compiled from source)

ii postgresql 9.4+169.pgdg70+1 all

more specifically:

ii postgresql-9.4 9.4.4-1.pgdg70+1 amd64
object-relational SQL database, version 9.4 server

I don't use this machine daily, but from what I've been told this problem
appeared in the last two months or so. Please let me know if more
information is necessary.

Thanks in advance.

Regards,

V. Schurink