Created attachment 1761485 [details] gnome-abrt screenshot Description of problem: gnome-abrt shows multiple crashes attributed to the kernel-core, which are not kernel crashes; and also not enough information is being collected to file a bug report either using the retrace server or locally processed; suspiciously systemd-coredump is also not collecting a coredump. Version-Release number of selected component (if applicable): gnome-abrt-1.3.6-2.fc34.x86_64 abrt-2.14.5-2.fc34.x86_64 How reproducible: Often, looks like most every reboot *if* there's something crashing in user space like gnome-shell, gnome-session, uresourced, etc. Steps to Reproduce: I'm not sure what the pattern is, because not every user space crash results in being wrongly assigned to kernel-core. Actual results: User space crash is assigned to kernel. Crash coredump is not collected. Expected results: User space crash should not be assigned to the kernel; and a coredump should be collected so it can be submitted to the retrace server or locally processed. Additional info:
Created attachment 1761486 [details] abrt.tar.gz tar of /var/spool/abrt/ drwxr-x---. 1 root abrt 760 Mar 7 22:42 ccpp-2021-03-05-12:55:30.94591-2002 drwxr-xr-x. 1 chris abrt 562 Mar 7 22:42 oops-2021-03-05-12:54:53-1745-0 drwxr-xr-x. 1 root abrt 562 Mar 7 22:42 oops-2021-03-05-12:55:30-1745-0 drwxr-xr-x. 1 chris abrt 562 Mar 7 22:42 oops-2021-03-05-13:00:13-1437-0 drwxr-xr-x. 1 root abrt 562 Mar 7 22:42 oops-2021-03-07-21:39:41-3148-0 drwxr-xr-x. 1 chris abrt 562 Mar 7 22:42 oops-2021-03-07-21:43:47-990-0 drwxr-xr-x. 1 chris abrt 562 Mar 7 22:42 oops-2021-03-07-22:20:25-1488-0
https://github.com/abrt/gnome-abrt/issues/295
Proposed as a Blocker for 34-beta by Fedora user chrismurphy using the blocker tracking app because: "Bug hinders execution of required Beta test plans or dramatically reduces test coverage" We've been saying abrt bugs aren't blockers if bugs can be processed either with the retrace server, or locally. In this case the crashes can't be processed at all. However, systemd-coredump also isn't collecting a coredump for these, and I'm not sure why. So this might be a conditional blocker. Proposing for discussion and visibility.
Created attachment 1761487 [details] journal.log 06bcc1f Excerpt [ 2111.147791] kernel: traps: gnome-shell[5449] general protection fault ip:7fdc44bbb81a sp:7ffd777b1df0 error:0 in libgobject-2.0.so.0.6705.0[7fdc44b93000+31000] [ 2110.993509] systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-coredump/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). [ 2110.993682] systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction for systemd-coredump/start is destructive (umount.target has 'start' job queued, but 'stop' is included in transaction). [ 2110.993884] systemd[1]: systemd-coredump.socket: Failed with result 'resources'. [ 2110.993992] systemd-coredump[6709]: Failed to send coredump datagram: Broken pipe [ 2111.018246] polkitd[994]: Unregistered Authentication Agent for unix-session:8 (system bus name :1.119, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) [ 2111.020158] systemd[2446]: org.gnome.Shell: Main process exited, code=dumped, status=11/SEGV [ 2111.032397] systemd[2446]: org.gnome.Shell: Failed with result 'core-dump'. [ 2111.032926] systemd[2446]: Stopped GNOME Shell on Wayland. [ 2111.033132] systemd[2446]: org.gnome.Shell: Triggering OnFailure= dependencies. [ 2111.033456] systemd[2446]: Requested transaction contradicts existing jobs: Transaction for org.gnome.Shell-disable-extensions.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction). [ 2111.033568] systemd[2446]: org.gnome.Shell: Failed to enqueue OnFailure= job, ignoring: Transaction for org.gnome.Shell-disable-extensions.service/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
Created attachment 1761489 [details] journal.log 3c8b85f Excerpt: [ 359.909386] kernel: traps: uresourced[3375] general protection fault ip:7f5ae294f517 sp:7ffe8fcca490 error:0 in libglib-2.0.so.0.6704.0[7f5ae2948000+8d000] [ 360.086402] systemd[1]: Started Show Plymouth Reboot Screen. [ 360.086603] audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 360.122750] systemd[1]: Requested transaction contradicts existing jobs: Transaction for systemd-coredump/start is destructive (systemd-reboot.service has 'start' job queued, but 'stop' is included in transaction). [ 360.122964] systemd[1]: systemd-coredump.socket: Failed to queue service startup job (Maybe the service file is missing or not a non-template unit?): Transaction for systemd-coredump/start is destructive (systemd-reboot.service has 'start' job queued, but 'stop' is included in transaction). [ 360.123043] systemd[1]: systemd-coredump.socket: Failed with result 'resources'. [ 360.124542] systemd[1]: uresourced.service: Main process exited, code=dumped, status=11/SEGV [ 360.124651] systemd[1]: uresourced.service: Failed with result 'core-dump'. [ 360.124977] systemd[1]: Stopped User resource assignment daemon.
I don't know if abrt needs systemd to collect the coredump in the first place; if so it might be a systemd or service unit bug? Possibly another factor, looks like these crashes all happen during reboot.
I think this is happening because the kernel is catching a GPF happening in some other process. Both the examples you posted are in parts of glib2, so may well be the same or related.
See also: https://github.com/abrt/abrt/issues/1386
Discussed during the 2021-03-08 blocker review meeting: [0] The decision to classify this bug as a "RejectedBlocker (Beta)" was made as this is definitely a case abrt should handle better, but it's not new and we know the bounds of it quite well (GPFs); it's not broad enough to block a release. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-08/f34-blocker-review.2021-03-08-17.00.txt
Actual upstream bug is https://github.com/abrt/abrt/issues/1386
*** Bug 1937439 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.