I am not able to boot the custom webtop. When I boot webtop, I just get the standard version with no ability to install programs, run LXTerm, etc...
I am running a rooted stock Bionic 902
I have applied the HDMI webtop hack
I ran webtop2sd
I ran the custom busybox installer
I applied the e mbm.tar.bz2 patch
I reran the webtop2sd installer.
No change in the webtop that booted after any of those steps.
My diagnostics for webtop2sd is:
version: 2.0.1
Mount executable Version webtop2sd/2.0.0
Custom busybox installed: Y
Webtop configurator version: 33
Currently mounted webtops: webtop, mmcblk0p2
Does anybody have a solution for this?
mbm's patch just enables the gnome terminal in Webtop, so that you can then access other things through command line. try Ctrl-alt-t. that should bring up the Terminal built in to Ubuntu. can you link the mbm.tar.bz2? if you have a working one, which you seem to, i cant find one anywhere! thanks!
Related
I have been deploying my service on App Engine for a long time now and never had an issue until today.
Command to Deploy
gcloud app deploy app.yaml
Output
Beginning deployment of service [default]...
Building and pushing image for service [default]
ERROR: gcloud crashed (ModuleNotFoundError): No module named 'distutils.spawn'
I just deployed this morning with no issues and randomly when I tried to redeploy now I get the above error. Hopefully someone can help figure out what caused this issue.
For info:
app.yaml
runtime: custom
env: flex
manual_scaling:
instances: 1
resources:
cpu: 1
memory_gb: 4
disk_size_gb: 10
Gcloud version
$ gcloud --version
Google Cloud SDK 341.0.0
alpha 2021.05.14
beta 2021.05.14
bq 2.0.68
core 2021.05.14
gsutil 4.62
minikube 1.20.0
skaffold 1.23.0
I had a similar issue, on my case this was the solution:
sudo apt-get install python3-distutils
Same exact problem.
Building and pushing image for service [default]
ERROR: gcloud crashed (ModuleNotFoundError): No module named 'distutils.spawn'
This issue seemed to be in the snap install of google-cloud-sdk in Ubuntu 20.04.2 LTS (You can select it pre-installed during the ISO setup.. DONT)
I was getting this in 18.04 as well
FINALLY solved it..
But.. I had to make sure I did not snap install google-cloud-sdk
I also..
sudo apt update
sudo apt upgrade
Then I made sure the snap install was not installed. (After a fresh install of Ubuntu). Sense I use dockerfiles it's easy for me to zap a dev environment and get it back.
But Id imagine if you can't zap your os and make sure not to let the OS put it's snap install of google-cloud-sdk.. You could snap remove google-cloud-sdk and then hunt for all it's configuration files.. And remove them.
At that point
https://cloud.google.com/sdk/docs/install#deb
Follow that... I did so exactly... FINALLY seemed to work. I used the apt install route they explain.. NOT the snap.
I tried all the pip install sudo apt-get install python3-distutils Till I was blue in the face... NADA.
somehow.. The Snap being present puts PATH settings that use the wrong distutils.
On my box now that I search for it.. In Totally fresh OS state... No Snap install and going through exactly the cloud.google.com/sdk/docs/install#deb work..
Here is distutils everywhere on my box in Ubuntu 20.03.2 LTS
$ sudo find / -name distutils
/snap/lxd/19188/lib/python2.7/distutils
/snap/core18/1944/usr/lib/python3.6/distutils
/snap/core18/1944/usr/lib/python3.7/distutils
/snap/core18/1944/usr/lib/python3.8/distutils
/usr/lib/python3.8/distutils
/usr/lib/python3.9/distutils
/usr/lib/python2.7/distutils
Note.. There's no google-cloud-sdk in the snap!!
The gcloud app deploy FINALLY works!! Passes the part where it starts to deploy.
But as the others in this.. It happened completly random.
All I can guess is...... Something clobered distutils as an update somewhere and started pointing to a garbage path.
Make sure you search for distutils find out where it is.. what's referencing it.. Somewhere in that mess you can fix it.
One thing I was able to discover is this problem will come default from 20.04.2.
I downloaded the most recent iso.. thinking it was an 18.04 issue.
Installed it fresh into Virtual Box.. And got exactly this same issue. So my solution fix (no SNAP).. Is against a totally clean 20.04.2 brand spanking new Ubuntu LTS VM. Default everything.
===============
Regarding the random one day it worked.. the next it didn't...
Here's the thing about snaps in Ubuntu:
https://www.google.com/search?q=Do+snap+packages+update+automatically%3F&rlz=1C1CHBF_enUS834US834&ei=ygynYJGRIo3f-gSLzb3YDg&oq=Do+snap+packages+update+automatically%3F&gs_lcp=Cgdnd3Mtd2l6EAMyCAghEBYQHRAeUJ-TCVifkwlgj5kJaABwAXgAgAFziAHVAZIBAzEuMZgBAKABAqABAaoBB2d3cy13aXrAAQE&sclient=gws-wiz&ved=0ahUKEwiRnrfXz9nwAhWNr54KHYtmD-sQ4dUDCA4&uact=5
"Do snap packages update automatically?
Snaps update automatically, and by default, the snapd daemon checks for updates 4 times a day. Each update check is called a refresh."
so that's how it randomly broke if you used a snap
I am using Eclipse Photon CDT on Windows 10, with all Docker integration Prerequisite already installed.
I have one ubuntu docker image which is running on same machine.
I can check running ubuntu container from Docker Explorer view of Eclipse.
Now I am facing problem in building and launching Hello World C++ simple application inside docker.
When I change my build settings and uncheck build inside container, then application gets built for local environment but when I select run inside container, No binary is formed..
Please help me figuring this out, I am following all steps as defined in latest eclipsecon. Not sure what's wrong.
Please if any one knows about this problem, try to resolve it.
Thanks
The current (and older) release of Eclipse CDT (2018-09) does not print an error if the command in the docker container fails with command not found, see bug 529656. A fix will be included in the December release (2018-12).
The official ubuntu docker image does not include make and g++. Therefore, the build will silently fail. Instead of the ubuntu image, you could use the gcc image.
This nice article describe very well how to install minishift on Windows, MacOS and RHEL:
Hello World!
Unfortunately, there is no procedure for Fedora, can you provide some guidelines?
It is possible to download the CDK (minishift) binary directly from download page. You just need to be registered.
Next, you should configure your system environment (ie. set up hypervisor driver), take a look here.
Make the downloaded CDK binary executable:
chmod +x cdk-x.y.z-minishift-linux-amd64
Finally, you can continue with setting up the cdk binary as described in section 2 in Hello World page. Mainly, this is about preparing minishift configuration for proper hypervisor (as user can use more than one):
./cdk-x.y.z-minishift-linux-amd64 setup-cdk
or
./cdk-x.y.z-minishift-linux-amd64 setup-cdk --default-vm-driver xxx
in case that you are using different than default hypervisor (kvm on linux, could be virtualbox).
I need to install Concourse(CI/CD) on my Local windows machine
Below process I followed :
Install Bosh on local system.
It was successfully install and while executing command at command prompt
then it show version all "bosh" -- "version 3.0.1-712bfd7-2018-03-13T23:26:43Z".
Try Download the concourse-lite deployment manifest file but it fails it shows below error.
Follow the below link to install Concourse :
https://concoursetutorial.com/ --- section For Windows:
I don't reccomend doing this at all because you'll be swimming so far out of the main stream that you'll find tons of issues and no one is going to care enough to want to fix them.
Even if you didn't find any issues, resources require a linux worker for anything to work so your going to need linux anyways.
I recommend running your db, web and linux worker on linux and then running windows workers as needed.
I'm new to collectd and Riemann. Im essentially trying to direct collectd logs to a riemann server instance. I understand that I need write_riemann plugin installed. I tried compiling the source files for write_riemann available online, but it includes a file called "riemann.pb-c.h", which is no where to be found. Please help!
Download the binary. After running the build script, while running the configure script include "--enable-write_riemann", this should install it. I had a lot of dependencies missing on CentOS, which threw a lot of errors. Once they were installed, write_riemann plugin was compiled and installed. Another issue you might face while installing the dependency is not able to find the right packages for protobuf-c.I was using yum package installer. Go to sudo vi /etc/yum.repos.d/epel.repo and change enabled from 0 to 1. After this, the protobuf-c processor was recognised while running the configure script. This solved my issue. Hope it does yours too!