Bug 2091917
| Summary: | Abrt fails with "Unable to make sense of XML-RPC response from server" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Clemens Eisserer <linuxhippy> | ||||
| Component: | abrt | Assignee: | abrt <abrt-devel-list> | ||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 37 | CC: | abrt-devel-list, abrt-sig, gui1ty, jakub, jan.public, jmilan, mgrabovs, michal.toman, msrb | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | Flags: | msrb:
needinfo?
(linuxhippy) |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-05-25 15:16:43 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Clemens Eisserer
2022-05-31 10:25:33 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
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! This might be a duplicate of 2127287. 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. 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). ;-) 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. 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. I cannot provide the requested tarball, also, I did not see this bug happening for a long time. |