jami-client-gnome issueshttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues2021-11-12T02:56:37Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1277Call UI not shown when being answered2021-11-12T02:56:37ZPier-Luc ThériaultCall UI not shown when being answeredBug report form
---------------
## OS
Debian
## Jami daemon version:
10.1.0-e8dbf2af93
## Jami GNOME client version:
6dcd20b4489d303e8fcae996a4d83ab7c2e5d875
## Where did you get Jami?
<!-- (add an x in between the square bracket...Bug report form
---------------
## OS
Debian
## Jami daemon version:
10.1.0-e8dbf2af93
## Jami GNOME client version:
6dcd20b4489d303e8fcae996a4d83ab7c2e5d875
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [ ] I downloaded it from jami.net
- [x] I built it from source using the build.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
Steps:
1.Open Jami
2.Make a call
3.Wait for connection
## What you expect to happen:
When the other side picks up the call UI is shown.
## What happens instead:
The connecting interface is kept with the Talking label.
I need to click the contact to see the call ui.
## Additional information
At that moment I am already listening to my asterisk music
![connecting](/uploads/7cf2b7e00ecfe8d27fe69f3ec6079b66/connecting.png)
It should look like this:
![call-ui](/uploads/8fd36bf6cb3d81068d5af0ded0d435cb/call-ui.png)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1239If no call, force close and go to the chatview2023-05-26T13:59:13ZSébastien BlinIf no call, force close and go to the chatviewif "Could not hang up non-existant call XXXXXX" this means that the daemon has crashed, restarted via dbus, so the call should be closed no matter what and go to the chatviewif "Could not hang up non-existant call XXXXXX" this means that the daemon has crashed, restarted via dbus, so the call should be closed no matter what and go to the chatviewhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1229Chatview: record video message - preview is missing2020-12-24T21:36:05ZSébastien BlinChatview: record video message - preview is missingIteration 25Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1215important memory leak to be investigated2020-11-04T20:48:28ZGuillaume Hellerimportant memory leak to be investigated![image](/uploads/b0d102b8223d7e378f0958ed27fd7c3e/image.png)
do not have much information to share, but each time I make a call and hangup, the memory increase by at least 0,2 GiB. When I restart Jami, the memory is already at 4,0 GiB.![image](/uploads/b0d102b8223d7e378f0958ed27fd7c3e/image.png)
do not have much information to share, but each time I make a call and hangup, the memory increase by at least 0,2 GiB. When I restart Jami, the memory is already at 4,0 GiB.Amin BandaliSébastien BlinAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1214Drag&Drop of a pictures in a conversation (text chat entry) doesn't work anymore2020-11-19T23:54:28ZCyrille BéraudDrag&Drop of a pictures in a conversation (text chat entry) doesn't work anymoreAmin BandaliSébastien BlinAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1212Incorrect account selected in the top right combo box when there's a disabled...2020-10-27T19:25:47ZAmin BandaliIncorrect account selected in the top right combo box when there's a disabled accountWhen an account is at the top of the list in the account combo box and it is disabled, quitting the application and relaunching it has that disabled account wrongly selected, making it inconsistent with the main window (the main window c...When an account is at the top of the list in the account combo box and it is disabled, quitting the application and relaunching it has that disabled account wrongly selected, making it inconsistent with the main window (the main window correctly shows the next enabled account).
Reported to me by @sblin.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1210preview frozen after accessing media settings during a call2020-12-24T21:40:28ZGuillaume Hellerpreview frozen after accessing media settings during a call* During a video call, Open Settings
* Go to Media
* Go back to video call
--> preview is frozen* During a video call, Open Settings
* Go to Media
* Go back to video call
--> preview is frozenhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1204Incoming call notifications stay visible for unanswered call2020-10-23T21:41:48ZHussein AbdallahIncoming call notifications stay visible for unanswered callIncoming call notifications appear as expected with the Accept and Reject buttons when Jami is ringing. However, these notifications stay forever visible for unanswered calls unless the user clicks on the notification. It is obviously im...Incoming call notifications appear as expected with the Accept and Reject buttons when Jami is ringing. However, these notifications stay forever visible for unanswered calls unless the user clicks on the notification. It is obviously impossible to accept or reject a incoming call that has already been missed after Jami stopped ringing but it is still confusing.
The expected behavior is that notifications disappear once Jami has stopped ringing (the incoming call times out).
Note: it is possible to reproduce this bug both for Jami and SIP calls.Amin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1195if you type a message and receive a call at the same time, text is erased2021-07-09T21:00:00ZGuillaume Hellerif you type a message and receive a call at the same time, text is erasedalso occurs if you receive a call, start typing a message then peer hangs up
--> text is erasedalso occurs if you receive a call, start typing a message then peer hangs up
--> text is erasedhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1181File transfer fails when ~/Downloads/Jami does not exist2020-06-26T19:26:37ZBrando TovarFile transfer fails when ~/Downloads/Jami does not existOn Ubuntu 20.04 and Jami from jami.net receiving a file transfer fails when ~/Downloads/Jami does not exist: [FTP] Can't open file /home/test/Downloads/Jami/IMG_6.png
[log.txt](/uploads/b1180dd3c6d21e0e1296debb09ea0531/log.txt)On Ubuntu 20.04 and Jami from jami.net receiving a file transfer fails when ~/Downloads/Jami does not exist: [FTP] Can't open file /home/test/Downloads/Jami/IMG_6.png
[log.txt](/uploads/b1180dd3c6d21e0e1296debb09ea0531/log.txt)https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1161Camera settings drop-down boxes not updated when webcam attached or removed2023-01-04T18:58:15ZArvid BrodinCamera settings drop-down boxes not updated when webcam attached or removedUnder Settings->Media, the drop-down boxes for Camera Settings, where resolution etc is selected, stays blank and disabled even when camera device has been attached.
To reproduce:
* Start dring and jami-gnome with no camera device attac...Under Settings->Media, the drop-down boxes for Camera Settings, where resolution etc is selected, stays blank and disabled even when camera device has been attached.
To reproduce:
* Start dring and jami-gnome with no camera device attached to system.
* Attach webcam.
* Go to Settings->Media. The drop-down boxes remain empty and greyed-out even though live video preview is shown.
Also:
* Start dring and jami-gnome with webcam attached.
* Unplug webcam.
* Go to Settings->Media. The drop-down boxes shows old video device info.
System info:
$ /usr/lib/ring/dring --version
Jami Daemon 9.1.0, by Savoir-faire Linux 2004-2019
https://jami.net/
[Video support enabled]
$ jami-gnome --version
74ef874ea412985a5cfb49e3e162d20b5707733b - unknown (About page says "Free as in Freedom" built on 2020-04-14 20:24:50 UTC)
OS: Xubuntu 18.04 with kernel 5.5.17
This is reproducible also on Xubuntu 20.04 beta with Jami Daemon 7.4.0/jami-gnome "Live Free or Die" built on 2020-03-23 06:24:58.
----------
As an aside, I once got a dring segfault in relation to this, but unfortunately I cannot reproduce that bug. Just FYI, here's the log of that one occurrance (as much of it as I have):
```
[1587224157.967| 3071|video_input.cpp :493 ] MRL: 'camera:///dev/video0'
[1587224157.967| 3071|audio_input.cpp :53 ] Creating audio input with id: audiolayer_id
[1587224157.967|13310|sinkclient.cpp :195 ] ShmHolder[Jami Daemon_shm_3071_0]: new sizes: f=0, a=103
[1587224157.967|13310|sinkclient.cpp :161 ] ShmHolder: new holder 'Jami Daemon_shm_3071_0'
[1587224157.967|13310|video_input.cpp :165 ] VideoInput ready to capture
[1587224157.967| 3071|audio_input.cpp :260 ] Switching audio source to match 'camera:///dev/video0'
[1587224157.967|13310|media_decoder.cpp :129 ] Trying to open device /dev/video0 with format video4linux2, pixel format , size 640x480, rate 30.000000
[1587224157.967|13311|audio_input.cpp :77 ] Switching audio input to '/dev/video0'
[1587224157.967| 3071|audiolayer.cpp :123 ] Hardware audio format available : {s16, 2 channels, 44100Hz} 0
[1587224157.967| 3071|audiostream.cpp :49 ] Playback: trying to create stream with device (44100Hz, 2 channels)
[1587224157.967| 3071|audiostream.cpp :134 ] Stream is creating...
[1587224157.967| 3071|audiostream.cpp :49 ] Ringtone: trying to create stream with device (44100Hz, 2 channels)
[1587224157.967| 3071|audiostream.cpp :134 ] Stream is creating...
[1587224157.967| 3071|audiostream.cpp :49 ] Capture: trying to create stream with device alsa_input.pci-0000_00_1b.0.analog-stereo (44100Hz, 2 channels)
[1587224157.967| 3071|audiostream.cpp :134 ] Stream is creating...
[1587224157.968| 3071|audio_input.cpp :53 ] Creating audio input with id: audiolayer_id
[1587224158.015| 3091|audiostream.cpp :142 ] Stream successfully created, connected to alsa_output.usb-Binary_Audio_UAC1_DAC-01.analog-stereo
[1587224158.015| 3091|audiostream.cpp :142 ] Stream successfully created, connected to alsa_output.usb-Binary_Audio_UAC1_DAC-01.analog-stereo
[1587224158.015| 3091|audiostream.cpp :124 ] Stream 53 to alsa_output.usb-Binary_Audio_UAC1_DAC-01.analog-stereo.echo-cancel
[1587224158.015| 3091|audiostream.cpp :124 ] Stream 54 to alsa_output.usb-Binary_Audio_UAC1_DAC-01.analog-stereo.echo-cancel
[1587224158.015| 3091|audiostream.cpp :142 ] Stream successfully created, connected to alsa_input.pci-0000_00_1b.0.analog-stereo.echo-cancel
[1587224158.015| 3091|pulselayer.cpp :330 ] All streams ready, starting !
[1587224158.015| 3091|pulselayer.cpp :184 ] Updating PulseAudio source list
[1587224158.015| 3091|pulselayer.cpp :200 ] Updating PulseAudio server infos
[1587224158.015| 3091|pulselayer.cpp :168 ] Updating PulseAudio sink list
[1587224158.016| 3091|pulselayer.cpp :601 ] PulseAudio server info:
Server name: pulseaudio
Server version: 11.1
Default Sink alsa_output.usb-Binary_Audio_UAC1_DAC-01.analog-stereo.echo-cancel
Default Source alsa_input.pci-0000_00_1b.0.analog-stereo.echo-cancel
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
[1587224158.017|13313|pulselayer.cpp :578 ] Staying on
alsa_output.usb-Binary_Audio_UAC1_DAC-01.analog-stereo.echo-cancel
alsa_input.pci-0000_00_1b.0.analog-stereo.echo-cancel
[1587224159.740| 3071|video_input.cpp :493 ] MRL: ''
[1587224159.740| 3071|audio_input.cpp :260 ] Switching audio source to match ''
[1587224159.740|13312|audio_input.cpp :75 ] Switching to default audio input
[video4linux2,v4l2 @ 0x7fe3e00b7540] Cannot open video device /dev/video0: Device or resource busy
[1587224160.783|13310|media_decoder.cpp :139 ] avformat_open_input failed: Device or resource busy
[1587224160.784| 3073|video_device_monitor_impl.cpp:219 ] udev: removing /dev/video0
[1587224160.785| 3073|video_device_monitor_impl.cpp:219 ] udev: removing /dev/video1
Segmentation fault (core dumped)
```LaterSébastien BlinYang WangSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1142Can't lookup names with only 3 characters2020-03-23T17:41:35ZAdrien BéraudCan't lookup names with only 3 characterswhen searching for "nvi" or "vda" I get "invalid ID".when searching for "nvi" or "vda" I get "invalid ID".Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1131Detect headset connection change2021-05-06T20:39:17ZDenis Roussel (ACSONE)Detect headset connection changeWhen headset disconnects (e.g.: bluetooth one) and then reconnect, does not take change into account.
In parameters > Media, the headset does not appear.
To solve it, quit Jami and then launch it.When headset disconnects (e.g.: bluetooth one) and then reconnect, does not take change into account.
In parameters > Media, the headset does not appear.
To solve it, quit Jami and then launch it.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1126Open Jami with the last opened account selected2021-05-13T22:22:11ZovariOpen Jami with the last opened account selected1. Enable Jami to automatically start when computer starts.<br>
Jami → Settings → General → System → Enable `Start application on login`<br>
Linux Mint Menu → Startup Applications → Enable `Jami`
2. Create/Import two (2) JAMI Protocol ac...1. Enable Jami to automatically start when computer starts.<br>
Jami → Settings → General → System → Enable `Start application on login`<br>
Linux Mint Menu → Startup Applications → Enable `Jami`
2. Create/Import two (2) JAMI Protocol accounts
3. Select the first account (near the top right)
4. Restart Linux Mint
5. Jami opens with the second account showing.<br>
`Bug: the last opened account, i.e. the first account in the drop-down (near the top right), should be showing`.
What do you think?
Thank you
Linux Mint 19.3 Cinnamon<br>
Jami built on 2019-12-24 19:09:08 UTChttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1112libnatpmp socket error2020-10-05T18:17:31ZAndrzej Matuchlibnatpmp socket errorIf Jami is opened with a session in Kubuntu 19.10, whether the computer is connected to a network or not, Jami will report "failed to initialize libnatpmp - socket error" repeatedly, adding 100MB of data to syslog every 30 seconds and sa...If Jami is opened with a session in Kubuntu 19.10, whether the computer is connected to a network or not, Jami will report "failed to initialize libnatpmp - socket error" repeatedly, adding 100MB of data to syslog every 30 seconds and sallowing dozens of GB every hour.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1100Remove XDG_BACKEND=x11 aka support Wayland backend (see main.cpp)2023-05-26T13:59:31ZSébastien BlinRemove XDG_BACKEND=x11 aka support Wayland backend (see main.cpp)This breaks gtkwebkit supports now (can't see the chatview on Wayland)
However, removing this line causes crashes on media (these lines):
```
auto stage = gtk_clutter_embed_get_stage(GTK_CLUTTER_EMBED(widgets->video_widget));
auto acto...This breaks gtkwebkit supports now (can't see the chatview on Wayland)
However, removing this line causes crashes on media (these lines):
```
auto stage = gtk_clutter_embed_get_stage(GTK_CLUTTER_EMBED(widgets->video_widget));
auto actor_info = gtk_clutter_actor_new_with_contents(widgets->hbox_call_info);
auto actor_controls = gtk_clutter_actor_new_with_contents(widgets->hbox_call_controls);
auto actor_smartInfo = gtk_clutter_actor_new_with_contents(widgets->vbox_call_smartInfo);
clutter_actor_add_child(stage, actor_info);
```
Related backtrace:
```
#0 0x00007ffff1922d37 in __memmove_avx_unaligned_erms () at /lib64/libc.so.6
#1 0x00007fffe621f908 in brw_upload_indices () at /usr/lib64/dri/i965_dri.so
#2 0x00007fffe622f231 in brw_upload_render_state () at /usr/lib64/dri/i965_dri.so
#3 0x00007fffe621eb74 in brw_draw_prims () at /usr/lib64/dri/i965_dri.so
#4 0x00007fffe64be303 in _mesa_validated_drawrangeelements () at /usr/lib64/dri/i965_dri.so
#5 0x00007fffe64be61c in _mesa_DrawElements () at /usr/lib64/dri/i965_dri.so
#6 0x00007ffff6844c8d in _cogl_framebuffer_gl_draw_indexed_attributes ()
at /lib64/libcogl.so.20
#7 0x00007ffff6888685 in _cogl_journal_flush_modelview_and_entries () at /lib64/libcogl.so.20
#8 0x00007ffff6888b0f in batch_and_call.part () at /lib64/libcogl.so.20
#9 0x00007ffff6889139 in _cogl_journal_flush_texcoord_vbo_offsets_and_entries ()
at /lib64/libcogl.so.20
#10 0x00007ffff6888dbf in _cogl_journal_flush_vbo_offsets_and_entries ()
at /lib64/libcogl.so.20
#11 0x00007ffff688a172 in _cogl_journal_flush () at /lib64/libcogl.so.20
#12 0x00007ffff68586c8 in cogl_flush () at /lib64/libcogl.so.20
#13 0x00007ffff688f022 in cogl_onscreen_swap_buffers_with_damage () at /lib64/libcogl.so.20
#14 0x00007ffff694def6 in clutter_stage_cogl_redraw () at /lib64/libclutter-1.0.so.0
#15 0x00007ffff69512df in clutter_stage_gdk_redraw () at /lib64/libclutter-1.0.so.0
#16 0x00007ffff69beee0 in _clutter_stage_do_update () at /lib64/libclutter-1.0.so.0
#17 0x00007ffff6950b7c in clutter_master_clock_gdk_update () at /lib64/libclutter-1.0.so.0
#18 0x00007ffff70cd742 in g_closure_invoke () at /lib64/libgobject-2.0.so.0
```
or
```
#0 0x00007ffff1a4c667 in __memmove_avx_unaligned_erms () at /lib64/libc.so.6
#1 0x00007fffe603f958 in u_upload_data () at /usr/lib64/dri/radeonsi_dri.so
#2 0x00007fffe68b2e43 in tc_draw_vbo () at /usr/lib64/dri/radeonsi_dri.so
#3 0x00007fffe6534490 in st_draw_vbo () at /usr/lib64/dri/radeonsi_dri.so
#4 0x00007fffe65d2c43 in _mesa_validated_drawrangeelements () at /usr/lib64/dri/radeonsi_dri.so
#5 0x00007fffe65d2f5c in _mesa_DrawElements () at /usr/lib64/dri/radeonsi_dri.so
#6 0x00007ffff694dcad in () at /lib64/libcogl.so.20
#7 0x00007ffff69914c5 in () at /lib64/libcogl.so.20
#8 0x00007ffff699194f in () at /lib64/libcogl.so.20
#9 0x00007ffff6991f79 in () at /lib64/libcogl.so.20
#10 0x00007ffff6991bff in () at /lib64/libcogl.so.20
#11 0x00007ffff6992fa2 in () at /lib64/libcogl.so.20
#12 0x00007ffff6961738 in cogl_flush () at /lib64/libcogl.so.20
#13 0x00007ffff6997e02 in cogl_onscreen_swap_buffers_with_damage () at /lib64/libcogl.so.20
#14 0x00007ffff6a56f16 in () at /lib64/libclutter-1.0.so.0
#15 0x00007ffff6a5a30f in () at /lib64/libclutter-1.0.so.0
#16 0x00007ffff6ac7df0 in () at /lib64/libclutter-1.0.so.0
#17 0x00007ffff6a59bac in () at /lib64/libclutter-1.0.so.0
#18 0x00007ffff71d2742 in g_closure_invoke () at /lib64/libgobject-2.0.so.0
```https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1089user data migration from ring to jami takes forever when database is corrupte...2020-11-20T00:21:14ZThomas Debesseuser data migration from ring to jami takes forever when database is corrupted by an older version of ring```
[account@box:~] $ jami
** Message: 21:16:52.743: Jami GNOME client version: b784e232f8412135d76bd643baec14ef9ff0940a
** Message: 21:16:52.744: git ref: unknown
Migrate "/home/account/.local/share/gnome-ring" / "." to "/home/accou...```
[account@box:~] $ jami
** Message: 21:16:52.743: Jami GNOME client version: b784e232f8412135d76bd643baec14ef9ff0940a
** Message: 21:16:52.744: git ref: unknown
Migrate "/home/account/.local/share/gnome-ring" / "." to "/home/account/.local/share/jami/."
Migrate "/home/account/.local/share/gnome-ring" / ".." to "/home/account/.local/share/jami/.."
Migrate "/home/account/.local/share/gnome-ring" / "profiles" to "/home/account/.local/share/jami/profiles"
Migrate "/home/account/.local/share/gnome-ring" / "ring.db" to "/home/account/.local/share/jami/ring.db"
Migrate "/home/account/.local/share/gnome-ring" / "vCard" to "/home/account/.local/share/jami/vCard"
database "/home/account/.local/share/jami/ring.db" version set to: "1.1"
Migrating account: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." ...
database "/home/account/.local/share/jami/Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken./history.db" version set to: "1"
```
Look at the unexpected `/home/account/.local/share/jami/Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken./history.db` file path.
Edit: migration takes forever.Sé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/1072Network Manager, detect when leaving a VPN2020-11-20T15:10:51ZSébastien BlinNetwork Manager, detect when leaving a VPNconnectivityChanged seems not to be called when leaving a VPNconnectivityChanged seems not to be called when leaving a VPNhttps://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 Blin