jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2019-11-06T15:19:53Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1075allow to record and send audio and video clips2019-11-06T15:19:53ZAdrien Béraudallow to record and send audio and video clipsNew release 1Sébastien BlinSébastien Blin2019-10-31https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1083Conference: display username instead of hash + other improvements2023-05-26T13:59:19ZGuillaume HellerConference: display username instead of hash + other improvements* Display username instead of user hash in the conference add contact list
* Add online green dot to avoid any confusion (even if the list only displays the online contacts)
* Add the possibility to hang up/cancel the addition of a ne...* Display username instead of user hash in the conference add contact list
* Add online green dot to avoid any confusion (even if the list only displays the online contacts)
* Add the possibility to hang up/cancel the addition of a new participant before he picked up(cf implementation done on MacOS, cancel option appears directly in the chatview)New release 1https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1076Date should show in correct locale format2021-03-20T20:35:18ZovariDate should show in correct locale formatWas speaking to a contact who has macOS and he didn't like how the date was showing in US format. He would like the date to show in accordance with the date sets in the system locale settings which is dd/mm/yy. Unsure of exactly where th...Was speaking to a contact who has macOS and he didn't like how the date was showing in US format. He would like the date to show in accordance with the date sets in the system locale settings which is dd/mm/yy. Unsure of exactly where this date was showing incorrectly as we do not have a macOS. @kkostiuk are you able to find where this is? If so does another issue need to be created in the Jami macOS client section?
The date format is also incorrectly shown in the Jami GNOME client. The chatview seems to show the date correctly according to the system locale setting. Please see image below. @sblin can you please fix the date format to show from `mm/dd/yy` to `dd/mm/yyyy`?
If the last conversation was in the last week, can the date in the conversations panel be replaced by the day? i.e. `Monday`, `Tuesday`, `Wednesday`, `Thursday`, `Friday`, `Saturday`, `Sunday`
If the last conversation was in the last day, can the date in the conversations panel be replaced by the time in accordance with the system time setting? i.e. `6:57 PM`, `6:57 p.m.` or `18:57`
![image](/uploads/3cdc1c568df4ff41d05b1c7a3b3efc4f/image.png)
Do the other clients need fixing too? Or is this a issue with the daemon or otherwise?
Thank youNew release 1Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1066Frame Rate in media settings should remain after restart2019-11-15T10:10:30ZannaFrame Rate in media settings should remain after restartHi, at the moment the value is reset to `10` by Jami after every restart. This happens for all active accounts.
Or does it have something to do with automatic adjustment? https://jami.net/video-encoding-in-jami/Hi, at the moment the value is reset to `10` by Jami after every restart. This happens for all active accounts.
Or does it have something to do with automatic adjustment? https://jami.net/video-encoding-in-jami/New release 1Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1001Gnome client crashes on "Clear all history"2019-11-15T10:09:12ZJérôme OufellaGnome client crashes on "Clear all history"* Fedora 29
* ring-20190319.4.a16a99f-1.fc29.x86_64
How to reproduce:
* Go to Settings
* Clear chat history
```
Mar 28 11:01:20 hostname systemd-coredump[29158]: Process 26945 (gnome-ring) of user 1000 dumped core.
...* Fedora 29
* ring-20190319.4.a16a99f-1.fc29.x86_64
How to reproduce:
* Go to Settings
* Clear chat history
```
Mar 28 11:01:20 hostname systemd-coredump[29158]: Process 26945 (gnome-ring) of user 1000 dumped core.
Stack trace of thread 26945:
#0 0x00007f11873f153f raise (libc.so.6)
#1 0x00007f11873db895 abort (libc.so.6)
#2 0x00007f11877b0f1b n/a (libstdc++.so.6)
#3 0x00007f11877b738c n/a (libstdc++.so.6)
#4 0x00007f11877b73e7 _ZSt9terminatev (libstdc++.so.6)
#5 0x00007f11877b7648 __cxa_throw (libstdc++.so.6)
#6 0x00007f118d2b5954 n/a (libringclient.so.1.0.0)
#7 0x00000000004608c8 _ZN12_GLOBAL__N_17detailsL28on_clear_all_history_foreachEP13_GtkTreeModelP12_GtkTreePathP12_GtkTreeIterPv (gnome-ring)
#8 0x00007f118cd9408a n/a (libgtk-3.so.0)
#9 0x00007f118cd954c9 gtk_tree_model_foreach (libgtk-3.so.0)
#10 0x0000000000460a4d _ZN12_GLOBAL__N_17detailsL28on_clear_all_history_clickedEP15_RingMainWindow (gnome-ring)
#11 0x00007f118c56c3dd g_closure_invoke (libgobject-2.0.so.0)
#12 0x00007f118c57f983 n/a (libgobject-2.0.so.0)
#13 0x00007f118c588aaa g_signal_emit_valist (libgobject-2.0.so.0)
#14 0x00007f118c5890a3 g_signal_emit (libgobject-2.0.so.0)
#15 0x00000000004a5530 _ZL13clear_historyP10_GtkWidgetP20_GeneralSettingsView (gnome-ring)
#16 0x00007f118c56c636 n/a (libgobject-2.0.so.0)
#17 0x00007f118c588b01 g_signal_emit_valist (libgobject-2.0.so.0)
#18 0x00007f118c5890a3 g_signal_emit (libgobject-2.0.so.0)
#19 0x00007f118cb7b19d n/a (libgtk-3.so.0)
#20 0x00007f118cb7b209 n/a (libgtk-3.so.0)
#21 0x00007f118c56c3dd g_closure_invoke (libgobject-2.0.so.0)
#22 0x00007f118c57fb26 n/a (libgobject-2.0.so.0)
#23 0x00007f118c588aaa g_signal_emit_valist (libgobject-2.0.so.0)
#24 0x00007f118c5890a3 g_signal_emit (libgobject-2.0.so.0)
#25 0x00007f118cb79664 n/a (libgtk-3.so.0)
#26 0x00007f1186872ace ffi_call_unix64 (libffi.so.6)
#27 0x00007f118687248f ffi_call (libffi.so.6)
#28 0x00007f118c56d3a6 g_cclosure_marshal_generic_va (libgobject-2.0.so.0)
#29 0x00007f118c56c636 n/a (libgobject-2.0.so.0)
#30 0x00007f118c588b01 g_signal_emit_valist (libgobject-2.0.so.0)
#31 0x00007f118c5890a3 g_signal_emit (libgobject-2.0.so.0)
#32 0x00007f118cc40e0c n/a (libgtk-3.so.0)
#33 0x00007f118c56f7ee g_cclosure_marshal_VOID__BOXEDv (libgobject-2.0.so.0)
#34 0x00007f118c56c636 n/a (libgobject-2.0.so.0)
#35 0x00007f118c588b01 g_signal_emit_valist (libgobject-2.0.so.0)
#36 0x00007f118c5890a3 g_signal_emit (libgobject-2.0.so.0)
#37 0x00007f118cc3df12 n/a (libgtk-3.so.0)
#38 0x00007f118cc3f51b n/a (libgtk-3.so.0)
#39 0x00007f118cc4241e n/a (libgtk-3.so.0)
#40 0x00007f118cc0a245 gtk_event_controller_handle_event (libgtk-3.so.0)
#41 0x00007f118cdca35b n/a (libgtk-3.so.0)
#42 0x00007f118ce1f7c8 n/a (libgtk-3.so.0)
#43 0x00007f118c56c636 n/a (libgobject-2.0.so.0)
#44 0x00007f118c588524 g_signal_emit_valist (libgobject-2.0.so.0)
#45 0x00007f118c5890a3 g_signal_emit (libgobject-2.0.so.0)
#46 0x00007f118cdcc634 n/a (libgtk-3.so.0)
#47 0x00007f118cc88946 n/a (libgtk-3.so.0)
#48 0x00007f118cc8ab03 gtk_main_do_event (libgtk-3.so.0)
#49 0x00007f118c97ba39 n/a (libgdk-3.so.0)
#50 0x00007f118c9ad446 n/a (libgdk-3.so.0)
#51 0x00007f118c48a06d g_main_context_dispatch (libglib-2.0.so.0)
#52 0x00007f118c48a438 n/a (libglib-2.0.so.0)
#53 0x00007f118c48a4d0 g_main_context_iteration (libglib-2.0.so.0)
#54 0x00007f118c65ad25 g_application_run (libgio-2.0.so.0)
#55 0x0000000000458e4f main (gnome-ring)
#56 0x00007f11873dd413 __libc_start_main (libc.so.6)
#57 0x0000000000458c1e _start (gnome-ring)
Stack trace of thread 26947:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a762 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f118c68810a n/a (libgio-2.0.so.0)
#4 0x00007f118c4b32aa n/a (libglib-2.0.so.0)
#5 0x00007f118730b58e start_thread (libpthread.so.0)
#6 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26946:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a4d0 g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f118c48a521 n/a (libglib-2.0.so.0)
#4 0x00007f118c4b32aa n/a (libglib-2.0.so.0)
#5 0x00007f118730b58e start_thread (libpthread.so.0)
#6 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26992:
#0 0x00007f1187311a8a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f118885a65e _ZN3WTF15ThreadCondition9timedWaitERNS_5MutexENS_8WallTimeE (libjavascriptcoregtk-4.0.so.18)
#2 0x00007f118882f723 _ZN3WTF10ParkingLot21parkConditionallyImplEPKvRKNS_12ScopedLambdaIFbvEEERKNS3_IFvvEEERKNS_24TimeWithDynamicClockTypeE (libjavascriptcore>
#3 0x00007f11888329aa _ZN3WTF5sleepENS_7SecondsE (libjavascriptcoregtk-4.0.so.18)
#4 0x00007f118947b4d5 n/a (libwebkit2gtk-4.0.so.37)
#5 0x00007f118883354f _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18)
#6 0x00007f1188859c1d n/a (libjavascriptcoregtk-4.0.so.18)
#7 0x00007f118730b58e start_thread (libpthread.so.0)
#8 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26949:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a4d0 g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f118d563c7d n/a (libdconfsettings.so)
#4 0x00007f118c4b32aa n/a (libglib-2.0.so.0)
#5 0x00007f118730b58e start_thread (libpthread.so.0)
#6 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26951:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a4d0 g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f118c1fb593 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
#4 0x00007f118c1a9e0b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5 0x00007f118c011e86 _ZN7QThread4execEv (libQt5Core.so.5)
#6 0x00007f118733cf89 n/a (libQt5DBus.so.5)
#7 0x00007f118c01b2fb n/a (libQt5Core.so.5)
#8 0x00007f118730b58e start_thread (libpthread.so.0)
#9 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 29057:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a762 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f118885bbc0 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18)
#4 0x00007f118883354f _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18)
#5 0x00007f1188859c1d n/a (libjavascriptcoregtk-4.0.so.18)
#6 0x00007f118730b58e start_thread (libpthread.so.0)
#7 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26950:
#0 0x00007f118731173c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f11808f68bb n/a (i965_dri.so)
#2 0x00007f11808f65fb n/a (i965_dri.so)
#3 0x00007f118730b58e start_thread (libpthread.so.0)
#4 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26993:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a762 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f118885bbc0 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18)
#4 0x00007f118883354f _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18)
#5 0x00007f1188859c1d n/a (libjavascriptcoregtk-4.0.so.18)
#6 0x00007f118730b58e start_thread (libpthread.so.0)
#7 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26994:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a762 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f118885bbc0 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18)
#4 0x00007f118883354f _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18)
#5 0x00007f1188859c1d n/a (libjavascriptcoregtk-4.0.so.18)
#6 0x00007f118730b58e start_thread (libpthread.so.0)
#7 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 27030:
#0 0x00007f11874ab421 __poll (libc.so.6)
#1 0x00007f118c48a3a6 n/a (libglib-2.0.so.0)
#2 0x00007f118c48a762 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f118885bbc0 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18)
#4 0x00007f118883354f _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18)
#5 0x00007f1188859c1d n/a (libjavascriptcoregtk-4.0.so.18)
#6 0x00007f118730b58e start_thread (libpthread.so.0)
#7 0x00007f11874b66a3 __clone (libc.so.6)
Stack trace of thread 26991:
#0 0x00007f118731173c pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f11877dd6f0 _ZNSt18condition_variable4waitERSt11unique_lockISt5mutexE (libstdc++.so.6)
#2 0x00007f118886b58c _ZN7bmalloc9Scavenger13threadRunLoopEv (libjavascriptcoregtk-4.0.so.18)
#3 0x00007f118886b8df _ZN7bmalloc9Scavenger16threadEntryPointEPS0_ (libjavascriptcoregtk-4.0.so.18)
#4 0x00007f11877e39a3 n/a (libstdc++.so.6)
#5 0x00007f118730b58e start_thread (libpthread.so.0)
#6 0x00007f11874b66a3 __clone (libc.so.6)
```New release 1Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1052Improve conference creation2019-11-20T08:44:30ZSébastien BlinImprove conference creationActually to add a call to the conference, the user has to drag and drop the other call. This is bad, because the feature is hidden and can be improved a lot. Also, this behaviour make it impossible to merge a SIP call with a Jami call (w...Actually to add a call to the conference, the user has to drag and drop the other call. This is bad, because the feature is hidden and can be improved a lot. Also, this behaviour make it impossible to merge a SIP call with a Jami call (which is possible to do in the daemon).
# Idea
Use the same widget as the SIP transfer call (the dropdown), showing current calls on all enabled accounts + present contacts (because calling a non present contact is a non sense in our case). And just click on the wanted item to add it to the conference.
# TODO
- [ ] UI: create the dropdown showing active calls/conferences and present contacts (a treeview should be created for the user)
- [ ] LRC: refacto, and readd a collectionInterface to be able to create custom models like this one
- [ ] UI: The interface should be updated when new presence/calls
- [ ] Daemon: avoid automatic call holding when creating a new call
- [ ] LRC: modify joinCalls to be able to merge with calls from other accounts
- [ ] UI: add filter
- [ ] tests, tests, tests, tests.
# POC
https://review.jami.net/c/ring-client-gnome/+/12140
https://review.jami.net/c/ring-lrc/+/12141
![07-26-19-11_18_55](/uploads/98b56a26482fb8d74dc0401a3b011673/07-26-19-11_18_55.png)New release 1Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1079replace "pause" picto when conversation is on hold2019-11-06T15:09:33ZGuillaume Hellerreplace "pause" picto when conversation is on holdWhen a conversation (audio or video) is on hold, the "Pause" picto should be replaced by a "Play" picto.
It works fine on others platforms
![image](/uploads/c06d650bf6ed6cb21878552c86d71303/image.png)When a conversation (audio or video) is on hold, the "Pause" picto should be replaced by a "Play" picto.
It works fine on others platforms
![image](/uploads/c06d650bf6ed6cb21878552c86d71303/image.png)New release 1Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1084text font+background color clash with adwaita dark (since gnome 3.34 or 3.34.1?)2019-11-06T15:09:15ZIT wrxtext font+background color clash with adwaita dark (since gnome 3.34 or 3.34.1?)Arch linux
gnome 3.34.1
jami-gnome 20190813-1
incoming text messages and call status messages (ex: "Missed outgoing call") are now white on light grey background and almost completely unreadable since gnome 3.34 or so (IIRC). I'm using ...Arch linux
gnome 3.34.1
jami-gnome 20190813-1
incoming text messages and call status messages (ex: "Missed outgoing call") are now white on light grey background and almost completely unreadable since gnome 3.34 or so (IIRC). I'm using the dark adwaita theme. Works fine on default/light adwaita theme.
thanksNew release 1Sébastien BlinSébastien Blin