Bug 824206 - Problems submitting bug reports for gnome-mplayer
Summary: Problems submitting bug reports for gnome-mplayer
Keywords:
Status: CLOSED DUPLICATE of bug 823706
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 16
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Gavin Romig-Koch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-23 01:28 UTC by Thomas Mitchell
Modified: 2012-05-28 13:01 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-28 13:01:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Thomas Mitchell 2012-05-23 01:28:07 UTC
several times in the past i have tried to report crash problems with gnome-mplayer but everytime i get

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Creating a new bug
fatal: XML-RPC(51): RPC failed at server.  There is no component named 'gnome-mplayer' in the 'Fedora' product.
(exited with 1)



when submitting bug reports.

Comment 1 Chris Lumens 2012-05-24 13:03:12 UTC
There is absolutely nothing about this that is an anaconda bug, but sure I'll spend some of my work day reassigning it.  Why not.

Comment 2 Thomas Mitchell 2012-05-25 22:53:45 UTC
Still having trouble submitting bug reports for gnome-mplayer wich are occuring regulary especially SIGSEGV signal 11 crashes. i also have been getting

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

when trying to submit other bug reports for other packages.
the above message was when i tried to submit a report for bug

"gvfsd-trash was killed by signal 11 (SIGSEGV)"

i have checked my login details for bugzilla and they are fine so that rules out a login error.

Comment 3 Jiri Moskovcak 2012-05-28 13:01:05 UTC

*** This bug has been marked as a duplicate of bug 823706 ***


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