new update Assistant2Display

sdetweil

@raf no, that is only to upgrade MagicMirror itself

sdetweil

@raf please see this

https://www.hostinger.com/tutorials/linux-commands
and here
https://maker.pro/linux/tutorial/basic-linux-commands-for-beginners

cause it has a different start , which may prove helpful forever

raf

I’ve read a lot but don’t know where to start
I even don’t know where to look for the error let alone fix it

sdetweil

@raf come on, commands are executed in a terminal window. the second link shows you how to open one from the desktop.

some commands work on files…

so you either need to be in the same folder as the files, or use the full path to the files from the current folder.

u know the error, u and Bugsounet have discussed it… the program needs to be marked executable… this is a linux permissions thing, you cannot execute just anything… (like on windows)

u need to learn the system , and will be better off because of it. we are not here to give u every command in every situation…

raf

@sdetweil
i am thinking of an issue with the electron rebuild, if i disable Assistant2Display in the config.js the mirror will boot normally but if i enable it back in the config.js i only get a black image

A Former User

when you clone the repo, all needed files have the the executable flag … you have change it so … we give the way … now search

All of my module have same scheme… if there is some probleme all of my module will be impected

It’s not the case For you information : A2D is downloaded +/- 500X per week
So now you have make a mismake … now search, you have the way …
we can’t tell you better and we can’t do better ;)

we are not magican

Or like you says :

@raf said in new update Assistant2Display:

I’ll just remove the google assistant and assistant2display because I can’t find the error (then just a mirror without assistant)

it’s the best choice for you BUT don’t ask to me or @sdetweil some help in this case
and plz don’t notify me in future

raf

problem finally solved

banbutcher

@raf how did you solve it, incase anyone else hase the same issue?

A Former User

@banbutcher… It s not an issue

raf

I solved it by disabling the Assistant2Display in the config.js and then after removing the folder in the modules folder,
then done the installation back git clone … and enabled the module back in the config.js and what changed in the config changed to mine