Bug 2137249 - "Package 'gnome-calendar' isn't signed with proper key" -- but it should be
Summary: "Package 'gnome-calendar' isn't signed with proper key" -- but it should be
Keywords:
Status: CLOSED NOTABUG
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-10-24 08:41 UTC by Kamil Páral
Modified: 2022-10-25 14:07 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-25 14:07:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
rpm -qa (81.78 KB, text/plain)
2022-10-24 08:42 UTC, Kamil Páral
no flags Details
system journal (653.60 KB, text/plain)
2022-10-24 08:42 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2022-10-24 08:41:46 UTC
Description of problem:
ABRT ignores a gnome-calendar crash with this error:

říj 24 10:25:38 hydra abrt-server[3584]: Package 'gnome-calendar' isn't signed with proper key
říj 24 10:25:38 hydra abrt-server[3584]: 'post-create' on '/var/spool/abrt/ccpp-2022-10-24-10:25:37.801409-3484' exited with 1
říj 24 10:25:38 hydra abrt-server[3584]: Deleting problem directory '/var/spool/abrt/ccpp-2022-10-24-10:25:37.801409-3484'


However, I have a standard gnome-calendar installed from the fedora repo:

$ sudo dnf list --showduplicates gnome-calendar
Last metadata expiration check: 0:19:00 ago on Po 24. října 2022, 10:12:02.
Installed Packages
gnome-calendar.x86_64                        43.0-6.fc37                         @@commandline  
Available Packages
gnome-calendar.x86_64                        43.0-6.fc37                         fedora         
gnome-calendar.x86_64                        43.0-6.fc37                         updates-testing


Is something broken in ABRT?

Or, can this be caused by the fact that I'm running a non-official RPM for *systemd*? (In that case, the error would be very confusing).


Version-Release number of selected component (if applicable):
abrt-2.15.1-6.fc37.x86_64
gnome-calendar-43.0-6.fc37.x86_64
systemd-251.6-610.fc37.x86_64


How reproducible:
seems always

Steps to Reproduce:
1. I had to install systemd fix from bug 2135778 comment 13, to get a systemd-coredump fix
2. Make gnome-calendar crash as reported in https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/892
3. See that coredumpctl contains the crash, but ABRT doesn't. See the ABRT errors in journal.

Comment 1 Kamil Páral 2022-10-24 08:42:10 UTC
Created attachment 1919907 [details]
rpm -qa

Comment 2 Kamil Páral 2022-10-24 08:42:15 UTC
Created attachment 1919908 [details]
system journal

Comment 3 Kamil Páral 2022-10-25 12:29:38 UTC
> Or, can this be caused by the fact that I'm running a non-official RPM for *systemd*?

No, that wasn't the reason. I updated to an official build systemd-251.7-611.fc37 [1], but I still get the same error from ABRT.

[1] https://bodhi.fedoraproject.org/updates/FEDORA-2022-c72fd8b071

Comment 4 Michal Srb 2022-10-25 12:48:53 UTC
@kparal This doesn't seem to be a problem with the systemd, but rather with gnome-calendar. 

$ sudo dnf list --showduplicates gnome-calendar
Last metadata expiration check: 0:19:00 ago on Po 24. října 2022, 10:12:02.
Installed Packages
gnome-calendar.x86_64                        43.0-6.fc37                         @@commandline  

It seems like you have installed it from command line and not from official fedora repositories. Not sure where the local RPM came from, but I guess it is not signed by the distribution key?

Comment 5 Kamil Páral 2022-10-25 14:07:45 UTC
D'oh! I guess I installed it from Koji before it was submitted as an update. I reinstalled it and this problem is gone. Sorry!


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