Bug 449054 - Should file checking be an option in GRUB instead of the default boot?
Summary: Should file checking be an option in GRUB instead of the default boot?
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: Live/Install images (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-24 08:53 UTC by jimbo
Modified: 2025-09-20 09:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jimbo 2022-01-24 08:53:46 UTC
I use the LiveUSB quite often it's a fantastic tool for troubleshooting and diagnostics. However each time I'm prompted to do a file check. Cancelling the file check allows the LiveUSB to boot faster and it's never come up with any problems. 

I understand the usefulness of having a file check but does it need to run every single time? I would image that it should be an option if your LiveUSB fails to boot in GRUB but by default the LiveUSB should attempt to boot without it.

I'm considering this from a first impressions type-of-view. Without the check it boots in seconds which is really impressive for a first-time user. Also for troubleshooting purposes you may be rebooting multiple times and having to skip it is annoying. I know the LiveUSB works so running the file check every boot is pointless and I'd like the option to just boot normally. Thanks.
Comment 1 Carlos De Maine 2025-09-20 09:35:31 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!