Posts made by deemedia

@sdetweil
Suit this ubuntu_lxde_desktop_For_OrangePi_One

@sdetweil
what system should I put under this piece of iron to start. Thank you so much for helping.:folded_hands:

@sdetweil said in Orange PI:

н

no desktop no. installed Amdebian, without a graphical interface. I tried Ubuntu 15.04 mate desktop and also does not work.

@sdetweil said in Orange PI:

xwindows
I did not try xwindows, I am a weak user

@sdetweil said in Orange PI:

VNC

No, not VNC, directly from the device

Maybe someone has a ready image to install on a memory card and run without these tambourines.
ready to donate, for a working image on Orange Pi One

@sdetweil said in Orange PI:

жно установить libgtk

Thanks, it helped. But now another problem

On the way to launch. And again a mistake. I will soon throw out this Orange PI :face_with_steam_from_nose:
How to solve it?:dizzy_face:

(electron:4035): Gtk-WARNING **: cannot open display: :0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.7.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional log                ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/admin/.npm/_logs/2019-04-24T05_47_37_255Z-debug.log

Someone installed it on the Orange Pi one? can you please give instructions

Installation on the Armbian in manual mode ended in error. I do not know how to solve the problem start. There is who knows options:face_with_cold_sweat: :loudly_crying_face:

/home/admin/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.7.1 start: `sh run-start.sh`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.7.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/admin/.npm/_logs/2019-04-23T17_59_43_024Z-debug.log