English
Chinese (Simplified)
Dutch
French
German
Italian
Polish
Portuguese
Russian
SpanishRunning snap packages (snaps) is problematic on our default MX setup because of a couple of factors.
- snapd (the snaps backend) requires systemd and we use sysVinit by default
- snapd confinement doesn’t like the symlink we use to link /tmp to /var/tmp.
If you boot into systemd instead of the default sysVinit, you should be able to run snaps: when the GRUB screen is displayed on boot, click on Advanced options… and select to use systemd. You may also need to change the user’s PATH-variable to include /snap/bin
v. 20190428
4 thoughts on “Snap packages and MX Linux”
Check /etc/profile.d/apps-bin-path.sh there should the /snap/bin path defined, so a reboot will load it
is this were you extract-grab apps from for anbox
Has this been updated further? Can snaps safely be ran on the latest update?
I run snaps all the time, you just need to be running systemd.
I’ve only run across one snap that is problematic, and that’s telegram-desktop. I currently use the flatpak for that, and have chromium and xonotic snaps. (the chromium flatpak doesn’t work).
I have a video on snaps and mx on my youtube channel.