Description of problem: I tried to et to a hostname and cancelled because I realized it was behind cloudflare so wouldn't work Version-Release number of selected component: et-6.0.7-1.fc32 Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-651f5561-639c-4941-875a-e708fcc4bd85.scope cmdline: et dfwalliance.org crash_function: el::base::utils::abort executable: /usr/bin/et journald_cursor: s=d9589a24ff2246128b1155962036c03c;i=4483ee;b=369c758289334b9d89a4e17043248635;m=ca7cdae90;t=5a7cf9dba5878;x=c04c37df9ac640c8 kernel: 5.6.15-300.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #2 el::base::utils::abort at /usr/src/debug/et-6.0.7-1.fc32.x86_64/external_imported/easyloggingpp/src/easylogging++.cc:125 #3 el::base::Writer::triggerDispatch at /usr/src/debug/et-6.0.7-1.fc32.x86_64/external_imported/easyloggingpp/src/easylogging++.cc:2649 #4 el::base::Writer::~Writer at /usr/src/debug/et-6.0.7-1.fc32.x86_64/external_imported/easyloggingpp/src/easylogging++.h:3203 #5 el::base::debug::logCrashReason at /usr/src/debug/et-6.0.7-1.fc32.x86_64/external_imported/easyloggingpp/src/easylogging++.cc:2876 #6 el::base::debug::defaultCrashHandler at /usr/src/debug/et-6.0.7-1.fc32.x86_64/external_imported/easyloggingpp/src/easylogging++.cc:2887 #8 __libc_connect at ../sysdeps/unix/sysv/linux/connect.c:26 #9 et::TcpSocketHandler::connect at /usr/src/debug/et-6.0.7-1.fc32.x86_64/src/base/TcpSocketHandler.cpp:59 #10 ping at /usr/include/c++/10/bits/shared_ptr_base.h:1321
Created attachment 1696800 [details] File: backtrace
Created attachment 1696801 [details] File: core_backtrace
Created attachment 1696802 [details] File: cpuinfo
Created attachment 1696803 [details] File: dso_list
Created attachment 1696804 [details] File: environ
Created attachment 1696805 [details] File: limits
Created attachment 1696806 [details] File: maps
Created attachment 1696807 [details] File: mountinfo
Created attachment 1696808 [details] File: open_fds
Created attachment 1696809 [details] File: proc_pid_status
FEDORA-2020-2d604920e4 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d604920e4
FEDORA-2020-f2f7086bde has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-f2f7086bde
FEDORA-2020-2d604920e4 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2d604920e4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d604920e4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-f2f7086bde has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-f2f7086bde` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-f2f7086bde See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-25acfc34a8 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-25acfc34a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-2d604920e4 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-f2f7086bde has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-25acfc34a8 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.