jami-daemon issueshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues2019-07-08T17:50:15Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/107UPnP: IGD discovery doesn't work when using WiFi + Ethernet2019-07-08T17:50:15ZSébastien BlinUPnP: IGD discovery doesn't work when using WiFi + EthernetHow to reproduce:
1. Add a log for `UPNP_DISCOVERY_SEARCH_RESULT` (`upnp_context.cpp:951`)
2. Using only WiFi (UPnP available), launch the daemon, the log is printed
3. Using WiFi + Eth, launch the daemon, the log is not be printed.How to reproduce:
1. Add a log for `UPNP_DISCOVERY_SEARCH_RESULT` (`upnp_context.cpp:951`)
2. Using only WiFi (UPnP available), launch the daemon, the log is printed
3. Using WiFi + Eth, launch the daemon, the log is not be printed.Iteration 10Eden AbitbolEden Abitbolhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/103Calls negotiate TCP + UDP and use TCP if the negotiation succeed.2019-07-17T13:36:59ZSébastien BlinCalls negotiate TCP + UDP and use TCP if the negotiation succeed.Iteration 10Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/89add peer discovery enable option per account2019-04-25T19:42:29ZAdrien Béraudadd peer discovery enable option per accountIteration 5Adrien BéraudAdrien Béraud2019-04-12https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/63Manage database instead of LRC.2020-09-24T20:21:25ZSébastien BlinManage database instead of LRC.The daemon should manage the Ring database instead the client.
This will allow the daemon to synchronize messages between all devices for example.The daemon should manage the Ring database instead the client.
This will allow the daemon to synchronize messages between all devices for example.Swarm-chathttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/62Offline messages2020-09-30T21:15:41ZSébastien BlinOffline messagesTODO: investigate.
Some keywords:
+ Maidsafe
+ IPFS
+ SupernodesTODO: investigate.
Some keywords:
+ Maidsafe
+ IPFS
+ SupernodesSwarm-chathttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/61File transfer without TURN server2019-05-02T18:21:58ZSébastien BlinFile transfer without TURN serverFor now, and because ICE doesn't supports TCP in pjsip, the file transfer has to pass through a TURN server. This is not perfect.
A better way to do that after https://git.ring.cx/savoirfairelinux/ring-project/issues/486 is to negotiate...For now, and because ICE doesn't supports TCP in pjsip, the file transfer has to pass through a TURN server. This is not perfect.
A better way to do that after https://git.ring.cx/savoirfairelinux/ring-project/issues/486 is to negotiate a TCP connection directly between the sender and receivers.Swarm-chathttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/47LAN users fail to discover each other2022-11-14T21:52:32ZIurii VoitenkoLAN users fail to discover each otherWith true loyalty to distributed p2p communications, it's a real embarrassment to require high speed Internet connection for Ring when used in LAN. Consider the following setup: a private 10.x.x.x LAN network with very strict firewall ru...With true loyalty to distributed p2p communications, it's a real embarrassment to require high speed Internet connection for Ring when used in LAN. Consider the following setup: a private 10.x.x.x LAN network with very strict firewall rules and proxies for Internet connection needs a p2p messenger for chat, VoIP and presence. Moreover, this LAN has just 56K for Internet and about 10M throughput for Intranet. I considered Ring as a major candidate for this task, but I was really frustrated when Ring required the whole bunch of Internet IPs to discover nodes sitting in the same LAN!
Hence, improvement suggestions:
1. Add static IP support.
Yes, sometimes it's much better to simply assign IP address to a contact than allow DHT lookup running for minutes and fail.
2. Significantly lower the required bandwidth when in DHT mode.
If Internet connection is limited in bandwidth the whole DHT feature is not working properly.
3. Add LAN peer discovery support
Peers can send IP multicast/broadcast packets to identify each other and hence skip the DHT lookup at all.LaterMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/44Error during config save leads to major loss of config and account related data2022-11-14T21:52:32ZHugo LefeuvreError during config save leads to major loss of config and account related dataToday I opened my Ring client and found out that most of my account and contact related information has disappeared.
* 4/5 accounts lost their avatar, display name and registered name
* 1 account lost all its linked devices
* 1 account ...Today I opened my Ring client and found out that most of my account and contact related information has disappeared.
* 4/5 accounts lost their avatar, display name and registered name
* 1 account lost all its linked devices
* 1 account lost all its linked devices except one
* several accounts **MAY** have lost some contacts
4/5 accounts are not functional anymore.
Only one account does not appear to have suffered from data loss. This account is still functional.
**Affects:** latest daemon master with latest LRC and GNOME client
**Daemon logs when starting:**
```
[1536072827.730| 7916|ringaccount.cpp :1421 ] [Account 7c2c46b550fdf679] loading Ring account
[1536072827.730| 7916|ringaccount.cpp :898 ] [Account 7c2c46b550fdf679] loading identity: ring_device.crt ring_device.key
[1536072827.878| 7916|certstore.cpp :75 ] CertificateStore: loaded 327 local certificates.
[1536072827.880| 7916|ringaccount.cpp :836 ] [Account 7c2c46b550fdf679] checking device receipt for 7ba67dbee50ab99fe44a1daa0992a8b5d11b1a21
[1536072827.881| 7916|ringaccount.cpp :891 ] [Account 7c2c46b550fdf679] ring:7ba67dbee50ab99fe44a1daa0992a8b5d11b1a21 device 459eda6e5c5a5819b19a157e4fc1e7491bea644d receipt checked successfully
[1536072827.881| 7916|ringaccount.cpp :2695 ] [Account 7c2c46b550fdf679] loading known account device 459eda6e5c5a5819b19a157e4fc1e7491bea644d
[1536072827.882| 7916|ringaccount.cpp :2406 ] [Account 7c2c46b550fdf679] Found account device: 459eda6e5c5a5819b19a157e4fc1e7491bea644d
[1536072827.883| 7916|ringaccount.cpp :2992 ] [Account 7c2c46b550fdf679] new contact: 00e29c5d3d518f96297b032ca21f5f8770573da8
[1536072827.884| 7916|ringaccount.cpp :2992 ] [Account 7c2c46b550fdf679] new contact: 3c2a2fae84be1713e6d68d39360faa7441220c00
[1536072827.885| 7916|ringaccount.cpp :2992 ] [Account 7c2c46b550fdf679] new contact: ded6a9d278d05adac3265a0a69d07bd264e0861a
[1536072827.886| 7916|ringaccount.cpp :3138 ] [Account 7c2c46b550fdf679] error loading trust requests: Can't read file: incomingTrustRequests
[1536072827.886| 7916|manager.cpp :2792 ] Found abandonned Ring account: /home/hlefeuvre/.local/share/ring/500c78989b647104/export.gz
```
```
[1536072828.803| 7916|ringaccount.cpp :1421 ] [Account 7170fb591202047e] loading Ring account
[1536072828.803| 7916|ringaccount.cpp :898 ] [Account 7170fb591202047e] loading identity: ring_device.crt ring_device.key
[1536072828.806| 7916|ringaccount.cpp :836 ] [Account 7170fb591202047e] checking device receipt for e3494b660ea1f988d4d66ed96811d9445eaa093c
[1536072828.807| 7916|ringaccount.cpp :891 ] [Account 7170fb591202047e] ring:e3494b660ea1f988d4d66ed96811d9445eaa093c device 7646c5dad40347ad8dc3524077a533f539d8a719 receipt checked successfully
[1536072828.807| 7916|ringaccount.cpp :2695 ] [Account 7170fb591202047e] loading known account device 7646c5dad40347ad8dc3524077a533f539d8a719
[1536072828.808| 7916|ringaccount.cpp :2406 ] [Account 7170fb591202047e] Found account device: 7646c5dad40347ad8dc3524077a533f539d8a719
[1536072828.809| 7916|ringaccount.cpp :2992 ] [Account 7170fb591202047e] new contact: 00e29c5d3d518f96297b032ca21f5f8770573da8
[1536072828.810| 7916|ringaccount.cpp :2992 ] [Account 7170fb591202047e] new contact: 3c2a2fae84be1713e6d68d39360faa7441220c00
[1536072828.811| 7916|ringaccount.cpp :3138 ] [Account 7170fb591202047e] error loading trust requests: Can't read file: incomingTrustRequests
[1536072828.811| 7916|manager.cpp :2792 ] Found abandonned Ring account: /home/hlefeuvre/.local/share/ring/2c8f461a28b01e2/export.gz
[1536072828.813| 7916|ringaccount.cpp :1421 ] [Account da65023c64f3d1a5] loading Ring account
[1536072828.814| 7916|ringaccount.cpp :898 ] [Account da65023c64f3d1a5] loading identity: ring_device.crt ring_device.key
[1536072828.817| 7916|ringaccount.cpp :836 ] [Account da65023c64f3d1a5] checking device receipt for 4a76358f13177319b906f1cc511175394e09c01a
[1536072828.818| 7916|ringaccount.cpp :891 ] [Account da65023c64f3d1a5] ring:4a76358f13177319b906f1cc511175394e09c01a device d524cf3a29c2db45d927cba48002a03ef73d2276 receipt checked successfully
[1536072828.819| 7916|ringaccount.cpp :2688 ] [Account da65023c64f3d1a5] error loading devices: Can't read file: knownDevicesNames
[1536072828.819| 7916|ringaccount.cpp :3022 ] [Account da65023c64f3d1a5] error loading contacts: Can't read file: contacts
[1536072828.819| 7916|ringaccount.cpp :3138 ] [Account da65023c64f3d1a5] error loading trust requests: Can't read file: incomingTrustRequests
```
**Client logs when starting:**
```
** (gnome-ring:7775): DEBUG: updating RING account display name to:
** (gnome-ring:7775): DEBUG: updating RING account display name to:
** (gnome-ring:7775): DEBUG: updating RING account display name to:
** (gnome-ring:7775): DEBUG: updating RING account display name to:
Trying to create a certificate node with an already used id. This can have unforneen consequences
```
As you can see the daemon is not able to load account information. In fact these files have been wiped out:
```
.local/share/ring/
├── 2c8f461a28b01e2
│ ├── contacts
│ ├── export.gz
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
├── 500c78989b647104
│ ├── export.gz
│ ├── ring_device.crt
│ └── ring_device.key
├── 7170fb591202047e
│ ├── config.yml
│ ├── contacts
│ ├── export.gz
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
├── 7c2c46b550fdf679
│ ├── config.yml
│ ├── contacts
│ ├── export.gz
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
├── 9fba7138a1fc3f51
│ ├── config.yml
│ ├── contacts
│ ├── export.gz
│ ├── incomingTrustRequests
│ ├── knownDevicesNames
│ ├── ring_device.crt
│ └── ring_device.key
.
.
.
```
This bug has been identified on at least 2 different computers with different builds and accounts. One of these two computers might even run a released version of Ring.Next major releasehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/42Add ringing timeout2022-11-14T21:52:32ZHugo LefeuvreAdd ringing timeoutCurrently there is no timeout for emitted calls. If a peer is connected but doesn't answer a call, then this call will ring 'forever', at least until the user manually aborts it or peer becomes unreachable.
We should implement such a ti...Currently there is no timeout for emitted calls. If a peer is connected but doesn't answer a call, then this call will ring 'forever', at least until the user manually aborts it or peer becomes unreachable.
We should implement such a timeout.Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/29Temporary IPv6 addresses can cause PJSIP to fail2022-11-14T21:52:31ZJami BotTemporary IPv6 addresses can cause PJSIP to failIssue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
\* Environment:
This problem seems to affect mostly GNU/Linux and macOS systems configured to change their iPv6 address often, a...Issue generated from Tuleap's migration script.
**Originally submitted by: Maxim Cournoyer (mcournoyer)**
\* Environment:
This problem seems to affect mostly GNU/Linux and macOS systems configured to change their iPv6 address often, as a privacy measure. It would affect any platform that gathers a sufficient number of temporary IPv6 addresses.
\* Reproduce steps:
1. Register multiple IPv6 addresses:
A script used to generate those temporary IPv6 addresses can be found here: https://gitlab.savoirfairelinux.com/snippets/116
That script and the accompanying 'gen-random-ipv6.sh' should be placed in the same directory. The IFDEV and IPV6\_PREFIX should be adjusted to match your network device and IPv6 prefix, respectively. It is important that the IFDEV environment matches the \*currently\* used network interface if you have many, otherwise the problem will not be triggered.
Run the script like this: sudo ./add-ipv6-addresses.sh
2. Launch Ring and try to place a call.
\* Expected result:
The call should succeed.
\* Actual result (as seen in the daemon's debug output):
[1513801602.823|14926|ice\_transport.cpp :429 ] [ice:0x2fa48b0] initialization success
[1513801602.823|14926|ice\_transport.cpp :482 ] ICE as master
[1513801602.829|14926|ice\_transport.cpp :576 ] [ice:0x2fa48b0] (local) ufrag=2567c1bd, pwd=51e44a5d
[1513801602.829|12099|sipcall.cpp :776 ] [call:10040259774347710226] fill SDP with ICE transport 0x2d97040
dring: ../src/pjmedia/sdp.c:187: pjmedia\_sdp\_attr\_add: Assertion `\*count < (32\*2 + 4)' failed.
Abandon (core dumped)
A patch addressing the issue is in review here: https://gerrit-ring.savoirfairelinux.com/\#/c/8462/Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/21SIP register fails: No username on digest authentication2024-02-08T18:58:54ZAlba MendezSIP register fails: No username on digest authenticationThis bug has been driving me mad for quite some time. I just installed Ring for Ubuntu 16.04 following official instructions, opened, set up a SIP account with hostname=10.139.205.101, username=10, password=test and it fails to register....This bug has been driving me mad for quite some time. I just installed Ring for Ubuntu 16.04 following official instructions, opened, set up a SIP account with hostname=10.139.205.101, username=10, password=test and it fails to register.
My Asterisk server sends:
From: "main" <sip:10@10.139.205.101>;tag=8005b703-201b-47e8-be88-03d7564a5ba8
To: "main" <sip:10@10.139.205.101>;tag=as3f952c47
...
WWW-Authenticate: Digest algorithm=MD5, realm="asterisk", nonce="0074f5d0"
And Ring then sends:
From: "main" <sip:10@10.139.205.101>;tag=8005b703-201b-47e8-be88-03d7564a5ba8
To: "main" <sip:10@10.139.205.101>
...
Authorization: Digest , realm="asterisk", nonce="0074f5d0", uri="sip:10.139.205.101", response="631415fcf3715907a48f11fec1e6a880", algorithm=MD5
i.e. notice the space and comma after `Digest`
ring-daemon version 2018-07-07. Bug could be on upstream, for some reason username is not set on `pjsip/src/pjsip/sip_auth_client.c` when adding the Authorization header, [header printed here](https://github.com/asterisk/pjproject/blob/106ec876a371b57bb3db8231a55cb5f368e6266b/pjsip/src/pjsip/sip_auth_msg.c#L73).Next major releaseSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/9dtmf tones do not work2024-03-08T19:26:14ZJami Botdtmf tones do not workIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>A user reported that sending dtmf tones (SIP or RTP) does not work.<br />
<br />
I think RTP tones are broken in the daem...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>A user reported that sending dtmf tones (SIP or RTP) does not work.<br />
<br />
I think RTP tones are broken in the daemon since a while ago. Its also possible that SIP tones work, but are not accepted in all cases on the other end?</p>
<p>Also the gnome UI is not very nice for sending them, so could also be an input issue.</p>SIP support - first iterationSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/975Link voice setup callback to host (without rtp session)2024-03-25T18:36:16ZSébastien BlinLink voice setup callback to host (without rtp session)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/974Various asserts and crashes with TURN / PJNATH2024-03-25T18:29:13ZAdrien BéraudVarious asserts and crashes with TURN / PJNATHTypical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 D...Typical assertion when PJSIP built with asserts:
```
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Build fingerprint: 'google/cheetah/cheetah:14/AP1A.240305.019.A1/11445699:user/release-keys'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Revision: 'MP1.0'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A ABI: 'arm64'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Timestamp: 2024-03-22 14:13:31.550572829-0400
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Process uptime: 2s
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Cmdline: cx.ring
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A pid: 8414, tid: 9172, name: Thread-64 >>> cx.ring <<<
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A uid: 10352
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A tagged_addr_ctrl: 0000000000000001 (PR_TAGGED_ADDR_ENABLE)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A Abort message: '../src/pjnath/turn_session.c:740: pj_status_t pj_turn_session_alloc(pj_turn_session *, const pj_turn_alloc_param *): assertion "sess->state>PJ_TURN_STATE_NULL && sess->state<=PJ_TURN_STATE_RESOLVED" failed'
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x0 0000000000000000 x1 00000000000023d4 x2 0000000000000006 x3 000000795e531320
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x4 2f333639622d6d6e x5 2f333639622d6d6e x6 2f333639622d6d6e x7 7f7f7f7f7f7f7f7f
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x8 00000000000000f0 x9 0000007d40c87200 x10 0000000000000001 x11 0000007d40cd1ba0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x12 0000007d5ac86020 x13 000000007fffffff x14 00000000009ffbec x15 00000247cba606d0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x16 0000007d40d3cfc8 x17 0000007d40d1a160 x18 000000795b0d8000 x19 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x20 00000000000023d4 x21 00000000ffffffff x22 0000000000002374 x23 00000000000020de
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x24 000000795e5318b0 x25 000000795e5318b0 x26 000000795e531bf0 x27 00000000000fc000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A x28 00000000000fe000 x29 000000795e5313a0
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A lr 0000007d40cc2e48 sp 000000795e531300 pc 0000007d40cc2e74 pst 0000000000001000
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A 11 total frames
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A backtrace:
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #00 pc 000000000005ee74 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #01 pc 000000000005f284 /apex/com.android.runtime/lib64/bionic/libc.so (__assert2+36) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #02 pc 0000000001922e2c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_turn_session_alloc+284) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #03 pc 000000000192a61c /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #04 pc 000000000192a258 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #05 pc 000000000194d5f4 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #06 pc 00000000019414bc /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (ioqueue_dispatch_write_event+416) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #07 pc 0000000001945428 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (pj_ioqueue_poll+1476) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #08 pc 0000000001739b98 /data/app/~~VtmIPQIw72akn02OjhBU0g==/cx.ring-aDZMbBTi4zOBSAIxpYGD2w==/base.apk!libjami-core-jni.so (offset 0xd64000) (BuildId: f128353698d79bade99658daa4d09034a3aee20e)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #09 pc 00000000000ca7cc /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+204) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
2024-03-22 14:13:31.793 9191-9191 DEBUG pid-9191 A #10 pc 00000000000607b0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 33ad5959e2b38fc822cda3c642e16c94)
```Sébastien BlinFrançois-Simon Fauteux-ChapleauSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/973Flatpak: Automatic Upgrades: tag versions of jami-daemon which jami-client de...2024-03-22T09:29:01ZovariFlatpak: Automatic Upgrades: tag versions of jami-daemon which jami-client depends on>> It would be great if this Flatpak package would upgrade automatically if a newer upstream version of Jami is released.
> Not possible because of how jami-client depends on specific untagged versions of jami-daemon.
https://github.co...>> It would be great if this Flatpak package would upgrade automatically if a newer upstream version of Jami is released.
> Not possible because of how jami-client depends on specific untagged versions of jami-daemon.
https://github.com/flathub/net.jami.Jami/issues/86https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/972Modified contact profile synchronization2024-03-19T13:01:46ZPierre NicolasModified contact profile synchronizationhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1402#note_48719
> The display name and the profile picture, which I have assigned to my contact myself, have not been synchronised.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1402#note_48719
> The display name and the profile picture, which I have assigned to my contact myself, have not been synchronised.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/971"jamid" received signal SIGABRT, Aborted.2024-03-08T19:26:08ZCyrille Béraud"jamid" received signal SIGABRT, Aborted.`1709906012.321|57318|conversation.cpp :1675] Sync e43a7778189cc4adc94185c8db7e96c8d1097ed7 with 9138aa43a57c4cb0c77409837637d62e2c8731f176699e38c8c892a8f884f151
Thread 2 "jamid" received signal SIGABRT, Aborted.
[Switching to Th...`1709906012.321|57318|conversation.cpp :1675] Sync e43a7778189cc4adc94185c8db7e96c8d1097ed7 with 9138aa43a57c4cb0c77409837637d62e2c8731f176699e38c8c892a8f884f151
Thread 2 "jamid" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffff39ff6c0 (LWP 319436)]
__pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: Aucun fichier ou dossier de ce type.
(gdb) bt
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6737c9b in __GI___fortify_fail (msg=msg@entry=0x7ffff67c8a98 "bit out of range 0 - FD_SETSIZE on fd_set") at ./debug/fortify_fail.c:24
#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
#14 0x0000555555f214bf in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dhtnet::upnp::UPnPContext::createIoContext(std::shared_ptr<asio::io_context> const&, std::shared_ptr<dht::log::Logger> const&)::{lambda()#1}> > >::_M_run() ()
#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6737c9b in __GI___fortify_fail (msg=msg@entry=0x7ffff67c8a98 "bit out of range 0 - FD_SETSIZE on fd_set") at ./debug/fortify_fail.c:24
#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
#14 0x0000555555f214bf in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dhtnet::upnp::UPnPContext::createIoContext(std::shared_ptr<asio::io_context> const&, std::shared_ptr<dht::log::Logger> const&)::{lambda()#1}> > >::_M_run() ()
#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff66428e6 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4 0x00007ffff66268b7 in __GI_abort () at ./stdlib/abort.c:79
#5 0x00007ffff6627750 in __libc_message (fmt=fmt@entry=0x7ffff67c38d3 "*** %s ***: terminated\n") at ../sysdeps/posix/libc_fatal.c:150
#6 0x00007ffff6737c9b in __GI___fortify_fail (msg=msg@entry=0x7ffff67c8a98 "bit out of range 0 - FD_SETSIZE on fd_set") at ./debug/fortify_fail.c:24
#7 0x00007ffff6737792 in __GI___fdelt_chk (d=<optimized out>) at ./debug/fdelt_chk.c:26
#8 0x0000555555f41224 in dhtnet::upnp::NatPmp::readResponse(natpmp_t&, natpmpresp_t&) ()
#9 0x0000555555f42790 in dhtnet::upnp::NatPmp::getIgdPublicAddress() ()
#10 0x0000555555f430e3 in dhtnet::upnp::NatPmp::initNatPmp() ()
#11 0x0000555555f47075 in dhtnet::upnp::NatPmp::searchForIgd() ()
#12 0x0000555555f43b99 in asio::detail::wait_handler<dhtnet::upnp::NatPmp::searchForIgd()::{lambda(std::error_code const&)#1}, asio::any_io_executor>::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) ()
#13 0x0000555555f2115e in asio::detail::scheduler::run(std::error_code&) [clone .isra.0] ()
#14 0x0000555555f214bf in std::thread::_State_impl<std::thread::_Invoker<std::tuple<dhtnet::upnp::UPnPContext::createIoContext(std::shared_ptr<asio::io_context> const&, std::shared_ptr<dht::log::Logger> const&)::{lambda()#1}> > >::_M_run() ()
#15 0x00007ffff6ae6333 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#16 0x00007ffff6697b5a in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444
#17 0x00007ffff67285fc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
(gdb)
`Adrien BéraudSébastien BlinAdrien Béraudhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/970Video camera stream is black when hardware acceleration is enabled2024-03-08T13:26:13ZPaul Le Guen de KerneizonVideo camera stream is black when hardware acceleration is enabled## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue i...## How to report a bug
## One bug = one bug report
If you have multiple issues, please file separate bug reports. It will be much easier to track bugs that way.
## Avoid duplicates
Search for similar problem - update existing issue instead of creating new one.
## Bug report form
## Describe your environment
Please specify the following:
- OS: Ubuntu 22.04.4 LTS
- Jami version: 202402141827
- What build you are using: jami.net
## Steps to reproduce
1. Enable hardware acceleration in parameters with 960x540 resolution
2. Start a video call
- Actual result: My video camera stream is black on the Jami screen of other contacts in the meeting. However, I can see myself on my Jami screen. Must disable hardware acceleration to solve the problem or change the video resolution to 1280x720
- Expected result: Other people can see my camera video stream instead of a black screen.
## Additional information
- With Jami enable with `--debug`, this log appeared:
```
[1709890977.592|52761|accel.cpp :298 ] Failed to push frame to GPU: Invalid argument
[1709890977.593|52761|media_encoder.cpp :438 ] Fail to get frame
[1709890977.593|52761|video_sender.cpp :87 ] encoding failed
```
- The issue appears whatever camera I use
- My laptop is a Lenovo P14S with AMD GPU and same hardware
- We achieve to reproduce the same bug with Fedora 39
On contact side:
![Screenshot_from_2024-03-08_11-29-49](/uploads/f93d51095c449899708f64255c9f4850/Screenshot_from_2024-03-08_11-29-49.png)
On my side:
![Screenshot_from_2024-03-08_11-29-48](/uploads/f5672232032c2ce2a9671ebf44825c2e/Screenshot_from_2024-03-08_11-29-48.png)
For retrieving logs, cf [this page](https://git.jami.net/savoirfairelinux/ring-project/wikis/tutorials/Bug-report-guide#logs).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/968Fix sporadic failures2024-03-05T17:58:43ZSébastien BlinFix sporadic failures```
1) test: jami::test::ConversationTest::testIsComposing (F) line: 986 conversation/conversation.cpp
assertion failed
- Expression: cv.wait_for(lk, 30s, [&]() { return bobData.composing; })
```
```
1) test: jami::test::ConversationM...```
1) test: jami::test::ConversationTest::testIsComposing (F) line: 986 conversation/conversation.cpp
assertion failed
- Expression: cv.wait_for(lk, 30s, [&]() { return bobData.composing; })
```
```
1) test: jami::test::ConversationMembersEventTest::testAddAcceptOfflineThenConnects (F) line: 613 conversation/conversationMembersEvent.cpp
assertion failed
- Expression: cv.wait_for(lk, 60s, [&]() { return !bobData.conversationId.empty(); })
```
```
!!!FAILURES!!!
Test Results:
Run: 4 Failures: 3 Errors: 0
1) test: jami::test::TypersTest::testSetIsComposing (F) line: 203 conversation/typers.cpp
assertion failed
- Expression: cv.wait_for(lk, 5s, [&]() { return bobData.composing[aliceUri]; })
2) test: jami::test::TypersTest::testTimeout (F) line: 229 conversation/typers.cpp
assertion failed
- Expression: cv.wait_for(lk, 5s, [&]() { return bobData.composing[aliceUri]; })
3) test: jami::test::TypersTest::testTypingRemovedOnMemberRemoved (F) line: 254 conversation/typers.cpp
assertion failed
- Expression: cv.wait_for(lk, 5s, [&]() { return aliceData.composing[bobUri]; })
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/966Merge bind and attach methods2024-02-28T15:12:19ZSébastien BlinMerge bind and attach methods