FAQ

Installation

Why is XFCE the only available option in the live environment?

XFCE is considered our “flagship” desktop environment and receives the most maintenance. Other Gnoppix ISO variants were not maintained to the same standard, so we focus our efforts on delivering the best experience with XFCE.

We recommend installing Gnoppix in a VM for testing different desktop environments and window managers, as the live ISO is primarily used for installation and system recovery.

Since we do not currently have community maintainers for other desktop environments, those images are reserved exclusively for Gnoppix members until contributors step forward.

Caution

Installing Gnoppix on older Apple Macs will not work out of the box.

When starting the gnoppix installer nothing seems to happen?

Caution

Make sure you have an active internet connection, otherwise nothing will happen after pressing this button.

While it may seem like nothing happened, a preparation script runs in the background to avoid issues such as an outdated keyring.

The script performs the following steps:

1. Removes the existing keyring file found in /etc/apt/trusted.gpg.
2. Updates Gnoppix keyring packages.
3. Enables network time synchronization via timedatectl set-ntp true.
4. Determines if the system type is UEFI or BIOS/MBR.
5. If UEFI, prompts the user to select a bootloader.

This is why the installer takes a moment to load.

My installation got stuck at 33% for a while.

This means your internet connection is either slow or unstable, causing the package manager to struggle when downloading packages.

Software management

”unable to lock database” error

sudo rm /var/lib/apt/lists/lock

Tip

You can also use the “Remove lock” function in Gnoppix Hello under the Apps/Tweaks tab.

File is corrupted (invalid or corrupted package)

Refresh package lists and fix corrupted downloads

sudo apt update
sudo apt clean
sudo apt install --fix-broken

If issues persist, try reinstalling the package:

sudo apt install --reinstall <package-name>

error: failed retrieving file, The requested URL returned error: 404

# Example
sudo apt install telegram-desktop
Reading package lists...
Building dependency tree...
E: Unable to locate package telegram-desktop

This means your local package database is outdated, or the package name is different in the Debian/Gnoppix repositories.

Run the following to refresh the package database:

sudo apt update
# Then try to install the package again.

How to install software from outside the official repositories?

Gnoppix uses APT (the Debian package manager). If a package isn’t in the official repositories, you can:

• Check if it’s available as a Flatpak: flatpak search <name>
• Download a .deb package and install it: sudo apt install ./package.deb
• Use Snap: snap install <name>

When I try to open Discord, a window opens notifying me of an update

Example:

This is because Discord released an update that isn’t yet available in the Gnoppix repositories.

To work around this issue, download the latest .deb package from the Discord website and install it with:

sudo apt install ./discord*.deb

error: could not remove /var/cache/apt/archives/

Tip

You can clean the APT cache using Gnoppix Hello in Apps/Tweaks > Clear package cache

Example:

This usually appears when there are partial or locked downloads in the APT cache.

Run the following to clean the cache:

sudo apt clean
# Or to remove only partial packages:
sudo apt autoclean

ERROR: module not found: ‘nvidia’, ‘nvidia_modeset’, ‘nvidia_uvm’, ‘nvidia_drm’

Example

==> ERROR: module not found: 'nvidia'
==> ERROR: module not found: 'nvidia_modeset'
==> ERROR: module not found: 'nvidia_uvm'
==> ERROR: module not found: 'nvidia_drm'

Possible causes:

• The NVIDIA kernel modules are not built for your current kernel version.
• You may be missing the NVIDIA driver package for your kernel.

Install NVIDIA drivers:

sudo apt install nvidia-driver firmware-nvidia

GitHub Homepage makes the browser unusable and extremely slow.

• The Gnoppix browser disables WebGL by default for privacy reasons. GitHub depends on WebGL for rendering its homepage.
  • Re-enable it as shown in the screenshot:
    
  • After enabling WebGL, restart your browser and try again.

Your browser is being managed by your organization. Do I need to worry?

• No. This is because we include a policies file that disables certain features and adds modifications such as additional search engines.

Some keyboard combinations are not working in certain websites like Photopea

• This is caused by the privacy.resistFingerprinting feature in Firefox.
  • Follow the screenshot to disable it:
    
  • After disabling this setting, restart your browser and the keyboard combinations should work again.
  • Extra tip: Search for webgl.disabled and set it to false to enable hardware acceleration in Photopea.