Bug 1671499 - fatal: unable to make sense of XML-RPC response from server. XML-RPC response too large.
Summary: fatal: unable to make sense of XML-RPC response from server. XML-RPC response...
Keywords:
Status: CLOSED DUPLICATE of bug 1660227
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: 29
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-31 17:54 UTC by Brian J. Murrell
Modified: 2019-02-01 08:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 961520
Environment:
Last Closed: 2019-02-01 08:38:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Brian J. Murrell 2019-01-31 17:54:53 UTC
+++ This bug was initially created as a clone of Bug #961520 +++

Description of problem:

I encountered a crash with anaconda and automatic partitioning, i reported it.
The reporting process ended with the bug 961515 being reported and its attachments upload, or at least it seems so.


Version-Release number of selected component (if applicable):
F19b TC3 (19.24-1)

How reproducible:
once

Steps to Reproduce:
1. get a crash (bug 961515)
2. report it
  
Actual results:
unknown, got this error. the bug-report was generated.

Expected results:
no error.

Additional info:

Processing failed:
fatal: unable to make sense of XML-RPC response from server. XML-RPC response too large. Our limit... (off screen)
exited with #1.

[snip]

This is still a problem on Fedora 29 trying to report a crash with gnome-shell:

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla
fatal: Unable to make sense of XML-RPC response from server.  XML-RPC response too large.  Our limit is 4194304 characters.  We got 28196188 characters.  Use XMLRPC_TRACE_XML to see for yourself

Comment 1 Martin Kutlak 2019-02-01 08:38:39 UTC

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


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