Description of problem: Whatever application I try to crash, ABRT ignores that crash and says "Package isn't signed with proper key". But I see those packages as signed. Something is broken here. For example: Sep 19 16:00:06 chronos abrt-server[7916]: Package 'gnome-calculator' isn't signed with proper key Sep 19 16:00:06 chronos abrt-server[7916]: 'post-create' on '/var/spool/abrt/ccpp-2025-09-19-16:00:06.766796-7841' exited with 1 Sep 19 16:00:06 chronos abrt-server[7916]: Deleting problem directory '/var/spool/abrt/ccpp-2025-09-19-16:00:06.766796-7841' and Sep 19 16:01:35 chronos abrt-server[8135]: Package 'htop' isn't signed with proper key Sep 19 16:01:35 chronos abrt-server[8135]: 'post-create' on '/var/spool/abrt/ccpp-2025-09-19-16:01:35.17416-8070' exited with 1 Sep 19 16:01:35 chronos abrt-server[8135]: Deleting problem directory '/var/spool/abrt/ccpp-2025-09-19-16:01:35.17416-8070' But: $ rpm -qi gnome-calculator Name : gnome-calculator Version : 49.0 Release : 1.fc43 Architecture: x86_64 Install Date: Wed 17 Sep 2025 09:07:49 AM CEST Group : Unspecified Size : 8078248 License : GPL-3.0-or-later AND CC-BY-SA-3.0 AND CC0-1.0 Signature : RSA/SHA256, Mon 15 Sep 2025 12:26:57 PM CEST, Key ID 829b606631645531 Source RPM : gnome-calculator-49.0-1.fc43.src.rpm Build Date : Mon 15 Sep 2025 12:14:16 PM CEST Build Host : buildhw-x86-09.rdu3.fedoraproject.org Packager : Fedora Project Vendor : Fedora Project URL : https://wiki.gnome.org/Apps/Calculator Bug URL : https://bugz.fedoraproject.org/gnome-calculator Summary : A desktop calculator Description : gnome-calculator is a powerful graphical calculator with financial, logical and scientific modes. It uses a multiple precision package to do its arithmetic to give a high degree of accuracy. and $ rpm -qi htop Name : htop Version : 3.4.1 Release : 2.fc43 Architecture: x86_64 Install Date: Fri 12 Sep 2025 10:22:38 AM CEST Group : Unspecified Size : 467297 License : GPL-2.0-or-later Signature : RSA/SHA256, Fri 25 Jul 2025 06:54:32 AM CEST, Key ID 829b606631645531 Source RPM : htop-3.4.1-2.fc43.src.rpm Build Date : Thu 24 Jul 2025 07:10:22 PM CEST Build Host : buildvm-x86-25.rdu3.fedoraproject.org Packager : Fedora Project Vendor : Fedora Project URL : https://htop.dev/ Bug URL : https://bugz.fedoraproject.org/htop Summary : Interactive process viewer Description : htop is an interactive text-mode process viewer for Linux, similar to top(1). I wonder if the problem can be somehow connected to the extra whitespace in the Signature field of rpm output? If Fedora 42, there's no extra whitespace. Version-Release number of selected component (if applicable): abrt-2.17.6-9.fc43.x86_64 rpm-5.99.91-5.fc43.x86_64 gnome-calculator-49.0-1.fc43.x86_64 htop-3.4.1-2.fc43.x86_64 How reproducible: always Steps to Reproduce: 1. run /usr/bin/gnome-calculator 2. pkill -SEGV -fx /usr/bin/gnome-calculator 3. see journalctl output for abrt messages
Proposing as F43 Final blocker due to: https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria#Default_application_functionality
+9(!!!) in https://pagure.io/fedora-qa/blocker-review/issue/1940 , marking accepted blocker.
Quite surprisingly today after system resume, I saw an abrt notification about glycin-svg crashing, so ABRT does process *some* crashes. But I have no idea what is different about this one: $ journalctl -b --since today | grep -E '(glycin|coredump|abrt)' Journal file /var/log/journal/9d9ff0a900544acb8693309e0fc63f3b/system~ is truncated, ignoring file. Sep 23 09:04:16 chronos audit[36255]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=36255 comm="blocking-41" exe="/usr/libexec/glycin-loaders/2+/glycin-svg" sig=31 res=1 Sep 23 09:04:16 chronos kernel: audit: type=1701 audit(1758611056.501:1051): auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=36255 comm="blocking-41" exe="/usr/libexec/glycin-loaders/2+/glycin-svg" sig=31 res=1 Sep 23 09:04:16 chronos systemd-coredump[94172]: Process 36255 (glycin-svg) of user 1000 terminated abnormally with signal 31/SYS, processing... Sep 23 09:04:16 chronos systemd[1]: Started systemd-coredump - Process Core Dump (PID 94172/UID 0). Sep 23 09:04:16 chronos audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@5-16385-94172_94173-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 23 09:04:16 chronos abrt-dump-journal-core[1729]: Failed to obtain all required information from journald Sep 23 09:04:16 chronos systemd-coredump[94184]: Process 36255 (glycin-svg) of user 1000 dumped core. Module /usr/libexec/glycin-loaders/2+/glycin-svg from rpm glycin-2.0.0-1.fc43.x86_64 ... Sep 23 09:04:16 chronos systemd[1]: systemd-coredump: Deactivated successfully. Sep 23 09:04:16 chronos audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@5-16385-94172_94173-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 23 09:04:16 chronos kernel: audit: type=1131 audit(1758611056.904:1064): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@5-16385-94172_94173-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 23 09:04:17 chronos abrt-server[94290]: Unsupported container technology Sep 23 09:04:17 chronos abrt-server[94290]: Lock file '.lock' was locked by process 94293, but it crashed? Sep 23 09:04:21 chronos abrt-server[94290]: Journal file /var/log/journal/9d9ff0a900544acb8693309e0fc63f3b/system~ is truncated, ignoring file. Sep 23 09:04:21 chronos abrt-applet[2656]: g_app_info_should_show: assertion 'G_IS_APP_INFO (appinfo)' failed Sep 23 09:04:21 chronos abrt-notification[94457]: Process 36255 (glycin-svg) crashed in syscall() However, the crash reporting failed with: > Backtrace is generated and saved, 23146 bytes > Can't open file 'component' for reading: No such file or directory So perhaps the fact that the 'component' (package name?) was missing might've been the reason why this crash was initially processed.
The problem is likely caused by the changes in rpm: https://github.com/rpm-software-management/rpm/issues/2403
FEDORA-2025-f7aec17ba3 (abrt-2.17.7-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-f7aec17ba3
FEDORA-2025-f7aec17ba3 (abrt-2.17.7-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-ed458ffe66 (abrt-2.17.7-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed458ffe66
FEDORA-2025-ed458ffe66 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-ed458ffe66` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed458ffe66 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-ed458ffe66 (abrt-2.17.7-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
(In reply to Fedora Update System from comment #9) > FEDORA-2025-ed458ffe66 (abrt-2.17.7-1.fc43) has been pushed to the Fedora 43 > stable repository. > If problem still persists, please make note of it in this bug report. Crash detection and reporting works now, thanks