Recent Fedora installation issues

It seems like getting Fedora going on my trusty but old computer is getting harder these days.

Getting Fedora 39 installed turnedout to be a bit of a chore. After getting Fedora 40 installed in a VM after a bit of wrangling, I thought I’d try the F39-F40 upgrade on the computer. The upgrade worked fine on the laptop, so I thought maybe the desktop would handle it ok.

Nope, not so much. While the upgrade itself went smoothly, all I got when I rebooted was a blank screen with a flashing cursor in the corner. Fortunately Ctrl-Alt-F2 got me to a console login prompt, so the system was running to some extent.

Logging in to check things out showed a ton of

traps: drkonqi-coredum[1922] trap invalid opcode ip:7f9a6270ea9c sp:7ffc3e6b9dd8 error:0 in[7f9a626b0000+3e7000]

messages in the dmesg output. Looked like whatever was going on kept crashing, generating coredumps and restarting ad-nauseum.

In /var/log/messages, there were a bunch of

systemd-coredump[11667]: Process 11641 (drkonqi-coredum) of user 0 dumped core.
Module from rpm libxcrypt-4.4.36-5.fc40.x86_64
Module from rpm util-linux-2.40-0.9.rc1.fc40.x86_64
Module from rpm cyrus-sasl-2.1.28-19.fc40.x86_64
Module from rpm libevent-2.1.12-12.fc40.x86_64
Module from rpm libunistring-1.1-7.fc40.x86_64
Module from rpm util-linux-2.40-0.9.rc1.fc40.x86_64
Module from rpm glib2-2.80.0-1.fc40.x86_64
Module from rpm openssl-3.2.1-2.fc40.x86_64
Module from rpm libpsl-0.21.5-3.fc40.x86_64
Module from rpm libssh-0.10.6-5.fc40.x86_64
Module from rpm libidn2-2.3.7-1.fc40.x86_64
Module from rpm nghttp2-1.59.0-2.fc40.x86_64
Module from rpm libffi-3.4.4-7.fc40.x86_64
Module from rpm duktape-2.7.0-7.fc40.x86_64
Module from rpm glib2-2.80.0-1.fc40.x86_64
Module from rpm curl-8.6.0-7.fc40.x86_64
Module from rpm libselinux-3.6-4.fc40.x86_64
Module from rpm pcre2-10.42-2.fc40.2.x86_64
Module from rpm icu-74.2-1.fc40.x86_64
Module from rpm glib2-2.80.0-1.fc40.x86_64
Module from rpm libproxy-0.5.3-5.fc40.x86_64
Module from rpm brotli-1.1.0-3.fc40.x86_64
Module from rpm keyutils-1.6.3-3.fc40.x86_64
Module from rpm krb5-1.21.2-5.fc40.x86_64
Module from rpm e2fsprogs-1.47.0-5.fc40.x86_64
Module from rpm krb5-1.21.2-5.fc40.x86_64
Module from rpm krb5-1.21.2-5.fc40.x86_64
Module from rpm xz-5.6.0-3.fc40.x86_64
Module from rpm lz4-1.9.4-6.fc40.x86_64
Module from rpm libcap-2.69-3.fc40.x86_64
Module from rpm pcre2-10.42-2.fc40.2.x86_64
Module from rpm libb2-0.98.1-11.fc40.x86_64
Module from rpm double-conversion-3.3.0-3.fc40.x86_64
Module from rpm glib2-2.80.0-1.fc40.x86_64
Module from rpm icu-74.2-1.fc40.x86_64
Module from rpm icu-74.2-1.fc40.x86_64
Module from rpm openssl-3.2.1-2.fc40.x86_64
Module from rpm libproxy-0.5.3-5.fc40.x86_64
Module from rpm zlib-ng-2.1.6-2.fc40.x86_64
Module from rpm brotli-1.1.0-3.fc40.x86_64
Module from rpm krb5-1.21.2-5.fc40.x86_64
Module from rpm zstd-1.5.5-5.fc40.x86_64
Module from rpm systemd-255.4-1.fc40.x86_64
Module from rpm qt6-qtbase-6.6.2-6.fc40.x86_64
Module from rpm qt6-qtbase-6.6.2-6.fc40.x86_64
Module drkonqi-coredump-processor from rpm plasma-drkonqi-6.0.2-1.fc40.x86_64
Stack trace of thread 11641:
#0 0x00007f2dc4d0ea9c _ZL10aeshash128PKhmmm ( + 0x10ea9c)
#1 0x00007f2dc4f5e45b _ZN18QCommandLineParser9addOptionERK18QCommandLineOption ( + 0x35e45b)
#2 0x00007f2dc4f601f3 _ZN18QCommandLineParser13addHelpOptionEv ( + 0x3601f3)
#3 0x0000555ce386ea43 main (drkonqi-coredump-processor + 0x5a43)
#4 0x00007f2dc463d088 __libc_start_call_main ( + 0x2a088)
#5 0x00007f2dc463d14b __libc_start_main@@GLIBC_2.34 ( + 0x2a14b)
#6 0x0000555ce386fff5 _start (drkonqi-coredump-processor + 0x6ff5)
#ELF object binary architecture: AMD x86-64

messages being dumped there (carriage returns added for clarity) over and over.

There were also a lot of SELinux errors in the message log as well

setroubleshoot[2604]: SELinux is preventing abrt-dump-journ from write access on the sock_file io.systemd.DynamicUser.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that abrt-dump-journ should be allowed write access on the io.systemd.DynamicUser sock_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
# ausearch -c 'abrt-dump-journ' --raw | audit2allow -M my-abrtdumpjourn
# semodule -X 300 -i my-abrtdumpjourn.pp

Seems like there’s a lot going on here.

Since Fedora 40 is working fine on my laptop, I’m guessing that there’s something about my desktop that the Fedora binaries don’t like. I haven’t tried another distro yet so I don’t know if it’s just Fedora’s KDE Plasma, or just KDE Plasma in general that my desktop doesn’t like. I also haven’t tried Fedora Workstation yet, so I don’t know if the problem is with Fedora in general or Fedora KDE.

Still a lot of troubleshooting and digging I need to do. One of the problems I’ve run into is that the errors happen so frequently and generated coredumps get deleted so quickly that I can’t really generate useful dumps and bug reporting information.

Wrestling with Fedora


Fedora 39 installer kept hanging the computer. Adding uefi="no" to a dracut config file let the install finish successfully on my BIOS-based (non-UEFI) computer.

In which I try to reinstall Fedora on my computer

The computer has been having a few strange issues recently so a few weeks ago, with Fedora 39 going into beta, I decided it was time to do a reinstall.

It turned into a several weeks long and unexpected ordeal.

The install process worked fine up until the Fedora installer was saying “Installing bootloader”, at which point the computer froze before getting to the next stage. I could reboot the computer, and Fedora would start up fine but the user accounts hadn’t been created yet so there was no way to log in.

Booting up the live image and using a chroot to create the user accounts worked, but the system was still behaving abnormally. Tried a few other Fedora versions going back all the way back to Fedora 35, but the installer would still always hang the computer at the same place, somewhere during the bootloader installation.

I ended up going to KDE Neon, and then settling on Kubuntu for a bit just to get the computer working again so I could figure out what was going on. Had no problems installing either and both of them ran fine, so that gave me some confidence that my Fedora installation issues weren’t hardware related.

Finally, going all the way back to Fedora 33, I was able to get Fedora reinstalled on the system.

Yay! Cue celebration! Now I can upgrade my way to Fedora 39!

Hold up there bubba, not so fast.

The first upgrade step (33->35) went fine up until the kernel install scripts ran, at which point the computer froze up again. All the packages had installed at this point, so I rebooted and promptly got an error because the initramfs file for the Fedora 35 kernel wasn’t there.

Frustrating, but a valuable clue. Something must be happening to cause the computer to hang before or while creating the initramfs.

Fortunately I could still boot into the Fedora 33 kernel. Kicked off another upgrade step (35-37) and again, the computer froze up when the kernel install scripts ran. Again, the initramfs for the Fedora 37 kernel hadn’t been generated.

Dracut, what you doing?

The initramfs file is generated by dracut. Booting into the Fedora 33 kernel again, I tried to manually generate the missing initramfs files (dracut --kver <kernel>). In the middle of the process, the computer froze again. Now I had my culprit, dracut. But what was different about dracut that let it work on my computer with Fedora 33, but not after that?

Going through the dracut man page, the --uefi/--no-uefi options stood out to me. The computer is BIOS-based and doesn’t have UEFI, so I gave dracut --no-uefi --kver <kernel> a try. It worked! The initramfs was generated where the computer previously froze, and rebooting into the newly generated kernel worked without any problems.

Generated a few more missing initramfs files, and those also booted up without problems.

According to the dracut.conf man page, the uefi option can be set in a config file. It’s supposed to default to “no”, but it seemed like that either wasn’t the case, or the Fedora installer sets it to “yes” somewhere. Creating a dracut config file (/etc/dracut.conf.d/00-nouefi.conf) with just uefi="no" let dracut --kver <kernel> run successfully again.

Now that I had a potential solution, I booted up the Fedora 39 beta live image again, created the /etc/dracut.conf.d/00-nouefi.conf file, and started up the installer. This time the installer made it past the point it used to freeze and finished successfully!

Woohoo! Cue celebration! Now the computer is back to running Fedora!

452: Out of range pointer error

For the last couple weeks, my computer has been up and down, spitting out an error when booting up:

452: out of range pointer: 0x100010
Backgrace (.text 0xa058 .data 0x15a6c):
Aborted. Press any key to exit.

It started happening after rebooting following an update. Internet searches I did brought up some older forum posts that pointed to grub being the cause. Since it had been several Fedora versions (before Fedora 30 I think) since I last reinstalled and the system was feeling a bit crusty, I figured I’d just start fresh with a new install.

Wrestled with getting a Fedora 37 live image to boot off, did a reinstall and updates, rebooted, and ended up with the same message. Did this a couple times and started investigating the hardware.

Several iterations of testing the DDR3 memory modules and pulling out hard drives, I managed to get my computer back up and running with 8GB less memory, two 500 GB drives and a 250 GB SSD (the original boot drive) removed. All of the memory tested fine individually but with all of them installed, memtest consistently gave errors when performing one test the 21-22 GB range. Not sure if something’s happened to one of the memory slots, but the system stayed pretty stable for a few days.

Then, after reinstalling some software, running some updates, and rebooting, the error came back.


At this point, rather than reinstall again, I tried reinstalling the bootloader and rebuilt the grub config file. Rebooted and the system came back up without any issues.

Still don’t know what caused the breakage, but it’s been pretty stable so far the past few days. Let’s hope it stays that way. It’s running a bit slower because now I’m back to booting off a regular hard drive (1 TB) rather than an SSD. At some point I might try to put the other 8 GB back in to see how stable the system stays. I’d been having some problems with the computer intermittently freezing up at random points, so I’ll just leave it like this for a while. The 500 GB drives will go into a couple other systems that I inherited a while back. I think one of them will be put to work in the garage, probably on the CNC mill. The other one might end up being used with the radio in the shack.

I tried to reinstall Fedora on the 250 GB SSD drive, but the install would always freeze in the middle of doing something. Even though the drive’s SMART status shows it’s fine, I suspect it has started to develop some issues somewhere.

Fedora KDE, Plasma Wayland, and Emacs

My previous attempts at using Fedora KDE with Wayland were pretty miserable, and KDE was pretty much unusable under Wayland with the nVidia drivers. Never tried it with the nouveau drivers at the time, but after dumping the nVidia drivers a while back, I thought I’d give KDE Plasma Wayland another shot.

I don’t know if Wayland support under KDE got better or if it’s because I’m not using the nVidia drivers anymore (probably both), but I’m finding Plasma is pretty snappy under Wayland.

I normally have emacs started as a systemd service (systemd --user start emacs) which runs emacs in daemon mode. Then I can just run emacsclient and have it connect to the already running emacs. One big issue I came across was not being able to run emacsclient and getting an *ERROR*: Display :0 can't be opened when I ran emacsclient -c from the command line.

The general consensus I found after searching the web for a while seemed to be that with systemd, the emacs daemon was starting before the graphical environment (Plasma), so display related environment variables weren’t available to emacs. Why this only happened with Plasma Wayland and not with Plasma X11, I don’t know.

When the emacs systemd service is enabled (systemd --user enable emacs), /usr/lib/systemd/user/emacs.service is symlinked into ~/.config/systemd/user/ My first attempt to fix the issue was to move emacs.service to, but that didn’t help.

Thinking about the apparent root cause of the issue, I found a Unix StackExchange post about how to have systemd services start in a particular order. I copied /usr/lib/systemd/user/emacs.service to ~/.config/systemd/user and linked it into Then I added two lines to the [Unit] section:


This makes emacs.service a dependency of plasma-kwin_wayland.service and delays starting until after plasma-kwin_wayland.service has finished starting.

After rebooting and logging back in, I verified that the emacs daemon was still starting up (systemd --user status emacs) and was able to get emacsclient -c to bring up the emacs window. Everything was back to working the way I expected.

Fedora + Corsair K70 quirks

This will be an ongoing post of some of the quirks I run into using this new keyboard with Fedora.

  1. Turning the backlight LEDs off seems to behave like pressing F5. If I turn the LEDs off when a browser window is active, the browser ends up doing a refresh.
  2. Trying to assign keyboard shortcuts in Gnome Settings/Keyboard, I can’t seem to get it to do any key combinations with the Super/Windows key. Not sure if I’m just missing something or what.
  3. Interestingly enough, KDE recognizes the Super/Windows key as Meta.