Description of problem: gnome-abrt cannot report problems when behind a proxy without a direct access to Internet. Version-Release number of selected component (if applicable): gnome-abrt-0.3.7-3.fc20.x86_64 abrt-addon-ccpp-2.2.2-1.fc20.x86_64 abrt-retrace-client-2.2.2-1.fc20.x86_64 abrt-addon-python3-2.2.2-1.fc20.x86_64 abrt-addon-vmcore-2.2.2-1.fc20.x86_64 abrt-libs-2.2.2-1.fc20.x86_64 abrt-desktop-2.2.2-1.fc20.x86_64 abrt-plugin-bodhi-2.2.2-1.fc20.x86_64 abrt-2.2.2-1.fc20.x86_64 abrt-dbus-2.2.2-1.fc20.x86_64 abrt-gui-2.2.2-1.fc20.x86_64 abrt-addon-xorg-2.2.2-1.fc20.x86_64 abrt-gui-libs-2.2.2-1.fc20.x86_64 abrt-addon-python-2.2.2-1.fc20.x86_64 abrt-addon-kerneloops-2.2.2-1.fc20.x86_64 abrt-addon-pstoreoops-2.2.2-1.fc20.x86_64 abrt-java-connector-1.0.10-1.fc20.x86_64 abrt-python-2.2.2-1.fc20.x86_64 abrt-python3-2.2.2-1.fc20.x86_64 How reproducible: easily Steps to Reproduce: 1. Network without a direct access to Internet. DNS does not resolve Internet-wide address. Internet access is available via HTTP proxy 2. ABRT has some crash to report 3. run gnome-abrt 4. choose a crash to report 5. press "report" button Actual results: A messagebox "An error occured while connecting to 'retrace.fedoraproject.org'" appears Log says "Can't resolve host name 'retrace.fedoraproject.org'. NSS error -5973." Expected results: Abrt connects to required services via HTTP proxy and is able to report crash. Additional info:
Thanks for the report! How do you configure proxy settings?
Hello. I've tried manual proxy configuration for HTTP and HTTPS protocols in Gnome Settings. I've also tried automatic proxy configuration (with and without URL to .pac file). My .bashrc also has http_proxy and https_proxy exports, but I don't think they are used by gnome-abrt. In our office DNS server resolves only internal hosts, so to access public Internet applications have to connect via a proxy embedding a target hostname into a request.
ABRT makes HTTP requests using curl and thus http_proxy and https_proxy are used by gnome-abrt. Please verify that your .bashrc exports work correctly. If I put an invalid value to https_proxy, gnome-abrt fails to report: $ https_proxy=invalid-https-proxy $ export https_proxy $ gnome-abrt -> Report ... Failed to upload uReport to the server 'https://retrace.fedoraproject.org/faf' with curl: Could not resolve proxy: invalid-https-proxy ...
First of all, gnome-abrt should use Gnome settings. When I start gnome-abrt from console: [cqx874@cqx874-tmp ~]$ export http_proxy=http://wwwgate0.mot.com:1080/ [cqx874@cqx874-tmp ~]$ export https_proxy=http://wwwgate0.mot.com:1080/ [cqx874@cqx874-tmp ~]$ env | grep proxy http_proxy=http://wwwgate0.mot.com:1080/ https_proxy=http://wwwgate0.mot.com:1080/ no_proxy=127.0.0.1,localhost,*.lync.com [cqx874@cqx874-tmp ~]$ gnome-abrt and press "Report" button I have this error: -- Running report_uReport --- ('report_uReport' completed successfully) --- Running analyze_CCpp --- Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data). 'YES' Querying server settings An error occurred while connecting to 'retrace.fedoraproject.org' Can't resolve host name 'retrace.fedoraproject.org'. NSS error -5973. Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace). 'NO' ('analyze_CCpp' exited with 1) Please note, that whatever program tried to connect to retrace.fedoraproject.org, it failed to _resolve_ the address, because our DNS server won't resolve public hostnames. But when I use wget to download some page via proxy, I get: [cqx874@cqx874-tmp ~]$ wget https://retrace.fedoraproject.org/faf/summary/ -O tmp/output.html --2014-11-05 16:44:28-- https://retrace.fedoraproject.org/faf/summary/ Resolving wwwgate0.mot.com (wwwgate0.mot.com)... 140.101.21.130 Connecting to wwwgate0.mot.com (wwwgate0.mot.com)|140.101.21.130|:1080... connected. Proxy request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘tmp/output.html’ [ <=> ] 248 903 130KB/s in 1,9s 2014-11-05 16:44:33 (130 KB/s) - ‘tmp/output.html’ saved [248903] Because wget does not resolve retrace.fedoraproject.org to connect, it resolves my proxy name to IP only.
(In reply to Pavel Malyshev from comment #4) > First of all, gnome-abrt should use Gnome settings. I agree and I'll add support for GNOME proxy settings soon. > > and press "Report" button I have this error: > -- Running report_uReport --- > ('report_uReport' completed successfully) > https_proxy was used here. 'report_uReport' communicates with 'retrace.fedoraproject.org' too. > --- Running analyze_CCpp --- > Ok to upload core dump? (It may contain sensitive data). If your answer is > 'No', a stack trace will be generated locally. (It may download a huge > amount of data). 'YES' > Querying server settings > An error occurred while connecting to 'retrace.fedoraproject.org' > Can't resolve host name 'retrace.fedoraproject.org'. NSS error -5973. > Do you want to generate a stack trace locally? (It may download a huge > amount of data but reporting can't continue without stack trace). 'NO' > ('analyze_CCpp' exited with 1) > 'analyze_CCpp' is the only piece of ABRT which does not use curl and HTTP proxy support needs to be added to this tool. Do you think you could file a new bug against abrt component for this issue?
Sure! Submitted: https://bugzilla.redhat.com/show_bug.cgi?id=1161138 Thanks!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Upstream issue: https://github.com/abrt/gnome-abrt/issues/173
This bug is currently reported against a Fedora version which is already unsuported. I am changing the version to '27', the latest supported release. Please check whether this bug is still an issue on the '27' release. If you find this bug not being applicable on this release, please close it.
Seems to be an issue with Fedora 28 as well.
Running gnome-abrt from command line I get this when trying to report a bug ``` WARNING:root:Can't initialize gnome-abrt's DBus services: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (gnome-abrt:13020): GLib-GIO-CRITICAL **: 14:12:24.051: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed Failed to open connection to D-Bus session bus: The connection is closed (abrt:13025): GLib-GIO-CRITICAL **: 14:12:30.784: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed ``` And looking at network traffic I see it trying to connect to the server directly on port 443
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I think that it is still worth to work on so I'm changing the Fedora version to Rawhide.
Changed in commit https://github.com/abrt/abrt/commit/f1d99e1d7593ab49147268b383cc82acbb0d94c1
abrt-2.11.1-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b74a80dd86
If it's a bug in abrt rather than gnome-abrt, shouldn't we change the Component field of this bug report?
abrt-2.11.1-2.fc29 has been pushed to the Fedora 29 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-2019-b74a80dd86
abrt-2.11.1-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.