Context:
- Package: telegram-desktop 6.3.6
- Desktop environment: Sway (Wayland)
- Guix revision: commit e67189651f8909fbe0ed677c8e41ad12926a8c1e
Hello,
I would like to report an issue with the `.desktop` file shipped by the
`telegram-desktop` package in GNU Guix.
The file `org.telegram.desktop.desktop` currently contains:
```
DBusActivatable=true
```
On non-GNOME desktop environments (for example Sway, wlroots-based
compositors, i3-like setups), this causes Telegram Desktop to fail
silently when launched from application menus. The menu tries DBus
activation instead of executing `Exec=`, but Telegram Desktop is not
reliably DBus-activatable in such environments. As a result, nothing
happens when clicking the launcher, while launching the exact same
command from a terminal works correctly.
This issue usually does not appear under GNOME because GNOME Shell
compensates for failed DBus activation. In more minimal or
spec-compliant environments, however, the problem is immediately visible.
From testing, removing `DBusActivatable=true` (or setting it to
`false`) restores correct and consistent behavior: the menu launches
Telegram using `Exec=`, matching the terminal behavior.
Since Telegram Desktop does not seem to require DBus activation for
correct operation, and since this key breaks usability on non-GNOME
desktops, I believe it would be better to drop `DBusActivatable=true`
from the `.desktop` file in the Guix package.
For transparency: this report was written with the assistance of
ChatGPT, under my direction. The investigation and understanding of the
root cause were reached through an interactive debugging process with
ChatGPT; without this assistance, I would likely not have identified the
origin of the problem.
Thank you for your work on maintaining Telegram Desktop in Guix, and for
considering this report.
Best regards,
Mathieu
