Description of problem: Happened after trying to click on server in thee after connection to the server was lost. Version-Release number of selected component: pgadmin3-1.22.1-2.fc24 Additional info: reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/pgadmin3 crash_function: ____strtol_l_internal executable: /usr/bin/pgadmin3 global_pid: 6424 kernel: 4.6.6-300.fc24.x86_64 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ____strtol_l_internal at ../stdlib/strtol_l.c:293 #1 atoi at /usr/include/stdlib.h:280 #2 pgConn::GetPort at ../pgadmin/include/db/pgConn.h:199 #3 pgConn::GetName at db/pgConn.cpp:659 #4 frmMain::EndMsg at frm/frmMain.cpp:1361 #5 pgObject::ShowTree at schema/pgObject.cpp:772 #6 frmMain::setDisplay at frm/events.cpp:531 #7 frmMain::execSelChange at frm/events.cpp:508 #8 frmMain::OnTreeSelChanged at frm/events.cpp:390 #9 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1239
Created attachment 1193345 [details] File: backtrace
Created attachment 1193346 [details] File: cgroup
Created attachment 1193347 [details] File: core_backtrace
Created attachment 1193348 [details] File: dso_list
Created attachment 1193349 [details] File: environ
Created attachment 1193350 [details] File: exploitable
Created attachment 1193351 [details] File: limits
Created attachment 1193352 [details] File: maps
Created attachment 1193353 [details] File: mountinfo
Created attachment 1193354 [details] File: namespaces
Created attachment 1193355 [details] File: open_fds
Created attachment 1193356 [details] File: proc_pid_status
Created attachment 1193357 [details] File: var_log_messages
Do you have a quick way to reproduce? I can test by suspending laptop with server open, and when I get to my destination, the connection will be lost. But that is rather slow. I have added a null ptr check at the point of failure. I can push to testing and let you try it. Otherwise, I'll try to remember to test before suspending laptop. pgadmin4 is in the works, but I'm pretty sure it won't be ready for f25.
pgadmin3-1.22.1-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-a5e9bf0d38
pgadmin3-1.22.1-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-14bb4e38b3
pgadmin3-1.22.1-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-3aa5465ba6
I fixed some more "null this" problems, and pgadmin3 can now handle losing a database connection for me anyway.
pgadmin3-1.22.1-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-14bb4e38b3
pgadmin3-1.22.1-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3aa5465ba6
pgadmin3-1.22.1-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-a5e9bf0d38
pgadmin3-1.22.1-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
pgadmin3-1.22.1-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
pgadmin3-1.22.1-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.