Package: arthaVersion: 1.0.5-5 Severity: important No relevant error messages are logged to Artha's stdout afaict.
1. Artha does not start via [XDG autostart](https://specifications.freedesktop.org/autostart/latest/). 2. Artha does not start when launched from its desktop entry (nor show its window when launched a 2nd time because the 1st time didn't start it) unless Artha has already been started through another means (running `artha` in the terminal does start Artha even if Artha's default behavior is to not show its window on start). 3. Artha does not show a system tray icon when running & the option to control whether or not Artha shows a system tray icon when running is missing. As a workaround for failure to autostart and failure to launch from the desktop entry, creating a desktop file `/usr/local/share/applications/net.sourceforge.artha.desktop` with `DBusActivatable=true` commented out worked for me. ``` $ sudo mkdir -p /usr/local/share/applications/ $ sudo cp /usr/share/applications/net.sourceforge.artha.desktop /usr/local/share/applications/ $ sudo vi /usr/local/share/applications/net.sourceforge.artha.desktop # comment out `DBusActivatable=true` ``` Artha's desktop file id did change between Debian 12 and Debian 13 which would reasonably result in XDG autostart to newly fail on Debian 13 migration, but even with the correct desktop file id, Artha still fails XDG autostart unless the mentioned workaround was applied. An example autostart file that I am using on Debian 13 is: ``` $ cat ~/.config/autostart/net.sourceforge.artha.desktop [Desktop Entry] Type=Application Name=net.sourceforge.artha.desktop TryExec=gtk-launch Exec=gtk-launch net.sourceforge.artha.desktop AutostartCondition=unless-exists disable-autostart ``` That is not a minimal example. No workaround for Artha being absent from the system tray was found. Artha, once running, can be configured to show its window when Artha's global hotkey (usually Ctrl+Alt+W) is hit, but this is not the default configuration & is not easy for a user to change upon facing these bugs so I would not suggest that is a workaround. Changing Artha's configuration via the GUI requires getting Artha to show its window which is made more confusing by Artha's (not a bug) default behavior of not showing the window on 1st launch but showing it if launched a 2nd time. I am not aware of if Artha has any file-based configuration that would be an alternative workaround. Expected behavior for the system-tray part would be that: 1. Artha should show its icon in the system tray by default once launched by any means, including autostart. 2. And left-clicking on Artha's system tray icon should launch Artha's window by default (I assume this is the default based on Debian 12 Artha's behavior) 3. And Artha's GUI should have the configuration settings found in in Debian 12 Artha (or presumably in upstream Artha) that allow hiding and unhiding the system tray icon. Unrelated to this bug but worth mentioning for anyone trying to use Artha's global hotkey to launch Artha's window as described above: At least one application uses Ctrl+Shift+W as the hotkey to close all open documents so maybe consider changing Artha's hotkey (usually defaults to Ctrl+Alt+W) to something you won't regret when you inevitably forget and try the wrong key combination... I am reporting these bugs together as one bug because these bugs were not present in Artha on Debian 12 and comparing the patches between Debian 13 and Debian 12, it's possible that one or more of the patches in Debian 13 but not in Debian 12 could have caused these behaviors. I am using Artha in a virtual machine under Qubes OS so I'm not clear whether or not parts of this like the `DBusActivatable=true` line in the desktop file are making Artha effectively inoperable for all users on Debian 13. But as far as the Artha package is considered for me on Debian 13 under virtualization, it's not working out of the box at all and Artha did previously work as expected on Debian 12 for me, so this is at least severity important. Higher if someone can reproduce all of these 3 seemingly related issues on a stock Debian 13 system.
