Slow App Start with bugs after fresh install

Ask Fedora
1

Hi

I’ve actually a problem with my apps starting from search menu or over shortcuts, so that the apps start really slow, and buggy. sometimes apps are called (icon on mouse showed) but but not opened then. Sometimes i need to call apps twice or more, to start them, and even then it’s slow. And even when the app is opened, it kind of needs half a minute or such to be usable. i had a fresh install of fedora 43 (Plasma) (now updated to 44), and problem kind of persisted from the beginning.
i tried x11 as well as wayland, both is problematic. i’ve tried to look, if it’s a problem with the compositor, which seems not to be, but possible. (activate / deactivate). I talked for “hours” with GPT and tried much stuff which don’t seem to fix it.
my GPU is Nvidia. (rpm drivers)

Don’t know if this is important. But System startup is also kind of really slow: LUKS takes 2 minutes or such, and login perhaps 1-1.5, (not exactly mesearued).

When i measure app start time over cli it seems to be better (and sometimes good). generally, starting apps over cli seems to function better.

So: I’ve really tried much (perhaps also stupid stuff) and do just not find out, what the problem is. Now i wonder, if i should refresh / reinstall the whole system or if even should change to the Gnome Version of fedora, because this could also more be a problem with plasma. (but i really like plasma… ;-))

so my question is, if somebody knows this problem, or has a link / hint to this? is this common? I’m not so motivated to reinstall the whole system, since this takes much time.

kind regards

goedelgoes

2

btw. the problem persisted for weeks

3

That is not normal.

What desktop are you on? Edit: Plasma.

What are your system specs?

4

sudo dnf install inxi

Then run inxi -Fzxxx

Please post the output between code tags by clicking on the </> icon in the composer and pasting the content inside the grey area that appears.

Thanks

5 
System:
  Kernel: 6.19.14-300.fc44.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.6.5 Distro: Fedora Linux 44 (KDE Plasma Desktop
    Edition)
Machine:
  Type: Desktop Mobo: ASRock model: X399 Taichi serial: <superuser required>
    Firmware: UEFI vendor: American Megatrends v: P3.90 date: 12/04/2019
Battery:
  ID-1: hidpp_battery_0 charge: 73% condition: N/A
CPU:
  Info: 12-core model: AMD Ryzen Threadripper 1920X bits: 64 type: MT MCP
    cache: L2: 6 MiB
  Speed (MHz): avg: 2082 min/max: 2200/3500 cores: 1: 2082 2: 2082 3: 2082
    4: 2082 5: 2082 6: 2082 7: 2082 8: 2082 9: 2082 10: 2082 11: 2082 12: 2082
    13: 2082 14: 2082 15: 2082 16: 2082 17: 2082 18: 2082 19: 2082 20: 2082
    21: 2082 22: 2082 23: 2082 24: 2082
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080] driver: nvidia v: 595.71.05
  Display: wayland server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
    gpu: nv_platform,nvidia,nvidia-nvswitch resolution: 1: 3840x2160~60Hz
    2: 3840x2160~30Hz
  API: EGL v: 1.5 drivers: nvidia,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 595.71.05
    renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
  API: Vulkan v: 1.4.341 drivers: nvidia,llvmpipe surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: Advanced Micro Devices [AMD] Family 17h HD Audio
    driver: snd_hda_intel
  Device-2: NVIDIA TU104 HD Audio driver: snd_hda_intel
  API: ALSA v: k6.19.14-300.fc44.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.6.5 status: active
Network:
  Device-1: Intel I211 Gigabit Network driver: igb
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi
  IF: wlp5s0 state: up mac: <filter>
  Device-3: Intel I211 Gigabit Network driver: igb
  IF: enp6s0 state: down mac: <filter>
  Device-4: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800]
    driver: ath12k_pci
  IF: wlp8s0 state: down mac: <filter>
  IF-ID-1: br-955582836b41 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IF-ID-3: nordlynx state: unknown speed: N/A duplex: N/A mac: N/A
  IF-ID-4: veth639e3f6 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-5: ztv7k74ekz state: unknown speed: 10000 Mbps duplex: full
    mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai driver: btusb type: USB
  Report: btmgmt ID: hci1 state: up address: <filter> bt-v: 5.3
  Device-2: Intel Wireless-AC 3168 Bluetooth driver: btusb type: USB
  Report: ID: hci0 state: up address: <filter> bt-v: 4.2
Drives:
  Local Storage: total: 10.92 TiB used: 2.75 TiB (25.2%)
  ID-1: /dev/sda vendor: Western Digital model: WD40EFRX-68N32N0
    size: 3.64 TiB
  ID-2: /dev/sdb vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
  ID-3: /dev/sdc vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB
  ID-4: /dev/sdd vendor: Western Digital model: WD40EFRX-68N32N0
    size: 3.64 TiB
Partition:
  ID-1: / size: 3.64 TiB used: 1.41 TiB (38.7%) fs: btrfs dev: /dev/dm-0
  ID-2: /boot size: 1.9 GiB used: 802.4 MiB (41.2%) fs: ext4 dev: /dev/sda2
  ID-3: /boot/efi size: 598.8 MiB used: 20 MiB (3.3%) fs: vfat
    dev: /dev/sda1
  ID-4: /home size: 3.64 TiB used: 1.41 TiB (38.7%) fs: btrfs dev: /dev/dm-0
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 648 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB available: 31.21 GiB used: 10.86 GiB (34.8%)
  Processes: 637 Uptime: 7h 34m Shell: Zsh inxi: 3.3.40
6

its just the inxi -Fz, hope thats sufficiant, anyway too much information in the net.

7

see below

8

You’re quite a few kernels behind and the BIOS on this machine is 7 years old - is there a newer version available?

Please post the output of systemd-analyze and systemd-analyze blame using the pre-formatted text </> button, and we might as well check if there’s anything in the journal by posting the output from journalctl -b -1 -p 3 --no-hostname --no-pager.

Hopefully there’s nothing unpleasant in there about disks and so forth

9

I have noticed longer boot times on systems with multiple disks. It does not happen for every system with multiple disks, only on some. I am yet to figure out why.

10

journalctl

Mai 23 10:47:43 systemd-tmpfiles[535]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:2: Failed to resolve user 'tss': Unknown user
Mai 23 10:47:43 systemd-tmpfiles[535]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:4: Failed to resolve user 'tss': Unknown user
Mai 23 10:47:43 systemd-tmpfiles[535]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:6: Failed to resolve group 'tss': Unknown group
Mai 23 10:47:43 systemd-tmpfiles[535]: /usr/lib/tmpfiles.d/tpm2-tss-fapi.conf:7: Failed to resolve group 'tss': Unknown group
Mai 23 10:47:43 systemd-udevd[630]: /usr/lib/udev/rules.d/60-tpm-udev.rules:3 Failed to resolve user 'tss', ignoring: Unknown user
Mai 23 10:47:43 systemd-udevd[630]: /usr/lib/udev/rules.d/60-tpm-udev.rules:4 Failed to resolve group 'tss', ignoring: Unknown group
Mai 23 10:47:44 (udev-worker)[701]: usb7: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[719]: usb3: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[678]: 7-4: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[701]: 7-1: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[719]: 3-1: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[686]: usb2: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[698]: usb1: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[635]: usb4: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[666]: 1-9: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[660]: 1-12: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[692]: usb8: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[634]: usb5: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 10:47:44 (udev-worker)[685]: usb6: Failed to find and pin callout binary "/usr/lib/virtualbox/VBoxCreateUSBNode.sh": No such file or directory
Mai 23 08:48:52 kernel: 
Mai 23 08:49:06 bluetoothd[2709]: Failed to set default system config for hci1
Mai 23 08:49:06 bluetoothd[2709]: Failed to set default system config for hci0
Mai 23 08:49:19 kernel: kvm_intel: VMX not supported by CPU 5
Mai 23 08:49:20 kernel: kvm_intel: VMX not supported by CPU 12
Mai 23 08:49:20 kernel: kvm_intel: VMX not supported by CPU 7
Mai 23 08:49:37 cupsd[3528]: Missing value on line 112 of /var/cache/cups/job.cache.
Mai 23 08:49:37 cupsd[3528]: Missing value on line 125 of /var/cache/cups/job.cache.
Mai 23 08:50:14 systemd[1]: Failed to start setroubleshootd.service - SETroubleshoot daemon for processing new SELinux denial logs.
Mai 23 08:51:31 SetroubleshootPrivileged.py[4243]: failed to retrieve rpm info for path '/var/lib/selinux/targeted/active/modules/200/snappy':
Mai 23 08:51:33 setroubleshoot[3988]: SELinux hindert snap-confine daran, mit read-Zugriff auf Verzeichnis /var zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 859916e2-96f0-43cc-a5e1-d02e1ac18337
Mai 23 08:51:58 firewalld[2846]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Mai 23 08:52:49 SetroubleshootPrivileged.py[5351]: failed to retrieve rpm info for path '/var/lib/selinux/targeted/active/modules/200/snappy':
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit search-Zugriff auf Verzeichnis /usr/share/cracklib zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 4277cd9b-8eff-429f-908c-089bccfa94b1
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit getattr-Zugriff auf Datei /usr/share/cracklib/pw_dict.hwm zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 815fe0ce-7491-439a-b893-2e08808f9083
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit search-Zugriff auf Verzeichnis /usr/share/cracklib zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 4277cd9b-8eff-429f-908c-089bccfa94b1
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit search-Zugriff auf Verzeichnis /usr/share/cracklib zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 4277cd9b-8eff-429f-908c-089bccfa94b1
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit search-Zugriff auf Verzeichnis /usr/share/cracklib zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 4277cd9b-8eff-429f-908c-089bccfa94b1
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit search-Zugriff auf Verzeichnis /usr/share/cracklib zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus:  sealert -l 4277cd9b-8eff-429f-908c-089bccfa94b1
Mai 23 08:53:27 setroubleshoot[7677]: SELinux hindert snap-confine daran, mit remount-Zugriff auf Dateisystem  zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l b1c330e3-2653-41f5-ac0b-cad76eb111c1
Mai 23 09:04:42 org_kde_powerdevil[11369]: [ 11369] Error(s) opening ddc devices
Mai 23 09:04:42 org_kde_powerdevil[11369]: [ 11369] Error EACCES(-13): Keine Berechtigung opening /dev/i2c-1
Mai 23 09:05:26 systemd[10708]: Failed to start akonadi_control.service - Akonadi Control.
Mai 23 09:05:33 systemd[1]: Failed to start packagekit.service - PackageKit Daemon.
Mai 23 09:15:22 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 09:21:52 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 09:22:37 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 09:25:32 kernel: pcieport 0000:02:05.0: AER:   Error of this Agent is reported first
Mai 23 09:29:02 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 09:32:03 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 09:41:39 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:13:45 cupsd[118463]: Missing value on line 112 of /var/cache/cups/job.cache.
Mai 23 13:13:45 cupsd[118463]: Missing value on line 125 of /var/cache/cups/job.cache.
Mai 23 13:14:01 firewalld[2846]: ERROR: NAME_CONFLICT: new_policy_object(): 'docker-forwarding'
Mai 23 13:14:26 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:17:40 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:17:50 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:47:59 bluetoothd[2709]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)
Mai 23 13:48:06 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:48:11 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:48:13 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:48:22 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:48:35 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:48:56 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:49:01 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:49:33 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:49:47 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 13:50:42 bluetoothd[2709]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Mai 23 13:59:07 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 14:00:37 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 14:13:28 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 18:50:22 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 18:50:52 kwin_wayland[11135]: Libinput: event8  - Logitech G915 WIRELESS RGB MECHANICAL GAMING KEYBOARD Consumer Control: client bug: event processing lagging behind by 50ms, your system is too slow
Mai 23 18:52:12 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 18:52:12 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 18:54:42 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 19:11:54 kwin_wayland[11135]: Libinput: client bug: timer button-debounce-debounce-event23: scheduled expiry is in the past (-51ms), your system is too slow
Mai 23 19:13:43 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 19:16:28 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 19:51:41 kernel: pcieport 0000:02:05.0: AER:   Error of this Agent is reported first
Mai 23 19:51:56 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 19:52:36 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 20:04:29 kwin_wayland[11135]: Libinput: event23 - Logitech Wireless Mouse MX Master 3: client bug: event processing lagging behind by 191ms, your system is too slow
Mai 23 20:04:37 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 20:04:37 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 23:09:27 kwin_wayland[11135]: Libinput: client bug: timer button-debounce-debounce-event23: scheduled expiry is in the past (-342ms), your system is too slow
Mai 23 23:09:27 kwin_wayland[11135]: Libinput: client bug: timer button-debounce-debounce-short-event23: scheduled expiry is in the past (-355ms), your system is too slow
Mai 23 23:09:41 kernel: ath12k_pci 0000:08:00.0: AER:   Error of this Agent is reported first
Mai 23 23:10:26 dbus-broker-launch[2701]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mai 23 23:10:27 dbus-broker-launch[2701]: Activation request for 'org.bluez' failed.
Mai 23 23:10:27 dbus-broker-launch[2701]: Activation request for 'org.bluez' failed.
Mai 23 23:10:32 dbus-broker-launch[2701]: Activation request for 'org.bluez' failed.
Mai 23 23:10:32 dbus-broker-launch[2701]: Activation request for 'org.bluez' failed.
Mai 23 23:10:50 kwin_wayland[11135]: Applying output configuration failed!
Mai 23 23:10:50 kwin_wayland[11135]: Applying output configuration failed!
Mai 23 23:10:55 systemd-coredump[188691]: Failed to send coredump datagram: Broken pipe
Mai 23 23:10:59 dbus-broker-launch[2701]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mai 23 23:11:01 systemd-coredump[188776]: Failed to send coredump datagram: Connection reset by peer
Mai 23 23:11:03 systemd-coredump[188783]: Failed to send coredump datagram: Broken pipe
Mai 23 23:11:10 dbus-broker-launch[2701]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mai 23 23:11:10 dbus-broker-launch[2701]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mai 23 23:11:10 dbus-broker-launch[2701]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Mai 23 23:11:11 auditd[2676]: plugin /usr/sbin/sedispatch terminated unexpectedly
Mai 23 23:11:11 systemd-cryptsetup[188953]: Device luks-x is still in use.
Mai 23 23:11:11 systemd-cryptsetup[188953]: Failed to deactivate 'luks-x': Device or resource busy
  1. perhaps you should know that there was also some problem with my new Wireless / Bluetooth Card, which actually lacks drivers, but somehow shouldn’t need extra drivers, hopefully. → just said, that the problem with the wireless card appeared much after the fresh install and the described problem was there, before installing the cards.
  2. i sometimes wonder what’s about these message here (a bit off topic sorry):
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit getattr-Zugriff auf Datei /usr/share/cracklib/pw_dict.hwm zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 815fe0ce-7491-439a-b893-2e08808f9083
Mai 23 08:52:49 setroubleshoot[5386]: SELinux hindert snap-confine daran, mit search-Zugriff auf Verzeichnis /usr/share/cracklib zuzugreifen.Zum Anzeigen der kompletten SELinux-Benachrichtigung führen Sie folgenden Befehl aus: sealert -l 4277cd9b-8eff-429f-908c-089bccfa94b1

and sorry for some german in the logs here, my sys is on german actually. the lines just say, that SELinux is blocking snap-confine to do gettattr on /usr/share/cracklib/pw_dict.hwm and search on /usr/share/cracklib

i’ve had those message on several systems, it looks just like a sandbox problem or proper block or something like this. but…

btw. i’ve deleted my luks id’s and cleaned up the journal, but just deleted all the doubled entries when content was repeatedly printed.

11 
systemd-analyze

Startup finished in 16.886s (firmware) + 6.376s (loader) + 4.057s (kernel) + 44.232s (initrd) + 6min 16.426s (userspace) = 7min 27.978s 
graphical.target reached after 6min 14.004s in userspace.

and
systemd-analyze blame

5min 34.269s akmods.service
4min 42.368s vboxdrv.service
2min 45.241s docker.service
1min 16.653s dev-disk-by\x2dpartuuid-bf7d449b\x2d1ecc\x2d4f2a\x2da5e3\x2d43896694b6de.device
1min 16.653s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartuuid-bf7d449b\x2d1ecc\x2d4f2a\x2da5e3\x2d43896694b6de.device
1min 16.653s dev-disk-by\x2did-wwn\x2d0x50014ee213446915\x2dpart2.device
1min 16.653s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda2.device
1min 16.653s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K4EUFCLX\x2dpart2.device
1min 16.653s dev-disk-by\x2duuid-159e2f3f\x2d8cfa\x2d48de\x2d8bc9\x2d02f433bc38ff.device
1min 16.653s dev-sda2.device
1min 16.653s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2duuid-159e2f3f\x2d8cfa\x2d48de\x2d8bc9\x2d02f433bc38ff.device
1min 16.653s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartnum-2.device
1min 16.653s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3\x2dpart2.device
1min 16.653s dev-disk-by\x2ddiskseq-1\x2dpart2.device
1min 16.653s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart2.device
1min 15.695s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2duuid-B020\x2d770A.device
1min 15.695s dev-sda1.device
1min 15.695s dev-disk-by\x2did-wwn\x2d0x50014ee213446915\x2dpart1.device
1min 15.695s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 15.695s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3\x2dpart1.device
1min 15.695s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart1.device
1min 15.695s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 15.695s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda1.device
1min 15.694s dev-disk-by\x2duuid-B020\x2d770A.device
1min 15.694s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartnum-1.device
1min 15.694s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartuuid-e60f9c54\x2d87bf\x2d411d\x2da987\x2d6fa9e8001e1f.device
1min 15.694s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K4EUFCLX\x2dpart1.device
1min 15.694s dev-disk-by\x2dpartuuid-e60f9c54\x2d87bf\x2d411d\x2da987\x2d6fa9e8001e1f.device
1min 15.694s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
1min 12.308s dev-disk-by\x2ddiskseq-3.device
1min 12.308s dev-cdrom.device
1min 12.308s dev-sr0.device
1min 12.308s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d5.device
1min 12.308s dev-disk-by\x2did-ata\x2dASUS_BC\x2d12D2HT_KLLJ1582243.device
1min 12.308s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata5-host4-target4:0:0-4:0:0:0-block-sr0.device
1min 12.307s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d5.0.device
 1min 9.899s dev-disk-by\x2did-wwn\x2d0x50014ee213446915\x2dpart3.device
 1min 9.899s dev-disk-by\x2dpartuuid-580a7c57\x2ddffd\x2d489d\x2d944a\x2dec9b9e892fa9.device
 1min 9.899s dev-disk-by\x2duuid-4de97286\x2d8711\x2d40f6\x2d911c\x2df56789960b9d.device
 1min 9.899s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartnum-3.device
 1min 9.899s dev-disk-by\x2ddiskseq-1\x2dpart3.device
 1min 9.899s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata3-host2-target2:0:0-2:0:0:0-block-sda-sda3.device
 1min 9.899s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3\x2dpart3.device
 1min 9.899s dev-sda3.device
 1min 9.899s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart3.device
 1min 9.899s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K4EUFCLX\x2dpart3.device
 1min 9.899s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2dpartuuid-580a7c57\x2ddffd\x2d489d\x2d944a\x2dec9b9e892fa9.device
 1min 9.899s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0\x2dpart-by\x2duuid-4de97286\x2d8711\x2d40f6\x2d911c\x2df56789960b9d.device
 1min 9.854s dev-sda.device
 1min 9.853s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.0.device
 1min 9.853s dev-disk-by\x2ddiskseq-1.device
 1min 9.853s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d3.device
 1min 9.853s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata3-host2-target2:0:0-2:0:0:0-block-sda.device
 1min 9.853s dev-disk-by\x2did-wwn\x2d0x50014ee213446915.device
 1min 9.853s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K4EUFCLX.device
     59.581s dev-disk-by\x2dpartuuid-249fb072\x2d1b5f\x2d41ff\x2d93ff\x2d20374ead2019.device
     59.581s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata7-host6-target6:0:0-6:0:0:0-block-sdc-sdc1.device
     59.581s dev-disk-by\x2ddiskseq-5\x2dpart1.device
     59.581s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7.0\x2dpart1.device
     59.581s dev-disk-by\x2duuid-a6563c77\x2d01e3\x2d4148\x2da532\x2d588948dcd193.device
     59.581s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7.0\x2dpart-by\x2dpartnum-1.device
     59.581s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7\x2dpart1.device
     59.581s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7.0\x2dpart-by\x2dpartuuid-249fb072\x2d1b5f\x2d41ff\x2d93ff\x2d20374ead2019.device
     59.581s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7.0\x2dpart-by\x2duuid-a6563c77\x2d01e3\x2d4148\x2da532\x2d588948dcd193.device
     59.581s dev-disk-by\x2did-ata\x2dST2000DM008\x2d2FR102_ZFL0A78H\x2dpart1.device
     59.581s dev-sdc1.device
     59.581s dev-disk-by\x2did-wwn\x2d0x5000c500b541ca36\x2dpart1.device
     59.577s dev-disk-by\x2did-wwn\x2d0x5000c500b5427cb9\x2dpart1.device
     59.577s dev-sdb1.device
     59.577s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sdb-sdb1.device
     59.577s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6.0\x2dpart-by\x2dpartnum-1.device
     59.577s dev-disk-by\x2dpartuuid-fdb30e46\x2ddfa5\x2d49a9\x2d9684\x2df760e9c68f83.device
     59.577s dev-disk-by\x2ddiskseq-4\x2dpart1.device
     59.577s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6\x2dpart1.device
     59.577s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6.0\x2dpart-by\x2dpartuuid-fdb30e46\x2ddfa5\x2d49a9\x2d9684\x2df760e9c68f83.device
     59.577s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6.0\x2dpart1.device
     59.577s dev-disk-by\x2did-ata\x2dST2000DM008\x2d2FR102_ZFL0A4R8\x2dpart1.device
     59.577s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6.0\x2dpart-by\x2duuid-f57ba144\x2dad8a\x2d4bba\x2dbf6f\x2de725ba65998c.device
     59.577s dev-disk-by\x2duuid-f57ba144\x2dad8a\x2d4bba\x2dbf6f\x2de725ba65998c.device
     59.573s dev-sdd1.device
     59.573s dev-disk-by\x2duuid-823698e6\x2d969b\x2d4f77\x2d9656\x2d877e9829446e.device
     59.573s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.0\x2dpart-by\x2dpartnum-1.device
     59.573s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8\x2dpart1.device
     59.573s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.0\x2dpart-by\x2dlabel-Backups_internal.device
     59.573s dev-disk-by\x2dpartuuid-0c37d6db\x2d2bd0\x2d4cb6\x2d9752\x2d18f9b514a92f.device
     59.573s dev-disk-by\x2dlabel-Backups_internal.device
     59.573s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata8-host7-target7:0:0-7:0:0:0-block-sdd-sdd1.device
     59.573s dev-disk-by\x2ddiskseq-6\x2dpart1.device
     59.573s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.0\x2dpart-by\x2duuid-823698e6\x2d969b\x2d4f77\x2d9656\x2d877e9829446e.device
     59.573s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.0\x2dpart1.device
     59.573s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.0\x2dpart-by\x2dpartuuid-0c37d6db\x2d2bd0\x2d4cb6\x2d9752\x2d18f9b514a92f.device
     59.573s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K0DF17S1\x2dpart1.device
     59.573s dev-disk-by\x2did-wwn\x2d0x50014ee2bdefd21c\x2dpart1.device
     59.564s dev-disk-by\x2did-wwn\x2d0x5000c500b541ca36.device
     59.564s dev-sdc.device
     59.563s dev-disk-by\x2ddiskseq-5.device
     59.563s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7.device
     59.563s dev-disk-by\x2did-ata\x2dST2000DM008\x2d2FR102_ZFL0A78H.device
     59.563s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d7.0.device
     59.563s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata7-host6-target6:0:0-6:0:0:0-block-sdc.device
     59.562s dev-sdb.device
     59.562s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6.device
     59.562s dev-disk-by\x2did-ata\x2dST2000DM008\x2d2FR102_ZFL0A4R8.device
     59.562s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata6-host5-target5:0:0-5:0:0:0-block-sdb.device
     59.562s dev-disk-by\x2ddiskseq-4.device
     59.562s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d6.0.device
     59.562s dev-disk-by\x2did-wwn\x2d0x5000c500b5427cb9.device
     59.558s dev-sdd.device
     59.558s dev-disk-by\x2ddiskseq-6.device
     59.558s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.0.device
     59.558s dev-disk-by\x2dpath-pci\x2d0000:01:00.1\x2data\x2d8.device
     59.558s dev-disk-by\x2did-wwn\x2d0x50014ee2bdefd21c.device
     59.558s dev-disk-by\x2did-ata\x2dWDC_WD40EFRX\x2d68N32N0_WD\x2dWCC7K0DF17S1.device
     59.558s sys-devices-pci0000:00-0000:00:01.1-0000:01:00.1-ata8-host7-target7:0:0-7:0:0:0-block-sdd.device
     58.525s sys-module-fuse.device
     58.226s dev-ttyS1.device
     58.226s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
     58.065s sys-module-configfs.device
     57.798s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
     57.798s dev-ttyS3.device
     57.792s dev-ttyS2.device
     57.792s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
     57.788s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
     57.788s dev-ttyS0.device
     50.367s snapd.service
     33.104s dracut-initqueue.service
     32.436s systemd-cryptsetup@luks\x2d4de97286\x2d8711\x2d40f6\x2d911c\x2df56789960b9d.service
     26.687s systemd-journal-flush.service
     25.281s upower.service
     23.863s dev-loop40.device
     23.345s dev-loop41.device
     23.255s dev-loop34.device
     23.156s firewalld.service
     23.004s rsyslog.service
     22.322s dev-loop43.device
     22.282s containerd.service
     21.461s dev-loop38.device
     21.032s dev-loop27.device
     20.932s dev-loop13.device
     20.899s dev-loop1.device
     20.722s dev-loop12.device
     20.304s dev-loop2.device
     20.221s dev-loop28.device
     20.011s dev-loop26.device
     19.929s dev-loop29.device
     19.499s dev-loop39.device
     19.475s dev-loop32.device
     19.385s dev-loop42.device
     19.310s dev-loop15.device
     19.107s dev-loop22.device
     18.945s dev-loop9.device
     18.762s dev-loop35.device
     18.503s dev-loop8.device
     18.366s dev-loop31.device
     18.333s dev-loop0.device
     18.274s dev-loop37.device
     17.728s dev-loop24.device
     17.324s dev-loop30.device
     17.252s dev-loop7.device
     17.173s dev-loop11.device
     17.146s dev-loop14.device
     17.099s dev-loop33.device
     16.939s dev-loop23.device
     16.876s dev-loop3.device
     16.640s dev-loop6.device
     16.341s dev-loop20.device
     15.622s dev-zram0.swap
     15.484s dnf-makecache.service
     14.793s dev-loop25.device
     14.581s dev-loop19.device
     14.321s dev-loop21.device
     14.290s dev-loop5.device
     13.782s dev-loop17.device
     13.690s dev-loop18.device
     13.566s dev-loop16.device
     13.252s dev-loop10.device
     12.375s abrtd.service
     12.077s initrd-switch-root.service
     10.665s udisks2.service
     10.486s tuned.service
      9.665s unbound-anchor.service
      9.582s chronyd.service
      7.782s polkit.service
      7.761s smartd.service
      6.918s NetworkManager-wait-online.service
      6.768s accounts-daemon.service
      6.300s ModemManager.service
      5.678s thermald.service
      4.948s authselect-apply-changes.service
      4.900s foomaticrip-upgrade.service
      4.841s dev-loop4.device
      4.778s bluetooth.service
      4.486s cups.service
      4.403s switcheroo-control.service
      4.365s avahi-daemon.service
      4.334s lm_sensors.service
      2.709s systemd-udevd.service
      2.531s tuned-ppd.service
      2.365s systemd-logind.service
      2.236s gssproxy.service
      1.805s NetworkManager.service
      1.766s systemd-rfkill.service
      1.409s var-lib-snapd-snap-core-17292.mount
      1.274s systemd-tmpfiles-setup-dev-early.service
      1.241s systemd-zram-setup@zram0.service
      1.221s var-lib-snapd-snap-core-17284.mount
      1.211s lvm2-monitor.service
      1.181s audit-rules.service
      1.166s var-lib-snapd-snap-brave-630.mount
      1.148s var-lib-snapd-snap-receiver-100.mount
      1.131s var-lib-snapd-snap-core22-2339.mount
      1.114s var-lib-snapd-snap-core22-2411.mount
      1.096s var-lib-snapd-snap-banana\x2daccounting\x2dplus-47.mount
      1.084s var-lib-snapd-snap-brave-632.mount
      1.083s var-lib-snapd-snap-joplin\x2ddesktop-142.mount
      1.078s var-lib-snapd-snap-capturist-34.mount
      1.076s var-lib-snapd-snap-core24-1587.mount
      1.076s dbus-broker.service
      1.073s systemd-fsck@dev-disk-by\x2duuid-159e2f3f\x2d8cfa\x2d48de\x2d8bc9\x2d02f433bc38ff.service
      1.073s colord.service
      1.033s var-lib-snapd-snap-clockify\x2dcli-350.mount
      1.027s var-lib-snapd-snap-gnome\x2d42\x2d2204-247.mount
      1.000s var-lib-snapd-snap-tidal\x2dhifi-5.mount
       997ms var-lib-snapd-snap-core20-2769.mount
       983ms var-lib-snapd-snap-superproductivity-3638.mount
       974ms systemd-udev-trigger.service
       953ms var-lib-snapd-snap-spotify-94.mount
       933ms var-lib-snapd-snap-snapd-26865.mount
       932ms boot.mount
       923ms user@1000.service
       913ms plymouth-switch-root.service
       890ms var-lib-snapd-snap-snap\x2dstore-1338.mount
       889ms var-lib-snapd-snap-core24-1643.mount
       883ms var-lib-snapd-snap-gnome\x2d46\x2d2404-153.mount
       881ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount
       875ms var-lib-snapd-snap-clockify\x2dcli-347.mount
       868ms var-lib-snapd-snap-plexmediaserver-520.mount
       828ms var-lib-snapd-snap-mesa\x2d2404-1165.mount
       823ms var-lib-snapd-snap-todoist-1356.mount
       823ms var-lib-snapd-snap-core18-2999.mount
       816ms raid-check.service
       816ms var-lib-snapd-snap-plexmediaserver-524.mount
       795ms var-lib-snapd-snap-joplin\x2ddesktop-144.mount
       777ms var-lib-snapd-snap-receiver-107.mount
       758ms var-lib-snapd-snap-gnome\x2d3\x2d38\x2d2004-143.mount
       750ms systemd-tmpfiles-setup.service
       739ms var-lib-snapd-snap-snapd-26382.mount
       735ms var-lib-snapd-snap-vlc-3777.mount
       720ms var-lib-snapd-snap-pdfarranger-41.mount
       710ms systemd-user-sessions.service
       710ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount
       694ms var-lib-snapd-snap-tidal\x2dhifi-8.mount
       691ms var-lib-snapd-snap-spotify-95.mount
       690ms var-lib-snapd-snap-core20-2866.mount
       680ms var-lib-snapd-snap-mesa\x2dcore20-172.mount
       643ms systemd-resolved.service
       628ms var-lib-snapd-snap-snap\x2dstore-1367.mount
       587ms var-lib-snapd-snap-todoist-1355.mount
       579ms systemd-udev-load-credentials.service
       568ms var-lib-snapd-snap-plex\x2ddesktop-87.mount
       554ms systemd-remount-fs.service
       526ms dev-hugepages.mount
       525ms dev-mqueue.mount
       524ms sys-kernel-debug.mount
       523ms sys-kernel-tracing.mount
       497ms systemd-fsck@dev-disk-by\x2duuid-B020\x2d770A.service
       482ms sys-fs-fuse-connections.mount
       474ms systemd-journald.service
       458ms intel_lpmd.service
       450ms home.mount
       389ms dracut-shutdown.service
       387ms var-lib-snapd-snap-bare-5.mount
       384ms flatpak-system-helper.service
       361ms systemd-random-seed.service
       287ms boot-efi.mount
       271ms wpa_supplicant.service
       190ms var-lib-nfs-rpc_pipefs.mount
       180ms systemd-update-utmp.service
       177ms rtkit-daemon.service
       169ms systemd-network-generator.service
       160ms auditd.service
       158ms kmod-static-nodes.service
       157ms systemd-tmpfiles-clean.service
       147ms systemd-vconsole-setup.service
       145ms systemd-sysctl.service
       144ms systemd-hostnamed.service
       132ms sssd-kcm.service
       102ms plymouth-read-write.service
        88ms dracut-cmdline.service
        78ms systemd-userdbd.service
        71ms proc-sys-fs-binfmt_misc.mount
        66ms docker.socket
        59ms uresourced.service
        58ms vboxballoonctrl-service.service
        52ms vboxweb-service.service
        51ms systemd-userdb-load-credentials.service
        51ms systemd-tmpfiles-setup-dev.service
        51ms initrd-cleanup.service
        49ms user-runtime-dir@1000.service
        46ms var-lib-snapd-snap-superproductivity-3672.mount
        45ms initrd-parse-etc.service
        43ms dracut-pre-udev.service
        42ms vboxautostart-service.service
        40ms nordvpnd.socket
        35ms dracut-pre-pivot.service
        34ms pcscd.socket
        34ms plymouth-quit-wait.service
        34ms rpc-statd-notify.service
        33ms plymouth-quit.service
        32ms tmp.mount
        29ms systemd-fsck-root.service
        28ms plymouth-start.service
        27ms initrd-udevadm-cleanup-db.service
        27ms systemd-modules-load.service
        24ms systemd-udevd-control.socket
        23ms snapd.socket
        18ms cups.socket
        14ms dev-loop44.device
        13ms lvm2-lvmpolld.socket
         9ms sshd-unix-local.socket
         9ms systemd-userdbd.socket
         8ms iscsid.socket
         2ms systemd-coredump.socket
         1ms systemd-bootctl.socket
         1ms systemd-sysext.socket
         1ms systemd-ask-password.socket
         1ms systemd-factory-reset.socket
         1ms systemd-mute-console.socket
       837us systemd-repart.socket
       785us systemd-creds.socket
       784us avahi-daemon.socket
       628us dbus.socket
       570us dm-event.socket
       481us systemd-hostnamed.socket
       419us sssd-kcm.socket
       323us systemd-logind-varlink.socket
       312us systemd-resolved-monitor.socket
       227us systemd-udevd-varlink.socket
       179us iscsiuio.socket
       173us systemd-journald-audit.socket
       109us systemd-resolved-varlink.socket
        62us systemd-journald-dev-log.socket
        50us systemd-journald.socket
        42us systemd-rfkill.socket
        15us systemd-udevd-kernel.socket
12

and about kernel and BIOS:

  1. kernel → i did not notice that kernel is behind, will try to update that.
  2. BIOS → Ok, bios is really old → this system (Hardware) was not in use for a longer time, and i reused it this year in 2026, cause i change some things in my setups. but anyway → i just can try to update the bios, if i find actual versions and updates are actually still supported today
13

These are all spinning drives. If you were able to put an SSD in there and use it at least for your OS install, that would probably give a good speedup.

14

os is on an SSD

15

as far as i know…

16

What physical drive is it on? Your sda, sdb, sdc and sdd there are all spinning drives, unless I’m looking up the model numbers wrong.

17

If you can get a connection to https://Linuxhardware.org you can see what BIOS versions are being used on your model, but AI scrapers have been hammering the site so it is often unable to accept new connections. Maybe ask an AI for the BIOS version!

18

NVME drives usually show up as such, like mine here

zram0                                         251:0    0   7.4G  0 disk  [SWAP]
nvme0n1                                       259:0    0 238.5G  0 disk  
├─nvme0n1p1                                   259:1    0   600M  0 part  /boot/efi
├─nvme0n1p2                                   259:2    0     2G  0 part  /boot
└─nvme0n1p3                                   259:3    0 235.9G  0 part

Also are you using Snaps, they are more of an Ubuntu thing, maybe you want to use Flatpak or regular RPMs

19

The major pain point is the very slow detection of drives.

This will be a ball-ache to do but it will be the fastest way to either rule the drives and the controller out.

Physically unplug sdb, sdc, sdd and the DVD/optical drive sr0 (maybe start with sr0, as it should be relatively easy).

Boot with just the system disk.

Is the process much, much faster (like 40 seconds rather than 7 minutes). If so, the issue is with the spinning rust. Start plugging them back in, one by one until the boot times increase substantially - that’s your problem device (I assume you’ve had a look at the smartctl output for each device, and they all check out as “perfect”.

As akmods took some time this implies that it was rebuilding the nvidia drivers. Might want to check that is actually working by looking in /var/cache/nvidia/.last.log and making sure it’s full of “success” at the end of the file - last 10 lines or so.

Same with the virtualbox - it’s taking a while too… maybe this was just a bad boot to look at as there was a lot of stuff happening alongside the tragically slow boot process.

Please also post your /etc/fstab - need to make sure all devices are in there, with appropriate flags (nofail for example) and you could also post the output from journalctl -b -1 -p warning and journalctl -b -1 | grep -Ei "ata|ahci|failed|error|timeout|reset"

I’d also be checking all the sata cables for positive connections and maybe swapping them out for spares if you have some, just to rule out daft stuff like a failing cable.

20

oh man. Now i see… This setup is a complete mess! Story: When i refreshed my system i removed my 2 oly M.2 SSD’s from the board (old dual boot stuff) and put in a 4TB M.2. On the other hand, i have 2x2TB and 2x4TB HDD’s (which you see on the logs). When i started the sys for installing the os, i just saw the 2x2 and 2x4, and since i’ve not used it so much, i thought, one of the 4TB one’s would be the SSD… so i messed up the setup and installes the os on the wrong drive. Since i see now, my System does not even recognize the 4TB SSD, pehaps i’ve bought the wrong one or somethin like this.

Thanks a lot for this hint. I’ve decided try to fix the ssd issues, such that the system sees the drive, and then reinstall my whole setup. Since you’re right, and i’d like to have my os on a rather fast SSD, i think this is the way to go. After that, i’ll see, if some problems persist etc. and will then push an update here. If Drives are still slow or such, i will then try your recoomendations (above) → and use the whole proc.

And: Perhaps this whole Problem is just: 2TB of Data on LUKS HDD with 5400rpm. I’m not sure, but perhaps it’s just lots of data. And HDD are older too…

And Last: So, if a reinstall the os anyway, i would wonder, what you and others recommend to choose: even Official Gnome Version of Fedora 44 or stick to the Plasma. Personally i like Plasma a bit more, but sometimes there are some bugs and smaller Problems. Some people seem to say, that the main version (Gnome) is a bit more Stable and more easy to go? I’ve also thoght about installing Gnome version, and then install Plasma additionally for switching Desktops when useful. The main reason, why i did not do dual desktop setups before, is because i (i) heard this is more buggy, and (ii) i’ve already tried it sometimes, and had some problems.

I know… this is a bit off-topic now, for this thread… But i just wonder what’s the main differences between gnome and plasma today, in practice.

I neccesary → i could transfer this question in another topic or just read stuff which is already available.

In any case, I’d like to say a big thank you at this point