savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-08-16T20:54:28Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1243Message not received2021-08-16T20:54:28Zdanrobi11Message not receivedI've sent a msg from A to B.
B doesnt get the msg
```curl http://dhtproxy.jami.net/HASH_OF_YOUR_ACCOUNT```
Seems the presence is there because it returns my public key
This is the B output:
```
[1610447397.997|24738|jamiaccount.cpp ...I've sent a msg from A to B.
B doesnt get the msg
```curl http://dhtproxy.jami.net/HASH_OF_YOUR_ACCOUNT```
Seems the presence is there because it returns my public key
This is the B output:
```
[1610447397.997|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610447619.654|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610447674.911|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610447808.603|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610447869.755|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610447938.766|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610448014.053|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610448412.180|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610448419.393|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610448545.447|10864|sipaccountbase.cpp:505 ] Text message received from 6e9f6899e04c248aabb8325328dc4c219a298ac1, 1 part(s)
[1610448546.447|10864|sipaccountbase.cpp:505 ] Text message received from 6e9f6899e04c248aabb8325328dc4c219a298ac1, 1 part(s)
[1610448546.447|10864|sipaccountbase.cpp:505 ] Text message received from 6e9f6899e04c248aabb8325328dc4c219a298ac1, 1 part(s)
[1610448546.486|24715|message_engine.cpp:99 ] [message 2626223279278725] Retry sending
[1610448546.486|24715|sip_utils.cpp :210 ] Add header to SIP message: "User-Agent: Jami Daemon 9.8.0 (linux)"
[1610448546.487|24738|account_manager.cpp:571 ] Found 1 devices for 6e9f6899e04c248aabb8325328dc4c219a298ac1
[1610448546.487|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610448546.487|24720|message_engine.cpp:304 ] [Account a2978fab8c7d045e] saved 1 messages to /home/danrobi/.cache/jami/a2978fab8c7d045e/messages
[1610448546.947|10864|message_engine.cpp:141 ] [message 2626223279278725] Message sent: success
[1610448546.947|10864|message_engine.cpp:153 ] [message 2626223279278725] Status changed to SENT
[1610448546.947|24721|message_engine.cpp:304 ] [Account a2978fab8c7d045e] saved 1 messages to /home/danrobi/.cache/jami/a2978fab8c7d045e/messages
[1610448600.049|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610449014.003|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610449024.029|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
[1610449167.796|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 connecting
[1610449177.838|24738|jamiaccount.cpp :2139 ] [Account a2978fab8c7d045e] Dht status : IPv4 connected; IPv6 disconnected
```
This is the A output:
```
[1610372703.905|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610372703.907|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610381300.801|30990|p2p.cpp :225 ] New file channel for outgoing transfer with id(13561621824184549404)
[1610381301.504|31101|sipaccountbase.cpp:542 ] Message displayed: can't parse message ID
[1610381347.839|31097|p2p.cpp :241 ] Channel down for outgoing transfer with id(13561621824184549404)
[1610389043.156|30968|configurationmanager.cpp:964 ] received connectivity changed - trying to re-connect enabled accounts
[1610389043.156|30968|jamiaccount.cpp :2522 ] connectivityChanged
[1610389043.157|31097|jamiaccount.cpp :3467 ] Refresh cache for TURN server resolution
[1610389043.157|30992|jamiaccount.cpp :2146 ] [Account c3982805fbbdb893] connecting to the DHT network...
[1610389043.183|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610389043.183|31097|jamiaccount.cpp :3517 ] Cache refreshed for TURN resolution
[1610389046.272|30968|configurationmanager.cpp:964 ] received connectivity changed - trying to re-connect enabled accounts
[1610389046.273|30968|jamiaccount.cpp :2522 ] connectivityChanged
[1610389046.273|30990|jamiaccount.cpp :3467 ] Refresh cache for TURN server resolution
[1610389046.274|30990|jamiaccount.cpp :3517 ] Cache refreshed for TURN resolution
[1610389046.274|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610389047.721|30992|jamiaccount.cpp :2150 ] [Account c3982805fbbdb893] connected to the DHT network
[1610389056.279|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610389056.282|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610392207.668|30968|configurationmanager.cpp:964 ] received connectivity changed - trying to re-connect enabled accounts
[1610392207.668|30968|jamiaccount.cpp :2522 ] connectivityChanged
[1610392207.669|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610392207.670|31097|jamiaccount.cpp :3467 ] Refresh cache for TURN server resolution
[1610392207.670|31097|jamiaccount.cpp :3517 ] Cache refreshed for TURN resolution
[1610392207.671|30992|jamiaccount.cpp :2146 ] [Account c3982805fbbdb893] connecting to the DHT network...
[1610392217.669|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610392220.483|30968|configurationmanager.cpp:964 ] received connectivity changed - trying to re-connect enabled accounts
[1610392220.484|30968|jamiaccount.cpp :2522 ] connectivityChanged
[1610392220.484|30990|jamiaccount.cpp :3467 ] Refresh cache for TURN server resolution
[1610392220.484|30990|jamiaccount.cpp :3517 ] Cache refreshed for TURN resolution
[1610392220.485|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610392220.904|30992|jamiaccount.cpp :2150 ] [Account c3982805fbbdb893] connected to the DHT network
[1610392230.494|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610392230.497|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610414741.507|31099|multiplexed_socket.cpp:154 ] Tls endpoint is down, shutdown multiplexed socket
[1610414741.508|31099|ice_transport.cpp :1476 ] [ice:0x7f7fec1d2190] ice send failed: Broken pipe
[1610414741.508|31099|tls_session.cpp :903 ] [TLS] transport failure on tx: errno = 5
[1610414741.508|31102|channeled_transport.cpp:265 ] [SIPS] process disconnect event
[1610414741.508|31101|channeled_transport.cpp:265 ] [SIPS] process disconnect event
[1610424686.063|30968|configurationmanager.cpp:964 ] received connectivity changed - trying to re-connect enabled accounts
[1610424686.064|30968|jamiaccount.cpp :2522 ] connectivityChanged
[1610424686.065|30992|jamiaccount.cpp :2146 ] [Account c3982805fbbdb893] connecting to the DHT network...
[1610424686.065|30990|jamiaccount.cpp :3467 ] Refresh cache for TURN server resolution
[1610424686.066|30990|jamiaccount.cpp :3517 ] Cache refreshed for TURN resolution
[1610424696.813|30977|nat_pmp.cpp :403 ] NAT-PMP: Can't send all port mapping removal request
[1610424696.814|30977|nat_pmp.cpp :403 ] NAT-PMP: Can't send all port mapping removal request
[1610424696.814|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610424699.568|30968|configurationmanager.cpp:964 ] received connectivity changed - trying to re-connect enabled accounts
[1610424699.568|30968|jamiaccount.cpp :2522 ] connectivityChanged
[1610424699.568|31097|jamiaccount.cpp :3467 ] Refresh cache for TURN server resolution
[1610424699.568|30977|nat_pmp.cpp :90 ] NAT-PMP: Can't initialize libnatpmp -> CONNECTERR
[1610424699.568|31097|jamiaccount.cpp :3517 ] Cache refreshed for TURN resolution
[1610424700.127|30992|jamiaccount.cpp :2150 ] [Account c3982805fbbdb893] connected to the DHT network
[1610424965.071|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610425092.822|30977|nat_pmp.cpp :413 ] NAT-PMP: Can't remove all port mappings: NOGATEWAYSUPPORT
[1610439278.984|30992|jamiaccount.cpp :3555 ] Ask 2e0591fbbd73852fb6a0a256b437cb86876b4f1d for a new SIP channel
[1610439289.686|30992|account_manager.cpp:314 ] Found peer device: 2e0591fbbd73852fb6a0a256b437cb86876b4f1d account:7c7bcd4beda4c92a5d8428078876f7d9a880e71c CA:7d5ff324646a7021f74009878405b9cb9db0136e
[1610439289.686|30992|connectionmanager.cpp:693 ] [Account c3982805fbbdb893] New connection requested by 2e0591fbbd73852fb6a0a256b437cb86876b4f1d
[1610439289.688|30992|account_manager.cpp:314 ] Found peer device: 2e0591fbbd73852fb6a0a256b437cb86876b4f1d account:7c7bcd4beda4c92a5d8428078876f7d9a880e71c CA:7d5ff324646a7021f74009878405b9cb9db0136e
[1610439289.690|30992|jamiaccount.cpp :2189 ] Accepting ICE request from account 7c7bcd4beda4c92a5d8428078876f7d9a880e71c
[1610439289.717|30992|connectionmanager.cpp:515 ] [Account c3982805fbbdb893] New response received from 2e0591fbbd73852fb6a0a256b437cb86876b4f1d
[1610439290.340|30992|account_manager.cpp:314 ] Found peer device: 2e0591fbbd73852fb6a0a256b437cb86876b4f1d account:7c7bcd4beda4c92a5d8428078876f7d9a880e71c CA:7d5ff324646a7021f74009878405b9cb9db0136e
[1610439291.485|32154|jamiaccount.cpp :3778 ] New SIP channel opened with 2e0591fbbd73852fb6a0a256b437cb86876b4f1d
[1610439292.282|31097|p2p.cpp :225 ] New file channel for outgoing transfer with id(11838955725066805196)
[1610439292.783|30990|p2p.cpp :241 ] Channel down for outgoing transfer with id(11838955725066805196)
[1610439298.102|32149|ice_transport.cpp :569 ] [ice:0x7f7fec061ed0] TCP negotiation failed: All ICE checklists failed (PJNATH_EICEFAILED)
[1610439298.102|32149|connectionmanager.cpp:438 ] ICE negotiation failed.
[1610439353.886|30990|p2p.cpp :225 ] New file channel for outgoing transfer with id(18340978044395196169)
[1610439354.385|32154|p2p.cpp :241 ] Channel down for outgoing transfer with id(18340978044395196169)
[1610439354.389|32159|sipaccountbase.cpp:542 ] Message displayed: can't parse message ID
```https://git.jami.net/savoirfairelinux/jami-project/-/issues/1161[UI] Currently Used Icons2021-11-19T16:57:11Ztr37ion[UI] Currently Used Icons# Issues
The currently used UI icons and their state is quite unintuitive.
If I suggest Jami to friends, I have a hard time explaining the UI and what the used icons mean or even in which current state they represent.
It goes as far...# Issues
The currently used UI icons and their state is quite unintuitive.
If I suggest Jami to friends, I have a hard time explaining the UI and what the used icons mean or even in which current state they represent.
It goes as far as the microphone icon is highlighted when the microphone is OFF. That would be ok, if the icon is e.g. colored red or clearly crosses the microphone with a red cross.
## Desktop
1. How do I share my Desktop? Where is the Desktop Share button?
2. Is my Microphone ON or OFF?
3. How can I share my desktop without starting a Video Call?
4. How do I know an incoming Call will start my webcam?
5. How can I force/switch incoming video Calls into Voice Chat only?
## Mobile
1. What is the meaning of the first and last icon?
2. Is my microphone ON or OFF?
## Suggestions
Please, use colors like red/green not just black/white icons, especially if icons like the first and last one almost look very similar (same shape) and you almost never know if they show a state or are just function buttons and their ON/OFF state looks almost the same.
[Example](https://www.elgato.com/themes/custom/smalcode/image/products/streaming-deck/proactive-deck-mic-off.png)
I had more strange situations. I will add them later if they come to my mind.
Please make the icons and their state clear. Enabling icons which actually show the current state is OFF is counterintuitive.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/255Changing account settings is slow2021-07-12T15:34:18ZAlbert Babí OllerChanging account settings is slowReloading account information takes more time than it should.Reloading account information takes more time than it should.Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/254Accessing settings view and changing a parameter during a call returns to cal...2022-10-29T17:27:33ZAlbert Babí OllerAccessing settings view and changing a parameter during a call returns to callviewAlbert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1160basic_ios::clear: iostream error every 493 seconds2021-01-26T15:25:56ZJürgen Lütersbasic_ios::clear: iostream error every 493 secondsHi, happy new Year.
I have just noticed that jami and dring are producing the following write errors, which are occuring in a regular interval. 8 minutes and 13 seconds or 493 seconds.
uname -a:
5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2...Hi, happy new Year.
I have just noticed that jami and dring are producing the following write errors, which are occuring in a regular interval. 8 minutes and 13 seconds or 493 seconds.
uname -a:
5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2020-12-17) x86_64 GNU/Linux
Jami Version : "Together" 2021-01-04 18:01:04 UTC
Jan 12 00:26:54 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:26:54 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:35:07 nuc dring: [Account ] Couldn't save messages to /home/xxxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:35:07 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:35:07 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:43:20 nuc dring: [Account xxx] Couldn't save messages to /home/xx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:43:20 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:43:20 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:51:33 nuc dring: [Account xxxx] Couldn't save messages to /home/xxxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:51:33 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:51:33 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:59:46 nuc dring: [Account xxx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:59:46 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:59:46 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:07:59 nuc dring: [Account xxx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:07:59 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:07:59 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:16:12 nuc dring: [Account xx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:16:12 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 01:16:12 nuc jami-gnome.desktop[4019]: Syncing lrc accounts list with the daemon
Jan 12 00:51:33 nuc dring: Keep alive registration callback for account 6eec02b60ae98264
Jan 12 00:51:33 nuc dring: [Account xxx] SIP port changed to 5060: reregistering SIP account
Jan 12 00:51:33 nuc dring: [Account xxx] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:51:33 nuc dring: Creating transport
Jan 12 00:51:33 nuc dring: Recycling transport 0.0.0.0:5060
Jan 12 00:59:46 nuc dring: Keep alive registration callback for account xxx
Jan 12 00:59:46 nuc dring: [Account xxx] SIP port changed to 5060: reregistering SIP account
Jan 12 00:59:46 nuc dring: [Account xxx] Couldn't save messages to /home/xxxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 00:59:46 nuc dring: Creating transport
Jan 12 00:59:46 nuc dring: Recycling transport 0.0.0.0:5060
Jan 12 01:07:59 nuc dring: Keep alive registration callback for account xxx
Jan 12 01:07:59 nuc dring: [Account xxx] SIP port changed to 5060: reregistering SIP account
Jan 12 01:07:59 nuc dring: [Account ] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:07:59 nuc dring: Creating transport
Jan 12 01:07:59 nuc dring: Recycling transport 0.0.0.0:5060
Jan 12 01:16:12 nuc dring: Keep alive registration callback for account 6eec02b60ae98264
Jan 12 01:16:12 nuc dring: [Account ] SIP port changed to 5060: reregistering SIP account
Jan 12 01:16:12 nuc dring: [Account ] Couldn't save messages to /home/xxx/.cache/jami/xxx/messages: basic_ios::clear: iostream error
Jan 12 01:16:12 nuc dring: Creating transport
Jan 12 01:16:12 nuc dring: Recycling transport 0.0.0.0:5060https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/109Calling a number with spaces in SIP fails2021-02-15T15:23:02ZStéphane GuillouCalling a number with spaces in SIP failsWhen calling a number with an SIP account, if the number includes spaces (which iOS does automatically to increase readability), the call fails.
For example, +32 123 45 67 89 vs +32123456789: the first one would do nothing (while it see...When calling a number with an SIP account, if the number includes spaces (which iOS does automatically to increase readability), the call fails.
For example, +32 123 45 67 89 vs +32123456789: the first one would do nothing (while it seems it is trying to connect, showing the call screen, but no sound), whereas the second one would work.
I am not sure how dependent this is from the SIP service it connects to (I am with DiamondCard.us), but I think Jami should remove the spaces if they exist in the first place anyway, before placing the call?Kateryna KostiukKateryna Kostiukhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1159Update contact info2021-01-11T16:35:13ZMartin MayerUpdate contact infoHi,
I'm also using (matrix,fractal) and wanted to join the jami freenode instance. However I don't know, how to do that and it is not described [here](https://git.jami.net/savoirfairelinux/ring-project/wikis/home#what-is-jami).
Now th...Hi,
I'm also using (matrix,fractal) and wanted to join the jami freenode instance. However I don't know, how to do that and it is not described [here](https://git.jami.net/savoirfairelinux/ring-project/wikis/home#what-is-jami).
Now this should be [possible](https://www.matrix.org/blog/2015/06/22/the-matrix-org-irc-bridge-now-bridges-all-of-freenode) and it would be nice to add the how-to information to the contact info.
Thanks!https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1242Screen sharing not discoverable2021-01-11T16:54:49ZMichal SuchánekScreen sharing not discoverableFrom FAQ
> How can I share my screen?
> 1. During a call, right-click on the correspondence screen.
> 1. Select the “Screen Sharing” option.
> 1. Your screen is now shared.
Why do I have to right-click something that can't even be expla...From FAQ
> How can I share my screen?
> 1. During a call, right-click on the correspondence screen.
> 1. Select the “Screen Sharing” option.
> 1. Your screen is now shared.
Why do I have to right-click something that can't even be explained in an intelligible way?
Can't there be just plain button that everyone can see?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1241account settings, connectivity, "Auto registration after expired" is only for...2021-11-10T20:20:32ZSébastien Blinaccount settings, connectivity, "Auto registration after expired" is only for SIPAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1158Feature Request: Hold sent messages on local device if recipient isn't online2021-01-08T13:12:14ZTylerFeature Request: Hold sent messages on local device if recipient isn't onlineI am interested in using this software and moving my friends over to it. I am reserved by the fact that if a friend is not reachable at the time I send a message it is stored on a server until they are online (from what I am told).
My s...I am interested in using this software and moving my friends over to it. I am reserved by the fact that if a friend is not reachable at the time I send a message it is stored on a server until they are online (from what I am told).
My suggestion is having my phone or PC hold my message and try to resend it every five-ten minutes until my friend is online and it sends. I know the messages are encrypted but I would just feel better if my phone or PC held the message and attempted to resend it.
Again, I was told that the first sentence is how the service works, if it behaves how I am requesting that would put my mind at ease.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/253Swarm: invalid message order2021-02-15T15:42:21ZGuillaume HellerSwarm: invalid message orderScenario:
* Same account on two different devices A and B
* Send message either from device A or device B
* Messages sent from device A are not displayed in the correct order on device B
![image](/uploads/3847d53f6b734dd9dbee39baf93e...Scenario:
* Same account on two different devices A and B
* Send message either from device A or device B
* Messages sent from device A are not displayed in the correct order on device B
![image](/uploads/3847d53f6b734dd9dbee39baf93ea821/image.png)Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/252Choose the contact directly after clearing conversation history will still be...2021-01-07T22:09:07ZMing Rui ZhangChoose the contact directly after clearing conversation history will still be able to see the historyMing Rui ZhangMing Rui Zhanghttps://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-daemon/-/issues/382Support multi-stream - remove the use of template for Call/SipCall classes2021-03-02T15:48:03ZMohamed ChibaniSupport multi-stream - remove the use of template for Call/SipCall classesThis is a refactoring and preparation activity for multi-stream support.This is a refactoring and preparation activity for multi-stream support.Mohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1238Screen capture doesn't work on wayland2021-01-05T19:46:16ZИльдар АхметгалеевScreen capture doesn't work on waylandScreen capture for wayland should use libportal and pipewire like FireFox and Chromium do.
For now Jami captures only black screen and X11 windows.Screen capture for wayland should use libportal and pipewire like FireFox and Chromium do.
For now Jami captures only black screen and X11 windows.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1156jami-gnome ate 102GB of virtual memory2021-05-29T03:25:45ZHypnosis@I2Pjami-gnome ate 102GB of virtual memoryA memory leak?
OS: ubuntu-mate 20.04
Jami version:
```
aptitude show -vvv jami
Package: jami
Version: 20201222.2.67e50b1~dfsg1-1
Package: jami
Version: 20201222.2.67e50b1~dfsg1-1
Package: jami
Version: 20190215...A memory leak?
OS: ubuntu-mate 20.04
Jami version:
```
aptitude show -vvv jami
Package: jami
Version: 20201222.2.67e50b1~dfsg1-1
Package: jami
Version: 20201222.2.67e50b1~dfsg1-1
Package: jami
Version: 20190215.1.f152c98~ds1-1build2
State: installed (20201222.2.67e50b1~dfsg1-1), upgrade available (20190215.1.f152c98~ds1-1build2)
```https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1237Microphone and webcam still in use after bad end call2021-01-04T09:21:11ZkoolokMicrophone and webcam still in use after bad end callWhen a call end up badly (ex: loose of connection on the other side), the microphone and the webcam are still "in use" until restarting Jami.When a call end up badly (ex: loose of connection on the other side), the microphone and the webcam are still "in use" until restarting Jami.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1236Bluetooth system setting2023-05-26T13:59:36ZkoolokBluetooth system settingThe situation:
I have a Bose qc35 II, and for some reason, the microphone deosn't work on linux over bluetooth, it's a well known issue not related to Jami.
The solution is to setup my laptop microphone as default, so I can hear people ...The situation:
I have a Bose qc35 II, and for some reason, the microphone deosn't work on linux over bluetooth, it's a well known issue not related to Jami.
The solution is to setup my laptop microphone as default, so I can hear people from my headphone andthe can hear me from my laptop microphone. (see attached screeshot)![Capture_d_écran_de_2021-01-03_12-05-38](/uploads/1235a21a8f780aba3689f6fd08821b41/Capture_d_écran_de_2021-01-03_12-05-38.png)
This setup works well on telegram app, whereby and nextcloud talk (using firefox or chrome) but on Jami it's lookalike the app try to use my headset microphone, so nobody can hear me.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1235Can't make call, need restart2021-08-20T19:07:18ZkoolokCan't make call, need restartRandomly I can't, neither make a call or receive call, but I can still chat without issue.
After restarting Jami, everything works again.
Just to let you know, on my computer I have both ipv4 and ipv6 but the ipv6 connection is not avai...Randomly I can't, neither make a call or receive call, but I can still chat without issue.
After restarting Jami, everything works again.
Just to let you know, on my computer I have both ipv4 and ipv6 but the ipv6 connection is not available all the time, when waking up from standby, the ipv6 connection can be off for ~1 minutes before working again.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/876Bluetooth headset2023-03-03T21:06:19ZkoolokBluetooth headsetNeither the microphone or the headphone works.
The sound still come from the phone and on the other side nobody can hear me.Neither the microphone or the headphone works.
The sound still come from the phone and on the other side nobody can hear me.