Description of problem: I tried to report an issue caught by Abrt but the report failed and this was caugh immediately. Version-Release number of selected component: libreport-plugin-bugzilla-2.17.6-2.fc38 Additional info: reporter: libreport-2.17.6 kernel: 6.2.0-0.rc7.20230206gitd2d11f342b17.50.fc38.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.1-4.fc38.x86_64 comment: I tried to report an issue caught by Abrt but the report failed and this was caugh immediately. Truncated backtrace: #1 [/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py:97] get_short_backtrace #2 [/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py:269] process_section_items #3 [/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py:291] process_section_items #4 [/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py:316] generate_report #5 [/usr/bin/reporter-bugzilla:709] <module> Potential duplicate: bug {crossver_id}
Created attachment 1942861 [details] File: os_info
Created attachment 1942862 [details] File: environ
Created attachment 1942863 [details] File: mountinfo
Created attachment 1942864 [details] File: open_fds
Created attachment 1942865 [details] File: namespaces
Created attachment 1942866 [details] File: backtrace
Created attachment 1942867 [details] File: cpuinfo
This is reported in the log of the process that caused libreport to crash. Traceback (most recent call last): File "/usr/bin/reporter-bugzilla", line 709, in <module> report = pf.generate_report() ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 316, in generate_report section['items'] = self.process_section_items(section) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 291, in process_section_items child['items'] = self.process_section_items(child) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 269, in process_section_items short_bt = get_short_backtrace(self.problem_data, self.logger) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 97, in get_short_backtrace truncated = backtrace.to_short_text() ^^^^^^^^^^^^^^^^^^^^^^^^^ LookupError: Crash thread not found ('report_Bugzilla' exited with 1)
i just tried to send in a bug report but it failed reporter: libreport-2.17.6 kernel: 6.2.0-0.rc7.20230208git0983f6bf2bfc.52.fc38.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.1-4.fc38.x86_64 comment: i just tried to send in a bug report but it failed
Would it be possible to check the directory of the original problem that triggered this ABRT crash and upload "backtrace" and "core_backtrace" files from there please? You should find the files when you right click on the original problem in gnome-abrt and select "Open problem data directory". Thanks in advance ;)
i tried to report a problem reporter: libreport-2.17.6 kernel: 6.2.0-0.rc7.20230208git0983f6bf2bfc.52.fc38.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.1-4.fc38.x86_64 comment: i tried to report a problem
Created attachment 1943811 [details] Requested backtrace file The problem only has the backtrace file available. There was no core_backtrace file found in that directory.
@lruzicka Sorry, what I meant was: There was a crash in some other component. You tried to report that crash and you hit this another crash in libreport. I am interested in that very first crash (backtrace) that you were trying to report. Do you still have that one around please?
i tried to report a bug reporter: libreport-2.17.6 kernel: 6.2.0-0.rc7.20230208git0983f6bf2bfc.52.fc38.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.1-4.fc38.x86_64 comment: i tried to report a bug
(In reply to Michal Srb from comment #14) > @lruzicka > > Sorry, what I meant was: > > There was a crash in some other component. You tried to report that crash > and you hit this another crash in libreport. I am interested in that very > first crash (backtrace) that you were trying to report. Do you still have > that one around please? Whoah sorry for uploading that again and again since it always said it failed i thought it would not have posted the issue. I'm afraid i may not have the original issue but i think I've encountered the same bug again so i might have it again if it is relevant. My sincere apology but i do not know how to attach the requested files. Also later on i tried to report an issue with ibus and that also caused libreport to crash. Might that also be of relevance?
@rudikarius No worries ;) Yes, absolutely. If you still have the ibus crash, then it would work as well. If you open gnome-abrt, select ibus crash and press CTRL+O to open the directory with crash-related files. You should see "backtrace" file there. You could then either attach the whole file as an attachment here in Bugzilla: https://bugzilla.redhat.com/attachment.cgi?bugid=2168223&action=enter Or you could open the file and copy+paste what's inside into https://paste.centos.org/, press "Create" and then share the link here in a comment. Thanks!
Created attachment 1944140 [details] Crash related files The original issue causing the crash in libreport was from dleyna-renderer so here should now be all required files including the backtrace and core_backtrace from that original issue.
Running a report for ibus. reporter: libreport-2.17.6 kernel: 6.2.0-0.rc8.57.fc39.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc39.x86_64 comment: Running a report for ibus.
Ran the problem reporting for ibus. reporter: libreport-2.17.6 kernel: 6.2.0-0.rc8.20230214gitf6feea56f66d.58.fc39.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc39.x86_64 comment: Ran the problem reporting for ibus.
Indeed. I can reproduce the problem with ibus as well. Thank you everyone -- fix incoming ;)
Fix: https://github.com/abrt/satyr/pull/336
Reported a bug. reporter: libreport-2.17.6 kernel: 6.2.0-0.rc8.20230217gitec35307e18ba.60.fc39.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc39.x86_64 comment: Reported a bug.
*** Bug 2142626 has been marked as a duplicate of this bug. ***
Crash happened when I tries send another report reporter: libreport-2.17.6 kernel: 6.2.0-0.rc8.20230217gitec35307e18ba.60.fc39.x86_64+debug cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.freedesktop.GnomeAbrt-5980.scope uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.6-2.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc39.x86_64 comment: Crash happened when I tries send another report
FEDORA-2023-8d52b5e826 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8d52b5e826
FEDORA-2023-22bf3de1bc has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-22bf3de1bc
FEDORA-2023-8d52b5e826 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-22bf3de1bc has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
happens when I tries report other issue reporter: libreport-2.17.7 kernel: 6.2.0-test-a5c95ca18a98d742d0a4a04063c32556b5b66378+ cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.freedesktop.GnomeAbrt-135398.scope uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.7-1.fc39 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc39.x86_64 comment: happens when I tries report other issue
What's the version of satyr on your computer please? rpm -q satyr
❯ rpm -q satyr satyr-0.41-1.fc39.x86_64
Would you mind sharing the backtrace of the problem that you're trying to report please? In gnome-abrt, right click and select "open problem data directory". There you will find the "backtrace" file. You can upload it as an attachment here. Thanks!
Created attachment 1946225 [details] backtrace
Created attachment 1946245 [details] backtrace
Reporting. reporter: libreport-2.17.7 kernel: 6.3.0-0.rc0.20230221git89f5349e0673.1.fc39.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.7-1.fc39 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc39.x86_64 comment: Reporting.
I am having this problem with rawhide as of Feb 24 2023.
--- Running report_Bugzilla --- Checking for duplicates Traceback (most recent call last): File "/usr/bin/reporter-bugzilla", line 709, in <module> report = pf.generate_report() ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 318, in generate_report section['items'] = self.process_section_items(section) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 293, in process_section_items child['items'] = self.process_section_items(child) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 270, in process_section_items short_bt = get_short_backtrace(self.problem_data, self.logger) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 97, in get_short_backtrace truncated = backtrace.to_short_text() ^^^^^^^^^^^^^^^^^^^^^^^^^ LookupError: Crash thread not found ('report_Bugzilla' exited with 1)
A crash report failed at the stage where it files a bug in bugzilla. So I repeated the report, but this time libreport crashed. reporter: libreport-2.17.7 kernel: 6.2.0-63.fc38.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.7-1.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc38.x86_64
Reopening because the bug is still present even though my system has satyr-0.41-1.fc38.x86_64
I verified the fix that was causing the original problem. I suspect this is a different problem that simply manifest itself the same way. Would you mind sharing the "backtrace" file of the original problem that you were trying to report? In gnome-abrt, right click and select "open problem data directory". "backtrace" file should be there. Thanks!
Created attachment 1946496 [details] backtrace --- Running report_uReport --- ('report_uReport' completed successfully) --- Skipping collect_GConf --- No matching actions found for this event. --- Skipping collect_vimrc_system --- No matching actions found for this event. --- Skipping collect_vimrc_user --- No matching actions found for this event. --- Skipping collect_xsession_errors --- No matching actions found for this event. --- Running analyze_CCpp --- Generating backtrace Backtrace is generated and saved, 94628 bytes --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla --- Running report_Bugzilla --- Checking for duplicates error: rpmdbNextIterator: skipping h# 2135 Header V4 DSA/SHA1 Signature, key ID 7f8840ce: BAD Header SHA256 digest: OK Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4444 Header V4 RSA/SHA256 Signature, key ID 222d23d0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 11001 Header V4 RSA/SHA256 Signature, key ID 222d23d0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 12988 Header V4 DSA/SHA1 Signature, key ID 7fac5991: BAD Header SHA256 digest: OK Header SHA1 digest: OK Traceback (most recent call last): File "/usr/bin/reporter-bugzilla", line 709, in <module> report = pf.generate_report() ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 318, in generate_report section['items'] = self.process_section_items(section) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 293, in process_section_items child['items'] = self.process_section_items(child) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 270, in process_section_items short_bt = get_short_backtrace(self.problem_data, self.logger) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 97, in get_short_backtrace truncated = backtrace.to_short_text() ^^^^^^^^^^^^^^^^^^^^^^^^^ LookupError: Crash thread not found ('report_Bugzilla' exited with 1)
Crosspoted here: https://github.com/abrt/libreport/issues/780
Indeed. The latest backtrace from Mikhail also causes the LookupError exception. That one is from /usr/bin/Xwayland crash. It would help if other people could also upload their backtrace files so we have more data for verification. Thanks for reporting ;)
Created attachment 1946550 [details] backtrace --- Running report_uReport --- ('report_uReport' completed successfully) --- Skipping collect_GConf --- No matching actions found for this event. --- Skipping collect_vimrc_system --- No matching actions found for this event. --- Skipping collect_vimrc_user --- No matching actions found for this event. --- Skipping collect_xsession_errors --- No matching actions found for this event. --- Running analyze_CCpp --- Generating backtrace Backtrace is generated and saved, 191509 bytes --- Running analyze_BodhiUpdates --- Looking for similar problems in bugzilla abrt-action-find-bodhi-update [WARNING] Duplicate Bugzilla bug '#2156108' was found abrt-action-find-bodhi-update [ERROR] abrt-bodhi does not support product version 'Rawhide' --- Running report_Bugzilla --- Checking for duplicates error: rpmdbNextIterator: skipping h# 2135 Header V4 DSA/SHA1 Signature, key ID 7f8840ce: BAD Header SHA256 digest: OK Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 4444 Header V4 RSA/SHA256 Signature, key ID 222d23d0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 11001 Header V4 RSA/SHA256 Signature, key ID 222d23d0: BAD Header SHA1 digest: OK error: rpmdbNextIterator: skipping h# 12988 Header V4 DSA/SHA1 Signature, key ID 7fac5991: BAD Header SHA256 digest: OK Header SHA1 digest: OK Traceback (most recent call last): File "/usr/bin/reporter-bugzilla", line 709, in <module> report = pf.generate_report() ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 318, in generate_report section['items'] = self.process_section_items(section) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 293, in process_section_items child['items'] = self.process_section_items(child) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 270, in process_section_items short_bt = get_short_backtrace(self.problem_data, self.logger) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib64/python3.11/site-packages/reportclient/internal/problem_formatter.py", line 97, in get_short_backtrace truncated = backtrace.to_short_text() ^^^^^^^^^^^^^^^^^^^^^^^^^ LookupError: Crash thread not found ('report_Bugzilla' exited with 1)
Reporting a bug for trackers-miners just got libreport to crash again even with the patched version of satyr installed. backtrace: https://gist.github.com/rudi4463/99b284ea8174c41eba166644a7b2a100
If you'd be interested, here is a scratch-build with proposed fix: https://koji.fedoraproject.org/koji/taskinfo?taskID=98098173
FEDORA-2023-305eb0f3e0 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-305eb0f3e0
FEDORA-2023-dee6975299 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dee6975299
FEDORA-2023-305eb0f3e0 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-dee6975299 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dee6975299 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
When reporting an issue with clpeak, I clicked on Report button multiple times, and ended up with multiple instances of the report dialog. Maybe it matters that finding my API key took many minutes with the dialogs open... reporter: libreport-2.17.7 kernel: 6.2.0-63.fc38.x86_64 cmdline: /usr/bin/python3 /usr/bin/reporter-bugzilla -b -c /etc/libreport/plugins/bugzilla.conf -F /etc/libreport/plugins/bugzilla_format.conf -A /etc/libreport/plugins/bugzilla_formatdup.conf cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.freedesktop.problems.applet uid: 1000 reason: problem_formatter.py:97:get_short_backtrace:LookupError: Crash thread not found executable: /usr/bin/reporter-bugzilla type: Python3 package: libreport-plugin-bugzilla-2.17.7-1.fc38 runlevel: N 5 exception_type: LookupError crash_function: get_short_backtrace interpreter: python3-3.11.2-1.fc38.x86_64
Please make sure you have satyr-0.42-1.fc38 installed.
FEDORA-2023-dee6975299 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.