No Tray Icon (KDE)

[cameronj86]

Everything else is working as expected I believe, so not a huge priority tbh.

I used to run the standalone modules before transitioning over to the bundled version, so my (un)educated guess is that there might be some overlap there perhaps?

I checked ~/.config/activitywatch/aw-qt.toml and it is just the following:

[aw-qt]
autostart_modules = ["aw-server","aw-watcher-mpv","aw-awatcher","aw-sync","aw-watcher-media-player"] #Wayland Config

[aw-qt-testing]
#autostart_modules = ["aw-server", "aw-watcher-afk", "aw-watcher-window","aw-watcher-mpv","aw-watcher-mpd"]

#autostart_modules = ["aw-server", "aw-watcher-afk", "aw-watcher-window","aw-watcher-mpv"] #X11 Config
#,"aw-watcher-mpd" #Not working so I removed it to stop the minor error when I launch the server

I tried changing aw-server -> aw-server-rust and commenting out [aw-qt-testing] as well just now on a whim but doesn't appear to make any difference either. I'm at the 'throw it against the wall and see what sticks' phase and figured I should ask someone before I break something important lol.

[cameronj86]

It stopped working completely over the last few days. I removed activitywatch and then awatcher. Reinstalled bundled awatcher .deb file solely to avoid any duplication of servers but that wasn't working. I then reinstalled activitywatch alongside it, and not only is activitywatch working again, but the tray appeared for the first time also.

Not quite sure what's going on tbh but I was getting the 'connection refused' error like #38 prior to my deletion/reinstall

Closing this out since the tray is showing, and the 'bundle still requiring stock aw' quirk is being addressed in other tix

Edit: Just realized I repurposed the suggested .service file but didn't update ExecStart to point to awatcher instead of the default aw-watcher. Might explain the inconsistencies a bit.

[2e3s]

Alright, glad it works now! Such an issue isn't easily approachable. I would suggest to look at and post the output logs from the terminal to facilitate the debug, there might be some warnings to notice.

Closing this out since the tray is showing, and the 'bundle still requiring stock aw' quirk is being addressed in other tix

What do you mean, where is this addressed? It's not supposed to require the stock activitywatch, I don't see how it could. Maybe the issue was a mix of autorunning original watchers, server and awatcher.

[cameronj86]

Sorry, to clarify my Edit was the actual issue/resolution.

I vaguely remember getting a connection error similar to #38 and was following the last post. (In retrospect, the OP was talking about the bundle while the last post recommends a solution using the standalone version).

I think the similar names tripped me up a few times overall. Now that I'm sitting down and thinking about it, the naming convention makes sense (ie: aw-awatcher starts w/ aw-and is therefore a normal aw watcher), but I still got it wrong. One unsolicited suggestion is to differentiate the bundle w/ a bit more of a unique name (ie awatcher-bundle instead of simply awatcher)

Then again, it might break autostart/service files for anyone who upgrades so I get keeping things as is too