live-usb-maker tool now available as an AppImage

For those non-MX or non-antiX linux users who might need to write iso images to USB sticks, we now have the joint antiX/MX live-usb-maker tool available as an AppImage. The tool has been tested on Manjaro, Debian buster and stretch, arch, Porteus, gentoo, xubuntu and ubuntu. You can use it to make a “disc-on-a-stick” similar to etcher, and if you happen to be making a antiX/MX family live-usb, you can use the “full-featured” mode as well to be able to access our persistence features right on the first boot of your live-usb!

Many thanks to all the testers and to adrian (gui) & BitJam (live-usb-maker backend) for their help in getting the AppImage running.

The 64bit-only AppImage (sorry , no 32 bit) is available here:

Download the archive file containing the AppImage, extract to a folder, enter that folder, and use

sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage

to run the AppImage.

There is a known issue in that the help button does not work from the AppImage. An online version of the help is available here:

55 thoughts on “live-usb-maker tool now available as an AppImage”

    • quote: Hmm not very beginner or user friendly? Also the appimage has to be chmodded right? Could there be a Flatpak rather?

      That depends on your perspective. the AppImage is meant to run on the widest array of systems possible, requires no preinstalled daemons like flatpak or snaps, and doesn’t even require gksu or pkexec to be present for authentication. Even if a user was a hardcore debian user with no sudo available, the appimage can still be run by the root user as well.

      as for needing to chmod, usually its true that AppImages require that. However, in this case, the AppImage executable bit is preserved inside the archive file that the AppImage is packaged in. I figure its far more likely a that even a new linux user will be able to extract from an archive than know about the necessity to chmod an AppImage.

      • Sorry, it’s just too complicated. It is evident even in ur long reply! The developers often cannot see the point of view of a regular “normal” user.

        For instance Snaps are one click installs. The way it should be. Really! Appreciate MX and your work full on though!

        • With AppImage you don’t have to install (I suppose Snap must be installed, as well as Flatpak) – just run with one click and use.

          It is like portable version for some programs in Windows.

          When I try new software or newer versions of programs I prefer AppImage files – it’s quick and easy, download and try – if I don’t like it, I just delete it, no need for uninstalling.

        • Seems like pretty basic stuff, not that complex. I run MX at home and really like it but have been running Debian 10.1.0 at work so that I’m forced to learn. Don’t be afraid of the command line interface. It’s very powerful! Thanks guys for all of the great work.

        • Trish, as a Linux (and MX Linux) newbie, I can confirm your concern for folks like me! I have MX Linux on a smaller laptop that benefits from the smaller MX footprint and the MX Live USB Maker tool is a great one to have. But I also have Linux Mint installed on another laptop that has enough RAM to use the Cinnamon DE and I was hoping that the availability of this tool would make it easy to create the same for other distros. I downloaded the file, extracted it…and then when I double-clicked on that I got “Must be run as root.” Huh? That’s probably very basic stuff for a lot of Linux users….probably easy to accomplish via some sequence of commands in Terminal. But it’s enough to dissuade me.

          • You need root access to write to the partitions on any device connected by design on linux. Even if it was a snap or flatpak you wuld still need to entero your root/sudo password or the software would nota work.

          • For ten years I follow command line instructions like a cookbook. I get a distro of linux running. I eventually break it when I try to update something (most recently NVIDIA drivers) and then the command line is a foreign language to me again. I shudder at tar balls. I don’t know where to put them and how to open them. There is always some strange magic command with xyz and I have no understanding on why I’m being instructed to type the incantations mentioned. And yet through all of this, I still greatly prefer Linux to any other OS.

          • here’s the thing (coming from a near newbie) — it’s not too much to ask a total Linux newbie to explore enough to know what the message “Must be run as root” means, and, how to change from user to root. It’s so fundamental to the logic and systematic of Linux. I’ll liken it to having learn that you press the start button on many a newer, keyless car, with the brake petal depressed; vs inserting a key in the older-style ignitions, turning it, but with the car in Park in most cases. I conclude in jest with the slightest of puns: get with the program. In this case learn at the very least su and sudo … there are many short simple videos explaining these very basics

          • David, this is the first time ever I have seen an AppImage require ROOT. However this is a Good thing and 2000 times easier than you think.

            Open Terminal and just type: sudo (and press space once to leave a space next to it)
            then drag the AppImage into the terminal and press ENTER! and Password after. Whalla!

        • Trish…I mean this Nicely…but you are about 3 Billion Percent Wrong about AppImages. I never in my entire life of using Computer ever ever seen anything easier to install than AppImage….You were told wrong and are using it wrong.

          Let me show you how to install and AppImage:

          1. Download (everything regarldess has to be, wether SNAP, FLatpak, .deb etc)
          2. Just drag to the folder you want it in unless during download you chose already
          3. Rightclick the AppImage and select PROPERTIES then Permissions tab and Check where it says: Allow Executing File As Program (to the right of Execute: option)

          Thats it! NO terminal commands to remember ever! and to uninstall? just drag to trash……to install on a another computer? Just drag it onto t usb and to the computer!

          This means you can have previously downloaded 500 apps in AppImage format, and installed 500 Apps on someones computer in a matter of seconds!

          Not only that…if you downloaded a Newer Version of the same App for its new features, but still like the old one, you can have both in the folder and use them interchangeably. I have like 5 versions of ShotCut video Editor all as AppImage.

          it does not get easier Trish.
          plus you know where it is stored and what it is doing moreso than FLatpak or SNAPS which are spread out through your system. and Require about 1gb of predownload. Hell No!

          • Agreed!

            Step 3, changing permissions is not even needed when it’s packaged in an archive that understands permissions, like the MX Linux package. I just downloaded the package, extracted using the default GUI program, and ran the AppImage.

            And to expand on snap, it annoyingly creates an unhidden directory under the home directory. That is simply wrong!

        • Trish, um… and every Linux user in here who seem to think you EVER need to CHMOD to open an Appimage: You NEVER EVER EVER need to do that. Just RIGHT click the Appimage and select: Make Executable in the Permissions tab, DEFINITELY easiet than Flatpak or SNAP.

    • In Linux Mint Mate it’s possible to right click on the downloaded tar.gz package and choose Extract here. Then you right click on the extracted App image and choose Run as Administrator. Type in your password in the dialog box and Live Usb Maker will start.

      No need to make it executable, since that’s already enabled by default. But for App images that aren’t executable by default, all you have to do in Linux Mint is right click on the App image and go to Properties and then click on the Permissions tab and check Allow executing file as program.

  1. Good idea, as AFAIK ubuntu usb installer lost a lot of functionality, so users can judge firsthand how much mx is ahead in terms of live/installing tools.

    • yep, its baked right in. just make the live usb with our live-usb-maker tool or use something like rufus. things like dd and etcher make a readonly device, which obviously don’t work with persistence. I just finished a video series on the live features available in MX (and antiX) on my youtube channel

  2. Hi, but this fails like this:

    ssudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage
    ./live-usb-maker-qt-19.11.02.x86_64.AppImage: 1: ./live-usb-maker-qt-19.11.02.x86_64.AppImage: Syntax error: “(” unexpected

  3. I create this tool in Kde Neon and when i try to execute i get this error : You may run this as root and i can;t find a way to do that. Any help?

    • sometimes. persistence is set up by the live system on first boot, so as long as your file system is writable, you should be OK. unetbootin depends on the host system’s sysVinit, so as long as your sysVinit is new enough, it should work.

  4. Seems a shame that you need to start a GUI from the command line. Is it not possible to make it prompt for the SU password like the built in app?

  5. I used YUMI (Win7 1GBram ASUS 1005PE)
    to put MX (latest 19.1) on 128G SD card.
    Boots ok. *HOW* (pref cli) do I *add* persistence
    (to the LIVE RUNNING SD card)??? TiA!

  6. Kto te bzdury pisze? Jak wykonuje się te komendy i polecenia, to nic nie działa. A mówią, że Linux jest przyjazny, prosty i nie wymaga dużo zasobów sprzętowych. Śmiech na sali. Pozdrawiam

    • I write this nonsense. If it doesn’t work for you, sorry. appimages have turned out to not be quite as universal as they advertise. they still expect some set of libraries to be on the host system.

      but there have been a lot of reports of success, so not a total nonsense anyway.

    • You know, not every single system should be beginner friendly. There are dozens of those and more advanced users like myself need a system too! This MX thing may not be “beginner friendly” but it’s perhaps the most “user friendly” for a user like me, because it’s *not* dumbed down to the beginner level.

      Most things in my experience get dumbed down over time because beginners put pressure on every system and program, and the result is that a user like myself needs to constantly change to different programs because “user friendly” programs always hide and lack important things and severely limit user freedom. There’s nothing friendly about that for some of us.

      So pleeeease leave this one alone, and go with something else that’s “beginner friendly” by your standards.


  7. “Must be run as root.” ? HOW? probably very basic stuff for a lot of Linux users….probably easy to accomplish via some sequence of commands in Terminal. But it’s enough to dissuade me.

  8. link not works:
    Looks like something went wrong!

    We track these errors automatically, but if the problem persists feel free to contact us. In the meantime, try refreshing.

  9. I have a dozen or so appimages on my Mint 19 box running fine. However your Live USB maker throws an error:

    QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-root’
    Failed to connect to bus: No such file or directory

  10. Debian Buster results:
    sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage
    ./live-usb-maker-qt-19.11.02.x86_64.AppImage: 1: ./live-usb-maker-qt-19.11.02.x86_64.AppImage: Syntax error: “(” unexpected

  11. sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage No such command found. I tried to run this on Mint 20, any idea why I got that error?

    • @Quinton or others similarly affected with ‘Command Not Found’ and sudo GUI integration issues

      EDIT: apologies for absent reply

      @admin : some PatchStack-PHP-Firewall ‘Error Code 5516’ thing blocks my helpfully informative and elegant submission; you need code tags; what a waste of my time that was, composing a nice long full reply, offering suggestions for alternative integrated strategies; well okay, so be it: composition deleted.

      @admin : oh, and BTW, well done for removing the systemd tentacles from MX – now please remove from your site the GOOGLE TENTACLES too – looking at you, reCAPTCHA

  12. First time using Linux, and I managed after 20 mins , it seems daunting at first once extracted I opened terminal and ran sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage typed password done.

  13. tar ball downloaded then extracted then entered folder. right click – root actions – open in Konsole and the output was:
    # sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage
    sudo: ./live-usb-maker-qt-19.11.02.x86_64.AppImage: command not found

    OS Manjaro 64-bit

    trying to make bootable USB suggestions greatly appreciated.

  14. Tried to run it on Linux Mint 17.2. Gives me
    live-usb-maker-qt: /usr/lib/x86_64-linux-gnu/ version `CXXABI_1.3.9′ not found (required by /tmp/.mount_live-uQ5hxtN/usr/lib/x86_64-linux-gnu/
    and 5 similar error messages. Anything Qt hates me 😉 I thought the thing of AppImages is, that they contain all to run the app?

  15. Hi all,
    if using the terminal is too hard for you, simply right click the app image you extracted and choose, “Open as Administrator” or whatever your unit says.

    So simple that even i worked that out!!

    Thanks folks for the good work!

  16. Debian 11, sudo ./live-usb-maker-qt-19.11.02.x86_64.AppImage
    sudo: /etc/sudo.conf is owned by uid 65534, should be 0
    sudo: /usr/bin/sudo musi mieć uid 0 jako właściciela oraz ustawiony bit setuid

    Debian 11 this command does not work and the menu does not open as administrator.

  17. I would be VERY useful if it would require root only when writing the iso.
    In my case I use Appimagelauncher and I can’t start the appimage as root.


Leave a Comment

MX Linux