activitywatch: ActivityWatch doesn't start in Archlinux

ActivityWatch doesn’t start in Archlinux, I tried to install it from the AUR first and it didn’t work. Then I tried to install it by downloading it from the Github, it too gave me same errors:

 ╰─λ ./aw-qt
2021-09-01 15:20:08 [INFO ]: Searching for bundled modules in: ['/home/austin/.activitywatch/aw_qt', '/home/austin/.activitywatch']  (aw_qt.manager:67)
2021-09-01 15:20:08 [WARNING]: Found matching file but was not executable: /home/austin/.activitywatch/aw-server-rust/aw-server.service  (aw_qt.manager:54)
2021-09-01 15:20:08 [WARNING]: Found matching file but was not executable: /home/austin/.activitywatch/aw-qt.desktop  (aw_qt.manager:54)
2021-09-01 15:20:08 [INFO ]: Found bundled modules:  (aw_qt.manager:72)
2021-09-01 15:20:08 [INFO ]:  - aw-server at /home/austin/.activitywatch/aw-server/aw-server  (aw_qt.manager:24)
2021-09-01 15:20:08 [INFO ]:  - aw-watcher-window at /home/austin/.activitywatch/aw-watcher-window/aw-watcher-window  (aw_qt.manager:24)
2021-09-01 15:20:08 [INFO ]:  - aw-watcher-afk at /home/austin/.activitywatch/aw-watcher-afk/aw-watcher-afk  (aw_qt.manager:24)
2021-09-01 15:20:08 [INFO ]:  - aw-server-rust at /home/austin/.activitywatch/aw-server-rust/aw-server-rust  (aw_qt.manager:24)
2021-09-01 15:20:08 [INFO ]:  - aw-qt at /home/austin/.activitywatch/aw-qt  (aw_qt.manager:24)
2021-09-01 15:20:08 [INFO ]: Found system modules:  (aw_qt.manager:99)
2021-09-01 15:20:08 [INFO ]: Starting module aw-server  (aw_qt.manager:128)
2021-09-01 15:20:08 [INFO ]: Starting module aw-watcher-afk  (aw_qt.manager:128)
2021-09-01 15:20:08 [INFO ]: Starting module aw-watcher-window  (aw_qt.manager:128)
2021-09-01 15:20:08 [INFO ]: Creating trayicon...  (aw_qt.trayicon:206)
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, webgl, xcb.

2021-09-01 15:20:08 [ERROR]: Another instance is already running, quitting.  (aw_client.singleinstance:40)
2021-09-01 15:20:09 [ERROR]: Another instance is already running, quitting.  (aw_client.singleinstance:40)
WARNING:root:Could not import pymongo, not available as a datastore backend
2021-09-01 15:20:09 [INFO ]: Using storage method: peewee  (aw_server.main:32)
2021-09-01 15:20:09 [INFO ]: Starting up...  (aw_server.main:37)
2021-09-01 15:20:09 [INFO ]: Using database file: /home/austin/.local/share/activitywatch/aw-server/peewee-sqlite.v2.db  (aw_datastore.storages.peewee:116)
 * Serving Flask app "aw-server" (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
2021-09-01 15:20:09 [ERROR]: [Errno 98] Address already in use  (aw_server.server:112)
2021-09-01 15:20:09 [ERROR]: Unhandled exception  (root:43)
Traceback (most recent call last):
  File "__main__.py", line 3, in <module>
  File "aw_server/main.py", line 38, in main
  File "aw_server/server.py", line 113, in _start
  File "aw_server/server.py", line 103, in _start
  File "flask/app.py", line 990, in run
  File "werkzeug/serving.py", line 1052, in run_simple
  File "werkzeug/serving.py", line 996, in inner
  File "werkzeug/serving.py", line 862, in make_server
  File "werkzeug/serving.py", line 740, in __init__
  File "socketserver.py", line 452, in __init__
  File "http/server.py", line 138, in server_bind
  File "socketserver.py", line 466, in server_bind
OSError: [Errno 98] Address already in use
[69955] Failed to execute script __main__
fish: Job 1, './aw-qt' terminated by signal SIGABRT (Abort)

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 1
  • Comments: 16 (5 by maintainers)

Commits related to this issue

Most upvoted comments

After some discussion on the AUR and tracking down a similar issue for Steam, I found a fix: Remove the libharfbuzz.so.0 file from the installation directory.

This works fine on Arch for me, and I’ll update the AUR package to include this workaround.

For everyone else: will try to get it out of the next release entirely.

I’ve managed to reproduce (by updating) and build a release locally with the latest freetype 2.11.0 that runs fine.

Now the only issue is how to get that in CI (and figure out how it might affect older systems) and make a new release.

Thanks, @ErikBjare for fixing this issue. This is a great piece of software!

Hmm, I think I’ve seen this issue before during testing, but I don’t remember the cause…

I use Arch as well, and I can run the latest release on the AUR just fine. Not sure how our systems might differ?

Then how is it running fine for the developer?