Constantly getting kernel oopses in boot log

Recently, I encountered a very long boot, and every boot since then was longer than expected. Further, during the boot process, the screen is black the whole time. I inspected journalctl -b -1 and found one error like this every second:

Jun 09 14:55:45 fedora abrt-dump-journal-oops[1580]: abrt-dump-journal-oops: Creating problem directories
Jun 09 14:55:45 fedora abrt-server[10748]: Can't load public GPG key /etc/pki/rpm-gpg/RPM-EFDCEA77.asc
Jun 09 14:55:45 fedora abrt-server[10748]: Can't find a meaningful backtrace for hashing in '.'
Jun 09 14:55:45 fedora abrt-server[10748]: Preserving oops '.' because DropNotReportableOopses is 'no'
Jun 09 14:55:45 fedora abrt-notification[10765]: System encountered a non-fatal error in ??()
Jun 09 14:55:46 fedora abrt-dump-journal-oops[1580]: Reported 1 kernel oopses to Abrt
Jun 09 14:55:47 fedora abrt-dump-journal-oops[1580]: abrt-dump-journal-oops: Found oopses: 1
Jun 09 14:55:47 fedora abrt-dump-journal-oops[1580]: abrt-dump-journal-oops: Creating problem directories
Jun 09 14:55:47 fedora abrt-server[10767]: Can't load public GPG key /etc/pki/rpm-gpg/RPM-EFDCEA77.asc
Jun 09 14:55:47 fedora abrt-server[10767]: Can't find a meaningful backtrace for hashing in '.'
Jun 09 14:55:47 fedora abrt-server[10767]: Preserving oops '.' because DropNotReportableOopses is 'no'
Jun 09 14:55:47 fedora abrt-notification[10784]: System encountered a non-fatal error in ??()

Could I ask whether any of you kind persons know how I can resolve this issue?

EDIT: running sudo plymouth-set-default-theme details -R fixed this issue.

However, the screen is still black the whole boot. Does anyone have pointers on how to troubleshoot this?

My /etc/default/grub looks like this:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init"
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

EDIT2:

reading /var/log/boot.log I find that the delay is due to

M[*     ] Job NetworkManager-wait-online.service/start running (43s / no limit)
^M[**    ] Job NetworkManager-wait-online.service/start running (44s / no limit)
^M[***   ] Job NetworkManager-wait-online.service/start running (44s / no limit)
^M[ ***  ] Job NetworkManager-wait-online.service/start running (45s / no limit)
^M[  *** ] Job NetworkManager-wait-online.service/start running (45s / no limit)
^M[   ***] Job NetworkManager-wait-online.service/start running (46s / no limit)
^M[    **] Job NetworkManager-wait-online.service/start running (46s / no limit)
^M[     *] Job NetworkManager-wait-online.service/start running (47s / no limit)
^M[    **] Job NetworkManager-wait-online.service/start running (47s / no limit)
^M[   ***] Job NetworkManager-wait-online.service/start running (48s / no limit)
^M[  *** ] Job NetworkManager-wait-online.service/start running (48s / no limit)
^M[ ***  ] Job NetworkManager-wait-online.service/start running (49s / no limit)
^M[***   ] Job NetworkManager-wait-online.service/start running (49s / no limit)
^M[**    ] Job NetworkManager-wait-online.service/start running (50s / no limit)
^M[*     ] Job NetworkManager-wait-online.service/start running (50s / no limit)
^M[**    ] Job NetworkManager-wait-online.service/start running (51s / no limit)
^M[***   ] Job NetworkManager-wait-online.service/start running (51s / no limit)
^M[ ***  ] Job NetworkManager-wait-online.service/start running (52s / no limit)
^M[  *** ] Job NetworkManager-wait-online.service/start running (52s / no limit)
^M[   ***] Job NetworkManager-wait-online.service/start running (53s / no limit)
^M[    **] Job NetworkManager-wait-online.service/start running (53s / no limit)
^M[     *] Job NetworkManager-wait-online.service/start running (54s / no limit)
^M[    **] Job NetworkManager-wait-online.service/start running (54s / no limit)
^M[   ***] Job NetworkManager-wait-online.service/start running (55s / no limit)
^M[  *** ] Job NetworkManager-wait-online.service/start running (55s / no limit)
^M[ ***  ] Job NetworkManager-wait-online.service/start running (56s / no limit)
^M[***   ] Job NetworkManager-wait-online.service/start running (56s / no limit)
^M[**    ] Job NetworkManager-wait-online.service/start running (57s / no limit)
^M[*     ] Job NetworkManager-wait-online.service/start running (57s / no limit)
^M[**    ] Job NetworkManager-wait-online.service/start running (58s / no limit)
^M[***   ] Job NetworkManager-wait-online.service/start running (58s / no limit)
^M[ ***  ] Job NetworkManager-wait-online.service/start running (59s / no limit)
^M[  *** ] Job NetworkManager-wait-online.service/start running (59s / no limit)
^M[   ***] Job NetworkManager-wait-online.service/start running (1min / no limit)
^M[    **] Job NetworkManager-wait-online.service/start running (1min / no limit)
^M[     *] Job NetworkManager-wait-online.serv…start running (1min 1s / no limit)
^M[    **] Job NetworkManager-wait-online.serv…start running (1min 1s / no limit)
^M[   ***] Job NetworkManager-wait-online.serv…start running (1min 2s / no limit)
^M[FAILED] Failed to start NetworkMan…[0m - Network Manager Wait Online.

Network manager failing

I managed to fix the issues with NetworkManager, it was due to me adding a faulty bridge device.

1 Like