Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

aw-qt not starting : got an ImportError out of nowhere!

See original GitHub issue

I was happily living my life using activity watch. yesterday I found out that activity watch is not running so I checked my startup applications and copied the code that I’d added there long time ago to see the problem: as I pasted this to terminal: /usr/bin/activitywatch/activitywatch/aw-qt this error showed up:

Traceback (most recent call last):
  File "aw_qt/__main__.py", line 1, in <module>
  File "/home/travis/virtualenv/python3.5.3/lib/python3.5/site-packages/PyInstaller/loader/pyimod03_importers.py", line 631, in exec_module
  File "aw_qt/__init__.py", line 3, in <module>
  File "/home/travis/virtualenv/python3.5.3/lib/python3.5/site-packages/PyInstaller/loader/pyimod03_importers.py", line 631, in exec_module
  File "aw_qt/main.py", line 9, in <module>
  File "/home/travis/virtualenv/python3.5.3/lib/python3.5/site-packages/PyInstaller/loader/pyimod03_importers.py", line 631, in exec_module
  File "aw_qt/trayicon.py", line 9, in <module>
  File "/home/travis/virtualenv/python3.5.3/lib/python3.5/site-packages/PyInstaller/loader/pyimod03_importers.py", line 714, in load_module
ImportError: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1: undefined symbol: drmGetDevices2
[24271] Failed to execute script __main__

and since then I have not been able to work things around, and I just loosed all of my logs. please help. 😄

os : ubuntu 16.04

Issue Analytics

State:
Created 6 years ago
Comments:10 (8 by maintainers)

Top GitHub Comments

6reactions

ErikBjarecommented, Jan 26, 2018

Found some other projects having a very similar issue and setup:

Apparently, a workaround is to remove or rename libdrm.so.2 from the folder where the executable is located. Since libdrm should be available on all systems anyway we might want to remove them from the builds entirely.

2reactions

ErikBjarecommented, Feb 2, 2018

My best guess is that the previous instance of aw-server is still running. If you can still access the web UI, that is definitely the case.

Kill the process manually (using the terminal or a process manager) and try again.

Sorry for the problems, and thanks for helping us learn about these issues 😃