lesspipe | lesspipe - display more with less

You were missing libffi-dev earlier and now you are missing libssl-dev. Looks like you might be missing other requirements for buildozer too. Follow the steps given in buildozer documentation

Open your terminal and run following commands:

so...no idea how it happened but somehow I pasted a special character M-BM- in place of a proper space char.

The M-BM- characters are an ASCII representation of byte sequence 0xc2 0xa0, which is the UTF8 encoding of unicode character A0 - a non-breaking space character. This character can be inserted in both LibreOffice and Microsoft Word documents using the key sequence Ctrl+Shift+SPACE.

¯\(ツ)/¯

I guess you have your files in a directory named 'Lunar Aplocon'. The space ' ' in the file name is causing the issue. Even when you enter the name in your buildozer.sec file try not to include any space (you can include in title but not in org and other info). So you just have to rename your directory then it will be just fine.

ValueError: storage dir path cannot contain spaces, please specify a path with --storage-dir

As it says, try using a directory without spaces in its name.

Docker containers are stored in the default location at /var/lib/docker/ on Linux. If you can identify the container and delete this, and then try to start docker. If you are successful and can enter docker ps -a, then you can start deleting traces of this container.

Note: I would snapshot your VM before attempting to try this.

I believe the problem is you are running command on 32bit operating system. As mentioned in the BUG #1007

Thanks, I saw the logs.. But The Problem was that I was using a 32 bit linux system. So the drivers could not work. Then when I tried the same thing in a 64 bit linux system. Installed on virtual machine it worked fine. Thanks for your help.

test is a bash builtin (a synonym for [) so you should use another name for your alias.

It is causing a problem in the "enable color support of ls and also add handy aliases" section of your .bashrc which uses test -r ~/.dircolors && ... to check for the readability of a file.
With your alias it gets expanded to cd ~/CRiiS/criistest -r ~/.dircolors which leads to your error as cd only takes a single non-option argument.

It would be possible to fix this specific occurence by using [ instead of test ([ -r ~/.dircolors ] && ...) but you will definitely run into further problems by shadowing a builtin.

The 'env' command will print the environment - variables have to be exported. Either the CLASSPATH is exported later (via export CLASSPATH), or it may be used in the command line (java -cp "$CLASSPATH" ...).

You can get a list of ALL variables (exported variable, and internal shell variables) using the set command.

The problematic error stems from this piece of information here: Kivy-Garden==0.1.1

I had the same issue, buildozer, for some weird reason installs Kivy-Garden version 0.1.1 which produces that error when you try to install ANY garden flower. Kivy version 1.11.1 now uses Kivy-Garden>=0.1.4 which works without issues. If you install Kivy-Garden==0.1.1 and try to install a package, it crushes with that error. However, If you upgrade to Kivy-Garden==0.1.4. The problem is that buildozer will install Kivy-Garden==0.1.1 no matter what you do. So I tried a lot of things from downgrading buildozer to manually activating the environment that buildozer creates and upgrading garden there but when you run the buildozer command again. Buildozer will simply overwrite your upgraded garden AND install the non-working 0.1.1.

Finally I just gave up and did the one thing I COULD do at this moment. Simply fix buildozer myself:

1. Activate your environment(assuming you have one)
2. Go to where buildozer is installed. In my case this is: /home/samuel/repo/mobile/venv/finager/lib/python3.7/site-packages/buildozer-1.2.0.dev0-py3.7.egg/buildozer/__init__.py. You can find that out by checking the paths in your logs.
3. Now go to Line 533 and change where it says pip install Kivy-Garden==0.1.1 to pip install Kivy-Garden==0.1.4 That's it, your problem should go away now.

I hope they fix this soon as this is a pretty simple thing to do. Kivy itself requires Kivy-Garden>=0.1.4 which makes me wonder why buildozer would want 0.1.1 when it clearly doesn't work