Bug 837768 - "fatal: (null)" when reporting error to bugzilla
"fatal: (null)" when reporting error to bugzilla
Product: Fedora
Classification: Fedora
Component: abrt (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: ---
: ---
Assigned To: Martin Milata
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-07-05 03:57 EDT by Stef Walter
Modified: 2015-02-17 09:19 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 09:19:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stef Walter 2012-07-05 03:57:06 EDT
Description of problem:

Fails to check for duplicates at bugzilla.redhat.com when filing a bug. Output is:

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
fatal: (null)
(exited with 1)

Version-Release number of selected component (if applicable):

Name        : abrt
Arch        : x86_64
Version     : 2.0.10
Release     : 4.fc18

How reproducible:

Every 3rd or 4th crash report. If a crash report fails to submit with this problem, then doing it again will cause the same problem.

Steps to Reproduce:
1. Try to file a bug using ABRT, randomly see this problem.
Actual results:

Check for duplicates fails unexpectedly.

Expected results:

Check for duplicates succeeds.

Additional info:

Is there any way to pull up additional details?
Comment 1 Jiri Moskovcak 2012-08-27 07:37:42 EDT
> Additional info:
> Is there any way to pull up additional details?

you can try to run $ abrt-gui -vvv to get more verbose output
Comment 2 Stef Walter 2012-10-23 06:09:38 EDT
Unfortunately I can no longer duplicate this, despite trying.
Comment 3 Fedora End Of Life 2013-04-03 14:11:18 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
Comment 4 Fedora End Of Life 2015-01-09 12:14:18 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.
Comment 5 Fedora End Of Life 2015-02-17 09:19:45 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.