After the v4.8.7 release, I cannot launch telegram desktop because of the
recent dbus support introduced in
2dfe858327.
And it was fixed after I changed the value of the Exec field to absolute
path to the telegram-desktop executable.
In dbus specification they don't mention that they will find
executable from PATH variable, so this is a UB.
After this commit, cmake will use the full install path to generate the correct service file
and fix the above issue.
Signed-off-by: Avimitin <dev@avimit.in>
This key was mainly used to let flatpak and snap provide right desktop file name.
Now, we can compute it from the environment in runtime for both flatpak and snap.
There's no more need in this option. Desktop filename override by downstreams is highly discouraged.
Changed money-purchasing from 'none' to 'intense' as the in-app purchase of telegram premium is available.
Added money-advertising and set it to 'moderate' as telegram ads has been introduced.
SingleMainWindow is a part of XDG SPEC version 1.5 and bogus on 1.0.
Co-authored-by: gasinvein <gasinvein@gmail.com>
Signed-off-by: Vitaly Zaitsev <vitaly@easycoding.org>
`X-GNOME-SingleWindow` is best to be used for backward compatibility. Since `SingleMainWindow` was recently added, many Desktop Environments and Window Managers may not have it implemented yet.
This MR also moves `SingleMainWindow` before the `X-GNOME-*` keys, as requested in this comment: https://github.com/telegramdesktop/tdesktop/pull/23875#issuecomment-1008453759
Telegram is a single-instance app; attempting to open a second instance
fails and simply focuses the existing instance. However the app's
.desktop file does not indicate this to Linux desktop shells like GNOME
and KDE Plasma, causing them to show a "Start new instance/Open new
window" action for the app that will not work when used.
This commit fixes that by setting `X-GNOME-SingleWindow=true` in the
desktop file. This is a GNOME-specific key, but it is honored in KDE
Plasma too.
