Simplicity Linux 20.4 Release

We are pleased to announce the release of Simplicity Linux 20.4. This time there are four versions, all based on the excellent Buster Dog. (https://debiandog.github.io/doglinux/zz03busterdog.html).

First we have Mini, which uses LXDE and Openbox and is running the 5.6.4 XanMod Kernel. As usual with Mini, there isn’t a lot of software preinstalled, instead it uses web based apps which run as a Chrome instance. We have preinstalled Google Docs, Taiga.io Project Management software, Spotify, Mega, Gmail and Facebook Messenger.

For those looking for something with locally based applications, we have Desktop which also uses the 5.6.4 XanMod Kernel. Unlike Mini, it uses Cinnamon as it’s desktop. It comes preinstalled with Pidgin, LibreOffice, GIMP, Chrome, Thunderbird, Audacity, Spotify and MPV.

When we released Simplicity 20.1, we put X Edition on hiatus and replaced it with the experimental Gaming Edition. It seemed quite popular, so we have kept up work on Gaming Edition. It should still be classed as experimental, but we’re planning on making it a stable release for 20.7. Simplicity 20.4 Gaming Edition uses the Debian Backports 5.4.0 Kernel for stability, and comes with Brave Browser, OBS, Discord, Blacknut Cloud Gaming, Vortex Cloud Gaming, Wine, Steam, and Spotify as full local applications.

Lastly there is X Edition. We tried a few different ideas for X, including a hybrid of Gaming Edition and Mini which used minimal local applications and almost everything ran through cloud clients or Chrome Shortcuts. And it’s something we may revisit. Instead we settled on a more fully featured Mini using LXDE and Openbox. It runs the 5.6.6 XanMod Kernel, and comes with Chrome Shortcuts for Gmail, Zoho Docs, Mega, Plan, Buffer, Calendly, Canva, Speechnotes, Evernote, Spotify and Taiga.io Project Management. The idea behind it was that with everyone being stuck at home, some might like the chance to revamp some old hardware for office use.

Downloads:
Mini 20.4
MD5: 79864853e130c6f4f5f4d73cd3b8ab23
Size: 523mb

Desktop 20.4
MD5: f2ac1fa5822f7304993043984c4e0ed2
Size: 1GB

Gaming 20.4
MD5: 51a57c210b052ac64b9d2ff4a3772af5
Size: 1.3GB

X 20.4
MD5: 8d6acb6b33ce97bd6d15a139ac450edc
Size: 533mb

13 thoughts on “Simplicity Linux 20.4 Release

  1. I tried etcher and sudo dd bs=4M if=path/to/Desktop204.iso of=/dev/sdb status=progress oflag=sync but I can’t boot it on my usb

    1. Have you tried changing the BIOS boot mode to Legacy? Some people who have had this problem before have been able to resolve it this way. Hope that helps!

      1. Yes! I tried changing to legacy and stuff. Changed to another USB brand too

        I noticed to desktop iso has a live folder. Should I copy this live folder to the root of the USB Fat 32 formatted drive?

        I tried using etcher, dd and rufus. Would you try to boot on a USB drive to see if desktop.iso works?

        1. Yes, the USB needs to have the live folder in the root of the USB, as this contains the bulk of what Simplicity needs to boot. I will try the Desktop ISO and get back to you.

          1. Bonjour
            J’ai le même probleme avec mini 20.4
            live-usb ne démarre pas
            md5 bon pourtant
            essayé plusieurs logiciels Gnome-disque , etcher

            Merci

          2. Yes, I used unetbootin and put it on an external USB hard drive, and it booted just fine from there.

  2. hi

    I tried to make the Gaming Edition bootable with Balena Etcher on a USB Stick
    I said I would encounter problems when booting….

    And Indeed, it would not boot on my legacy laptop…(Toshiba L670-14RE)

    what’s wrong ??
    thank you

  3. We think alike, but what the X version should be is icewm-session; it’s a window manager, a session manager, a desktop background manager, and a taskbar all for about 15MB of ram total. LXpanel alone is 30MB of ram 🙂 Whenever you can add the word session i.e., icewm-session, it means at minimum that it must include the WM’s autostart and typically it will launch dbus which on a systemd machine would initiate gvfs daemon and alsa. This is why both Tinycore and Antix use it as their default window manager. It looks hideous at first, and takes a while to configure; there’s like 5 or 6 files. The themes under the letters K and I are less hideous. You just have to piggy back off MX repo for the control panel and all the applets therein that make handling icewm a breeze. Likely I will do this myself, we’ll see if your release supports 8822BE. realtek. We’ll also see if you removed GVFS, and put a modern file manager such as pcmanfm-qt (which works without GVFS) or spacefm. The release should move away from gnome dependencies as much as possible, but must have impeccable wireless support. My netbook only has wireless, we’ll see. Pulseaudio should also be absent; merely supports multiple audio streams at the cost of reduced audio quality. We’ll see how you did. What I dislike the most about antiX is how complicated their setup is, and thus more difficult to modify. Also I would screw the login manager on X edition. Also, this may come in handy if you play with Window Managers. I was horsing around with LXQT core, initially combining it with lxpanel but the session manager wouldn’t show modules when launched from lxpanel and pcmanfm-qt wouldn’t show drives likewise; I thought exports were the solution, but I came up with an engenius solution, xinitrc:
    exec startlxqt {Iamgod,lxpanel,lxterminal}
    This forces all information flow of LXQT to be shared with Iamgod, lxpanel,lxterminal thus restoring aforementioned functions. Two things I like about sparky linux are the cli-installer and nmtui. I don’t know why I liked the cli-installer, one tiny mistake and your back to the tty. Well actually, one thing I liked is it didn’t require internet to install unlike you know who. If you had released any later or sooner, I would have likely never come across your release.

  4. Your ISO’s are not proper. Even if you exclude EFI support, there should still be a boot folder at minimum. If extract a sparky linux iso, you got 4 extra folders:
    [BOOT]
    boot
    EFI
    offline

    There offline folder is not required. Im not sure if those files within [BOOT] are required, but it they were you could use poweriso on windows to include them and then your directory tree of the iso would include boot, EFI, isolinux, live. There’s no reason not to include the EFI folder, none. You don’t need a special one, take from sparky if you must. You must include the boot folder; even if you can bypass grub and load the iso immediately, you’re missing those files within [BOOT] and EFI. Remake your isos.

    1. Thank you for this comment and the previous one, they were extremely helpful. I will look into the issues you raised, especially the one about the ISOs.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.