savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-09-13T13:41:42Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1293Linux Kubuntu 0B updates hanging for ever2021-09-13T13:41:42ZJazLinux Kubuntu 0B updates hanging for everAn update for Jami libqt-jami came over a month ago saying update to version 5.15.2-1
however the update is 0 B and does not update, always staying in the list of discover updates
Today 28 August 2021 another Jami update was added to th...An update for Jami libqt-jami came over a month ago saying update to version 5.15.2-1
however the update is 0 B and does not update, always staying in the list of discover updates
Today 28 August 2021 another Jami update was added to the list with 0 B
update to version 20210825.1.000a1f6-dfsg1-1
Peculiar things about this one is that it appears twice in the list of updates and does not update as I suppose it is 0 B
![Screenshot_20210828_130025](/uploads/bf8f6f1e59646048a584a400de7f768c/Screenshot_20210828_130025.png)
------------------------
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8 (built against 5.12.5)
Kernel Version: 5.4.0-81-generic
OS Type: 64-bit
Discover 5.18.5https://git.jami.net/savoirfairelinux/jami-project/-/issues/1292Voice changer2021-08-28T12:39:04ZDavid HedlundVoice changerAn option to switch on and off a voice changer, also during calls, would be useful.
Originally posted at https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/20An option to switch on and off a voice changer, also during calls, would be useful.
Originally posted at https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/20https://git.jami.net/savoirfairelinux/jami-plugins/-/issues/20Voice changer2021-08-28T12:58:05ZDavid HedlundVoice changerWho wouldn't like to have voice changer option?Who wouldn't like to have voice changer option?https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/618ICE/PJNATH - assertion failure in start_nominated_check()2023-02-06T20:56:58ZMohamed ChibaniICE/PJNATH - assertion failure in start_nominated_check()Assertion failure in start_nominated_check() method:
```
2890 pj_assert(c->err_code == PJ_SUCCESS);
```
err_code is PJ_EPENDING instead of PJ_SUCCESS. \
Seen with TCP connections.Assertion failure in start_nominated_check() method:
```
2890 pj_assert(c->err_code == PJ_SUCCESS);
```
err_code is PJ_EPENDING instead of PJ_SUCCESS. \
Seen with TCP connections.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/989F-Droid build failed2021-12-17T18:48:43ZlinsuiF-Droid build failedhttps://monitor.f-droid.org/builds/log/cx.ring/314
```
Git checkout of 'android/release_314' failed
==== detail begin ====
error: pathspec 'android/release_314' did not match any file(s) known to git
==== detail end ====
```
https://mo...https://monitor.f-droid.org/builds/log/cx.ring/314
```
Git checkout of 'android/release_314' failed
==== detail begin ====
error: pathspec 'android/release_314' did not match any file(s) known to git
==== detail end ====
```
https://monitor.f-droid.org/builds/log/cx.ring/316
```
Git checkout of 'android/release_316' failed
==== detail begin ====
error: pathspec 'android/release_316' did not match any file(s) known to git
==== detail end ====
```
Could you please take a look? Thanks!https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/617ICE - resort the check list after adding prflx candidates2021-09-30T21:08:46ZMohamed ChibaniICE - resort the check list after adding prflx candidatesThe check list is not sorted after adding new prflx candidates, which can cause the nomination of candidates pairs with less priority. \
See https://github.com/pjsip/pjproject/pull/2806
[EDIT]
The patch was reverted until issue https://...The check list is not sorted after adding new prflx candidates, which can cause the nomination of candidates pairs with less priority. \
See https://github.com/pjsip/pjproject/pull/2806
[EDIT]
The patch was reverted until issue https://git.jami.net/savoirfairelinux/ring-daemon/-/issues/627 is resolvedMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1291Probably wrong online status and messages never delivered to a contact2023-04-07T20:04:52ZArtiom-MProbably wrong online status and messages never delivered to a contactI have a contact in my list and we can exchange messages while both online. Contact's client is Android, I have both Android and desktop clients and both has the same problem: I see that contact as online but messages are not delivered. ...I have a contact in my list and we can exchange messages while both online. Contact's client is Android, I have both Android and desktop clients and both has the same problem: I see that contact as online but messages are not delivered. Never.
I would suspect that the client is killed by android and not really connected.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1290Daemon submodule Update Fails2021-09-17T17:22:57ZBrightson JupiriDaemon submodule Update Failshi Jami,
I'm compiling for the client-qt for Windows
was trying to update submodule "git submodule update --init daemon lrc client-qt"
but got error,
**error: no such remote ref d1aa79d02af606861b1bf9029cb31645e059b079
Fetched in sub...hi Jami,
I'm compiling for the client-qt for Windows
was trying to update submodule "git submodule update --init daemon lrc client-qt"
but got error,
**error: no such remote ref d1aa79d02af606861b1bf9029cb31645e059b079
Fetched in submodule path 'daemon', but it did not contain d1aa79d02af606861b1bf9029cb31645e059b079. Direct fetching of that commit failed.**
Tried this on Android/release_316 and the Master, both produce the same problem
kindly Assist on this, Thank you :smile:https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/616ICE/TURN - assertion failure in PJNATH2021-12-29T17:10:58ZMohamed ChibaniICE/TURN - assertion failure in PJNATHAssertion failure in pjnath (pj_assert) when calling pj_ice_strans_init_ice. See back trace in the comments. The error seems to be caused by a failure of TURN allocation. \
Note that the assertion is only enabled in debug mode. In releas...Assertion failure in pjnath (pj_assert) when calling pj_ice_strans_init_ice. See back trace in the comments. The error seems to be caused by a failure of TURN allocation. \
Note that the assertion is only enabled in debug mode. In release mode, the error might not be noticeable, ICE session will succeed/fail depending on the other candidates of the impacted component. \
Might be related to https://github.com/pjsip/pjproject/pull/2525Backloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/506Call ends when changing internet source2021-09-26T08:01:00ZovariCall ends when changing internet source# Jami offline when there are 2 concurrent internet sources and 1 is removed
1. Connected to the internet via USB tethering to an Android 10 device (mobile internet)
2. Plug in Ethernet to connect to a fixed-line internet connection (th...# Jami offline when there are 2 concurrent internet sources and 1 is removed
1. Connected to the internet via USB tethering to an Android 10 device (mobile internet)
2. Plug in Ethernet to connect to a fixed-line internet connection (the computer now has 2 different concurrent internet connections)
3. Unplug the Ethernet connection and Jami is Offline, even though the mobile internet is available. Writing this bug report using only the mobile internet connect while Jami is showing itself as offline.
![image](/uploads/e3e1c0adcca1337019d0115aaf1d4d42/image.png)
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt Version: 202108172029https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/615UPNP - IGD search must restarted if a connectivity check is received and ther...2021-09-02T15:00:10ZMohamed ChibaniUPNP - IGD search must restarted if a connectivity check is received and there is no valid IGDMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/988Push notification will not show at the beginning when the device is restarted2021-08-24T07:19:05ZMing Rui ZhangPush notification will not show at the beginning when the device is restartedWhen the device is restarted, there will be for sure no Jami running in the background.
At this time, when a push notification is received, Jami will wake up from the debugging log and
messages, calls will be received and handled correc...When the device is restarted, there will be for sure no Jami running in the background.
At this time, when a push notification is received, Jami will wake up from the debugging log and
messages, calls will be received and handled correctly.
But, there will be no system notification being showed unless the contact keeps sending or calling (until ```bootstrapDaemon``` is called again).
Current speculations:
1. When the client is started normally, the ```ConversationFacade``` instance will be created which is in charge of
notifications' build.
```
2021-08-23 12:22:52.434 17572-17572/cx.ring D/DERP: init conv facade
java.lang.RuntimeException
at net.jami.services.ConversationFacade.<init>(ConversationFacade.kt:631)
at cx.ring.dependencyinjection.ServiceInjectionModule.provideConversationFacade(ServiceInjectionModule.kt:140)
at cx.ring.dependencyinjection.ServiceInjectionModule_ProvideConversationFacadeFactory.provideConversationFacade(ServiceInjectionModule_ProvideConversationFacadeFactory.java:78)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC.conversationFacade(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:285)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC.access$3800(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:200)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$SwitchingProvider.get(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1569)
at dagger.internal.DoubleCheck.get(DoubleCheck.java:47)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$ActivityCImpl.injectHomeActivity2(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1339)
at cx.ring.application.DaggerJamiApplicationFirebase_HiltComponents_SingletonC$ActivityCImpl.injectHomeActivity(DaggerJamiApplicationFirebase_HiltComponents_SingletonC.java:1242)
at cx.ring.client.Hilt_HomeActivity.inject(Hilt_HomeActivity.java:67)
at cx.ring.client.Hilt_HomeActivity$1.onContextAvailable(Hilt_HomeActivity.java:38)
at androidx.activity.contextaware.ContextAwareHelper.dispatchOnContextAvailable(ContextAwareHelper.java:99)
at androidx.activity.ComponentActivity.onCreate(ComponentActivity.java:322)
at androidx.fragment.app.FragmentActivity.onCreate(FragmentActivity.java:273)
at cx.ring.client.HomeActivity.onCreate(HomeActivity.kt:132)
at android.app.Activity.performCreate(Activity.java:7183)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1220)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2910)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3032)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1696)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
```
2. When the application wakes up by push notification, no instance of ```ConversationFacade``` will be created. Therefore,
there will be no subscription to create notifications on the representation level.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/505Corrupted ~/.cache/Jami/qmlcache leads to application crashing (Qt)2021-08-23T19:15:07ZMaxim CournoyerCorrupted ~/.cache/Jami/qmlcache leads to application crashing (Qt)## Describe your environment
Please specify the following:
- OS: GNU/Linux
- Jami version: any recent jami-qt client
- What build you are using: Guix
## Steps to reproduce
Not sure how to trigger the cache corruption, it seems to com...## Describe your environment
Please specify the following:
- OS: GNU/Linux
- Jami version: any recent jami-qt client
- What build you are using: Guix
## Steps to reproduce
Not sure how to trigger the cache corruption, it seems to come from changes from the C++ code base and or Qt. When the condition occurs, it crashes consistenly.
- Can you reproduce the bug: at will
- Steps:
1. get the qmlcache into a corrupted state (repro unknown)
2. try launching jami-qt
- Actual result:
Qt crashes.
- Expected result:
No crash, Jami runs.
## Workaround:
`rm -rf ~/.cache/Jami/qmlcache`
We need to come up with safeguards against this serious problem. There are hints as to how to go about it at the end of https://bugreports.qt.io/browse/QTBUG-85967?jql=text%20~%20%22qmlcache%20crash%22:
> Qt does not analyze all your properties to see if anything you use in QML changed in C++. That would be quite difficult. Incrementing the import versions should indeed help as that would also force you to change the QML code in order to import the new version. This, in turn, triggers a cache invalidation via a checksum mismatch on the QML code.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/504Build error glib.h not found2021-08-30T15:07:12ZFuchtelJockelBuild error glib.h not foundI'm trying to build jami-qt with flatpak but get the glib.h not found error. I added the following to the CMakeLists.txt:
```diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index ec83cb5..888ae6b 100644
--- a/CMakeLists.txt
+++ b/CMake...I'm trying to build jami-qt with flatpak but get the glib.h not found error. I added the following to the CMakeLists.txt:
```diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index ec83cb5..888ae6b 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -242,6 +242,12 @@ else()
find_package(PkgConfig REQUIRED)
+ pkg_check_modules(GLIB REQUIRED glib-2.0)
+ if(GLIB_FOUND)
+ add_definitions(${GLIB_CFLAGS_OTHER})
+ message(${GLIB_CFLAGS_OTHER})
+ endif()
+
pkg_check_modules(LIBNM libnm)
if(LIBNM_FOUND)
add_definitions(-DUSE_LIBNM)
@@ -294,7 +300,8 @@ else()
include_directories(${LRC_SRC_PATH}
${LIBNM_INCLUDE_DIRS}
${LIBNOTIFY_INCLUDE_DIRS}
- ${LIBGDKPIXBUF_INCLUDE_DIRS})
+ ${LIBGDKPIXBUF_INCLUDE_DIRS}
+ ${GLIB_INCLUDE_DIRS})
set(JAMI_DATA_PREFIX "${CMAKE_INSTALL_PREFIX}/share")
@@ -419,7 +426,8 @@ else()
${X11}
${LIBNM_LIBRARIES}
${LIBNOTIFY_LIBRARIES}
- ${LIBGDKPIXBUF_LIBRARIES})
+ ${LIBGDKPIXBUF_LIBRARIES}
+ ${GLIB_LIBRARIES})
# Installation rules
install(TARGETS jami-qt
```
This fixes the not found error but results in a new error:
```
/run/build/jami-qt/src/connectivitymonitor.cpp: In constructor ‘ConnectivityMonitor::ConnectivityMonitor(QObject*)’:
/run/build/jami-qt/src/connectivitymonitor.cpp:224:5: error: ‘GCancellable’ was not declared in this scope
224 | GCancellable * cancellable = g_cancellable_new();
| ^~~~~~~~~~~~
/run/build/jami-qt/src/connectivitymonitor.cpp:224:20: error: ‘cancellable’ was not declared in this scope
224 | GCancellable * cancellable = g_cancellable_new();
| ^~~~~~~~~~~
/run/build/jami-qt/src/connectivitymonitor.cpp:224:34: error: ‘g_cancellable_new’ was not declared in this scope
224 | GCancellable * cancellable = g_cancellable_new();
| ^~~~~~~~~~~~~~~~~
```
This is where my abilities are at an end.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/987SIP configuration options need explanation2022-11-11T16:33:23ZWarthog-CapitalSIP configuration options need explanationTo an SIP newcomer like me, the configuration options in the Jami app are very unclear. Specifically, entries that leave me wondering are:
- Advanced / Enable UPnP. I thought SIP is a client-server protocol, why would it need to open po...To an SIP newcomer like me, the configuration options in the Jami app are very unclear. Specifically, entries that leave me wondering are:
- Advanced / Enable UPnP. I thought SIP is a client-server protocol, why would it need to open ports?
- Advanced / Use DHT proxy. Similar question. In which way is DHT involved in SIP?
- Advanced / Use Stun/TURN. What is the effect of enabling these options?
- Security / Add credentials. Currently contains my password, and "*". What does the * mean? How can a SIP account possibly have multiple credentials?
- Security / Encrypt media streams (SRTP). Encryption sounds good, why is it disabled by default? Does it require server support, or client support on the other end (end-to-end)? What happens if my server or a caller do not support SRTP?
- Security / Enable SDES as key exchange protocol. What are the pros and cons of setting this option?
- Security / Use TLS Transport. Transport encryption should be standard on any protocol nowadays, why is this disabled by default?
- Security / Certification authorities, certificate file and private key file have a red exclamation mark, indicating that some action must be taken. But they are greyed out. What is the issue here? If this is related to TLS, why can it not use the system-wide certificate store for authentication?
- Security / TLS method: TLSv1. TLS version 1 is deprecated and should not be used. Why is this the default? TLSv1.3 is not even an option here, apparently?
- Security / TLS ciphers. Just opens a text field. What is the user supposed to put in here?
- Server name. I would assume that this is the domain name configured for the SIP account (user@domain). What does this option mean?
- Security / Verify server/client. What is the effect of these options?
- Security / TLS require client certificate. (default: on) What is the effect of this option?
My main reason for using SIP is having encrypted telephony. Based on these presented options, I have no idea whether my settings are secure and whether my voice calls are encrypted or not.
In particular, my provider Sipgate.de apparently does not support SRTP (https://basicsupport.sipgate.de/hc/de/articles/207246495-Ist-eine-SRTP-TLS-Sprachverschl%C3%BCsselung-m%C3%B6glich-), so does this mean that SRTP is involved in client-to-server communication, not end-to-end? Confusingly, if I enable SRTP in the options above, my connection is still shown as "online", so something seems to work.
Configuration options that I am missing are:
- ZRTP. Is ZRTP supported? Based on my research, this one is definitely end-to-end.
- Configuring a display name. Other SIP clients offered me to set up a display name, but this does not seem to be an option for SIP accounts in Jami.
Clarification would be appreciated! :)Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/614video configuration issue causes crashes2022-07-05T18:05:27ZFuchtelJockelvideo configuration issue causes crashesFor some reason the dring.yml gets set to:
```yml
video:
decodingAccelerated: true
encodingAccelerated: false
```
Jami will crash if set so when using the webcam.
setting it to:
```yml
video:
decodingAccelerated: true
encodingAc...For some reason the dring.yml gets set to:
```yml
video:
decodingAccelerated: true
encodingAccelerated: false
```
Jami will crash if set so when using the webcam.
setting it to:
```yml
video:
decodingAccelerated: true
encodingAccelerated: true
```
will prevent the crashhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/488emoji.css missing from CMakeLists.txt2021-08-24T10:33:58ZFuchtelJockelemoji.css missing from CMakeLists.txtThis is needed to build the gnome client.
```diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 29b9f1c2..a981ba01 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -384,6 +384,7 @@ SET(libringclient_WEB_chatview
src/web-chatv...This is needed to build the gnome client.
```diff
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 29b9f1c2..a981ba01 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -384,6 +384,7 @@ SET(libringclient_WEB_chatview
src/web-chatview/chatview.js
src/web-chatview/jed.js
src/web-chatview/emoji.js
+ src/web-chatview/emoji.css
src/web-chatview/linkify-html.js
src/web-chatview/linkify-string.js
src/web-chatview/linkify.js
```https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1272FreeBSD support2021-08-24T15:38:41ZxliivFreeBSD supportI'd like to run Jami on FreeBSD.
According to Wiki it's possible
![image](/uploads/bae1349616ee16602f2f5341cc8a3d41/image.png)
However, i think it refers the old version (thanks to jbeich from Discord for finding it out)
1. https://en...I'd like to run Jami on FreeBSD.
According to Wiki it's possible
![image](/uploads/bae1349616ee16602f2f5341cc8a3d41/image.png)
However, i think it refers the old version (thanks to jbeich from Discord for finding it out)
1. https://en.wikipedia.org/w/index.php?title=Jami_%28software%29&diff=prev&oldid=720506711
1. https://www.freshports.org/net-im/ring-gnomehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/503Rename device2021-09-26T07:43:27ZovariRename deviceOn Android, the device can be renamed in the Account Profile. `This device` field has a pen which can be tapped to change the name of the device.
1. Can the `This device` field also be shown on GNU/Linux client-qt?
2. How can the name ...On Android, the device can be renamed in the Account Profile. `This device` field has a pen which can be tapped to change the name of the device.
1. Can the `This device` field also be shown on GNU/Linux client-qt?
2. How can the name of the device be changed using the GUI on GNU/Linux client-qt?
3. <s>Updating the name of the `This device` field on an Android device, doesn't seem to update the name shown on linked GNU/Linux client-qt and another client-android device. How long does it take to update?</s> Renamed it again and now it worked
4. In the `This device` field, can the device ID please also be shown like they are shown in the linked devices?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt 202108172029https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/502Unable to revoke a device/remove a device from the list of linked devices2021-09-07T18:01:36ZovariUnable to revoke a device/remove a device from the list of linked devicesUnable to revoke a device.
client-android shows a message with title `Can't revoke device` with message `Unknown device.`
If the device is unknown, how can the device be removed from the list?
client-qt does not revoke the device and ...Unable to revoke a device.
client-android shows a message with title `Can't revoke device` with message `Unknown device.`
If the device is unknown, how can the device be removed from the list?
client-qt does not revoke the device and provides no feedback.
Can client-qt please show a message if it was unable to revoke a device like Android does?
Please advise if you need a screenshot from the Android device.
Thank you
client-andriod 20210812-01
Linux Mint 20.2 Cinnamon<br>
client-qt 202108172029