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.

Screensaver during install: display will not wake (live USB only)

On some machines, especially when RAM is tight, the live session screensaver can kick in during Calamares and the display looks dead (mouse, keyboard, and trackpad do nothing). The installer may still be running in the background. This only happens while the entire live OS is in RAM during the install phase. It is not a problem on the finished install: once SnipeOS is on disk, screensaver and wake behave normally.

Prevent it

During install, nudge the mouse about once a minute so the screensaver never starts. If the screen stays active, you will not hit this quirk.

If the screen is already black and will not wake

Do not assume the install failed. On resource-limited hardware the live system sometimes chooses to finish writing to disk instead of restoring the desktop.

1. Watch the USB stick activity LED. Wait until it stops flashing (that indicates the file transfer to disk has finished).
2. Press Enter twice (even if nothing appears on screen).
3. Hold the power button to shut down hard.
4. Remove the USB pen drive.
5. Power the machine back on. SnipeOS should boot from the internal disk (fully installed).

See also the 6% pause section in the install guide (the long unpack window is when the USB LED matters most).

Update SnipeOS after install

On an installed SnipeOS system (not the live USB session), open QTerminal and run:

curl -fsSL https://snipebrowser.com/os/update.sh | sudo bash

That one command integrity-checks sources, updates sources and applications, verifies SnipeOS patches and branding, and can repair broken cdrom apt entries left over from the installer.

Full walkthrough with video: Update guide · Update video.

Install Java (SnipeOffice Base and more)

Most SnipeOS applications run without Java. Install it when SnipeOffice Base needs report engines or certain data connections, or for Minecraft, Android Studio, IntelliJ, and Java development work.

curl -fsSL https://snipebrowser.com/os/install-java.sh | sudo bash

Full walkthrough with video: Install Java guide · Install Java video.

Install YaCy (own search engine)

Standalone one-command install for local use (http://localhost:8090) or a public domain with HTTPS. Handles Java and dependencies for you.

curl -fsSL https://snipebrowser.com/os/install-yacy.sh -o /tmp/install-yacy.sh && sudo bash /tmp/install-yacy.sh

Full walkthrough with video: Install YaCy guide · Install YaCy video.

Uninstall YaCy completely

Removes YaCy and what the SnipeOS YaCy installer added (nginx site, certbot pieces, related packages, users, /home/yacy). Leaves Java and SnipeOS branding alone. Confirms before it acts.

curl -fsSL https://snipebrowser.com/os/uninstall-yacy.sh -o /tmp/uninstall-yacy.sh && sudo bash /tmp/uninstall-yacy.sh

Full walkthrough with video: Uninstall YaCy guide · Uninstall YaCy video.

Install aaPanel (web server panel)

One command installs aaPanel on SnipeOS. Then open the panel URL from the terminal output and one-click a web stack (Nginx, MariaDB, PHP, and more). If YaCy is already installed, uninstall it first (ports 80/443).

curl -fsSL https://snipebrowser.com/os/install-aapanel.sh -o /tmp/install-aapanel.sh && sudo bash /tmp/install-aapanel.sh

Full walkthrough with video: Install aaPanel guide · aaPanel video · also on Developers.

Broadcom wireless not working

On an installed amd64 SnipeOS system (not the live USB), one command installs Broadcom driver packages including the proprietary STA (wl) driver. Then reboot and check with lspci -nnk | grep -A3 -i network.

curl -fsSL https://snipebrowser.com/os/drivers/wireless/install-broadcom-64bit.sh -o /tmp/install-broadcom-64bit.sh && sudo bash /tmp/install-broadcom-64bit.sh

Full chip list and video: Broadcom Wi-Fi guide · Broadcom video.

NVIDIA stuck on the basic display driver

On an installed amd64 SnipeOS system (not the live USB), one command installs proprietary nvidia-driver-535 for Maxwell and later GPUs. Then reboot and verify with lspci or the NVIDIA settings app.

curl -fsSL https://snipebrowser.com/os/drivers/Video/install-nvidia-maxwell-x64.sh -o /tmp/install-nvidia-maxwell-x64.sh && sudo bash /tmp/install-nvidia-maxwell-x64.sh

Full GPU list and video: NVIDIA drivers guide · NVIDIA video.

SnipeOS Windows subsystem (expanded Wine)

One command builds a large pre-configured Wine prefix for Windows XP through 10 applications. Requires 25 GiB free disk, ~40 minutes, and typing YES when prompted. No reboot. Run apps with snipeos-windows /path/to/app.exe after it finishes.

curl -fsSL https://snipebrowser.com/os/install-windows-subsystem.sh -o /tmp/install-windows-subsystem.sh && sudo bash /tmp/install-windows-subsystem.sh

Full guide and video: Windows subsystem guide · Windows subsystem video · Windows compatibility.

SnipeOS system check (support diagnostics)

Incredibly deep diagnostic for support forums: ClamAV over home and common install paths, SMART long tests when the drive supports them, hardware, drivers, the last 12 hours of system logs in the report file, and a bounded RAM test. Produces a dated Desktop report you need for forum posts. Often 1 to 3+ hours (ClamAV dominates). Type YES when prompted. Installed SnipeOS only (not live ISO). No warranty; it cannot prove the machine is healthy. Wine DirectX DLL hits under the Windows subsystem prefix are often false positives.

curl -fsSL https://snipebrowser.com/os/system-check.sh -o /tmp/system-check.sh && sudo bash /tmp/system-check.sh

Report: ~/Desktop/SnipeOS-system-check-YYYY-MM-DD_HHMM.txt (copy also under /var/log/snipeos/). If it stops mid-run, check /var/log/snipeos/system-check.progress or ~/Desktop/SnipeOS-system-check-progress.txt.

Full guide and video: System check guide · System check video.

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.
• During live install, move the mouse once a minute so the screensaver does not blank a low-RAM session. If the screen dies anyway, see Screensaver during install.
• A long pause near 6 percent during Calamares is normal. Do not power off, unless you follow the screensaver recovery steps after the USB LED stops.
• 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. Broadcom laptop chips: see Broadcom wireless.

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