savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-06-16T13:25:22Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/381Emojis picker translations2023-06-16T13:25:22ZovariEmojis picker translationsPlease enable the emojis picker to be translatable.
1. Search emojis…
1. Recent emojis
1. Smileys & emotions
1. People & body
1. Animals & nature
1. Food & drink
1. Activities
1. Travel & places
1. Objects
1. Symbols
1. Flags
1. Popups ...Please enable the emojis picker to be translatable.
1. Search emojis…
1. Recent emojis
1. Smileys & emotions
1. People & body
1. Animals & nature
1. Food & drink
1. Activities
1. Travel & places
1. Objects
1. Symbols
1. Flags
1. Popups when hovering on an emoji
![image](/uploads/a137fc72eeaba6fdaa3a1720e9605959/image.png)
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/926Unwanted app starts2021-04-18T18:47:21ZLicaon_KterUnwanted app starts...even if "start at boot" is disabled.
F-Droid 20210409-01 (293), Android 10 or Android 6
## Steps:
1. start Jami
2. force close Jami
3. use the device (no reboots needed)
## Expected:
Jami is off
## Actual result:
Jami is woken u......even if "start at boot" is disabled.
F-Droid 20210409-01 (293), Android 10 or Android 6
## Steps:
1. start Jami
2. force close Jami
3. use the device (no reboots needed)
## Expected:
Jami is off
## Actual result:
Jami is woken up seemingly at random _(I guess by network switching events)_.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/130add RDV point2024-02-15T15:52:40ZKateryna Kostiukadd RDV pointhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/366Enable chatview when `ringing` or `calling` a contact2021-05-27T22:45:02ZovariEnable chatview when `ringing` or `calling` a contact`jami-client-gnome`: The chatview is shown and messages can be typed when an audio/video calling is started (but not yet connected).
`jami-android`: The chatview can be shown when an audio/video calling is started (but not yet connected...`jami-client-gnome`: The chatview is shown and messages can be typed when an audio/video calling is started (but not yet connected).
`jami-android`: The chatview can be shown when an audio/video calling is started (but not yet connected).
`jami-client-qt`: Can messages be sent to a contact that is being called? If not, can this feature be implemented?
Thank youhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/507Unable to kick local participant from rendez-vous2024-01-26T12:42:50ZPierre LespagnolUnable to kick local participant from rendez-vous# Scenario
- Bob join RDV-Bob (2 accounts same device)
- Bob join RDV-Alice
- Alice join RDV-Alice (2 accounts same device)
- Bob kick Alice from conference
# Expected result
- Alice is kicked from RDV-Alice
# Current result
- Alice is...# Scenario
- Bob join RDV-Bob (2 accounts same device)
- Bob join RDV-Alice
- Alice join RDV-Alice (2 accounts same device)
- Bob kick Alice from conference
# Expected result
- Alice is kicked from RDV-Alice
# Current result
- Alice is not kicked
# Logs
```
Invalid conference state in detach participant: current "ACTIVE_DETACHED" - expected "ACTIVE_ATTACHED"
```Pierre LespagnolPierre Lespagnolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/506plugins: set handlers activation order2021-04-01T12:53:01ZAline Gondim Santosplugins: set handlers activation orderUser should be able to change the order each handler is called from the observable notify.User should be able to change the order each handler is called from the observable notify.BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/71Add permission to blueprint to forbid users searching the nameserver for othe...2021-04-07T10:30:13ZLarbi GharibAdd permission to blueprint to forbid users searching the nameserver for other contactsScenario:
When a user start searching in Jami he should not have results
Todo:
Add a boolean to the blueprint
Check the boolean on the
EN: Allow user to search and add other contacts
FR: Autoriser l'utilsateur à chercher et ajouter ...Scenario:
When a user start searching in Jami he should not have results
Todo:
Add a boolean to the blueprint
Check the boolean on the
EN: Allow user to search and add other contacts
FR: Autoriser l'utilsateur à chercher et ajouter d'autres contactsLarbi GharibGuillaume HellerLarbi Gharibhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1215Please detect status 488 from SIP server and offer suggestions to change codec2023-05-29T13:37:07ZreubenfirminPlease detect status 488 from SIP server and offer suggestions to change codecWhen a SIP server returns 488, it can mean a codec incompatibility. Your UI buries that 488 is returned. Please detect the status and pop up the settings asking the user to check the codecs vs what the voip provider allows.When a SIP server returns 488, it can mean a codec incompatibility. Your UI buries that 488 is returned. Please detect the status and pop up the settings asking the user to check the codecs vs what the voip provider allows.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/916samsung galaxy j3 prime: Video and sound become choppy and call drops2022-01-03T02:01:58ZMaxim Cournoyersamsung galaxy j3 prime: Video and sound become choppy and call dropsBug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Stor...Bug report form
---------------
## Describe your environment
Please specify the following:
- Ring version: 20210315-01
- Device model: Samsung Galaxy J3 (SM-J327W)
- Android version: 8.1.0
- On the Samsung Galaxy J3: Play Store; on the other device: Tried with Play store (20210315-01) or jami-gnome built from the latest sources on GNU/Linux
## Steps to reproduce
- Can you reproduce the bug: With one of my contacts though which is using a SM-J327W device, it always occur on her side (their Jami app crashes after a while). I couldn't reproduce using a SM-J320W8 (a different, but close model).
- Steps:
1. Call Jami on a Samsung Galaxy J3 SM-J327W
1. The call originally proceeds normally, with good video and audio and a decent framerate (~15 fps on both ends).
1. After 2-5 minutes of call, the video and audio sent from the Galaxy J3 device becomes choppy, with the framerate dropping to near zero (0.09 fps) and eventually the call dropping.
- Actual result: The call drops after a while.
- Expected result: The video and audio should remain fluid, and the call should not drop even after a prolonged period of time.
## Additional information
The phone specs are available from https://www.phonearena.com/phones/Samsung-Galaxy-J3-Prime_id10506. It has the following processor and GPU:
- CPU: Quad-core, 1400 MHz, ARM Cortex-A53, 64-bit, 28 nm
- GPU: Adreno 308
- RAM: 1.5 GiBhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/492libnatpmp is always used from contribs2023-05-05T19:02:06ZMaxim Cournoyerlibnatpmp is always used from contribsThe contrib build system relies on pkg-config to detect system libraries, as done here:
```
ifeq ($(call need_pkg,'libnatpmp'),)
PKGS_FOUND += natpmp
endif
```
This never marks natpmp as found, because libnatpmp doesn't install any pkg...The contrib build system relies on pkg-config to detect system libraries, as done here:
```
ifeq ($(call need_pkg,'libnatpmp'),)
PKGS_FOUND += natpmp
endif
```
This never marks natpmp as found, because libnatpmp doesn't install any pkg-config file (.pc), thus cannot be found via pkg-config.
Possible solution: Rather than reinvent the wheel in this contrib build system, perhaps we could use Autoconf as the configuration driver of the contribs build system, which is quite capable in this regard. It could return a list of targets needed from the contribs build system to be built, and add them as dependencies.https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/17SDK: add dependsOn to preference structure2021-03-19T16:09:21ZAline Gondim SantosSDK: add dependsOn to preference structure"dependsOn" was added to preferences structure and is supported by the client-qt.
Plugins SDK should foresee this preference characteristic."dependsOn" was added to preferences structure and is supported by the client-qt.
Plugins SDK should foresee this preference characteristic.BacklogAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/70Replace Statement database management with ORM such as Hibernate2021-03-17T20:17:11ZLarbi GharibReplace Statement database management with ORM such as HibernateAdrien BéraudGuillaume HellerLarbi GharibAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/126SIP account: could not detect audio only call2021-03-17T20:10:56ZKateryna KostiukSIP account: could not detect audio only callA video preview is showing for an incoming audio-only callA video preview is showing for an incoming audio-only callhttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/14Fancy hat plugin2021-04-14T15:08:13ZSébastien BlinFancy hat pluginCreate plugin to add accessories like hats, tiaras, glasses, wigs...Create plugin to add accessories like hats, tiaras, glasses, wigs...Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/907MIUI/Android's dark theme inverts my qr code image2021-03-15T17:55:08ZMIUI/Android's dark theme inverts my qr code imageWhen system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account...When system option "dark mode" is enabled jami qr code becomes inverted no matter what theme is active as jami's option.
All dark theme's differences are:
1. three button backgrounds "QR code" "Share" "Link a new device" in "Account" tab,
2. in qr section there are qr image and "Share my QR" button,
3. in "conversations" tab in "About jami" the "credits" button background,
4. In account choosing menu, default profile pictures (only the "human" part), and in profile picture choosing dialog. The human part changes its color to black, while in chats those stay white
(Button backgrounds in 1, 2, 3 are white in jami's dark theme, and android's dark mode turns them to very dark color. But button text is still kind of readable because of blueish text color)
MIUI 12.0.1 Android 10https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/476No SIP registration due to bad network detection2021-03-15T14:53:10ZEnrico ScholzNo SIP registration due to bad network detectionjami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
*...jami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
```
<details>
<summary>Full Log</summary>
<pre>
$ ring.cx --debug
(jami-gnome:822803): GLib-DEBUG: 14:24:25.931: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:822803): DEBUG: 14:24:25.931: debug enabled
** Message: 14:24:25.933: Jami GNOME client version: development
** Message: 14:24:25.933: git ref: unknown
** (jami-gnome:822803): DEBUG: 14:24:25.933: enabling autostart
** (jami-gnome:822803): DEBUG: 14:24:25.933: checking /usr/share/jami-gnome/jami-gnome.desktop
(jami-gnome:822803): dconf-DEBUG: 14:24:25.933: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
** (jami-gnome:822803): DEBUG: 14:24:25.934: '/home/ensc/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:822803): dbind-WARNING **: 14:24:25.945: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de_DE
(jami-gnome:822803): GLib-GIO-DEBUG: 14:24:26.106: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): GLib-DEBUG: 14:24:26.178: unsetenv() is not thread-safe and should not be used after threads are created
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Connecting to session manager
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
Can't open file: "/home/ensc/.local/share/jami/606bab6fe62f6e4c/profile.vcf"
** (jami-gnome:822803): DEBUG: 14:24:26.254: notify server name: naughty, vendor: awesome, version: 3.5, spec: 1.0
(jami-gnome:822803): Gtk-WARNING **: 14:24:26.255: Child name 'calls' not found in GtkStack
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.257: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 1)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.GoaVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (g-dbus-error-quark, 3)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.413: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.414: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.565: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 2)
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.585: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_notify: /net/jami/JamiGnome/show-main-window
(process:822825): GLib-GIO-DEBUG: 14:24:26.661: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: NetworkManager not running
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: _g_io_module_get_default: Found default implementation netlink (GNetworkMonitorNetlink) for ?gio-network-monitor?
(WebKitWebProcess:822824): dbind-WARNING **: 14:24:26.672: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
(jami-gnome:822803): dconf-DEBUG: 14:24:26.701: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_notify: /net/jami/JamiGnome/window-maximized
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
** (jami-gnome:822803): WARNING **: 14:24:26.718: no primary network connection detected, check network settings
(process:822825): GLib-GIO-DEBUG: 14:24:26.740: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-height
(WebKitWebProcess:822824): GLib-GIO-DEBUG: 14:24:26.796: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): Gdk-CRITICAL **: 14:24:26.880: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-height
</pre>
</details>
I am not using Gnome and network is managed manually (no NetworkManager)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/902Send image/videos form gallery - AndroidTV2021-03-08T18:59:39ZAmirhossein NaghshzanSend image/videos form gallery - AndroidTVCurrently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.Currently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/463Replace Portaudio with WASAPI to support communication device enumeration and...2021-03-22T19:50:52ZAndreas TraczykReplace Portaudio with WASAPI to support communication device enumeration and output loopbackAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/67Expired session will editing2021-02-24T17:40:41ZLarbi GharibExpired session will editingStart new session
Start editing
After few minutes user experiences issuesStart new session
Start editing
After few minutes user experiences issueshttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/119Please, write clear release notes at the AppStore2021-02-22T16:17:44ZArtemy GavrelyukPlease, write clear release notes at the AppStoreHello. I've found out that last three or five versions of Jami at AppStore has the following release notes: "bug fixes". This is very unclear for the user, what was fixed exactly.
Please, use more clear release notes when you publish a ...Hello. I've found out that last three or five versions of Jami at AppStore has the following release notes: "bug fixes". This is very unclear for the user, what was fixed exactly.
Please, use more clear release notes when you publish a new version of Jami at AppStore