savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-12-18T16:45:47Zhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/299Question: Background services2023-12-18T16:45:47ZNishQuestion: Background servicesJust a few question as I was trying to implement IOS support for new framework called Neon in nextcloud, they use a dependency named UnifiedPush which didn't support IOS because IOS doesn't allow support of background services. So, I was...Just a few question as I was trying to implement IOS support for new framework called Neon in nextcloud, they use a dependency named UnifiedPush which didn't support IOS because IOS doesn't allow support of background services. So, I was like how is Jami doing it's on notifications are they using APNs or they use the P2P network if so then how? But I saw that there's background app refresh which led to learning about Background Tasks so is the app using this to run the network?https://git.jami.net/savoirfairelinux/dhtnet/-/issues/4Add basic files README/COPYING/INSTALL instructions2024-03-09T00:41:19ZSébastien BlinAdd basic files README/COPYING/INSTALL instructionsAll is in the titleAll is in the titleAmna SneneAmna Snenehttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/895windows: UT: make and run unit tests in windows2023-11-17T16:34:28ZAline Gondim Santoswindows: UT: make and run unit tests in windowshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1364SIP account "randomly" disconnect with "connection error"2023-09-13T18:20:26ZThomas M.SIP account "randomly" disconnect with "connection error"Hello
I am new to Jami. I use it as a SIP client, with ntfy for push notifications
It appears that sometimes, “randomly”, at least I cannot reproduce it, it disconnects
It is written “Connection Error” and in the logs, I have read: “SIP ...Hello
I am new to Jami. I use it as a SIP client, with ntfy for push notifications
It appears that sometimes, “randomly”, at least I cannot reproduce it, it disconnects
It is written “Connection Error” and in the logs, I have read: “SIP registration failed, status=500 (Registering glare condition)”
I have to toggle on/off to reconnect. Sometimes it reconnects by itself after a while
What could it be? I tried different app, and two are installed at the same time (Jami and another one)
There could be a conflict?
I have already read some thread looking this one, but they date from 2021, they are maybe outdated?
Thank you in advance for your help
specifications:
* Another SIP client than Jami is installed on the smartphone
* I use e/OS and not "regular" Android
* I use a VPN
* It seems it only happens on Wifi, not on mobile data (with mobile data, I do not use the VPN)
Here is the log I exported finding the account disconnected (I hope I deleted all personal data...)
Thank you in advance for your help
<details><summary>Click to expand</summary>
```
[xxxxxxxxx.xxx|19808|manager.cpp :720 ] Not initialized
[xxxxxxxxx.xxx|19808|manager.cpp :794 ] Using PJSIP version 2.12.1 for aarch64-unknown-linux-android
[xxxxxxxxx.xxx|19808|manager.cpp :795 ] Using GnuTLS version 3.8.0
[xxxxxxxxx.xxx|19808|manager.cpp :796 ] Using OpenDHT version 2.6.0
[xxxxxxxxx.xxx|19808|manager.cpp :797 ] Using FFmpeg version 4.0.0-3315-g9899ae3f2
[xxxxxxxxx.xxx|19808|manager.cpp :800 ] Using Libgit2 version 1.6.4
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :742 ] SIPVoIPLink@xxxxxxxxxxxx
[xxxxxxxxx.xxx|19808|manager.cpp :816 ] Configuration file path: /data/user/0/cx.ring/app_config/dring.yml
[xxxxxxxxx.xxx|19808|system_codec_container.cpp:220 ] Can't find a usable accelerated H265/HEVC codec, disabling.
[xxxxxxxxx.xxx|19808|system_codec_container.cpp:250 ] Encoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU
[xxxxxxxxx.xxx|19808|system_codec_container.cpp:251 ] Decoders found: H264 VP8 MP4V-ES H263-1998 opus G722 G726-32 speex speex speex PCMA PCMU
[xxxxxxxxx.xxx|19808|sipaccount.cpp :1476] Presence enabled for xxxxxxxxxxxxxxxx : false.
[xxxxxxxxx.xxx|19808|ringbuffer.cpp :55 ] Create new RingBuffer urgentRingBuffer_id
[xxxxxxxxx.xxx|19808|audiolayer.cpp :65 ] [audiolayer] AGC: 1, noiseReduce: auto, VAD: 1, echoCancel: auto, audioProcessor: webrtc
[xxxxxxxxx.xxx|19808|sipaccount.cpp :1476] Presence enabled for xxxxxxxxxxxxxxxx : false.
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :332 ] Created UDP transport on address 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=2
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19808|sipaccount.cpp :528 ] [SIP Account xxxxxxxxxxxxxxxx] setPushNotificationToken:
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1565] [Account xxxxxxxxxxxxxxxx] Checking IP route after the registration
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1590] Checking received VIA address: 1xx.x.x.x.125
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1671] [account xxxxxxxxxxxxxxxx] Contact address changed: (xx.x.x.x:5060 --> 1xx.x.x.x.1xx.x.x.x). Updating registration.
[xxxxxxxxx.xxx|19824|sipaccount.cpp :887 ] New contact: <sip:003xxx.xxx.xx.xxx.2.1xx.x.x.x9238>
[xxxxxxxxx.xxx|19808|configurationmanager.cpp:967 ] received connectivity changed - trying to re-connect enabled accounts
[xxxxxxxxx.xxx|19808|sipaccount.cpp :307 ] Removing old transport [xxxxxxxxxxxx] from account
[xxxxxxxxx.xxx|19808|siptransport.cpp :104 ] ~SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=11
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [0x0]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :295 ] Recycling transport 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=11
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19825|message_engine.cpp :346 ] [Account xxxxxxxxxxxxxxxx] saved 0 messages to /data/user/0/cx.ring/cache/xxxxxxxxxxxxxxxx/messages
[xxxxxxxxx.xxx|19808|configurationmanager.cpp:967 ] received connectivity changed - trying to re-connect enabled accounts
[xxxxxxxxx.xxx|19808|sipaccount.cpp :957 ] pjsip_regc_send failed with error 171001: Object is busy (PJSIP_EBUSY)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :701 ] doUnregister VoipLinkException occurred: Unable to send request to unregister sip account
[xxxxxxxxx.xxx|19808|sipaccount.cpp :307 ] Removing old transport [xxxxxxxxxxxx] from account
[xxxxxxxxx.xxx|19808|siptransport.cpp :104 ] ~SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=15
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [0x0]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :295 ] Recycling transport 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=15
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19808|sipaccount.cpp :528 ] [SIP Account xxxxxxxxxxxxxxxx] setPushNotificationToken:
[xxxxxxxxx.xxx|19808|configurationmanager.cpp:967 ] received connectivity changed - trying to re-connect enabled accounts
[xxxxxxxxx.xxx|19808|sipaccount.cpp :957 ] pjsip_regc_send failed with error 171001: Object is busy (PJSIP_EBUSY)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :701 ] doUnregister VoipLinkException occurred: Unable to send request to unregister sip account
[xxxxxxxxx.xxx|19808|sipaccount.cpp :307 ] Removing old transport [xxxxxxxxxxxx] from account
[xxxxxxxxx.xxx|19808|siptransport.cpp :104 ] ~SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=21
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [0x0]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :566 ] doRegister xxx.xxxx.fr
[xxxxxxxxx.xxx|19808|sipvoiplink.cpp :1521] try to resolve 'xxx.xxxx.fr' (port: 0)
[xxxxxxxxx.xxx|19808|sipaccount.cpp :663 ] Creating transport
[xxxxxxxxx.xxx|19808|siptransport.cpp :295 ] Recycling transport 0.0.0.0:5060
[xxxxxxxxx.xxx|19808|siptransport.cpp :83 ] SipTransport@xxxxxxxxxxxx tr=xxxxxxxxxxxx rc=21
[xxxxxxxxx.xxx|19808|sipaccount.cpp :316 ] Set new transport [xxxxxxxxxxxx]
[xxxxxxxxx.xxx|19808|sipaccount.cpp :755 ] Using contact header <sip:xx.x.x.x2xxxx@xx.x.x.x:5060> in registration
[xxxxxxxxx.xxx|19824|sipaccount.cpp :854 ] SIP registration failed, status=500 (Registering glare condition)
[xxxxxxxxx.xxx|19824|sipaccount.cpp :1773] Scheduling re-registration retry in 51 seconds..
[xxxxxxxxx.xxx|19816] Connectivity change check: host address xx.x.x.x
[xxxxxxxxx.xxx|19808|sipaccount.cpp :528 ] [SIP Account xxxxxxxxxxxxxxxx] setPushNotificationToken:
```
</details>https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/297[iOS Client] Client locks up completely when trying to add a new device2023-12-18T16:46:45ZCNC Nerd[iOS Client] Client locks up completely when trying to add a new deviceWhen I try to add a new device, the complete app becomes unresponsive.
Client version is 3.51 (20230714)
How to reproduce:
Account Configuration>New Device
A password window pops up.
Introduce your password.
A window with the message "...When I try to add a new device, the complete app becomes unresponsive.
Client version is 3.51 (20230714)
How to reproduce:
Account Configuration>New Device
A password window pops up.
Introduce your password.
A window with the message "Verifying" appears and closes fairly quickly and the app has to be closed forcefully because there is no further interaction possible ( locked up ).
I can not assure that the password is the correct one, but if it wasn't at least it would be desirable to have a message on the screen stating that the pw is incorrect and not a complete lockup of the app.
Best Regardshttps://git.jami.net/savoirfairelinux/dhtnet/-/issues/3Daily run tests2024-03-09T00:41:18ZSébastien BlinDaily run testsut_connectionManager is disabled daemon side because it was moved to dhtnet, but they are not run in any CI causing potential regressions to be undetectedut_connectionManager is disabled daemon side because it was moved to dhtnet, but they are not run in any CI causing potential regressions to be undetectedAmna SneneAmna Snenehttps://git.jami.net/savoirfairelinux/dhtnet/-/issues/2Add CI for review.jami.net2024-03-09T00:41:18ZSébastien BlinAdd CI for review.jami.netJenkins doesn't build anything, causing frequent regressions on windowsJenkins doesn't build anything, causing frequent regressions on windowsAmna SneneAmna Snenehttps://git.jami.net/savoirfairelinux/dhtnet/-/issues/1Disabling UPnP is bugguy2024-03-09T00:41:18ZSébastien BlinDisabling UPnP is bugguy# Scenario
+ Alice uses UPnP
+ Alice disable the upnp (upnpEnabled = false)
# Expected
+ New connections should not use any upnp candidates
# Current result
+ New connections can use upnp candidates.
+ Need to restart the applicatio...# Scenario
+ Alice uses UPnP
+ Alice disable the upnp (upnpEnabled = false)
# Expected
+ New connections should not use any upnp candidates
# Current result
+ New connections can use upnp candidates.
+ Need to restart the application to apply the preferencehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1333Crash when enabling back my account2023-09-14T13:08:37ZPierre NicolasCrash when enabling back my account## Describe your environment
Please specify the following:
- OS: Ubuntu 22.04
- Jami version: 202307311629
- What build you are using: Ubuntu Store
## Steps to reproduce
1. Launch Jami
2. Disable account
3. Enable account
I noticed ...## Describe your environment
Please specify the following:
- OS: Ubuntu 22.04
- Jami version: 202307311629
- What build you are using: Ubuntu Store
## Steps to reproduce
1. Launch Jami
2. Disable account
3. Enable account
I noticed that I should not wait too long between disabling and enabling if I want to reproduce the bug.
## Additional information
[Kazam_screencast_00021.webm](/uploads/ea96678c6c50053fb8d2a1667a7d3a08/Kazam_screencast_00021.webm)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1362ForegroundServiceStartNotAllowedException2023-09-12T14:45:14ZPierre NicolasForegroundServiceStartNotAllowedExceptionGoogle play console : crash at runtime
Devices : android 12, 12L and 13
```plaintext
Exception java.lang.RuntimeException:
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5110)
at android.app.ActivityThread.ac...Google play console : crash at runtime
Devices : android 12, 12L and 13
```plaintext
Exception java.lang.RuntimeException:
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5110)
at android.app.ActivityThread.access$2100 (ActivityThread.java:310)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2319)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loopOnce (Looper.java:226)
at android.os.Looper.loop (Looper.java:313)
at android.app.ActivityThread.main (ActivityThread.java:8663)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)
Caused by android.app.ForegroundServiceStartNotAllowedException:
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel (ForegroundServiceStartNotAllowedException.java:54)
at android.app.ForegroundServiceStartNotAllowedException$1.createFromParcel (ForegroundServiceStartNotAllowedException.java:50)
at android.os.Parcel.readParcelable (Parcel.java:3345)
at android.os.Parcel.createExceptionOrNull (Parcel.java:2432)
at android.os.Parcel.createException (Parcel.java:2421)
at android.os.Parcel.readException (Parcel.java:2404)
at android.os.Parcel.readException (Parcel.java:2346)
at android.app.IActivityManager$Stub$Proxy.setServiceForeground (IActivityManager.java:8094)
at android.app.Service.startForeground (Service.java:786)
at cx.ring.services.DataTransferService.onStartCommand (DataTransferService.kt:62)
at android.app.ActivityThread.handleServiceArgs (ActivityThread.java:5092)
Caused by android.os.RemoteException: Remote stack trace:
at com.android.server.am.ActiveServices.setServiceForegroundInnerLocked (ActiveServices.java:1955)
at com.android.server.am.ActiveServices.setServiceForegroundLocked (ActiveServices.java:1455)
at com.android.server.am.ActivityManagerService.setServiceForeground (ActivityManagerService.java:14154)
at android.app.IActivityManager$Stub.onTransact (IActivityManager.java:3648)
at com.android.server.am.ActivityManagerService.onTransact (ActivityManagerService.java:3038)
```Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/120Can't create users on a fresh install2023-10-05T12:57:27ZIgor AlmeidaCan't create users on a fresh installFresh install and I can't create a new user.
`[Timer-0] WARN net.jami.jams.server.update.UpdateCheckTask - Could not establish connection to JAMS Update Center with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: s...Fresh install and I can't create a new user.
`[Timer-0] WARN net.jami.jams.server.update.UpdateCheckTask - Could not establish connection to JAMS Update Center with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[https-jsse-nio-443-exec-9] INFO net.jami.jams.server.servlets.filters.ARequestLoggingFilter - Request: POST /api/admin/user
[https-jsse-nio-443-exec-9] INFO net.jami.jams.ca.workers.csr.builders.UserBuilder - User certificate: Not valid after: Thu Sep 05 16:17:07 EDT 2024
[https-jsse-nio-443-exec-1] INFO net.jami.jams.server.servlets.filters.ARequestLoggingFilter - Request: POST /api/admin/user
[https-jsse-nio-443-exec-1] INFO net.jami.jams.ca.workers.csr.builders.UserBuilder - User certificate: Not valid after: Thu Sep 05 16:17:25 EDT 2024
[https-jsse-nio-443-exec-2] INFO net.jami.jams.server.servlets.filters.ARequestLoggingFilter - Request: POST /api/admin/user
[https-jsse-nio-443-exec-2] INFO net.jami.jams.ca.workers.csr.builders.UserBuilder - User certificate: Not valid after: Thu Sep 05 16:17:48 EDT 2024
[https-jsse-nio-443-exec-10] INFO net.jami.jams.server.servlets.filters.ARequestLoggingFilter - Request: POST /api/admin/user
[https-jsse-nio-443-exec-10] INFO net.jami.jams.ca.workers.csr.builders.UserBuilder - User certificate: Not valid after: Thu Sep 05 16:18:34 EDT 2024
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/cryptoengine.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/authentication-module.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ldap-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ad-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-launcher.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-server.jar
[Timer-0] WARN net.jami.jams.server.update.UpdateCheckTask - Could not establish connection to JAMS Update Center with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/cryptoengine.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/authentication-module.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ldap-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ad-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-launcher.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-server.jar
[Timer-0] WARN net.jami.jams.server.update.UpdateCheckTask - Could not establish connection to JAMS Update Center with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[Thread-3] INFO net.jami.jams.ca.workers.crl.CRLWorker - Successfully ran revocation routine
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/cryptoengine.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/authentication-module.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ldap-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ad-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-launcher.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-server.jar
[Timer-0] WARN net.jami.jams.server.update.UpdateCheckTask - Could not establish connection to JAMS Update Center with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/cryptoengine.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/authentication-module.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ldap-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/libs/ad-connector.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-launcher.jar
[Timer-0] INFO net.jami.jams.common.utils.VersioningUtils - Found version 3.5 of /root/jams/jams/jams-server.jar
[Timer-0] WARN net.jami.jams.server.update.UpdateCheckTask - Could not establish connection to JAMS Update Center with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target`
Error on browser when typing the username:
`xhr.js:251 GET https://jams.XXXXXX.XX/api/nameserver/name/ialmeida 404
(anonymous) @ xhr.js:251
xhr @ xhr.js:49
q @ dispatchRequest.js:51
value @ Axios.js:146
(anonymous) @ bind.js:5
(anonymous) @ EditCreateUserProfile.tsx:444
h @ regeneratorRuntime.js:45
(anonymous) @ regeneratorRuntime.js:133
(anonymous) @ regeneratorRuntime.js:74
r @ asyncToGenerator.js:3
s @ asyncToGenerator.js:22
(anonymous) @ asyncToGenerator.js:27
(anonymous) @ asyncToGenerator.js:19
(anonymous) @ EditCreateUserProfile.tsx:439
onKeyUp @ FormikField.tsx:41
Wt @ react-dom.production.min.js:52
Yt @ react-dom.production.min.js:52
(anonymous) @ react-dom.production.min.js:53
kr @ react-dom.production.min.js:100
Er @ react-dom.production.min.js:101
(anonymous) @ react-dom.production.min.js:113
It @ react-dom.production.min.js:292
(anonymous) @ react-dom.production.min.js:50
Lr @ react-dom.production.min.js:105
Je @ react-dom.production.min.js:75
Ge @ react-dom.production.min.js:74
e.unstable_runWithPriority @ scheduler.production.min.js:18
Vi @ react-dom.production.min.js:122
Tt @ react-dom.production.min.js:292
Xe @ react-dom.production.min.js:73
EditCreateUserProfile.tsx:459 Error checking for existing users: AxiosError: Request failed with status code 404`https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1332link conversation unreadable2023-09-05T18:51:28ZFa_blink conversation unreadableHi, Why use blue for dialog in a chat window ?
It's the same blue as the link :
![Capture d’écran du 2023-09-05 18-33-06.png](/uploads/62aded6b0880a61d5b5fb5985d5169f1/Capture_d_%C3%A9cran_du_2023-09-05_18-33-06.png)
It's better with ...Hi, Why use blue for dialog in a chat window ?
It's the same blue as the link :
![Capture d’écran du 2023-09-05 18-33-06.png](/uploads/62aded6b0880a61d5b5fb5985d5169f1/Capture_d_%C3%A9cran_du_2023-09-05_18-33-06.png)
It's better with dark theme, but not at all :
![image.png](/uploads/0ce49de8c224d8a2d83fb225c1624e68/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1331libsecp256k1-1:0.3.2-2 not found2023-09-05T12:49:37Zbitnomlibsecp256k1-1:0.3.2-2 not foundWhen installing the jami-qt or jami-qt-git packages on arch, I get 404 error for libsecp256k1-1:0.3.2-2. Need to bump to libsecp256k1-1:0.3.2-3When installing the jami-qt or jami-qt-git packages on arch, I get 404 error for libsecp256k1-1:0.3.2-2. Need to bump to libsecp256k1-1:0.3.2-3https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1361QR code to link device2023-11-22T21:25:18ZEmma FalkiewitzQR code to link deviceIt would be better to have a QR code in addition to the NIP string when we want to link another device to our account.
Design: https://xd.adobe.com/view/3736bb7b-6777-4b48-a766-8645ae50380e-6265/screen/9609bc65-6cd6-44fc-9508-3ca740b6a4d...It would be better to have a QR code in addition to the NIP string when we want to link another device to our account.
Design: https://xd.adobe.com/view/3736bb7b-6777-4b48-a766-8645ae50380e-6265/screen/9609bc65-6cd6-44fc-9508-3ca740b6a4d6/specs/Emma FalkiewitzEmma Falkiewitzhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/115Groups: blueprint not saved2023-10-01T07:48:08ZSébastien BlinGroups: blueprint not saved# Scenario
+ go to groups
+ Select a blueprint=>Change blueprint
# Expected
+ Blueprint saved
# Current result
+ Blueprint not saved (default is kept)# Scenario
+ go to groups
+ Select a blueprint=>Change blueprint
# Expected
+ Blueprint saved
# Current result
+ Blueprint not saved (default is kept)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/892When kicked out of a Swarm, conversations still appears and make it like you ...2024-01-26T12:42:50ZThomas BallasiWhen kicked out of a Swarm, conversations still appears and make it like you can still discussThis would probably require the daemon to be able to put Swarm into an "archive" state that is read-only.
This behaviour has been observed in both client-qt and client-android:
![image](/uploads/55e741ab8b9a35d575822785560b8e22/image.p...This would probably require the daemon to be able to put Swarm into an "archive" state that is read-only.
This behaviour has been observed in both client-qt and client-android:
![image](/uploads/55e741ab8b9a35d575822785560b8e22/image.png) ![image](/uploads/043cf50d9609dbb57808e4d6e7b3a065/image.png)
(for some reason my name doesn't appear in client-qt)
Sending a message returns the following error:
```
[1693497329.637|56019|conversationrepository.cpp:1715] Invalid parent path (not in members or admins
[1693497329.637|56019|conversation_module.cpp :1077] Failed to send message to conversation 9d864ebe6712f18d1790b70d8ba7b605f78e63ac
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/891build fails on armhf, aarch64 and i686 for version 20230619.1 due to "to_guil...2024-02-14T14:03:59ZMaxim Cournoyerbuild fails on armhf, aarch64 and i686 for version 20230619.1 due to "to_guile(long int&)" ambiguous callHi,
The native armhf-linux build of libjami has broken since the upgrade to 20230619.1:
```plaintext
libtool: compile: g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I../.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJA...Hi,
The native armhf-linux build of libjami has broken since the upgrade to 20230619.1:
```plaintext
libtool: compile: g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I../.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJAMI_BUILD -Djami_EXPORTS -DASIO_STANDALONE -DMSGPACK_NO_BOOST -I/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/src -I/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/src/config -I/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/src/media -I/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/test -I/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/src/jami -DPREFIX=\"/gnu/store/snhlmq7k9lgmjx5h24rzz69phlfxc0zy-libjami-20230619.1\" -DJAMI_DATADIR=\"/gnu/store/snhlmq7k9lgmjx5h24rzz69phlfxc0zy-libjami-20230619.1/share/jami\" -DENABLE_TRACE -DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 -g -fno-omit-frame-pointer -Wall -Wextra -Wnon-virtual-dtor -Wno-deprecated -Wno-deprecated-declarations -Wno-unknown-pragmas -Wformat=2 -O0 -I../../src -I./src -I/gnu/store/da6ikq281d235hvb1cil2ls3iq80ni2m-guile-3.0.9/include/guile/3.0 -MT src/bindings/bindings.lo -MD -MP -MF src/bindings/.deps/bindings.Tpo -c src/bindings/bindings.cpp -o src/bindings/bindings.o >/dev/null 2>&1
In file included from ./src/bindings/bindings.h:27,
from src/bindings/signal.cpp:42:
./src/utils.h: In instantiation of ‘scm_unused_struct* pack_to_guile(Args ...) [with Args = {std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::vector<unsigned char, std::allocator<unsigned char> >, long int}; SCM = scm_unused_struct*]’:
./src/utils.h:147:31: required from ‘scm_unused_struct* apply_to_guile(SCM, Args ...) [with Args = {std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::vector<unsigned char, std::allocator<unsigned char> >, long int}; SCM = scm_unused_struct*]’
src/bindings/signal.cpp:83:37: required from ‘void Handler<Args>::doExecuteInGuile(Args ...) [with Args = {const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::vector<unsigned char, std::allocator<unsigned char> >&, long int}]’
src/bindings/signal.cpp:103:37: required from ‘static void* Handler<Args>::executeInGuile(void*) [with Args = {const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::vector<unsigned char, std::allocator<unsigned char> >&, long int}]’
src/bindings/signal.cpp:117:23: required from ‘void Handler<Args>::execute(Args ...) [with Args = {const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::vector<unsigned char, std::allocator<unsigned char> >&, long int}]’
src/bindings/signal.cpp:159:24: required from ‘void add_handler(std::map<std::__cxx11::basic_string<char>, std::shared_ptr<libjami::CallbackWrapperBase> >&, const char*) [with T = libjami::ConfigurationSignal::IncomingTrustRequest; Args = {const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const std::vector<unsigned char, std::allocator<unsigned char> >&, long int}]’
src/bindings/signal.cpp:317:24: required from here
./src/utils.h:129:40: error: call of overloaded ‘to_guile(long int&)’ is ambiguous
129 | std::vector<SCM> values = {to_guile(args)...};
| ~~~~~~~~^~~~~~
./src/utils.h:28:1: note: candidate: ‘scm_unused_struct* to_guile(bool)’
28 | to_guile(bool b)
| ^~~~~~~~
./src/utils.h:40:1: note: candidate: ‘scm_unused_struct* to_guile(uint8_t)’
40 | to_guile(uint8_t x)
| ^~~~~~~~
./src/utils.h:46:1: note: candidate: ‘scm_unused_struct* to_guile(uint16_t)’
46 | to_guile(uint16_t x)
| ^~~~~~~~
./src/utils.h:52:1: note: candidate: ‘scm_unused_struct* to_guile(uint32_t)’
52 | to_guile(uint32_t x)
| ^~~~~~~~
./src/utils.h:58:1: note: candidate: ‘scm_unused_struct* to_guile(uint64_t)’
58 | to_guile(uint64_t x)
| ^~~~~~~~
./src/utils.h:64:1: note: candidate: ‘scm_unused_struct* to_guile(int8_t)’
64 | to_guile(int8_t x)
| ^~~~~~~~
./src/utils.h:70:1: note: candidate: ‘scm_unused_struct* to_guile(int16_t)’
70 | to_guile(int16_t x)
| ^~~~~~~~
./src/utils.h:76:1: note: candidate: ‘scm_unused_struct* to_guile(int32_t)’
76 | to_guile(int32_t x)
| ^~~~~~~~
./src/utils.h:82:1: note: candidate: ‘scm_unused_struct* to_guile(int64_t)’
82 | to_guile(int64_t x)
| ^~~~~~~~
./src/utils.h:88:1: note: candidate: ‘scm_unused_struct* to_guile(double)’
88 | to_guile(double x)
| ^~~~~~~~
./src/utils.h:129:22: error: could not convert ‘{<expression error>}’ from ‘<brace-enclosed initializer list>’ to ‘std::vector<scm_unused_struct*>’
129 | std::vector<SCM> values = {to_guile(args)...};
| ^~~~~~
| |
| <brace-enclosed initializer list>
make[3]: *** [Makefile:652: src/bindings/signal.lo] Error 1
make[3]: Leaving directory '/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/test/agent'
make[2]: *** [Makefile:458: all-recursive] Error 1
make[2]: Leaving directory '/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon/test'
make[1]: *** [Makefile:593: all-recursive] Error 1
make[1]: Leaving directory '/tmp/guix-build-libjami-20230619.1.drv-0/jami-20230619.1/daemon'
make: *** [Makefile:499: all] Error 2
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("-j" "8" "V=1") exit-status: 2 term-signal: #f stop-signal: #f>
phase `build' failed after 576.2 seconds
command "make" "-j" "8" "V=1" failed with status 2
```
The full build log can be seen at: https://bordeaux.guix.gnu.org/build/1b4804ec-87df-4a7c-bd37-aab493e3bca7/loghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1360Can't make video calls without internet (Wifi hotspot)2024-01-19T19:53:22ZElysCan't make video calls without internet (Wifi hotspot)Steps to reproduce:
You are using two Android phones with the same Jami account (device 1 (sameuseraccount) - device 2 (sameuseraccount)).
Now you disable all internet connections (on all devices; wifi and/or LTE)
1. Now use device 1 ...Steps to reproduce:
You are using two Android phones with the same Jami account (device 1 (sameuseraccount) - device 2 (sameuseraccount)).
Now you disable all internet connections (on all devices; wifi and/or LTE)
1. Now use device 1 to create a Wi-Fi hotspot
1. Now device 2 will use the same Wi-Fi hotspot like device 1 (and will warn you that there is no internet)
1. If you tap a contact ONLY device 1 will show "no network connection" (NOT device 2 although it uses the same hotspot (without internet))
- You can send messages (haven't tried attachments) but at first you'll have to wait like 30 seconds or a minute (even if you're already connected to the WiFi)
- If you switch- so that device 2 no creates a hotspot even text messaging won't work anymore?
- But you can never make any calls (Desktop (hotspot WITH internet?) - Android had no issues?)
Maybe related: https://git.jami.net/savoirfairelinux/jami-docs/-/issues/9#note_38594https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1359Change emoji in the toolbar2023-08-31T10:47:16ZEmma FalkiewitzChange emoji in the toolbarIt would be better to choose which emoji to attach to the toolbar for more customization of the app
![Capture_d_écran_du_2023-08-30_16-27-50](/uploads/3453f075431e23692fa52cf82ba1af11/Capture_d_écran_du_2023-08-30_16-27-50.png)It would be better to choose which emoji to attach to the toolbar for more customization of the app
![Capture_d_écran_du_2023-08-30_16-27-50](/uploads/3453f075431e23692fa52cf82ba1af11/Capture_d_écran_du_2023-08-30_16-27-50.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1330CMake Qt version check is allowing the configure to succeed with versions bel...2024-02-21T22:02:20ZAndreas TraczykCMake Qt version check is allowing the configure to succeed with versions below the minumumThis will possibly allow the build to succeed leading to runtime failure.This will possibly allow the build to succeed leading to runtime failure.Andreas TraczykAndreas Traczyk