No GUI on Mark II

[aofc]

Just downloaded the latest raspOVOS-gui image for Mycroft devices, but the GUI doesn't seem to start, it just ends up opening a command-line shell session. I haven't tested the latest dev build yet since it downloads painfully slow.

Is there a command to start the GUI manually? Looking forward to test it.

[JarbasAl]

currently raspOVOS targets only headless devices without a GUI

[aofc]

So you have a gui image without a gui? that is kind of misleading. Why is the ovos-gui not running? Can I get it to work?

[JarbasAl]

The readme lists the stable images and says the others are dev images and might be broken or incomplete, it doesn't even list the gui image, it is only mentioned in the bottom explicitly as work in progress. How is that misleading?

Ovos-installer is currently the easiest way to get the gui running, but you can also compile from source yourself

[JarbasAl]

duplicate of #3 , keep an eye on that one for updates

[aofc]

I came from the download page. Clicked on the Mark II because that is what I own. Then on the link to download the images, the gui-image is the first in the list in the "stable" directory. Maybe you should check before telling me it's a dev image. Or put it in the right folder. If it's a dev image it really is misleading.

But I ended up compiling it from sources and it works great (no idea why your gui-image can't do it, it's not like there are so many different versions of the hardware out there).

Anyway thank you for your great work. I use Neon for now but they are way behind on some features. Even though they use some OVOS modules they use very old versions. I hope they catch up soon. I would like to have a central AI unit at home powering Mark IIs as clients to have them use less resources and be more responsive.

[JarbasAl]

@aofc thanks for the nudge about that outdated link! we are working on bringing up the main website up to date to avoid this sort of confusion. i thought you were coming from the github repo directly

the GUI image is just in the backlog, not that we don't want to support it just low priority (the GUI itself is outdated and in need of updates, quite rough around the edges)