Hi,
I just wanted to report an evolution crash report with abrt. All I get (besides a stacktrace) is "libcurl failed HTTP Post". Since I suspect that libcurl generally can handle HTTP posts, I wonder if this is some general bug in abrt?
Did anybody submit bugs successfully using this tool?
regards
Christoph
Am Dienstag, den 17.11.2009, 11:33 +0100 schrieb Christoph Höger:
Since I suspect that libcurl generally can handle HTTP posts, I wonder if this is some general bug in abrt?
It's a problem with libcurl's resolver.
Did anybody submit bugs successfully using this tool?
Yes I did. However I had to add bugzilla.redhat.com to my /etc/hosts After that it worked.
Felix
On Nov 17, 2009, at 3:33 AM, Christoph Höger wrote:
Hi,
I just wanted to report an evolution crash report with abrt. All I get (besides a stacktrace) is "libcurl failed HTTP Post". Since I suspect that libcurl generally can handle HTTP posts, I wonder if this is some general bug in abrt?
Did anybody submit bugs successfully using this tool?
I've submitted a handful of bugs.
On Tue, 2009-11-17 at 11:33 +0100, Christoph Höger wrote:
Hi,
I just wanted to report an evolution crash report with abrt. All I get (besides a stacktrace) is "libcurl failed HTTP Post".
It would help if your bug report would be more informative:
What version of abrt?
Can you give the _complete_ error message?
Since I suspect that libcurl generally can handle HTTP posts, I wonder if this is some general bug in abrt?
There was a fix to name resolution, but since you did not give abrt version number, there is no way to know whether you run abrt with that fix or not.
Did anybody submit bugs successfully using this tool?
Yes.
-- vda
On Wed, 18 Nov 2009 10:29:10 +0100, Denys wrote:
Did anybody submit bugs successfully using this tool?
Yes.
Well, with F-12 and a segfault in Claws Mail, it created a bugzilla ticket for me, but I couldn't get it to upload/attach the backtrace. Not even when retrying multiple times to send the report again with the mark in the checkbox next to the backtrace info. No error message.
With F-11, documentation on setting up abrt is either missing or placed somewhere where it's difficult to find. Simply installing the packages, the plugins/addons, the gui and starting the daemon doesn't yield anything [and I haven't search for external doc files yet].