Bazzite 43 20251118 absurdly long boot times still present
Gonna put this out here for more visibility. After the update to 20251118 from 20251114.1 I'm still experiencing ridiculously long boot times. I've noticed the systemd-remount-fs service is in a failed state, but that's a service I've noticed has been failing since I started using Bazzite back in March.
SystemD has been entirely unhelpful, as is the lack of ability to function key over to service start up on boot to find where the bug in question is. Below is a shot of the only failed service stub in my stack on a fresh boot (but again, this service has been failing for 3/4ths of the year, ever since I've used Bazzite).
SystemD unit file that is in a failed state
==================================
× systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Fri 2025-11-21 14:01:00 EST; 1min 1s ago
Invocation: d4a6cc7da49c4e9cac9c45df3d08c187
Docs: man:systemd-remount-fs.service(8)
https://systemd.io/API_FILE_SYSTEMS
Process: 1209 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
Main PID: 1209 (code=exited, status=1/FAILURE)
Mem peak: 2M
CPU: 5ms
Nov 21 14:01:00 violet systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
Nov 21 14:01:00 violet systemd-remount-fs[1210]: mount: /: fsconfig() failed: overlay: No changes allowed in reconfigure.
Nov 21 14:01:00 violet systemd-remount-fs[1210]: dmesg(1) may have more information after failed mount system call.
Nov 21 14:01:00 violet systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 14:01:00 violet systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
Nov 21 14:01:00 violet systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
====================
Below is my fastfetch
====================
%%%%%%====%%%%%%%%%%
%%%%%%%% %%%%%%%%%%%%%% �� bazzite:stable
%%%%%%%%% %%%%%%%%%%%%%%%% �� Bazzite
%%%%%%%%% %%%%%%%%%%%%%%%### Linux 6.17.7-ba14.fc43.x86_64
%%%%%%%%% %%%%%%%%%%%%%###### �� 13 mins
== =======######
== =========##### �� AMD Ryzen 9 9900X (24) @ 5.66 GHz
%%%%%%%%% %%%%%%%####======##### �� AMD Radeon RX 9070 XT [Discrete]
%%%%%%%%% %%%%%#######=====##### �� AMD Radeon Graphics [Integrated]
%%%%%%%%% %%%#########=====##### 8.35 GiB / 60.46 GiB (14%)
%%%%%%%%% %%##########=====##### 711.63 GiB / 929.93 GiB (77%) - btrfs
%%%%%%%%%====###########=====###### 1.25 TiB / 1.58 TiB (79%) - btrfs
%%%%%%%%====#########======###### �� 3840x2160 @ 60 Hz in 72" [External, HDR]
%%%%%%%=====#####========###### �� 2560x1440 @ 144 Hz in 27" [External]
%%%%###===============####### �� 2560x1440 @ 165 Hz in 31" [External] *
%#######==========######### �� Corsair CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard
#######################
################### �� KDE Plasma 6.5.2
########### KWin (Wayland)
bash 5.3.0
Ptyxis 49.2
�� 2658 (rpm), 76 (flatpak), 53 (brew), 1 (brew-cask)
● ● ● ● ● ● ● ●
SystemD has been entirely unhelpful, as is the lack of ability to function key over to service start up on boot to find where the bug in question is. Below is a shot of the only failed service stub in my stack on a fresh boot (but again, this service has been failing for 3/4ths of the year, ever since I've used Bazzite).
SystemD unit file that is in a failed state
==================================
× systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; enabled-runtime; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Fri 2025-11-21 14:01:00 EST; 1min 1s ago
Invocation: d4a6cc7da49c4e9cac9c45df3d08c187
Docs: man:systemd-remount-fs.service(8)
https://systemd.io/API_FILE_SYSTEMS
Process: 1209 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
Main PID: 1209 (code=exited, status=1/FAILURE)
Mem peak: 2M
CPU: 5ms
Nov 21 14:01:00 violet systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
Nov 21 14:01:00 violet systemd-remount-fs[1210]: mount: /: fsconfig() failed: overlay: No changes allowed in reconfigure.
Nov 21 14:01:00 violet systemd-remount-fs[1210]: dmesg(1) may have more information after failed mount system call.
Nov 21 14:01:00 violet systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 14:01:00 violet systemd[1]: systemd-remount-fs.service: Failed with result 'exit-code'.
Nov 21 14:01:00 violet systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.
====================
Below is my fastfetch
====================
%%%%%%====%%%%%%%%%%
%%%%%%%% %%%%%%%%%%%%%% �� bazzite:stable
%%%%%%%%% %%%%%%%%%%%%%%%% �� Bazzite
%%%%%%%%% %%%%%%%%%%%%%%%### Linux 6.17.7-ba14.fc43.x86_64
%%%%%%%%% %%%%%%%%%%%%%###### �� 13 mins
== =======######
== =========##### �� AMD Ryzen 9 9900X (24) @ 5.66 GHz
%%%%%%%%% %%%%%%%####======##### �� AMD Radeon RX 9070 XT [Discrete]
%%%%%%%%% %%%%%#######=====##### �� AMD Radeon Graphics [Integrated]
%%%%%%%%% %%%#########=====##### 8.35 GiB / 60.46 GiB (14%)
%%%%%%%%% %%##########=====##### 711.63 GiB / 929.93 GiB (77%) - btrfs
%%%%%%%%%====###########=====###### 1.25 TiB / 1.58 TiB (79%) - btrfs
%%%%%%%%====#########======###### �� 3840x2160 @ 60 Hz in 72" [External, HDR]
%%%%%%%=====#####========###### �� 2560x1440 @ 144 Hz in 27" [External]
%%%%###===============####### �� 2560x1440 @ 165 Hz in 31" [External] *
%#######==========######### �� Corsair CORSAIR K100 RGB Optical-Mechanical Gaming Keyboard
#######################
################### �� KDE Plasma 6.5.2
########### KWin (Wayland)
bash 5.3.0
Ptyxis 49.2
�� 2658 (rpm), 76 (flatpak), 53 (brew), 1 (brew-cask)
● ● ● ● ● ● ● ●
Solution
I believe I found the issue... and this is a bit crazy. The post on the endeavor forums mentioned a mouse. I have a Elecom Deft Pro for a mouse, and I have the USB dongle plugged into my keyboard, as well as having it hooked up to bluetooth (there for a while there was a problem with bluetooth so I'd switch it to use the RF dongle). I unplugged the RF dongle and rebooted, and now it boots within seconds. @nagito || Knight of Emilia I really appreciate your help.
To anyone else who might stumble into this, check your USB devices
To anyone else who might stumble into this, check your USB devices
