Guides 11792 Published by Philipp Esselbach 0

This guide shows how to install Visual Studio Code on Linux Mint Debian Edition 5 (“Elsie”) by using Microsoft’s official .deb package, which fits the Debian‑12 base of LMDE and avoids the extra overhead of Snap or Flatpak. It walks through downloading Microsoft’s signing key, adding a signed repository entry, updating APT and installing the “code” meta‑package while handling common missing‑library problems with apt --fix-broken or manual lib installs. The article also explains how to keep VS Code up‑to‑date automatically via the added repo (or unattended upgrades) and offers a fallback method of downloading the .deb directly and installing it with dpkg if the repository is unavailable. Following these steps gives you a fully functional, regularly updated VS Code installation on LMDE 5 with minimal configuration hassle.

Guides 11792 Published by Philipp Esselbach 0

The guide explains how to add Microsoft’s repository and signing key to a fresh LMDE 5 installation, then use APT to install the PowerShell package and verify it with pwsh -Version. It highlights why PowerShell may be needed on LMDE—particularly for scripts that depend on Windows‑specific modules—and notes common issues such as missing libssl1.1 dependencies. Optional steps include making PowerShell the default login shell via chsh, while recommending against Snap installations due to performance overhead. Finally, it points out that once the repository is configured, future updates will be handled automatically through regular apt upgrade commands.

Guides 11792 Published by Philipp Esselbach 0

The guide walks through installing VSCodium—a fully open‑source, telemetry‑free fork of Visual Studio Code—on Linux Mint Debian Edition 5 (the “Elsie” spin) by using the official apt repository so updates are handled automatically. It begins with a system update, then imports the project’s GPG signing key and adds a signed‑by entry to a new source list file before refreshing the package index and installing the “codium” package. The article also covers typical hiccups such as a missing libsecret‑1‑0 library after kernel upgrades or conflicts with an existing VS Code Snap, providing simple reinstall or removal commands to resolve them. Finally, it shows how to point VSCodium at the Open VSX extension marketplace and verifies the setup by launching the application.

Guides 11792 Published by Philipp Esselbach 0

The guide walks you through installing Opera on Linux Mint Debian Edition 5 using the official .deb package instead of a snap, which keeps the installation lightweight and integrates with the system’s update mechanism. It shows how to download the deb, pre‑install required libraries (e.g., libpangocairo‑1.0‑0, libnss3, libatk‑bridge2.0‑0), install the package with dpkg, and resolve any remaining dependencies via apt --fix-broken. It also explains how to verify the installation, add Opera’s repository for automatic upgrades, and troubleshoot common issues such as missing graphics drivers or sandbox initialization failures (the latter can be bypassed temporarily with opera --no‑sandbox). By following these steps you get a fully functional Opera browser on LMDE 5 without pulling in unnecessary extra packages.

Guides 11792 Published by Philipp Esselbach 0

The guide explains how to replace Pop!_OS 22.04’s default kernel with a performance‑focused XanMod build by adding the official XanMod repository, importing its GPG key, and installing the desired variant (typically xanmod‑lts). After refreshing the package index, you install the kernel package, rebuild initramfs for systemd‑boot, and reboot to confirm the new kernel version with uname -r. It warns that mixing kernels can render the system unbootable, so keeping a known‑good entry in the boot menu and knowing how to revert by selecting an older entry and purging XanMod is essential. Finally, it notes you may need to reinstall DKMS modules (e.g., NVIDIA drivers) after the switch and to monitor future kernel updates for compatibility.

Guides 11792 Published by Philipp Esselbach 0

The guide shows how to get Git up and running on a fresh Fedora 36 system by using the native DNF package manager. It walks through installing git with sudo dnf install git, verifying the installation via git --version, and setting your global user name and email so commits are properly identified. It also covers a common “missing libcurl” error—fixed by reinstalling git and curl—and notes an optional way to pull newer pre‑release builds from the updates-testing repository. Following these steps leaves you with a fully functional, DNF‑managed Git ready for committing and collaborating.