Bug 2091917 - Abrt fails with "Unable to make sense of XML-RPC response from server" [NEEDINFO]
Summary: Abrt fails with "Unable to make sense of XML-RPC response from server"
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-31 10:25 UTC by Clemens Eisserer
Modified: 2023-06-30 10:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 15:16:43 UTC
Type: Bug
Embargoed:
msrb: needinfo? (linuxhippy)


Attachments (Terms of Use)
abrt directories related to the failed bug report of Xorg (12.18 MB, application/x-bzip)
2023-05-14 22:28 UTC, Sandro
no flags Details

Description Clemens Eisserer 2022-05-31 10:25:33 UTC
Description of problem:

When trying to report bugs/crashes via GnomeAbrt it fails submitting the report with the following error: 

fatal: Unable to make sense of XML-RPC response from server.  62-byte supposed UTF-8 string is not valid UTF-8.  UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff0).  Use XMLRPC_TRACE_XML to see for yourself
(»report_Bugzilla« abgebrochen durch 1)


Version-Release number of selected component (if applicable):
abrt-2.15.1-1.fc36.x86_64

How reproducible:
everytime

Steps to Reproduce:
1. report a crash
2. provide the details
3. XML-RPC error


Additional info:

--- Running report_uReport ---
(»report_uReport« erfolgreich abgeschlossen)

--- Überspringe collect_GConf ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Überspringe collect_vimrc_system ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Überspringe collect_vimrc_user ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Überspringe collect_xsession_errors ---
Für diesen Event wurden keine passenden Aktionen gefunden.

--- Running analyze_CCpp ---
Sind Sie damit einverstanden, den Speicherauszug hochzuladen? Möglicherweise sind vertrauliche Daten darin enthalten. Falls Sie mit »Nein« bestätigen, wird eine lokale Stapelüberwachung erstellt - und damit unter Umständen ein große Datenmenge heruntergeladen. 'YES'
Servereinstellungen werden abgefragt
Archiv wird zur Übertragung vorbereitet
124,9 KiB hochladen
Übertragung war erfolgreich
Retrace job #911318165 started
Analyzing crash data
.............
Generating backtrace
.............
Finishing task

--- Running analyze_BodhiUpdates ---
Auf Bugzilla nach ähnlichen Fehlern suchen
abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#2065813' was found
Searching for updates
No updates for this package found

--- Running report_Bugzilla ---
Überprüfen auf Duplikate
fatal: Unable to make sense of XML-RPC response from server.  62-byte supposed UTF-8 string is not valid UTF-8.  UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff0).  Use XMLRPC_TRACE_XML to see for yourself
(»report_Bugzilla« abgebrochen durch 1)

Comment 1 Jan Vlug 2022-11-15 15:18:40 UTC
Confirming that I got this error today as well:

--- Running report_Bugzilla ---
Checking for duplicates
fatal: Unable to make sense of XML-RPC response from server.  1252-byte supposed UTF-8 string is not valid UTF-8.  UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff0).  Use XMLRPC_TRACE_XML to see for yourself
('report_Bugzilla' exited with 1)

On Fedora 36, fully up to date: abrt.x86_64 2.15.1-1.fc36

Comment 2 Michal Srb 2022-11-19 10:42:49 UTC
Thanks for the bug report. Would it be possible to create a tarball from the problem directory (/var/spool/abrt/<problem-that-you-are-trying-to-report> and upload it here? Please inspect the directory first and make sure that are no sensitive data. You can also make the attachment private so it is not visible for everyone. Thanks!

Comment 3 Michal Srb 2022-11-19 10:45:27 UTC
This might be a duplicate of 2127287.

Comment 4 Ben Cotton 2023-04-25 17:18:18 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Sandro 2023-05-14 22:28:17 UTC
Created attachment 1964530 [details]
abrt directories related to the failed bug report of Xorg

Very similar error message. For me this happens almost always when reporting a crash of xorg-X11-server-Xorg (Xorg killed by SIGABRT). I attached the directories from /var/spool/abrt 

--- Running report_Bugzilla ---
Checking for duplicates
fatal: Unable to make sense of XML-RPC response from server.  398-byte supposed UTF-8 string is not valid UTF-8.  UTF-8 string contains a character not in the Basic Multilingual Plane (first byte 0xfffffff0).  Use XMLRPC_TRACE_XML to see for yourself
('report_Bugzilla' exited with 1)

(In reply to Michal Srb from comment #3)
> This might be a duplicate of 2127287.

Rather the other way around since this bug report came first (2091917 < 2127287). ;-)

Comment 6 Ludek Smid 2023-05-25 15:13:49 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Ludek Smid 2023-05-25 15:16:43 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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

Comment 8 Jan Vlug 2023-06-30 10:00:14 UTC
I cannot provide the requested tarball, also, I did not see this bug happening for a long time.


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