jami-packaging issueshttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues2022-05-26T15:38:20Zhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/113snap: offload snap builds to launchpad2022-05-26T15:38:20ZAmin Bandalisnap: offload snap builds to launchpadAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/108snap: ibus-pinyin not working correctly with client-qt snap2021-10-04T14:28:26ZAmin Bandalisnap: ibus-pinyin not working correctly with client-qt snapThe ibus-pinyin input method does not work properly with the `jami` client-qt snap.
I've done some investigating, and I'm not sure about the exact cause of the issue. The client-qt snap, much like the client-gnome snap, creates a `deskt...The ibus-pinyin input method does not work properly with the `jami` client-qt snap.
I've done some investigating, and I'm not sure about the exact cause of the issue. The client-qt snap, much like the client-gnome snap, creates a `desktop-launch` script based on snapcraft-desktop-helpers's desktop export, which exports the relevant ibus socket path:
https://github.com/ubuntu/snapcraft-desktop-helpers/blob/ec861254c2a1d2447b2c589446e6cdf04c75c260/common/desktop-exports#L451
https://git.jami.net/savoirfairelinux/jami-project/-/blob/835f5ae66c5ccd97277a6bf8a228b516a79d8b29/packaging/rules/snap/jami/snapcraft.yaml#L187
Ideas and/or help with further investigating and fixing this issue are welcome. :slight_smile: