Every boot, I get these errors in my log... Jun 01 13:10:46 n7 abrt-dump-journal-oops[1055]: abrt-dump-journal-oops: Found oopses: 2 Jun 01 13:10:46 n7 abrt-dump-journal-oops[1055]: abrt-dump-journal-oops: Creating problem directories Jun 01 13:10:46 n7 abrt-server[1237]: Can't find kernel package corresponding to '5.15.41-gentoo' Jun 01 13:10:46 n7 abrt-server[1237]: 'post-create' on '/var/spool/abrt/oops-2022-06-01-13:10:46-1055-0' exited with 1 Jun 01 13:10:46 n7 abrt-server[1237]: Deleting problem directory '/var/spool/abrt/oops-2022-06-01-13:10:46-1055-0' Jun 01 13:10:47 n7 abrt-server[1321]: Can't find kernel package corresponding to '5.15.41-gentoo' Jun 01 13:10:47 n7 abrt-server[1321]: 'post-create' on '/var/spool/abrt/oops-2022-06-01-13:10:46-1055-1' exited with 1 Jun 01 13:10:47 n7 abrt-server[1321]: Deleting problem directory '/var/spool/abrt/oops-2022-06-01-13:10:46-1055-1' Seems to make abrt not usable. Reproducible: Always
I couldn't find any workaround for this in OpenMandriva or PLD Linux (that are also packaging this for their distributions). I would try to report it to upstream as abrt should handle better when the package is not found: https://github.com/abrt/abrt/issues If they refuse... well... I start to think that abrt will be treecleaned sooner or later as it would be too much focused on Fedora... even if it would be sad as there is no alternative for the other distributions :/
I was going through the abrt code, and I see what you mean. For one, it references rpm quite a bit. In fact, I wouldn't be surprised if really what this means is that it can't find an 'rpm' kernel package.
Yep, but we already build it with the rpm support disabled... I would expect all that parts to be skipped then 🤔
That's a fair point, but I'm not sure what 'package' they'd be referring to then. That said, if you look at https://github.com/abrt/abrt/blob/master/abrt.spec, it would seem that, in reality, only OpenSUSE and Fedora are supported by upstream as they have specific directives for the two of them.
ONLY might not have been the right word, but you get what I mean.
The other option would be to drop the *oops* helpers and keep the rest... but I would at least try to report to upstream and do that if they ignore the issue
Yeah, that's an option, for sure. Although I would hate to see that happen. Maybe I can dig deeper into it this weekend or something?
That would be really welcomed and appreciated as I don't think I will be able to review it :/ Thanks a lot
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8aedf444c3a5e2b943dcc82699121afe6334ed58 commit 8aedf444c3a5e2b943dcc82699121afe6334ed58 Author: Jakov Smolić <jsmolic@gentoo.org> AuthorDate: 2022-11-01 04:35:11 +0000 Commit: Jakov Smolić <jsmolic@gentoo.org> CommitDate: 2022-11-01 04:35:11 +0000 app-admin/abrt: treeclean Closes: https://bugs.gentoo.org/849095 Closes: https://bugs.gentoo.org/849305 Closes: https://bugs.gentoo.org/849092 Signed-off-by: Jakov Smolić <jsmolic@gentoo.org> app-admin/abrt/Manifest | 2 - app-admin/abrt/abrt-2.15.0.ebuild | 127 ------------------------------- app-admin/abrt/abrt-2.15.1.ebuild | 127 ------------------------------- app-admin/abrt/files/abrt-2.0.12-r1-conf | 27 ------- app-admin/abrt/files/abrt-2.0.12-r1-init | 76 ------------------ app-admin/abrt/metadata.xml | 11 --- profiles/features/prefix/package.mask | 1 - profiles/package.mask | 5 -- 8 files changed, 376 deletions(-)
