Arch Linux User Repository

Thanks, but running mycroft as system systemd unit makes difficult to run skills that are calling user session dbus (as krunner one for example). When I try it, it leads to:

Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead

All the scripts in /usr/share/mycroft-core/.venv/bin have wrong shebang after install, like "#!/home/francisco/mycroft-core/pkg/mycroft-core/usr/share/mycroft-core/.venv/bin/python" instead of "!/usr/share/mycroft-core/.venv/bin/python".

Typo in .install file: gpassd should be gpasswd

Also an issue with /usr/share/mycroft-core/.venv added by the package, but existing in the filesystem (not owned by any package).

Last update (pkgrel 2) should fix the problem with mycroft trying to change permissions.

Here are some patches to bring this up to date. Two key changes:

1) Instead of trying to patch out the check_dependencies function, I just avoid calling it in the start script.

2) I specify /usr/bin/python when init-ing the venv, because if you have conda activated, it leads to a permission error (might be an error in my setup).

https://pastebin.com/TzEM8Ney

This seems to be working so far, but I'll comment here if something went wrong.

mycroft-core is outdated it asks to be upgraded to version 19

@xenrox, sorry for slow reply forgot to enable notifications. The problem was that I only tried to run it through systemctl --user start starting it directly from start-mycroft.sh cli Shows that it trying to create (requires sudo) /opt/mycroft{,/skills}. Then changes the ownership(also needs sudo) and group to my user, shouldn't this be the user and group mycroft-core - it tries to change the owner/group every startup.

Now I have connection problems, the websocket library throws an uncaught exception which doesn't seem to appear in the logs (I assume in /var/log/mycroft/*)

@ixil That sounds more like an issue with your sudo setup/pam module than with this package. Can you tell me which command you used which caused this problem? Normally you would do: systemctl --user enable mycroft.service Sudo is not even required. /opt/mycroft/skills/ is created by mycroft when it is started for the first time and downloads the default skills. Edit: If you want a faster reply, write me an email (address is encoded in the PKGBUILD).

Using the systemd user file I'm getting an error:

hostname sudo[14288]: pam_unix(sudo:auth): conversation failed
hostname sudo[14288]: pam_unix(sudo:auth): auth could not identify password for myuser

Any hints?

Also previously it was trying to create /opt/mycroft/skills/ which I manually did and changed the group to mycroft-core - should this be in the post-install instructions? or changed in the settings - in which case that should probably follow the default arch directories

Thanks for maintaining this package. :)