You can install Pulsar on Ubuntu 26.04 LTS in three practical ways: the official .deb package, the Flatpak from Flathub, or the portable AppImage. For most people the .deb is the cleanest choice. Flatpak suits anyone who wants sandboxing, and AppImage suits locked-down machines where you have no root.
Why Pulsar Still Matters
Atom was shut down, and a lot of developers quietly moved on to VS Code. Some never felt at home there. Pulsar is the community-led continuation. Flathub describes it as a fork of the discontinued Atom editor and a “hyper-hackable” text editor. If you liked Atom’s packages, its CSON config files, and the way you could rewrite the editor from inside the editor, Pulsar is the obvious place to go.
Ubuntu 26.04 LTS, codenamed Resolute Raccoon, shipped on April 23, 2026 with Linux kernel 7.0 and GNOME 50. The 26.04.1 point release landed later, with ISO images dated August 26, 2026. That point release matters if you manage servers or fleets. Many teams wait for the first point release before upgrading, and as of today (October 31, 2026) that wait is over.
Here is the catch. A new LTS often breaks small things on the desktop that older tutorials never mention. Electron apps are the usual victims. Pulsar is built on Electron, so it inherits every quirk of sandboxing, display servers, and shared libraries. A guide written for Ubuntu 22.04 or 24.04 can leave you staring at a blank window or a cryptic sandbox error.
This guide covers each install method and the reasoning behind it. It also covers the failures you are most likely to hit on a fresh 26.04 install. The commands assume a standard Ubuntu desktop with sudo access. Where Debian or AlmaLinux behave differently, that is called out.
Check Your System First
A two-minute check saves a long troubleshooting session later. Start by confirming what you are running.
lsb_release -a
uname -m
echo $XDG_SESSION_TYPEThe first command should report Ubuntu 26.04. The second tells you the CPU architecture. The third tells you whether you are on Wayland or X11. GNOME 50 on Ubuntu 26.04 is the Wayland era, so expect wayland here. That detail matters later for font rendering and scaling.
Architecture decides which download you need. Pulsar publishes builds for Linux on both Intel/AMD (x86_64) and ARM64. Homebrew’s cask listing, for example, shows separate artifacts for each, with version 1.133.0 as the current one at the time of that listing. Flathub also lists both x86_64 and aarch64. If uname -m prints aarch64, grab the ARM build and do not try to force the x86 one.
Ubuntu’s release notes say the desktop needs a 2 GHz dual-core processor, 6 GB of RAM, and 25 GB of storage for a comfortable experience. Pulsar itself is lighter than that, but it is still an Electron app. Budget about 300 to 600 MB of RAM for an idle window with a handful of packages, and more with large projects open.
Update the system before installing anything:
sudo apt update
sudo apt full-upgrade -y
sudo apt install -y wget curl ca-certificatesWhy full-upgrade rather than plain upgrade? Because on a young LTS, dependency changes between point releases sometimes need new packages pulled in. full-upgrade allows that. On a production workstation, read the proposed changes before pressing Enter.
Method 1: Install the Official DEB Package
This is the method most readers should pick. A .deb integrates with the desktop menu, registers file associations, puts a pulsar command on your PATH, and lets apt resolve dependencies for you.
Download the package
Open the Pulsar download page or the project’s GitHub releases page and pick the .deb that matches your architecture. Release file names follow a pattern like Linux.pulsar_1.131.1_amd64.deb, as seen on a third-party mirror listing. Version numbers move quickly, so do not copy an old file name blindly. Check what is current.
If you prefer the terminal, set the filename yourself once you know the version:
cd ~/Downloads
VER="1.133.0"
wget "https://github.com/pulsar-edit/pulsar/releases/download/v${VER}/Linux.pulsar_${VER}_amd64.deb"If that URL returns a 404, the asset name has changed or the version number is wrong. Open the releases page in a browser and copy the real link. Guessing URLs in a script is how install automation breaks six months later.
Install with apt, not dpkg
sudo apt install ./Linux.pulsar_${VER}_amd64.debThe ./ matters. Without it, apt looks for a package named that in its repositories and fails. Using apt install instead of dpkg -i means missing dependencies get fetched automatically. With dpkg -i, you often end up with a half-configured package and have to run sudo apt -f install to clean up.
Verify the install
which pulsar
pulsar --version
dpkg -l | grep -i pulsarLaunch it from the Activities overview, or from a terminal:
pulsar &The trailing & returns your shell prompt. Without it, the terminal stays attached to the editor process.
A practical note on updates
A manually installed .deb does not update itself through apt upgrade. You will need to download newer packages as they appear. Some admins find that irritating. Others like it, because an editor that never changes under you is one less variable on a work machine. Set a calendar reminder if you want to stay current, or choose Flatpak below.
Method 2: Install Pulsar with Flatpak
Flatpak gives you a sandbox and independent updates. The Flathub listing for Pulsar is dev.pulsar_edit.Pulsar.
Ubuntu does not ship Flatpak enabled by default, so set it up first:
sudo apt install -y flatpak
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepoLog out and back in afterward. The session needs to pick up the new Flatpak export paths so that app launchers show up. Skipping this is a classic reason people think the install failed.
Now install the editor:
flatpak install flathub dev.pulsar_edit.PulsarRun it:
flatpak run dev.pulsar_edit.PulsarThe trade-off nobody mentions
A sandbox is great for security, but a code editor is a tool that wants to touch everything. Inside Flatpak, Pulsar may not see your compilers, language servers, or git configuration the way a native install does. A package that shells out to node, python3, or gcc may fail because those binaries do not exist inside the sandbox.
Check which permissions the app has:
flatpak info --show-permissions dev.pulsar_edit.PulsarIf you work in directories outside your home folder, grant access deliberately:
flatpak override --user --filesystem=/srv/projects dev.pulsar_edit.PulsarKeep overrides narrow. Granting --filesystem=host defeats most of the reason for choosing Flatpak. For anyone running language servers, linters, and build tools from inside the editor, the native .deb is usually less painful.
Method 3: Run the AppImage
AppImage means one app in one file. The AppImage project describes it as something you can download and run without a package manager, without altering system libraries or preferences. That makes it the best option for a shared machine, a locked-down workstation, or quick testing of a newer build before you commit to it.
mkdir -p ~/Applications
cd ~/Applications
wget "https://github.com/pulsar-edit/pulsar/releases/download/v1.133.0/Linux.Pulsar-1.133.0.AppImage"
chmod +x Linux.Pulsar-1.133.0.AppImage
./Linux.Pulsar-1.133.0.AppImageThe chmod +x step is a deliberate Linux safety feature. A downloaded file is not executable until you say so. The same source also warns that AppImages are usually not verified by others, so only run ones from a developer you trust. That is sound advice. Always download from the official release page, and compare checksums if the project publishes them.
The FUSE problem on modern Ubuntu
Here is the first real 26.04 gotcha. AppImages of this style rely on FUSE 2 to mount themselves. Newer Ubuntu releases do not install the old library by default, and the package name changed during the 64-bit time_t transition. If the AppImage refuses to start with a FUSE error, install it:
sudo apt install -y libfuse2t64On Ubuntu releases before 24.04 the package was simply libfuse2. If libfuse2t64 is not found on your system, run apt search libfuse2 to see what your release calls it. Package names shift between releases, and it pays to check rather than trust memory.
If you cannot or will not install FUSE, extract the image and run it directly:
./Linux.Pulsar-1.133.0.AppImage --appimage-extract
./squashfs-root/pulsarThat works with no FUSE at all. It uses more disk space, but it is reliable.
Create a desktop launcher
An AppImage does not appear in the app grid by itself. Create a launcher file:
mkdir -p ~/.local/share/applications
cat > ~/.local/share/applications/pulsar-appimage.desktop <<'EOF'
[Desktop Entry]
Name=Pulsar
Exec=/home/YOURUSER/Applications/Linux.Pulsar-1.133.0.AppImage %F
Type=Application
Terminal=false
Categories=Development;TextEditor;
StartupWMClass=Pulsar
EOF
update-desktop-database ~/.local/share/applicationsReplace YOURUSER with your actual username. Desktop files do not expand $HOME reliably in every launcher, so spell out the full path. Use a version-free symlink such as ~/Applications/Pulsar.AppImage if you want to avoid editing the file at every upgrade. Homebrew’s cask, for instance, uses that naming convention for the same reason.
Fix the Sandbox Error on Ubuntu 26.04
This is the problem you are most likely to hit. You launch Pulsar and nothing appears. Run it from a terminal and you see something like:
The SUID sandbox helper binary was found, but is not configured correctly.or
FATAL:setuid_sandbox_host.cc ... No usable sandbox!Why does it happen? Since Ubuntu 23.10, AppArmor restricts unprivileged user namespaces by default. Chromium-based apps, including Electron, use user namespaces for their sandbox. Under the restriction, the sandbox cannot start unless AppArmor has a profile that allows it. Ubuntu ships profiles for popular apps, but not for an AppImage sitting in your home directory.
The .deb install usually fares better because it sets up the helper binary with the right permissions. If you used AppImage and hit this, you have three options, in order of preference.
Option A: Write a narrow AppArmor profile
Create the file as root:
sudo tee /etc/apparmor.d/pulsar-appimage >/dev/null <<'EOF'
abi <abi/4.0>,
include <tunables/global>
profile pulsar-appimage /home/*/Applications/*Pulsar*.AppImage flags=(unconfined) {
userns,
include if exists <local/pulsar-appimage>
}
EOF
sudo apparmor_parser -r /etc/apparmor.d/pulsar-appimageThis grants user namespace permission only to that path pattern. It is far safer than loosening the whole system. Adjust the path if you keep the file somewhere else.
Option B: Use the .deb or Flatpak instead
Honestly, this is the fix to pick on a work machine. Moving to a packaged install avoids the profile maintenance entirely.
Option C: Launch with –no-sandbox
./Linux.Pulsar-1.133.0.AppImage --no-sandboxThis works, but it turns off a real security layer. A code editor opens untrusted files, renders Markdown previews, and runs community packages. Disabling the sandbox for that is a risk. Use it for a quick test, then move on to Option A or B.
Avoid the blunt system-wide fix of setting kernel.apparmor_restrict_unprivileged_userns=0 via sysctl. It works, but it removes a protection for every application on the box. On a shared or internet-facing system, that is a poor trade for one editor.
Wayland, Scaling, and Font Rendering
GNOME 50 means Wayland is the main path. Pulsar is Electron-based, and depending on the Electron version it bundles, it may default to XWayland. The symptoms are blurry text on HiDPI screens, odd window scaling, or a cursor that looks the wrong size.
Try native Wayland with Chromium’s hint flag:
pulsar --ozone-platform-hint=autoIf the result looks sharper and input behaves, make it permanent. For a .deb install, copy the desktop file and edit it locally so package upgrades do not overwrite your change:
cp /usr/share/applications/pulsar.desktop ~/.local/share/applications/pulsar.desktop
sed -i 's|^Exec=\(.*\)pulsar|Exec=\1pulsar --ozone-platform-hint=auto|' ~/.local/share/applications/pulsar.desktop
update-desktop-database ~/.local/share/applicationsCheck the result with grep Exec ~/.local/share/applications/pulsar.desktop. If the Exec line has multiple arguments or a %F placeholder, confirm the sed expression did what you expected before relying on it.
Some builds do not behave well under native Wayland. If you get a black window, flickering, or broken IME input (common for people typing in Indonesian, Japanese, or Chinese input methods), go back to the default. A working XWayland session beats a broken native one.
For blurry fonts at fractional scaling, there is no universal answer. Try integer scaling at 200% and then shrink the editor font size, or adjust the font size inside Pulsar’s settings. It is clumsy, but it behaves predictably.
First Launch Configuration
Once Pulsar starts, a few early decisions pay off.
Open Settings with Ctrl+,. Under Editor, set tab length and soft tabs to match your projects. For teams, an .editorconfig file at the repo root is better than personal preferences. Install the editorconfig package and let the project decide.
Pulsar keeps its data in ~/.pulsar. Learn the layout:
ls -la ~/.pulsarYou will find config.cson (settings), keymap.cson, styles.less, init.js, and a packages directory. Back up this folder, or track it in a dotfiles repository. When a laptop dies, restoring ~/.pulsar brings back your entire environment in minutes.
Managing packages from the terminal
Pulsar ships with a package manager command, ppm. List installed packages and install new ones:
ppm list --installed --bare
ppm install file-icons
ppm install minimapWhy use the CLI over the GUI? Scripting. If you provision developer machines, a one-line loop reproduces your setup:
while read -r p; do ppm install "$p"; done < ~/pulsar-packages.txtGenerate that list with ppm list --installed --bare. Keep it in version control next to your dotfiles.
A word on package choice: Atom-era packages that have been unmaintained for years can break on recent Electron versions. Look at the last commit date and open issues before installing. The Pulsar community has rewritten or replaced many abandoned packages, so there is often a maintained alternative with a similar name.
Troubleshooting Common Errors
These are the problems that come up most often on fresh Ubuntu installs, with the cause behind each.
Nothing happens when launching. Start from a terminal and read the output. Silent failures are almost always a sandbox or library issue. Try pulsar --safe to start without community packages and your custom config. If it launches in safe mode, a package or a corrupt init.js is the culprit.
“dpkg: dependency problems prevent configuration.” You used dpkg -i. Fix with:
sudo apt -f installNext time, use sudo apt install ./file.deb.
Library not found, such as libnss3.so or libgtk-3.so.0. A shared library is missing. Install the common Electron dependencies:
sudo apt install -y libnss3 libgtk-3-0t64 libxss1 libasound2t64 libgbm1Note the t64 suffixes. On Ubuntu 24.04 and later some library packages were renamed for the time_t transition. If apt says a name is not found, use apt search to find the current one. On AlmaLinux or Fedora-family systems the equivalents are nss, gtk3, libXScrnSaver, alsa-lib, and mesa-libgbm.
Black or white window. Usually GPU related. Test pulsar --disable-gpu. If that helps, update graphics drivers. If you are on Wayland, also try dropping the Ozone flag.
Corrupted settings after a crash. Move the config aside rather than deleting it:
mv ~/.pulsar ~/.pulsar.bak
pulsarYou get a clean slate and still have the old files to copy back selectively.
ppm install fails with node-gyp errors. Some packages compile native modules. Install the build toolchain:
sudo apt install -y build-essential python3 make g++If it still fails, the package may not support current Electron. Look for a maintained fork.
Cannot save files, permission denied. Check ownership with ls -l. If a project directory was created by root through a Docker volume or a sudo command, fix it with sudo chown -R $USER:$USER /path/to/project. Do not “fix” it by running the editor as root.
Flatpak version cannot find tools. Expected, as covered earlier. Either grant filesystem permissions, use the host-spawn approach, or switch to the .deb.
Duplicate icons or no icon in the dock. The StartupWMClass in the desktop file does not match the window class. Run xprop WM_CLASS on X11, or check Looking Glass in GNOME on Wayland, then correct the desktop file.
