Package Details: mycroft-core 21.2.2-1

Git Clone URL: https://aur.archlinux.org/mycroft-core.git (read-only, click to copy)
Package Base: mycroft-core
Description: The Mycroft Artificial Intelligence platform.
Upstream URL: https://github.com/MycroftAI/mycroft-core
Licenses: Apache
Submitter: manzo
Maintainer: robertfoster
Last Packager: robertfoster
Votes: 28
Popularity: 0.088791
First Submitted: 2016-12-27 12:48 (UTC)
Last Updated: 2021-12-17 14:56 (UTC)

Latest Comments

chowbok commented on 2022-02-18 14:08 (UTC)

@Focshole Thanks for this.

@robertfoster Can this be added to the PKGBUILD or the service file?

ShadowApex commented on 2022-01-18 22:53 (UTC)

If you're using the latest version of pipewire, you'll need to copy /usr/share/pipewire/pipewire-pulse.conf to ~/.config/pipewire/pipewire-pulse.conf and add this to server.address:

{ address = "tcp:127.0.0.1:4713"
  client.access = "allowed"     # permissions for clients
}

Focshole commented on 2021-10-12 17:26 (UTC) (edited on 2021-10-12 17:27 (UTC) by Focshole)

If you get an Please update dependencies by running ./dev_setup.sh again. error on start, I had solved in this way.

The dev_setup.sh script ends with an

md5sum requirements/requirements.txt requirements/extra-audiobackend.txt requirements/extra-stt.txt requirements/extra-mark1.txt requirements/tests.txt dev_setup.sh > .installed

which won't allow to start mycroft if .installed is not present. So I run that command in /usr/share/mycroft-core/ directory and it started properly.

chayleaf commented on 2021-09-28 15:53 (UTC)

this won't build for me because of an error: "neither symbolic link '..../usr/share/mycroft-core/mimic/bin/mimic' nor referent has been changed" during chmod -R 755. Consider moving symlink creation to after the chmod I guess?

Maxnet commented on 2021-06-22 12:51 (UTC)

How am I supposed to run this package? When executing the systemd unit I don't get any reponse. When running the start-mycroft.sh itself it says Connection Refused Error in debug mode.

kinta commented on 2020-01-02 22:04 (UTC) (edited on 2020-01-02 22:05 (UTC) by kinta)

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

pepper_chico commented on 2019-10-26 18:52 (UTC)

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".

jaxad0127 commented on 2019-10-15 04:38 (UTC)

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).

xenrox commented on 2019-05-15 12:01 (UTC)

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

ConorIA commented on 2019-03-31 20:39 (UTC)

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.

librewish commented on 2019-03-20 07:49 (UTC)

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

ixil commented on 2018-10-31 20:55 (UTC)

@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/*)

xenrox commented on 2018-10-23 08:43 (UTC) (edited on 2018-10-23 08:47 (UTC) by xenrox)

@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).

ixil commented on 2018-10-21 14:31 (UTC)

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

idleshand commented on 2018-10-19 20:25 (UTC)

Thanks for maintaining this package. :)

xenrox commented on 2018-10-19 12:18 (UTC)

@idleshand Thanks for notifying me. I updated the package.

idleshand commented on 2018-10-18 13:08 (UTC)

Looks to me like it is worth updating the pkgbuild to reflect the changes that have been made to the original "dev_setup.sh".

The only changes I can actually see are related to pip. Specifically upgrading to using pip v18 as in this commit: https://github.com/MycroftAI/mycroft-core/commit/5e6c1773e4daa2da99f63110944fd220bf2298ee#diff-18dbf5207379240f00af7b954cde81ff

And then using curl to get pip directly and installing to the virtual_env instead of using easy_install, in this commit https://github.com/MycroftAI/mycroft-core/commit/923ea9f532175ba70027d09eb250b2c81655bdde#diff-18dbf5207379240f00af7b954cde81ff

z3ntu commented on 2018-08-12 09:13 (UTC) (edited on 2018-08-12 15:05 (UTC) by z3ntu)

The postinstall script fails to build pyyaml for some reason. edit: Patching /usr/share/mycroft-core/requirements.txt to use pyyyaml 3.13 instead of 3.11 works (see https://github.com/yaml/pyyaml/issues/152) edit2: still can't properly start the mycroft service due to some permission problems even though I'm in the mycroft-core group

ubuntourist commented on 2018-06-21 17:24 (UTC)

See also https://community.mycroft.ai/t/change-virtualenvwrapper-to-pipenv/3968

ubuntourist commented on 2018-06-14 17:07 (UTC)

The python-pipenv package conflicts with the python-virtualenvwrapper package.

(pipenv is now the recommended replacement for pip and virtualenv according to Python Software Foundation [https://packaging.python.org/tutorials/managing-dependencies/#managing-dependencies])

xenrox commented on 2018-06-05 06:46 (UTC)

@jaxad0127 it is user-writable, if you add your user to the group mycroft-core. But you have to first reboot your computer/log out your user so that your user-account can gain the group rigths.

jaxad0127 commented on 2018-06-05 02:10 (UTC)

This package looks to be setup as a user daemon under Systemd, but it wants to write to /usr/share/mycroft-core/scripts/logs, which shouldn't be user-writable. Is there an easy fix for this?

ConorIA commented on 2018-04-07 21:05 (UTC) (edited on 2018-04-07 21:05 (UTC) by ConorIA)

@marlemion, that would be a temporary workaround. Really it is python-fann2 that should fix the dependency, or fann in the AUR should add a provides for libfann. I have made those two suggestions on the respective AUR pages.

marlemion commented on 2018-04-05 07:59 (UTC)

Please add fann to dependencies. Had to install it manually to let the installation exit without an error.

ConorIA commented on 2018-03-31 20:06 (UTC)

Lots of recent changes. Tried to keep on top of them. Not very well tested just yet. https://gitlab.com/ConorIA/mycroft-core-PKGBUILD

ConorIA commented on 2018-03-14 21:10 (UTC) (edited on 2018-03-14 21:13 (UTC) by ConorIA)

Hey @portaloffreedom, I'm using your PKGBUILD to test. I can use the Microphone OK on my laptop (can't tell on my desktop, because it doesn't have a mic).

I am hitting a wall trying to use skills, though. I am getting the following error:

>>> systemctl status --user mycroft-skills                                                                                                                                                                                                                                                        
● mycroft-skills.service - Mycroft skills provider
   Loaded: loaded (/usr/lib/systemd/user/mycroft-skills.service; disabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-03-14 16:47:31 EDT; 6min ago
 Main PID: 22185 (mycroft-skills)
    CGroup: /user.slice/user-1000.slice/user@1000.service/mycroft-skills.service
           └─22185 /usr/bin/python3 /usr/bin/mycroft-skills

Mar 14 16:54:07  mycroft-skills[22185]:   File "/home/user/.mycroft/skills/skill-installer/__init__.py", line 96, in get_skill_list
Mar 14 16:54:07  mycroft-skills[22185]:     self.ansi_escape.sub('', check_output([BIN, 'list'])).split('\n')
Mar 14 16:54:07  mycroft-skills[22185]: TypeError: cannot use a string pattern on a bytes-like object

Have you been seeing this too? Not sure if this is something to ask the Mycroft devs about.

schrieveslaach commented on 2018-03-13 05:19 (UTC) (edited on 2018-03-13 05:20 (UTC) by schrieveslaach)

@portaloffreedom I tried it with systemctl --user mycroft.target and I also tried it by running the scripts manually. I'm also using PulseAudio

portaloffreedom commented on 2018-03-12 19:10 (UTC)

@schrieveslaach Update: I got the same error as well. But I cannot reproduce it with certainty. Have you started it manually or with systemctl --user mycroft.target?

portaloffreedom commented on 2018-03-12 18:04 (UTC)

@schrieveslaach mmmmm, not really sure. I'm using pulseaudio and haven't tryed with Jack. Are you using jack in your system? It seems to me that is trying to connect to alsa and alsa to jack...

schrieveslaach commented on 2018-03-11 10:39 (UTC) (edited on 2018-03-11 10:39 (UTC) by schrieveslaach)

@portaloffreedom, I tried your version, however, the microphone is not working:

ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed

Do you have any idea what the cause of the error is?

schrieveslaach commented on 2018-03-10 06:55 (UTC)

@portaloffreedom, that looks nice. Tomorrow I have time to look into your code changes. Getting rid of virtualenv would be very nice.

Additionally, I found some other issues in the Mycroft core, I need to resolve.

portaloffreedom commented on 2018-03-08 19:12 (UTC)

So, I kind of overdid it. I made an entirely new package inspired from the opensuse package. You can find it here (it works!) https://git.covolunablu.org/portaloffreedom/mycroft-core-PKGBUILD

Other then working, the main differences are that my package doesn't use virtualenv hacks and uses python3.

If the mantainers of this package want to copy it into this, they are more than welcome. I would like to have this PKGBUILD for everyone but I don't want to create a duplicate on aur. If you don't want to use what I create for this package, then just tell me I'll come up with an idea for a new name in aur.

renyuneyun commented on 2018-03-08 11:50 (UTC) (edited on 2018-03-08 11:51 (UTC) by renyuneyun)

By the way, there maybe two possible bugs in mycroft-core.install.

  1. In post_remove(), I suspect the group to be removed should be mycroft-core (forgotten dash)
  2. In post_install() or somewhere, it may be necessary to set the default permission (maybe through mask or umask?) of the directory /usr/share/mycroft-core(or some of its subdirectories) to 0775, otherwise the user may not be able to alter that directory (so won't be able to install skills).

One last thing: is /usr/share/xxx a good place to install things which can change itself? Maybe /opt/ is a better place?

(I haven't made the software to run correctly, so I haven't had any experiences... Forgive me if any inference is wrong.)

renyuneyun commented on 2018-03-08 11:36 (UTC) (edited on 2018-03-08 11:37 (UTC) by renyuneyun)

@portaloffreedom Yes, I also solved that by installing libfann. However, I'm still getting trouble using the software, and was hoping to post the solution together... Though I can't get the software work. Do you have any clue?

portaloffreedom commented on 2018-03-08 10:49 (UTC)

in the post_install script I get a compilation error

    creating build/temp.linux-x86_64-2.7/fann2
    gcc -pthread -fno-strict-aliasing -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -fPIC -DSWIG_COMPILE -I./include -I../include -Iinclude -I/usr/include/python2.7 -c fann2/fann2_wrap.cxx -o build/temp.linux-x86_64-2.7/fann2/fann2_wrap.o
    g++ -pthread -shared -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now build/temp.linux-x86_64-2.7/fann2/fann2_wrap.o -L/usr/lib -ldoublefann -lpython2.7 -o build/lib.linux-x86_64-2.7/fann2/_libfann.so
    /usr/bin/ld: cannot find -ldoublefann
    collect2: error: ld returned 1 exit status
    error: command 'g++' failed with exit status 1

it seems there is a missing dependency in the package: libfann (installing the libfann package gets rid of the error)

renyuneyun commented on 2018-03-05 14:01 (UTC)

I'm getting error during installation (but the installation successfully finished).

(My locale is in Chinese and a few words in the error are in Chinese, so I manually translated them into English, which may make them not identical to the original one (but meaning is kept).

  Running setup.py bdist_wheel for fann2: started
  Running setup.py bdist_wheel for fann2: finished with status 'error'
  Complete output from command /usr/share/mycroft-core/.virtualenvs/mycroft/bin/python2 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-wBlr9_/fann2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmpTxg3tVpip-wheel- --python-tag cp27:
  running swig
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-2.7
  creating build/lib.linux-x86_64-2.7/fann2
  copying fann2/__init__.py -> build/lib.linux-x86_64-2.7/fann2
  copying fann2/libfann.py -> build/lib.linux-x86_64-2.7/fann2
  running egg_info
  writing fann2.egg-info/PKG-INFO
  writing top-level names to fann2.egg-info/top_level.txt
  writing dependency_links to fann2.egg-info/dependency_links.txt
  reading manifest file 'fann2.egg-info/SOURCES.txt'
  reading manifest template 'MANIFEST.in'
  writing manifest file 'fann2.egg-info/SOURCES.txt'
  copying fann2/fann2.i -> build/lib.linux-x86_64-2.7/fann2
  copying fann2/fann2_wrap.cxx -> build/lib.linux-x86_64-2.7/fann2
  copying fann2/fann_cpp_subclass.h -> build/lib.linux-x86_64-2.7/fann2
  running build_ext
  building 'fann2._libfann' extension
  creating build/temp.linux-x86_64-2.7
  creating build/temp.linux-x86_64-2.7/fann2
  gcc -pthread -fno-strict-aliasing -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -fPIC -DSWIG_COMPILE -I./include -I../include -Iinclude -I/usr/include/python2.7 -c fann2/fann2_wrap.cxx -o build/temp.linux-x86_64-2.7/fann2/fann2_wrap.o
  g++ -pthread -shared -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now build/temp.linux-x86_64-2.7/fann2/fann2_wrap.o -L/usr/lib -ldoublefann -lpython2.7 -o build/lib.linux-x86_64-2.7/fann2/_libfann.so
  /usr/bin/ld: can't find -ldoublefann
  collect2: error:ld returned 1
  error: command 'g++' failed with exit status 1

  ----------------------------------------
  Failed building wheel for fann2
  Running setup.py clean for fann2
  Running setup.py bdist_wheel for olefile: started
  Running setup.py bdist_wheel for olefile: finished with status 'done'
  Stored in directory: /usr/share/mycroft-core/.cache/pip/wheels/75/f2/18/9f073aab5b308aaccec50c17d4afb33dffc3265254e7962d67
  Running setup.py bdist_wheel for httplib2: started
  Running setup.py bdist_wheel for httplib2: finished with status 'done'
  Stored in directory: /usr/share/mycroft-core/.cache/pip/wheels/ca/ac/5f/749651f7925b231103f5316cacca82a487810c22d30f011c0c
  Running setup.py bdist_wheel for xxhash: started
  Running setup.py bdist_wheel for xxhash: finished with status 'done'
  Stored in directory: /usr/share/mycroft-core/.cache/pip/wheels/99/02/66/22b257c04a4c131f2114f38b7d367e8f1e259af1b293b0c75d
  Running setup.py bdist_wheel for netifaces: started
  Running setup.py bdist_wheel for netifaces: finished with status 'done'
  Stored in directory: /usr/share/mycroft-core/.cache/pip/wheels/28/e1/08/e66a4f207479500a27eae682a4773fa00605f2c5d953257824
Successfully built gTTS gTTS-token backports.ssl-match-hostname PyAudio pyee tornado websocket-client adapt-parser future requests-futures pyyaml pyalsaaudio xmlrunner pyserial psutil pocketsphinx inflection python-vlc olefile httplib2 xxhash netifaces
Failed to build fann2
Installing collected packages: six, requests, gTTS-token, gTTS, backports.ssl-match-hostname, PyAudio, pyee, SpeechRecognition, certifi, tornado, websocket-client, adapt-parser, futures, future, requests-futures, parsedatetime, pyyaml, pyalsaaudio, xmlrunner, pyserial, psutil, pocketsphinx, inflection, olefile, pillow, python-dateutil, protobuf, netifaces, zeroconf, pychromecast, python-vlc, pulsectl, httplib2, pyasn1, pyasn1-modules, rsa, oauth2client, uritemplate, google-api-python-client, pep8, fann2, xxhash, padatious
  Found existing installation: six 1.11.0
    Not uninstalling six at /usr/lib/python2.7/site-packages, outside environment /usr/share/mycroft-core/.virtualenvs/mycroft
  Running setup.py install for fann2: started
    Running setup.py install for fann2: finished with status 'error'
    Complete output from command /usr/share/mycroft-core/.virtualenvs/mycroft/bin/python2 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-wBlr9_/fann2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-LhkEAx-record/install-record.txt --single-version-externally-managed --compile --install-headers /usr/share/mycroft-core/.virtualenvs/mycroft/include/site/python2.7/fann2:
    running swig
    running install
    running build
    running build_py
    creating build
    creating build/lib.linux-x86_64-2.7
    creating build/lib.linux-x86_64-2.7/fann2
    copying fann2/__init__.py -> build/lib.linux-x86_64-2.7/fann2
    copying fann2/libfann.py -> build/lib.linux-x86_64-2.7/fann2
    running egg_info
    writing fann2.egg-info/PKG-INFO
    writing top-level names to fann2.egg-info/top_level.txt
    writing dependency_links to fann2.egg-info/dependency_links.txt
    reading manifest file 'fann2.egg-info/SOURCES.txt'
    reading manifest template 'MANIFEST.in'
    writing manifest file 'fann2.egg-info/SOURCES.txt'
    copying fann2/fann2.i -> build/lib.linux-x86_64-2.7/fann2
    copying fann2/fann2_wrap.cxx -> build/lib.linux-x86_64-2.7/fann2
    copying fann2/fann_cpp_subclass.h -> build/lib.linux-x86_64-2.7/fann2
    running build_ext
    building 'fann2._libfann' extension
    creating build/temp.linux-x86_64-2.7
    creating build/temp.linux-x86_64-2.7/fann2
    gcc -pthread -fno-strict-aliasing -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -fPIC -DSWIG_COMPILE -I./include -I../include -Iinclude -I/usr/include/python2.7 -c fann2/fann2_wrap.cxx -o build/temp.linux-x86_64-2.7/fann2/fann2_wrap.o
    g++ -pthread -shared -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now build/temp.linux-x86_64-2.7/fann2/fann2_wrap.o -L/usr/lib -ldoublefann -lpython2.7 -o build/lib.linux-x86_64-2.7/fann2/_libfann.so
    /usr/bin/ld: can't find -ldoublefann
    collect2: error:ld returned 1
    error: command 'g++' failed with exit status 1

    ----------------------------------------
Command "/usr/share/mycroft-core/.virtualenvs/mycroft/bin/python2 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-wBlr9_/fann2/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-LhkEAx-record/install-record.txt --single-version-externally-managed --compile --install-headers /usr/share/mycroft-core/.virtualenvs/mycroft/include/site/python2.7/fann2" failed with error code 1 in /tmp/pip-build-wBlr9_/fann2/
*** ATTENTION ***

schrieveslaach commented on 2018-03-01 07:09 (UTC)

@z3ntu, I have not yet a running version because the current version of Mycroft is not yet working with systemd. When I'm done, I will update this package.

z3ntu commented on 2018-02-27 19:21 (UTC)

@schrieveslaach: If you have working changes for this package (that fix the systemd units) please push it and bump the pkgrel.

schrieveslaach commented on 2018-02-19 08:43 (UTC)

I noticed that Mycroft is not ready to be installed a system package, therefore, I opened a new issue on Github: https://github.com/MycroftAI/mycroft-core/issues/1433

schrieveslaach commented on 2018-02-12 09:16 (UTC)

I'm trying to upgrade the package. Here is my fork of the AUR: https://gitlab.com/schrieveslaach/mycroft-core-aur

However, I'm getting another error and I checked the issues on Github and I found this one: https://github.com/MycroftAI/mycroft-core/issues/1419 Now, I'm waiting for a response.

bjo commented on 2018-01-23 21:01 (UTC)

I orphaned the package, maybe you can adopt it and fix the issues.

iffiuszabolcs commented on 2018-01-23 15:35 (UTC) (edited on 2018-01-23 15:36 (UTC) by iffiuszabolcs)

starting with:

systemctl --user start mycroft.target

and the result of:

systemctl --user status mycroft-service.service mycroft-skills.service mycroft-voice.service

● mycroft-service.service - Mycroft main service Loaded: loaded (/usr/lib/systemd/user/mycroft-service.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-01-23 17:24:57 EET; 7s ago Process: 3669 ExecStart=/bin/bash -c source /usr/share/mycroft-core/.virtualenvs/mycroft/bin/activat Main PID: 3669 (code=exited, status=127)

jan 23 17:24:57 arch systemd[498]: Started Mycroft main service. jan 23 17:24:57 arch bash[3669]: /bin/bash: /usr/share/mycroft-core/start.sh: No such file or director jan 23 17:24:57 arch systemd[498]: mycroft-service.service: Main process exited, code=exited, status=1 jan 23 17:24:57 arch systemd[498]: mycroft-service.service: Failed with result 'exit-code'.

● mycroft-skills.service - Mycroft skills provider Loaded: loaded (/usr/lib/systemd/user/mycroft-skills.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-01-23 17:24:57 EET; 7s ago Process: 3670 ExecStart=/bin/bash -c source /usr/share/mycroft-core/.virtualenvs/mycroft/bin/activat Main PID: 3670 (code=exited, status=127)

jan 23 17:24:57 arch systemd[498]: Started Mycroft skills provider. jan 23 17:24:57 arch bash[3670]: /bin/bash: /usr/share/mycroft-core/start.sh: No such file or director jan 23 17:24:57 arch systemd[498]: mycroft-skills.service: Main process exited, code=exited, status=12 jan 23 17:24:57 arch systemd[498]: mycroft-skills.service: Failed with result 'exit-code'.

● mycroft-voice.service - Mycroft voice processing Loaded: loaded (/usr/lib/systemd/user/mycroft-voice.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2018-01-23 17:24:57 EET; 7s ago Process: 3671 ExecStart=/bin/bash -c source /usr/share/mycroft-core/.virtualenvs/mycroft/bin/activat Main PID: 3671 (code=exited, status=127)

manzo commented on 2017-05-02 11:06 (UTC) (edited on 2017-05-02 11:07 (UTC) by manzo)

Waiting for https://github.com/MycroftAI/mycroft-core/issues/718 to update to v0.8.10. Also if someone wants to contribute to this package, please have a look at: https://gitlab.com/rafamanzo/aur-mycroft-core If someone wants to adopt it, please let me know. I've been time constrained for the last months.

BoBeR182 commented on 2017-04-26 21:02 (UTC)

The following error happens after running "systemctl --user start mycroft.target" https://gist.github.com/anonymous/f377f33961c31f4c9b2ee6d84ef15d89 User is added to mycroft-core group.

mastercoms commented on 2017-04-21 12:13 (UTC) (edited on 2017-04-23 14:30 (UTC) by mastercoms)

I get this error for mycroft-voice.service: https://gist.github.com/mastercoms/9269e9a1a183148ea4958835e7683654#file-gistfile1-txt Fixed it by using the repo version for Python OpenSSL and removing the Python OpenSSL site package.

ShadowMitia commented on 2017-04-05 14:17 (UTC)

I'm using Gnome and I had to go to /usr/share/mycroft-core and run ./dev_setup.sh manually before anything started to work. Then launching the systemctl command worked fine.

manzo commented on 2017-03-31 11:50 (UTC) (edited on 2017-03-31 11:50 (UTC) by manzo)

How are you starting mycroft? What command? Is your user part of the mycroft-core group? The systemd user unit is supposed to run using mycroft-core's user virtualenv. They should be installed on post_install: https://gitlab.com/rafamanzo/aur-mycroft-core/blob/master/mycroft-core.install#L17

stardiviner commented on 2017-03-30 02:50 (UTC)

Some python package dependencies are missing on my Arch Linux. I installed them with pip: pip install tornado inflection psutil pyee pyalsaaudio pyserial

manzo commented on 2017-03-28 18:25 (UTC)

Fixed. Thanks for the report.

z3ntu commented on 2017-03-28 12:45 (UTC)

The "mycroft-core" group doesn't get removed on uninstall so the postinstall script fails because the group already exists.

manzo commented on 2017-03-23 10:32 (UTC)

Please use the systemd user units: systemctl --user start mycroft.target

OdinEidolon commented on 2017-03-18 13:45 (UTC)

/usr/share/mycroft-core/mycroft.sh start mycroft-service failed to start. The log is below: tail: cannot open '/usr/share/mycroft-core/scripts/logs/mycroft-service.log' for reading: No such file or directory What is happening?

OdinEidolon commented on 2017-03-18 13:39 (UTC)

Please add screen to the dependencies. Otherwise: /usr/share/mycroft-core/mycroft.sh: line 45: screen: command not found

ams1 commented on 2017-02-22 11:29 (UTC)

Please change the dependency to "mimic", not "mimic-git". Both now exist, and the mimic-git package has always "provide"d the other name anyway.

manzo commented on 2017-02-08 18:30 (UTC)

Thanks for the feedback jhenriquez and sorry for the delay. I've just updated to v0.8.3 and performed a fresh install. The desktop launcher seems fine over here when I say: "Hey Mycroft, launch firefox". I'm using Gnome 3. What about you? Maybe your issue is related to Mycroft's integration to other desktop environments.

jhenriquez commented on 2017-02-03 11:17 (UTC)

I experienced an issue with one of the default skills, the desktop launcher one. Where the it is unable to initialize because it can't locate the module "gio". Honestly, I'm still unsure if this was an isolated issue, something wrong with my environment. Neither I'm 100% sure what fixed it for me. So, any confirmation or more information would be great. This is what I did: Added symbolic links: /usr/lib/python2.7/site-packages/gobject -> ~/.virtualenv/mycroft/lib/python2.7/site-packages/gobject /usr/lib/python2.7/site-packages/gi -> ~/.virtualenv/mycroft/lib/python2.7/site-packages/gi /usr/lib/python2.7/site-packages/glib -> ~/.virtualenv/mycroft/lib/python2.7/site-packages/glib But this incidentally had me changing the way the skill imported gio to: "from gi.repository import Gio" I believe this is because I unintentionally upgraded the PyGobjecft version :S But I'm not sure. I understand this second part belongs on an issue in the mycroft repo. But if the symbolic links suffice to fix the issue, I believe this can be addressed in this package.

manzo commented on 2017-01-15 18:34 (UTC)

Thank for your report z3ntu. Could you provide more details? I can't tell what is going on by these lines :/

manzo commented on 2016-12-30 15:00 (UTC)

Thank you for the suggestion. I've had no problem with it but probably to some specific configuration on my machine. I've released a fixed version with your suggestion.

ImNtReal commented on 2016-12-30 14:50 (UTC)

I had to change the sudo -u mycroft-core to sudo -Hu mycroft-core in the .install file to get this to work on my system.