ActivityWatch / ActivityWatch/activitywatch

After 0.12.1 -> 0.13.1 update "Activity" page doesn't show AFK/Window/Browser events

Abierto
#1,076 15 comentarios 3 reacciones 0 asignados Ver en GitHub
type: bug
Lenguaje dominante
Python
Estrellas
18.9k
Forks
1k
Merge medio
1 d 4 h
PR fusionados (30 d)
28

Descripción

- [x] I am on the [latest](https://github.com/ActivityWatch/activitywatch/releases/latest) ActivityWatch version.
- [x] I have searched the issues of this repo and believe that this is not a duplicate.

- **Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy Desktop: Xfce 4.18.1 tk: Gtk 3.24.33**:
- **v0.13.1**:

## Describe the bug
After updating from v0.12.1 to v0.13.1 on http://localhost:5600/#/activity/host_name/view/ nothing is displayed in "Summary", "Window", "Browser" tabs. Only "Editor" tab shows data.

While on http://localhost:5600/#/timeline I see all events, there are window and AFK events in http://localhost:5600/#/buckets. Other pages also work. From errors in log I see only `Gtk-Message: 09:31:31.782: Failed to load module "xapp-gtk3-module"` which doesn't look relevant.

Default configuration in "/home/user/.config/activitywatch" (everything is commented out). Default Views configuration on http://localhost:5600/#/activity/host_name/view/

## To Reproduce
1. Use 0.12.1 version some time. Installed from sources.
2. Download https://github.com/ActivityWatch/activitywatch/releases/download/v0.13.1/activitywatch-v0.13.1-linux-x86_64.zip
3. Remove "/home/user/activitywatch/" and unpack ZIP into it.
4. Run `/home/user/activitywatch/./aw-qt` and go to http://localhost:5600/#/activity/host_name/view/

## Expected behavior
![image](https://github.com/ActivityWatch/activitywatch/assets/2630978/d9197ed2-831e-4ab7-a2de-86e897cbf3d5)
(from old v0.12.1 which I have to revert back)

## Actual behavior
![image](https://github.com/ActivityWatch/activitywatch/assets/2630978/06e8075a-45c7-4265-8d98-e25bc3aa33e0)

## Documentation

## Additional context

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.