jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2023-05-26T13:59:27Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1230Continues music playback when accepting incoming calls2023-05-26T13:59:27ZBruno KleinertContinues music playback when accepting incoming callsHi,
in a GNOME 3 environment with Rhythmbox playing music, the music is paused by Jami when a call is incoming so I can easily hear the sound Jami makes to inform about the call. As soon as I accept the call, Jami makes Rhythmbox unexpe...Hi,
in a GNOME 3 environment with Rhythmbox playing music, the music is paused by Jami when a call is incoming so I can easily hear the sound Jami makes to inform about the call. As soon as I accept the call, Jami makes Rhythmbox unexpectedly continue to play back music.
I would expect Jami to keep music playback paused until I end the call.
The system is Debian sid/unstable with Jami installed also from Debian sid/unstable. The versions are:
- gnome-shell 3.38.2-1
- jami 20201217.1.80217fa~ds1-1
- rhythmbox 3.4.4-4
Cheers,
Brunohttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1228Webcam is not detected on raspberry2023-05-26T13:59:17ZFlowWebcam is not detected on raspberryHello,
The webcam isn't detected on raspberry 3 with camera module.
I tried multiple version:
- 20190215 from raspbian repo
- 20201208.3 from jami repo
- 20201027.1 from snap
I doesn't see any specific error in the log.
```
** Message: ...Hello,
The webcam isn't detected on raspberry 3 with camera module.
I tried multiple version:
- 20190215 from raspbian repo
- 20201208.3 from jami repo
- 20201027.1 from snap
I doesn't see any specific error in the log.
```
** Message: 15:23:31.124: Jami GNOME client version: 9bada8a43cf9fec860da2b2b2d2fc8d242220e33
** Message: 15:23:31.124: git ref: unknown
No migration required
Can't open file: "/home/pi/.local/share/jami/fba3beaba81aae3/profile.vcf"
(jami-gnome:2209): libnotify-WARNING **: 15:23:33.009: Failed to connect to proxy
(jami-gnome:2209): Gtk-WARNING **: 15:23:33.013: Child name 'calls' not found in GtkStack
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.026: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.026: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.026: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.027: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.027: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:33.027: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:2209): Gtk-CRITICAL **: 15:23:34.933: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
** (jami-gnome:2209): WARNING **: 15:23:35.357: no primary network connection detected, check network settings
(jami-gnome:2209): Gdk-CRITICAL **: 15:23:35.873: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:2209): Gtk-WARNING **: 15:23:40.832: Theme parsing error: <data>:1:79: Not using units is deprecated. Assuming 'px'.
could not open shm area "" , shm_open failed: Argument invalide
```
Thanks for your helphttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1218client crashes when conversation recorded from a Windows client2023-05-26T13:59:17ZGuillaume Hellerclient crashes when conversation recorded from a Windows clientScenario:
* call between Linux & Windows
* Windows start recording the conversation
* Jami crashes on Linux sideScenario:
* call between Linux & Windows
* Windows start recording the conversation
* Jami crashes on Linux sidehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1213[Feature request] Allow to add new contact by QR code & text2023-05-26T13:59:19ZNokia808[Feature request] Allow to add new contact by QR code & textHi. Currently, Linux application has no ability to add new friend if heir/his Jami ID is known to user unless be invited by that friend !
Kindly, ,make it possible to add new friend (or in fact make it possible to invite heir/him) eithe...Hi. Currently, Linux application has no ability to add new friend if heir/his Jami ID is known to user unless be invited by that friend !
Kindly, ,make it possible to add new friend (or in fact make it possible to invite heir/him) either by reading heir/him ID QR code (as currently in Android application) & also allow to do that by entering heir/his ID as a text not only as QR code. Last feature (allow to add it as text) is specially useful in case remote freind can not show QR code ....
This feature is already available in qTox which is a Tox client, & Jami should has it ....
Best.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1211jami-gnome crashes when accepting an incoming video call2021-05-10T21:08:29ZVan de Buggerjami-gnome crashes when accepting an incoming video callIn the first terminal window:
$ cat /etc/system-release
Fedora release 32 (Thirty Two)
$ rpm -q jami
jami-20201015.1.14e5df5-1.fc32.x86_64
$ rpm -q gnome-shell
gnome-shell-3.36.7-1.fc32.x86_64
$ printenv |...In the first terminal window:
$ cat /etc/system-release
Fedora release 32 (Thirty Two)
$ rpm -q jami
jami-20201015.1.14e5df5-1.fc32.x86_64
$ rpm -q gnome-shell
gnome-shell-3.36.7-1.fc32.x86_64
$ printenv | grep XDG_SESSION | sort
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=gnome-xorg
XDG_SESSION_TYPE=x11
$ ps -A | grep dring
$ /usr/lib64/ring/dring -d -c > dring.log 2>&1
In the second terminal window:
$ jami-gnome > jami-gnome.log 2>&1
Now I initiate video call from another device (smartphone). Gnome shows notification, I press "Accept", Jami window disappears, in the second terminal window appears message:
Aborted (core dumped)
$ coredumpctl list | tail -n 1
Wed 2020-10-21 00:16:19 MSK 35265 1001 1001 6 present /usr/bin/jami-gnome
$ coredumpctl info 35265 > coredump.log
In the first terminal window I stops dring by pressing Ctrl+C:
^C
Logs: [jami-gnome.log](/uploads/7bb9a5780090dd8903dcd8840f7f820a/jami-gnome.log)
[dring.log](/uploads/126420e6167140923846ccdf847c0cc5/dring.log)
[coredump.log](/uploads/0bed8672af1461710397df8740f6769a/coredump.log)
The last message in jami-gnome.log is:
(jami-gnome:35265): Gtk-WARNING **: 00:16:17.657: Theme parsing error: <data>:1:79: Not using units is deprecated. Assuming 'px'.
QFontDatabase: Must construct a QGuiApplication before accessing QFontDatabase
Since it is a QT error, I think QT version could be important:
$ rpm -qa | grep -E '^qt'
qt5-qtbase-5.14.2-5.fc32.x86_64
qt-common-4.8.7-55.fc32.noarch
qt5-qtgraphicaleffects-5.14.2-1.fc32.x86_64
qtsoap-2.7-22.fc32.x86_64
qt5-qtx11extras-5.14.2-1.fc32.x86_64
qt5-qtlocation-5.14.2-2.fc32.x86_64
qt5-qtbase-common-5.14.2-5.fc32.noarch
qt-settings-32.0-3.fc32.noarch
qt5-qtconnectivity-5.14.2-1.fc32.x86_64
qt5-qtdeclarative-5.14.2-1.fc32.x86_64
qtlockedfile-qt5-2.4-31.20150629git5a07df5.fc32.x86_64
qt5-qtwebengine-5.14.2-2.fc32.x86_64
qtwebkit-2.3.4-29.fc32.x86_64
qt5-qtwebsockets-5.14.2-1.fc32.x86_64
qt5-qtquickcontrols-5.14.2-1.fc32.x86_64
qt5-qtsvg-5.14.2-1.fc32.x86_64
qt5-qtxmlpatterns-5.14.2-1.fc32.x86_64
qt-4.8.7-55.fc32.x86_64
qt5-qtquickcontrols2-5.14.2-1.fc32.x86_64
qt5-qttools-libs-help-5.14.2-1.fc32.x86_64
qt5-qtwayland-5.14.2-4.fc32.x86_64
qt5-qtscript-5.14.2-1.fc32.x86_64
qt5-qdbusviewer-5.14.2-1.fc32.x86_64
qt5-qttools-common-5.14.2-1.fc32.noarch
qt5-qtmultimedia-5.14.2-1.fc32.x86_64
qt5-qtbase-gui-5.14.2-5.fc32.x86_64
qt5-qtserialport-5.14.2-1.fc32.x86_64
qt5-qtenginio-1.6.2-29.fc32.x86_64
qt5-qttools-libs-designer-5.14.2-1.fc32.x86_64
qtsingleapplication-qt5-2.6.1-38.fc32.x86_64
qt-mobility-location-1.2.2-0.37.20140317git169da60c.fc32.x86_64
qt5-qtwebchannel-5.14.2-1.fc32.x86_64
qt-x11-4.8.7-55.fc32.x86_64
qt5-qtpbfimageformat-2.1-1.fc32.x86_64
qt5-qtwebkit-5.212.0-0.46.alpha4.fc32.x86_64
qt-mobility-common-1.2.2-0.37.20140317git169da60c.fc32.x86_64
qt5-srpm-macros-5.14.2-3.fc32.noarch
qt-mobility-sensors-1.2.2-0.37.20140317git169da60c.fc32.x86_64
qt5-qtsensors-5.14.2-1.fc32.x86_64https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1207Feature request: add paste from clipboard with ctrl-v to messages2023-05-26T13:59:11ZDaniel NicolaiFeature request: add paste from clipboard with ctrl-v to messagesRight now it seems only possible to add images by dragging them into the message area (or by clikcing the paperclip). It would be great if we could add files (i.e. images) to messages bij pasting from the clipboard.Right now it seems only possible to add images by dragging them into the message area (or by clikcing the paperclip). It would be great if we could add files (i.e. images) to messages bij pasting from the clipboard.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1205Coredump Video Call Receiving Android Screenshare2023-05-26T13:59:26ZvindicatorrCoredump Video Call Receiving Android ScreenshareMaster commit 71ac99feaf73cc3bb29675b038a678107d9ee718
```
Stack trace of thread 56034:
#0 0x0000767daa2d6ad3 __memmove_avx_unaligned_erms (libc.so.6 + 0x165ad3)
#1 0x0000767dafd54c20 n/a...Master commit 71ac99feaf73cc3bb29675b038a678107d9ee718
```
Stack trace of thread 56034:
#0 0x0000767daa2d6ad3 __memmove_avx_unaligned_erms (libc.so.6 + 0x165ad3)
#1 0x0000767dafd54c20 n/a (libcogl.so.20 + 0x36c20)
#2 0x0000767dafd5822e n/a (libcogl.so.20 + 0x3a22e)
#3 0x0000767dafd58342 n/a (libcogl.so.20 + 0x3a342)
#4 0x0000767dafd3e85f n/a (libcogl.so.20 + 0x2085f)
#5 0x0000767dafd77a06 cogl_texture_allocate (libcogl.so.20 + 0x59a06)
#6 0x0000767dafd94cc4 n/a (libcogl.so.20 + 0x76cc4)
#7 0x0000767dafd95106 cogl_texture_new_from_data (libcogl.so.20 + 0x77106)
#8 0x0000767dafe8c7e0 clutter_image_set_data (libclutter-1.0.so.0 + 0x8c7e0)
#9 0x0000650bc5314ce4 clutter_render_image (jami-gnome + 0xb8ce4)
#10 0x0000650bc53150eb check_frame_queue (jami-gnome + 0xb90eb)
#11 0x0000767db050d194 n/a (libglib-2.0.so.0 + 0x53194)
#12 0x0000767db050cb00 g_main_context_dispatch (libglib-2.0.so.0 + 0x52b00)
#13 0x0000767db055e1f9 n/a (libglib-2.0.so.0 + 0xa41f9)
#14 0x0000767db050b421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
#15 0x0000767db0710d1e g_application_run (libgio-2.0.so.0 + 0xccd1e)
#16 0x0000650bc52c953e main (jami-gnome + 0x6d53e)
#17 0x0000767daa199152 __libc_start_main (libc.so.6 + 0x28152)
#18 0x0000650bc52c92ee _start (jami-gnome + 0x6d2ee)
Stack trace of thread 56062:
#0 0x0000767daa26646f __poll (libc.so.6 + 0xf546f)
#1 0x0000767db055e188 n/a (libglib-2.0.so.0 + 0xa4188)
#2 0x0000767db050c163 g_main_loop_run (libglib-2.0.so.0 + 0x52163)
#3 0x0000767dabc08b72 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18 + 0x1567b72)
#4 0x0000767dabba70ae _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18 + 0x15060ae)
#5 0x0000767dabc0ad1a n/a (libjavascriptcoregtk-4.0.so.18 + 0x1569d1a)
#6 0x0000767daa0d23e9 start_thread (libpthread.so.0 + 0x93e9)
#7 0x0000767daa271293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 56048:
#0 0x0000767daa0d86a2 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf6a2)
#1 0x0000767d9ef02b3c n/a (i965_dri.so + 0x51eb3c)
#2 0x0000767d9ef01e58 n/a (i965_dri.so + 0x51de58)
#3 0x0000767daa0d23e9 start_thread (libpthread.so.0 + 0x93e9)
#4 0x0000767daa271293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 56061:
#0 0x0000767daa0d89c8 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf9c8)
#1 0x0000767dabc0b54d _ZN3WTF15ThreadCondition9timedWaitERNS_5MutexENS_8WallTimeE (libjavascriptcoregtk-4.0.so.18 + 0x156a54d)
#2 0x0000767dabba270d _ZN3WTF10ParkingLot21parkConditionallyImplEPKvRKNS_12ScopedLambdaIFbvEEERKNS3_IFvvEEERKNS_24TimeWithDynamicClockTypeE (libjavascriptcoregtk-4.0.so.18 + 0x150170d)
#3 0x0000767dabba61dd _ZN3WTF5sleepENS_7SecondsE (libjavascriptcoregtk-4.0.so.18 + 0x15051dd)
#4 0x0000767dacc54a8b n/a (libwebkit2gtk-4.0.so.37 + 0xc2ba8b)
#5 0x0000767dacc551e9 n/a (libwebkit2gtk-4.0.so.37 + 0xc2c1e9)
#6 0x0000767dabba70ae _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18 + 0x15060ae)
#7 0x0000767dabc0ad1a n/a (libjavascriptcoregtk-4.0.so.18 + 0x1569d1a)
#8 0x0000767daa0d23e9 start_thread (libpthread.so.0 + 0x93e9)
#9 0x0000767daa271293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 56063:
#0 0x0000767daa26646f __poll (libc.so.6 + 0xf546f)
#1 0x0000767db055e188 n/a (libglib-2.0.so.0 + 0xa4188)
#2 0x0000767db050c163 g_main_loop_run (libglib-2.0.so.0 + 0x52163)
#3 0x0000767dabc08b72 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18 + 0x1567b72)
#4 0x0000767dabba70ae _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE (libjavascriptcoregtk-4.0.so.18 + 0x15060ae)
#5 0x0000767dabc0ad1a n/a (libjavascriptcoregtk-4.0.so.18 + 0x1569d1a)
#6 0x0000767daa0d23e9 start_thread (libpthread.so.0 + 0x93e9)
#7 0x0000767daa271293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 56095:
#0 0x0000767daa26646f __poll (libc.so.6 + 0xf546f)
#1 0x0000767d802b8c14 n/a (libpulse.so.0 + 0xdc14)
#2 0x0000767d802c6059 pa_mainloop_poll (libpulse.so.0 + 0x1b059)
#3 0x0000767d802d0301 pa_mainloop_iterate (libpulse.so.0 + 0x25301)
#4 0x0000767d802d03b1 pa_mainloop_
```
EDIT0: After re-opening jami-gnome, the "conversation" I was in suddenly had a bunch (68?) of empty "received" messages from Android. However, there weren't any corresponding "sent" messages on my Android device.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1202Be able to hide/minimize preview during a video call2023-07-27T22:33:11ZCyrille BéraudBe able to hide/minimize preview during a video callAmin BandaliAmin Bandali2020-09-27https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1175Output audio test buttons for `Ringtone device` and `Output device`2023-05-26T13:59:29ZovariOutput audio test buttons for `Ringtone device` and `Output device`1. Please add a button to test the `Ringtone device` as shown in the image below.<br>
a) The test sound could be the current ringtone.<br>
b) A button caption could be `Test ringtone device` which hopefully will help screen readers and h...1. Please add a button to test the `Ringtone device` as shown in the image below.<br>
a) The test sound could be the current ringtone.<br>
b) A button caption could be `Test ringtone device` which hopefully will help screen readers and hence people with vision impairment.
2. Please add a button to test the `Output device` as shown in the image below.
3. This would be similar to the `Input device` which has a `Input volume meter` to test
4. This would be similar to the `Device` which has an image to test
Thank you for having a separate `Ringtone device` available from `Jami built on 2020-06-09 07:43:45 UTC` as this helps when earphones are plugged into a computer.
What do you think?
Thank you once again
![Output audio test buttons for `Ringtone device` and `Output device`](/uploads/c00632e665c8cc8b64e63e8feeae6d2a/image.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1173Implement picture in picture for desktop clients2023-05-26T13:59:21Zring userImplement picture in picture for desktop clientsIt would be great if the desktop clients would also allow to use an picture in picture mode like on Android.It would be great if the desktop clients would also allow to use an picture in picture mode like on Android.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1165Wrong date format in message timestamps2023-05-26T13:59:19ZArvid BrodinWrong date format in message timestampsThe dates in message timestamps are shown in M/D/YYYY format, although my LC_TIME is set to "sv_SE.UTF-8" (i.e. ISO standard YYYY-MM-DD format). The format of dates that shows latest activity in the buddy list is correct though.
OS: Xub...The dates in message timestamps are shown in M/D/YYYY format, although my LC_TIME is set to "sv_SE.UTF-8" (i.e. ISO standard YYYY-MM-DD format). The format of dates that shows latest activity in the buddy list is correct though.
OS: Xubuntu 18.04
jami-gnome "Free as in Freedom" built on 2020-04-28 22:24:55 UTC
```
$ locale
LANG=en_US.UTF-8
LANGUAGE=en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=sv_SE.UTF-8
LC_TIME=sv_SE.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=sv_SE.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=sv_SE.UTF-8
LC_NAME=sv_SE.UTF-8
LC_ADDRESS=sv_SE.UTF-8
LC_TELEPHONE=sv_SE.UTF-8
LC_MEASUREMENT=sv_SE.UTF-8
LC_IDENTIFICATION=sv_SE.UTF-8
LC_ALL=
```
(These locale settings are chosen by the OS during install after I select the keyboard language, location, and language that I want; I haven't touched them directly.)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1155Text messages jitter, run off right margin of screen2023-05-26T13:59:27ZZulText messages jitter, run off right margin of screenMy text messages jitter irregularly, about once every ten seconds, sometimes a couple of line heights or so vertically, sometimes moving a similar or smaller distance horizontally, and sometimes in the word wrap (longer text messages oft...My text messages jitter irregularly, about once every ten seconds, sometimes a couple of line heights or so vertically, sometimes moving a similar or smaller distance horizontally, and sometimes in the word wrap (longer text messages often stop line-wrapping partway through, and changing the window width may or may not temporarily fix). One message was also are placed way off to the right of the bubble it should be in, running, like the unwrapped lines, right off the viewable screen. This makes it unreadable unless you can resize the window to be wide enough.
It would be nice if it only moved when there was something new to attend to, though I suppose having relative "30 minutes ago" timestamps makes that strictly impossible.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1152only calling of numbers working2023-05-26T13:59:16Zmokkinonly calling of numbers workingIf you copy and paste a string like `+49177-123456` or even `+49177123456` the call doesn't start because Jami cannot deal with other characters than numbers.
![image](/uploads/0dd57a363c2a9c505082c06bd181df11/image.png)If you copy and paste a string like `+49177-123456` or even `+49177123456` the call doesn't start because Jami cannot deal with other characters than numbers.
![image](/uploads/0dd57a363c2a9c505082c06bd181df11/image.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1151Add command line call / click to call2023-05-26T13:59:13ZmokkinAdd command line call / click to callOther SIP phones such as linphone have a command line call option. So you can click to a number or a `tel:` URIto start a call.
This would be great for JAMI too.Other SIP phones such as linphone have a command line call option. So you can click to a number or a `tel:` URIto start a call.
This would be great for JAMI too.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1146[Accessibility] Screenreader compatibility2023-05-26T13:59:20ZZul[Accessibility] Screenreader compatibilityUsing Jami "Live Free or Die" (old version) on Debian stable with Orca screenreader, it almost works, but only sometimes. It sometimes chants its status at you (I think it said "resting resting resting" when I changed profiles, but now I...Using Jami "Live Free or Die" (old version) on Debian stable with Orca screenreader, it almost works, but only sometimes. It sometimes chants its status at you (I think it said "resting resting resting" when I changed profiles, but now I can't replicate). It sometimes reads the letters you are typing as you type them, but sometimes doesn't. I have yet to get it to read incoming text messages except by highlighting them, and sometimes that didn't work. Of course, if you can't see, seeing that they are there to highlight would be a problem. I'm not sure I've ever heard it give an aural pop-up notification/earcon. I'm sorry not to have something more replicable, but the behaviour seems inconsistent.
Has anyone tested Jami with Orca, NVDA, Apple Voiceover, etc?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1143Monochrome icon2023-05-26T13:59:18ZPhiliMonochrome iconA very simple enhancement proposal: having a monochrome icon, like most of the gnome apps. See below the screen capture, currently it is not nice !
But many thanks for this great sofware !
![Capture_d_écran_du_2020-03-21_10-12-28](/uplo...A very simple enhancement proposal: having a monochrome icon, like most of the gnome apps. See below the screen capture, currently it is not nice !
But many thanks for this great sofware !
![Capture_d_écran_du_2020-03-21_10-12-28](/uploads/55ec45566787538434fb6ee99305218b/Capture_d_écran_du_2020-03-21_10-12-28.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1123[bug] Screen sharing Android->client gnome causes a "bus error"2023-05-26T13:59:35ZJan Wielkiewicz[bug] Screen sharing Android->client gnome causes a "bus error"I made a video call from Android client version 20191208 to Gnome client version 20191217 or 20191224, turned on and off screen sharing on Android a few times and then closed the screen sharing. This made the gnome client to close and th...I made a video call from Android client version 20191208 to Gnome client version 20191217 or 20191224, turned on and off screen sharing on Android a few times and then closed the screen sharing. This made the gnome client to close and throw "31452 Bus error", Android client was fine though.
I tested this only on Guix System with with the package I made. Patches for pjproject and ffmpeg were applied correctly, we use the 3.6.9 version instead of 3.6.10 though, don't know if it's a problem, but I can test it soon.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1113The tooltip of the + button should start with a capital letter2023-05-26T13:59:35ZannaThe tooltip of the + button should start with a capital letter-> "Open chat". That would be the minimal variant of this issue.
At the same time I wonder why the search bar is called "Find or start a conversation" and if it needs some more changes.
My idea: Simply rename the search bar to "Find co...-> "Open chat". That would be the minimal variant of this issue.
At the same time I wonder why the search bar is called "Find or start a conversation" and if it needs some more changes.
My idea: Simply rename the search bar to "Find conversation" and declare the + button as "Start conversation". Because the search field never starts a conversation.
Irritating would be the back button within the conversation view, which currently has the tooltip "Hide chat view". Is it actually spelled "chat view" or "chatview"? And shouldn't it be called "Conversation(s) view" and therefore "Hide conversation"?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1110WebKitWebProcess Memory Leak2023-05-26T13:59:23ZvindicatorrWebKitWebProcess Memory LeakI have a system uptime of 13 days and seeing reserved memory continually increase, now at 1.4GB for WebKitWebProcess which shows as a child under jami-gnome in htop in tree-view.
<pre>
VIRT RES SHR Command
99G 75204 26276 jami...I have a system uptime of 13 days and seeing reserved memory continually increase, now at 1.4GB for WebKitWebProcess which shows as a child under jami-gnome in htop in tree-view.
<pre>
VIRT RES SHR Command
99G 75204 26276 jami-gnome
83.7G 1458M 27356 WebKitWebProcess
81.9G 6096 0 WebKitNetworkProcess
</pre>
I may point the webkit folks to this post.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1107Call Recording -> The two options "Record local video" & "Always record calls...2023-05-26T13:59:29ZannaCall Recording -> The two options "Record local video" & "Always record calls" should be disabled by default as long as there is no solution for informed consentSee discussion
https://git.jami.net/savoirfairelinux/ring-project/issues/720
If both options are enabled by default, I have security concerns here.
This issue is for the GNOME client.
Can't say how the other clients handle this functiona...See discussion
https://git.jami.net/savoirfairelinux/ring-project/issues/720
If both options are enabled by default, I have security concerns here.
This issue is for the GNOME client.
Can't say how the other clients handle this functionality.
Maybe it makes sense to transform this issue into a global issue for all clients.