savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2024-03-09T00:41:19Zhttps://git.jami.net/savoirfairelinux/dhtnet/-/issues/6Add proper versions for releases & changelog2024-03-09T00:41:19ZSébastien BlinAdd proper versions for releases & changeloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1352[Windows 10] Jami will still be visible as a tray icon if you cancle a file t...2023-10-10T15:27:12ZElys[Windows 10] Jami will still be visible as a tray icon if you cancle a file transfer using the quit programm optionUsing the newest beta versions of Jami
might be Multi-Device related?
Not sure if you can reproduce?
Steps to reproduce:
1. In the past you made a file transfer (file size 95,75 MB) Windows 10 (device 1) -\> Android (device 2) (but y...Using the newest beta versions of Jami
might be Multi-Device related?
Not sure if you can reproduce?
Steps to reproduce:
1. In the past you made a file transfer (file size 95,75 MB) Windows 10 (device 1) -\> Android (device 2) (but you cancled the file transfer because you exit the app?)
2. After a few weeks you open Jami on Windows 10 (device 1) and Android (device2)
3. If you exit Jami on Android and/or Windows 10 the Android version will still show a download notification and although you quit Jami on Windows 10 it will remain visible in the tray icon (you've disabled "Run in background" and disabled "Minimize on Close" and "Launch at startup")
4. Windows 10 might not show the notification anymore if the file has been transfered? But Android still shows the "Downloading" notification
---
Maybe this happens if you are using the same Jami account on multiple devices?
Maybe related: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1385https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1377Issues with the new start screen2023-09-18T15:10:00ZWear GuxjIssues with the new start screenSome remarks on the new start screen that displays recent conversations. This is mainly so you can collect opinions and take into account. But at least one issue is a bug that needs to be fixed.
1. I think the former design was better, ...Some remarks on the new start screen that displays recent conversations. This is mainly so you can collect opinions and take into account. But at least one issue is a bug that needs to be fixed.
1. I think the former design was better, because then you could read the name of the selected account. Now, you're required to recognize the picture in order to know which account is selected.
2. The search action now appears too promoted IMHO. It demands a lot of space, suggesting that it's something frequently used, which I'm not so sure about.
3. The search bar behaves a bit weird when focused, it's supposed to feel like a zoom-in, but the impressions is as if it's a button that when clicked
takes you to another screen.
4. Since the three dots icon is located inside the search entry, it suggests that it holds options specific to the searching. But actually it holds the main menu for the whole app. This is confusing.
5. For no reason, the screen is now always scrollable despite having only a few items in the list. When scrolling, the top components too will move out of visibility.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1374Incorrect preview in conference2023-09-15T14:09:37ZSébastien BlinIncorrect preview in conference# Scenario
+ Alice (Desktop) calls Bob (Desktop)
+ Carla (Android) is added to the conference by Alice
# Expected result
Carla's video tile should show Carla
# Current result
Carla's video tile is empty.# Scenario
+ Alice (Desktop) calls Bob (Desktop)
+ Carla (Android) is added to the conference by Alice
# Expected result
Carla's video tile should show Carla
# Current result
Carla's video tile is empty.https://git.jami.net/savoirfairelinux/dhtnet/-/issues/5MultiplexedSocket: logger_ is always nullptr2024-03-09T00:41:19ZSébastien BlinMultiplexedSocket: logger_ is always nullptrNever passed to the constructorNever passed to the constructorhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1336Keyboard Shortcut Table with small screen2023-09-13T13:15:06ZovariKeyboard Shortcut Table with small screen1. Labels are outside of the buttons for sections
1. Should the padding to the left and right of the keyboard shortcuts be removed?
![image](/uploads/71aa502e502fd88fe71b8b32a1f8a02d/image.png)
Thank you
Linux Mint 21.2 Cinnamon<br>
J...1. Labels are outside of the buttons for sections
1. Should the padding to the left and right of the keyboard shortcuts be removed?
![image](/uploads/71aa502e502fd88fe71b8b32a1f8a02d/image.png)
Thank you
Linux Mint 21.2 Cinnamon<br>
Jami Version: 202309121613https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1371Disable block yourself2023-09-13T07:24:07ZPierre NicolasDisable block yourself![Screen_recording_20230912_163934.mp4](/uploads/4981aea24327eea37dfea304e8548c0c/Screen_recording_20230912_163934.mp4)![Screen_recording_20230912_163934.mp4](/uploads/4981aea24327eea37dfea304e8548c0c/Screen_recording_20230912_163934.mp4)https://git.jami.net/savoirfairelinux/jami-client-uwp/-/issues/26after window resize/minimize during call, jami window won't start/show any more2023-09-12T20:25:54ZAlexandre Olivaafter window resize/minimize during call, jami window won't start/show any moreI'm interacting with a non-technical remote Jami-on-MS-Windows user.
During a video call, they clicked on some button to resize or minimize the window, to find something in the browser that they wanted to show me. The call ended, the J...I'm interacting with a non-technical remote Jami-on-MS-Windows user.
During a video call, they clicked on some button to resize or minimize the window, to find something in the browser that they wanted to show me. The call ended, the Jami window disappeared, and it wouldn't come back.
From then on, the Jami window wouldn't open any more. They'd still get notifications about messages I sent, but attempting to open Jami, it would very quickly show the frame of the window, and then it would disappear right away.
They even tried restarting the computer, uninstalling and reinstalling the latest version of Jami from the web site, and it still failed to open (but notifications of messages would still appear).
I have zero experience with MS-Windows, I suppose some too-small window size setting got in effect, got Jami to half-close and, upon restart, restore that too-small size and again half-crash. Another theory is just that it's minimized, and coming back, and they don't know where to look to un-minimize it.
They haven't been using Jami for very long, they're non-technical, they don't know much about Windows either, and we're both baffled and unsure how to recover their ability to use Jami. Any thoughts or ideas of what to recommend them to try to make Jami work again for them?
Thanks in advance,https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1370Should not display color and emoji customisation for contact request2023-09-12T17:59:08ZPierre NicolasShould not display color and emoji customisation for contact requestAnd should load value by default.
![Screen_recording_20230912_135740.mp4](/uploads/4b19069a50aba8e4cb35f2d192a9a748/Screen_recording_20230912_135740.mp4)And should load value by default.
![Screen_recording_20230912_135740.mp4](/uploads/4b19069a50aba8e4cb35f2d192a9a748/Screen_recording_20230912_135740.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1369Should not display "link a new device" for Jams account2023-09-12T17:55:11ZPierre NicolasShould not display "link a new device" for Jams accountShould not propose the option since it will not work
![Screen_recording_20230912_135246.mp4](/uploads/0eace962956e8bb11d2600f379378fc8/Screen_recording_20230912_135246.mp4)Should not propose the option since it will not work
![Screen_recording_20230912_135246.mp4](/uploads/0eace962956e8bb11d2600f379378fc8/Screen_recording_20230912_135246.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1367Improve smartlist2023-09-12T17:33:30ZPierre NicolasImprove smartlistMeta ticket, create here what you need to be improvedMeta ticket, create here what you need to be improvedhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/300Impossible to play voice message2023-09-19T14:29:15ZPierre NicolasImpossible to play voice messageI didn't test it but user says voice message cannot be played on ios device.
Needs to determine **if bug is reproducible** and if yes, i**f it's android or ios related**.
![image.png](/uploads/0567eb92b33775ec5191c3dac0c5853a/image.png)I didn't test it but user says voice message cannot be played on ios device.
Needs to determine **if bug is reproducible** and if yes, i**f it's android or ios related**.
![image.png](/uploads/0567eb92b33775ec5191c3dac0c5853a/image.png)https://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/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-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-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/1358It is recommended to mark unread messages2023-09-05T15:20:47Zsession 21It is recommended to mark unread messagesI suggest marking unread messages on the device to alert users to the presence of unread messages.
Jami always has issues such as inconsistent online time or inconsistent network environment. This can lead to inevitable delays in the me...I suggest marking unread messages on the device to alert users to the presence of unread messages.
Jami always has issues such as inconsistent online time or inconsistent network environment. This can lead to inevitable delays in the message.
When there are too many messages, it is easy for users to miss some important messages. Therefore, I suggest highlighting unread messages and setting icons to alert users to the presence of unread letters.
At the same time, I suggest labeling unsent messages as it can remind us whether the messages have been sent, so that we can better adjust our network status to help Jami make remote connections.
**Sometimes, even though it shows that a friend is online and he is indeed online. But the message cannot be sent.**(Yes, I often encounter situations like this)
And it may be possible to successfully communicate with friends by simply restarting or bringing Jami back online, but this requires a clearer signal of 'message not sent'.
I think the current UI cannot help users check whether their messages have been successfully sent, which leads us to expect an impossible response because the message sending failed.
Thank you for reading.