Known quirks and fixes

System freezes or reports out of resources before GRUB

If the machine freezes, hangs, or throws an out-of-resources error before the SnipeOS GRUB menu appears (during POST, firmware splash, or the earliest boot hand-off), the failure is still at the hardware or motherboard BIOS/UEFI stage. The ISO has not failed yet; the firmware never handed control to GRUB cleanly.

1. Disable Fast Boot and Secure Boot

Power on and repeatedly press F2, Del, F10, or F12 (whichever your board uses) to enter BIOS/UEFI setup. Find and disable:

• Fast Boot (sometimes Ultra Fast Boot, Quick Boot, or similar)
• Secure Boot

Save and exit, then try the Live USB again. Do this first even if the rest of the list looks more dramatic. Fast Boot can skip USB init paths; Secure Boot can block or stall unsigned Live media before GRUB is ever shown.

2. Force the plain GRUB menu

On some Ubuntu-family Live USBs, GRUB is hidden and jumps straight into a graphic payload that can crash low-RAM machines. Immediately after power-on, repeatedly tap or hold:

• Shift for Legacy / BIOS mode
• Esc for UEFI mode

That forces the plain-text GRUB bootloader before graphical payload init. You should then see the normal SnipeOS GRUB entries.

3. Other firmware settings that free early memory

Still in BIOS/UEFI setup, if Fast Boot and Secure Boot are already off and the problem remains:

• Integrated graphics shared memory: if you use CPU graphics, lower shared VRAM allocation to 64 MB or 128 MB so more system RAM stays available during early init.
• Boot mode: if set to UEFI, try Legacy / CSM (or the reverse). Legacy often needs less memory before the bootloader loads.

4. Reset motherboard NVRAM / CMOS

If firmware still claims it is out of resources before GRUB, the BIOS/UEFI memory map or NVRAM may be corrupted:

1. Shut down and unplug power (and remove the battery on a laptop if you can do so safely).
2. Remove the motherboard CMOS coin cell for about five minutes, or use the board’s CMOS-clear jumper per the motherboard manual.
3. Reinsert the battery, power on, re-enter setup, set Fast Boot and Secure Boot off again, then retry the USB.

5. Test and reseat RAM

A hard fail before GRUB can also mean a bad stick or channel that never completes basic allocation:

1. Power off and open the case (or access SODIMM slots on a laptop).
2. Remove all modules, clean the contacts, and seat a single stick in the primary slot.
3. Try booting. If it fails, swap to the other stick and try again.

6. Rewrite the Live USB with a minimal writer

Some USB tools preload or memory-map the ISO in ways that crush low-RAM machines before GRUB. Prefer a raw write:

• On Windows, use Rufus in DD Image mode.
• On Linux, use dd to write the ISO straight to the device.
• BalenaEtcher is also fine: it writes the raw image without a heavy memory-mapped ramdisk layer.

Avoid Ventoy (or similar) with default settings on very low-RAM hardware until you have ruled out Fast Boot, Secure Boot, and a clean Rufus DD write.

Once GRUB appears, continue with the normal path in the install guide.

Steam shortcut missing after install or reset

If you install Steam using the provided link and the desktop shortcut is gone after a reset, you are usually hitting an account-level permissions bug. The steam.desktop entry under your user applications folder can end up wrong or incomplete for that account.

Fix it by deleting the broken entry, writing a clean one, making it executable, refreshing the desktop database, then restarting so the menu picks it up.

Step 1: Remove the broken shortcut

To delete the existing steam.desktop file so you can start fresh, run this command in your terminal:

rm ~/.local/share/applications/steam.desktop

Once you have deleted it, recreate it with the clean configuration below.

Step 2: Write a clean steam.desktop

Open the file again:

nano ~/.local/share/applications/steam.desktop

Clear out whatever is currently in there (or overwrite it) so it matches this exact configuration:

[Desktop Entry]
Name=Steam
Comment=Application for playing games
Exec=steam %U
Icon=steam
Terminal=false
Type=Application
Categories=Network;Game;

Save with Ctrl + O, press Enter, and exit with Ctrl + X.

Step 3: Make it executable and refresh

Run these two commands in your terminal to ensure permissions are set and the desktop registers the application:

chmod +x ~/.local/share/applications/steam.desktop
update-desktop-database ~/.local/share/applications/

Restart the system, then press the Super (Windows) key, search for Steam, and it should show up properly in your menu.

Snipe Browser shows as Chromium in the taskbar

Sometimes Snipe Browser appears in the taskbar as a generic Chromium window title or icon treatment. Snipe Browser is a Chromium fork (Ungoogled Chromium based), and this is a known quirk of that lineage. It does not mean you launched the wrong browser, and it does not mean telemetry returned.

The application is still Snipe Browser: uBlock Origin compiled into the core, local-only password storage, Google services stripped from the binary. If the taskbar label looks off, treat it as cosmetic. Closing and reopening the window, or logging out and back in, often clears the odd label for that session.

Install tips worth repeating

• If the machine never reaches GRUB, disable Fast Boot and Secure Boot first. See Freeze before GRUB.
• A long pause near 6 percent during Calamares is normal. Do not power off.
• If a live session feels tight on RAM, the installed system will still feel lighter on the same machine.
• For colour-critical work in Darktable, Kdenlive, or Scribus, disable Redshift for the session.
• Wi-Fi support follows upstream Ubuntu 26.04. Prefer Ethernet for the install if your chipset is exotic.

More context on why the installer behaves this way lives in the install guide and the download page.