Wiki Table of Contents

Snap packages and MX Linux

Running snap packages (snaps) is problematic on our default MX setup because of a couple of factors.

  1. snapd (the snaps backend) requires systemd and we use sysVinit by default
  2. 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

7 thoughts on “Snap packages and MX Linux”

    • 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.

  1. Is MX19 now supporting a fully systemd compliant version?

    One of the reasons I’m migrating most of my systems from Ubuntu, to MX19 is because I don’t want to be dependent on a core-system which — in my view — amounts to an attempt to establish third-party hegemonic control over the otherwise open architecture defined by Linux. My understanding of the way the MX19/AntiX developers have attempted to partially accommodate the demands of systemd, has been to provide some ‘shims’, over which they have complete control, and which enable a strictly limited subset of systemd support. (Are there any docs explaining the details of the hybrid systemd compatibility mode?)

    If I modify the GRUB settings as described above, can I revert back to the SysVinit GRUB configuration, and if so, how will that affect a) snaps, and b) any other aspects of the original MX19/SysVinit install.(?)

    PS:Thanks to MX19/AntiX for this outstanding collaborative distro, and exceptionally useful supoort community.

    • if you want to use snaps, you have to use systemd. but otherwise systemd is option on MX and not used at all on antiX. antiX can’t use snaps at all. but flatpak devs didn’t make their stuff depend on systemctl/systemd, so you aren’t missing much given that software in flatpaks is plentiful.

      basically the shim allows certain daemons, like system-logind, to operate without systemd being at PID 1. antiX uses the elogind system, which doesn’t rely on systemd at all.


Leave a Comment

MX Linux