savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-01-14T17:36:43Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1280Crashes with webkitgtk 2.34.1 built with libsoup3 (webkitgtk-2.34.1/lib/libwe...2022-01-14T17:36:43ZMaxim CournoyerCrashes with webkitgtk 2.34.1 built with libsoup3 (webkitgtk-2.34.1/lib/libwebkit2gtk-4.1.so.0)Using the stable version of Jami on the core-updates-frozen branch of Guix, which has more bleeding edge dependencies such as webkitgtk 2.34.1 built with libsoup, I get frequent crashes in webkitgtk.
Here's an example:
```
(gdb) bt
#0 ...Using the stable version of Jami on the core-updates-frozen branch of Guix, which has more bleeding edge dependencies such as webkitgtk 2.34.1 built with libsoup, I get frequent crashes in webkitgtk.
Here's an example:
```
(gdb) bt
#0 0x00007ffff7004969 in g_type_check_instance ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libgobject-2.0.so.0
#1 0x00007ffff6ffb66c in g_signal_emit_valist ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libgobject-2.0.so.0
#2 0x00007ffff6ffc732 in g_signal_emit ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libgobject-2.0.so.0
#3 0x00007ffff34848b6 in webkitWebViewWebProcessTerminated(_WebKitWebView*, WebKitWebProcessTerminationReason) () from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libwebkit2gtk-4.1.so.0
#4 0x00007ffff345bfeb in NavigationClient::processDidTerminate(WebKit::WebPageProxy&, WebKit::ProcessTerminationReason) ()
from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libwebkit2gtk-4.1.so.0
#5 0x00007ffff33c066e in WebKit::WebPageProxy::dispatchProcessDidTerminate(WebKit::ProcessTerminationReason) () from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libwebkit2gtk-4.1.so.0
#6 0x00007ffff33efe80 in WebKit::WebProcessProxy::processDidTerminateOrFailedToLaunch(WebKit::ProcessTerminationReason) ()
from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libwebkit2gtk-4.1.so.0
#7 0x00007ffff32cc3bb in WTF::Detail::CallableWrapper<IPC::Connection::connectionDidClose()::{lambda()#1}, void>::call() ()
from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libwebkit2gtk-4.1.so.0
#8 0x00007ffff24a7c12 in WTF::RunLoop::performWork() ()
from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libjavascriptcoregtk-4.1.so.0
#9 0x00007ffff2507999 in WTF::RunLoop::RunLoop()::{lambda(void*)#1}::_FUN(void*) ()
from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libjavascriptcoregtk-4.1.so.0
#10 0x00007ffff250833f in WTF::RunLoop::{lambda(_GSource*, int (*)(void*), void*)#1}::_FUN(_GSource*, int (*)(void*), void*) ()
from /gnu/store/7ffjxkqfi3d5mm2scji5v1gy448lfcml-webkitgtk-2.34.1/lib/libjavascriptcoregtk-4.1.so.0
#11 0x00007ffff6ef036f in g_main_context_dispatch ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libglib-2.0.so.0
#12 0x00007ffff6ef06e8 in g_main_context_iterate.constprop ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libglib-2.0.so.0
#13 0x00007ffff6ef078f in g_main_context_iteration ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libglib-2.0.so.0
#14 0x00007ffff710d4c5 in g_application_run ()
from /gnu/store/qqs98rxwjrji6aaf6dqwp7q4m545g2sn-glib-2.70.0/lib/libgio-2.0.so.0
#15 0x000000000047a727 in main ()
```
Attached is the same backtrace but applied to all threads:
[gdb.txt](/uploads/156d8ceab5afa6de32dc717966c9955f/gdb.txt)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/597API and "tel:" url2021-11-26T01:58:29ZDeeAPI and "tel:" urlHi
1. Is there a way to control yami over a API? To make a call or set settings?
2. Is there a way to use the "tel:XXXX" urls with jami?
GreetingsHi
1. Is there a way to control yami over a API? To make a call or set settings?
2. Is there a way to use the "tel:XXXX" urls with jami?
Greetingshttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/596Flatpak2021-11-19T15:18:14ZgiovannicaligarisFlatpakIs possible to create a flatpak for arm64 and host it on flathub? That way it can be used on linux mobile devices.Is possible to create a flatpak for arm64 and host it on flathub? That way it can be used on linux mobile devices.https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/112Correct nightly at dl.jami.net?2021-12-01T23:04:47ZovariCorrect nightly at dl.jami.net?The [Changelog](https://git.jami.net/savoirfairelinux/jami-client-gnome/-/wikis/Changelog) shows [Nightly 4 Nov](https://git.jami.net/savoirfairelinux/jami-client-gnome/-/wikis/Changelog#nightly-4-nov), [Nightly 8 Nov](https://git.jami.n...The [Changelog](https://git.jami.net/savoirfairelinux/jami-client-gnome/-/wikis/Changelog) shows [Nightly 4 Nov](https://git.jami.net/savoirfairelinux/jami-client-gnome/-/wikis/Changelog#nightly-4-nov), [Nightly 8 Nov](https://git.jami.net/savoirfairelinux/jami-client-gnome/-/wikis/Changelog#nightly-8-nov) and [Nightly 15 Nov](https://git.jami.net/savoirfairelinux/jami-client-gnome/-/wikis/Changelog#nightly-15-nov).
Jami with a GNU/Linux device has `Version: 202111041938`.
https://dl.jami.net/nightly/ubuntu_20.04/pool/main/j/jami/jami-all_20211104.1.db096e2~dfsg1-1_amd64.deb also shows the Nightly 4 Nov version.
https://dl.jami.net/internal/ubuntu_20.04/pool/main/j/jami/jami-all_20211022.2.873c35f~dfsg1-1_amd64.deb shows an older version.
Is this correct? Maybe the newer versions are internal version?
Thank youhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/669videoInput: calling self lock daemon2022-12-06T18:16:32ZSébastien BlinvideoInput: calling self lock daemon# Scenario
Account A call account B on same device (in auto answer)
# Expected
It should not block
# Current result
Blocked
cc @aberaud# Scenario
Account A call account B on same device (in auto answer)
# Expected
It should not block
# Current result
Blocked
cc @aberaudOlivier DionSébastien BlinOlivier Dionhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/668SIPCall: heap-use-after-free in inv_session_destroy2022-05-06T15:32:34ZOlivier DionSIPCall: heap-use-after-free in inv_session_destroyCommit: 0d1a7ab224a8d47642fc447d1237e5a275dafb57
Agent: [spam.scm](/uploads/801c1146617db4f37435fb9e4da3cdc9/test.scm)
ASAN report + gdb backtrace + Jami's log: [details.tgz](/uploads/8ce0f4b1fdb9047b88c34f75e79e43f1/details.tgz)
The ...Commit: 0d1a7ab224a8d47642fc447d1237e5a275dafb57
Agent: [spam.scm](/uploads/801c1146617db4f37435fb9e4da3cdc9/test.scm)
ASAN report + gdb backtrace + Jami's log: [details.tgz](/uploads/8ce0f4b1fdb9047b88c34f75e79e43f1/details.tgz)
The issue seems to be related when `icest_` fails to be initialized in `ice_transport.cpp`. Grep for `destroying (nil)` in Jami's log.BacklogSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1279request color emoticons in gtk environment2021-11-16T14:52:27Zhigol higolrequest color emoticons in gtk environmentin my xubuntu 21.10 and earlier in 21.04, black and white emoticons are poorly visible :( please make them colored, as in telegram, for example ;) ![IMG_20211116_144412](/uploads/907a953c3db66663ba3fdf2380bb5340/IMG_20211116_144412.jpg)!...in my xubuntu 21.10 and earlier in 21.04, black and white emoticons are poorly visible :( please make them colored, as in telegram, for example ;) ![IMG_20211116_144412](/uploads/907a953c3db66663ba3fdf2380bb5340/IMG_20211116_144412.jpg)![Снимок_экрана_2021-11-16_15-38-56](/uploads/e4e1fe9a42d28701e22e9f82848930c8/Снимок_экрана_2021-11-16_15-38-56.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1039In light mode, the record audio clip Icon in a conversation is invisible2021-12-15T19:04:28ZAltonsIn light mode, the record audio clip Icon in a conversation is invisible## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1
- What build you are using: F-droid
## Steps to reproduce
- Can you r...## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami (in light mode)
2. Open a conversation
2. tap on the tree points to send a specific message type
- Actual result: the record audio clip in a conversation is invisible
- Expected result: The icon should appear.
## Additional information
![image](/uploads/65e7e39c72a4c046d06db4e7582a09bb/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1038Plus sign in Link a new device doesn't appear (in light and dark mode)2023-04-07T20:19:22ZAltonsPlus sign in Link a new device doesn't appear (in light and dark mode)## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1
- What build you are using: F-droid
## Steps to reproduce
- Can you r...## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Go to the account settings (bottom right button)
3. Scroll down to "Link a new device"
- Actual result: Plus sign in Link a new device doesn't appear (in light and dark mode)
- Expected result: The plus sign should appear.
## Additional information
![image](/uploads/df83e79ab5b42e577e4f18e54925aef4/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1036Blurry profile picture (of the own account) in settings (eg. the T for Test i...2022-12-05T18:51:15ZAltonsBlurry profile picture (of the own account) in settings (eg. the T for Test is blurry)## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1
- What build you are using: F-droid
## Steps to reproduce
- Can you r...## Describe your environment
Please specify the following:
- Ring version: 20210924-01
- Device model: Samsung galaxy core prime
- Android version: 5.0.1
- What build you are using: F-droid
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Go to the account settings (bottom right button)
- Actual result: Blurry profile picture (of the own account) in settings (eg. the T for Test is blurry)
- Expected result: The profile picture should not be blurry.
## Additional information
![image](/uploads/1dd45702cbdfa77f211a1ed2eb6bc104/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/595Windows exe icon weird border2022-07-14T20:06:08ZMing Rui ZhangWindows exe icon weird borderNeed to update ico files to contain multiple sizes
https://docs.microsoft.com/en-us/windows/win32/uxguide/vis-icons?redirectedfrom=MSDNNeed to update ico files to contain multiple sizes
https://docs.microsoft.com/en-us/windows/win32/uxguide/vis-icons?redirectedfrom=MSDNMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1347Issue with Swarm conversation2022-07-11T14:41:27ZAltonsIssue with Swarm conversationMy issue is very strange to describe, but is the fact is, that my conversation had an issue with swarm.
To describe the situation (3 devices and 2 accounts involved):
- Device 1 (Fedora, build from jami.net) with account A
- Device 2 (Ub...My issue is very strange to describe, but is the fact is, that my conversation had an issue with swarm.
To describe the situation (3 devices and 2 accounts involved):
- Device 1 (Fedora, build from jami.net) with account A
- Device 2 (Ubuntu 21.04, older Appmage with first/old swarm "test") with account B
- Device 3 (Android, Fdroid version) with account B
Device 1 and 2 have a conversation.
Then I linked the device 3. All was working right.
Then the device 2 was disconnected and 1 and 3 were having a discussion.
Then device 2 was updated to the latest jami.net build with the ppa and I deleted the appimage. Just after launching jami the account B was already connected.
On device 2 there was a lock near the conversation and I had to renew the "contact" or something like that.
But now the messages from device 2 don't appear anymore and device 1, although I could make a call between them. The message didn't even sync on the device 3.
After a while the messages were updated on device 3 (a popup in the conversation saying "syncing the conversation"). After that all the past conversation was deleted and the new messages from device 2 appeard, but wrongly formated: `😀😃😁😆😅🤣😂🙂🙃😉😊😇🥰😍🤩` appeard as `ߘ0ߘðߘpߘưߘŰߤ㰟ߙ°`
After that I got a contact request from device 2 to device 3 (a conversation of account B with itself) that was autogenerated.
Sorry for my very bad explanation, I hope this experience can be helpful for debugging. (when I mean device, it means a certain instance of an account on a device(with a jami-client)).https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/667jami-daemon crashes while performing tls handshake2021-11-17T22:34:36ZFuchtelJockeljami-daemon crashes while performing tls handshakeContinuation from issue #573
I compiled a lot of different versions of jami-daemon and found the first commit that introduced the tls issues. On this first broken commit the daemon didn't crash but couldn't perform a successful handshak...Continuation from issue #573
I compiled a lot of different versions of jami-daemon and found the first commit that introduced the tls issues. On this first broken commit the daemon didn't crash but couldn't perform a successful handshake.
Log from commit 2053afe9 but the regression likely stems from 6d4630bf:
```
[1636931798.072| 182|tls_session.cpp :1059 ] [TLS] Start client session
[1636931798.080| 182|tls_session.cpp :530 ] [TLS] User identity loaded
[1636931798.080| 182|tls_session.cpp :1155 ] [TLS] handshake
...
[1636931827.631| 85|connectionmanager.cpp:334 ] no response from DHT to E2E request.
...
[1636931838.080| 182|tls_session.cpp :1163 ] [TLS] handshake failed: Die Zeit für den Vorgang wurde überschritten (time out)
[1636931838.081| 182|connectionmanager.cpp:710 ] TLS connection failure for peer 9cba26f5eb24ad71f8842c62ea5c5f2f577ef005326722789a69fc9f77168e3f - Initied by DHT request. Vid: 2958016247017314
```
Commit 2a676123 is first to crash jami-daemon with this error:
```
[1636933396.203| 146|tls_session.cpp :1059 ] [TLS] Start client session
[1636933396.211| 146|tls_session.cpp :530 ] [TLS] User identity loaded
[1636933396.212| 146|tls_session.cpp :1155 ] [TLS] handshake
/usr/include/c++/10.2.0/bits/stl_vector.h:1063: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = jami::IpAddr; _Alloc = std::allocator<jami::IpAddr>; std::vector<_Tp, _Alloc>::const_reference = const jami::IpAddr&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
```
To sum it up:
- 6d4630bf to b98db961 make tls handshakes fail
- 2a676123 and onward make jami-daemon crash
- the last working commit is: 43136e05https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/666Call re-invite - restart media only after successful ICE negotiation2022-01-05T18:21:56ZSébastien BlinCall re-invite - restart media only after successful ICE negotiationIf media transport uses ICE, and when a new media session is negotiated (incoming or outgoing re-invite) the current ICE session must be kept until the new ICE session is successfully negotiated, and the media is stopped and restarted us...If media transport uses ICE, and when a new media session is negotiated (incoming or outgoing re-invite) the current ICE session must be kept until the new ICE session is successfully negotiated, and the media is stopped and restarted using the new ICE session.
If the new session fails, the media transport must continue using the current ICE session.
# Scenario
+ In a call cut video
# Expected
+ the remote video should not be cut and retrieved a few secs after
# Current
During the negotiation remote video/audio is stopped and a glitch is seenMohamed ChibaniMohamed Chibanihttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/153iOS should show record notification from backend2022-10-20T15:38:09ZSébastien BliniOS should show record notification from backend# Scenario
+ Call an iOS
+ Record the call
# Expected
iOS should show that the peer is recording
# Current
no notification shown# Scenario
+ Call an iOS
+ Record the call
# Expected
iOS should show that the peer is recording
# Current
no notification shownBinal AhiyaBinal Ahiyahttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/594Record status is wrong2021-11-15T15:18:36ZSébastien BlinRecord status is wrong# Scenario
+ start call
+ Launch a record
+ Stop a call
+ Start a call
# Expected
Record should be off
# Current
Record is on, even if it's not recording# Scenario
+ start call
+ Launch a record
+ Stop a call
+ Start a call
# Expected
Record should be off
# Current
Record is on, even if it's not recordingSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/152Inconsistency in the account view2023-12-18T16:51:49ZAltonsInconsistency in the account viewWhen clicking on account profile (on top of the conversation view), I land in the "profile" page of the person. But there is an inconsistency, as we only see the registered jami username until we scroll and then only the "Name" assigned ...When clicking on account profile (on top of the conversation view), I land in the "profile" page of the person. But there is an inconsistency, as we only see the registered jami username until we scroll and then only the "Name" assigned to the person appears on the top bar.
We should display the account information as on the top of the conversation with "Name" and under it in a smaller size the jami username.https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/151Date and time format not adapted to the local format2022-09-22T18:41:42ZAltonsDate and time format not adapted to the local formatThe date and time format in the conversation is not in the local format selected on the iDevide.
![image](/uploads/346b25a7225815cb6e6a969fa5d84d2c/image.png)
Here the time in the conversation is in the 12 hours format, but the iDevice...The date and time format in the conversation is not in the local format selected on the iDevide.
![image](/uploads/346b25a7225815cb6e6a969fa5d84d2c/image.png)
Here the time in the conversation is in the 12 hours format, but the iDevice is in 24h format.
This bug just appears in the conversation, and not in the global chats list/overview.Binal AhiyaBinal Ahiyahttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/665swarm: removeContact("self") removes all swarm2021-11-26T15:15:24ZSébastien Blinswarm: removeContact("self") removes all swarm# Scenario
Click on remove contact on a conversation with self => it removes all conv# Scenario
Click on remove contact on a conversation with self => it removes all convSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1278Jami crashes on startup: Unable to initialize the Clutter backend: no availab...2023-05-26T13:59:15ZreubenfirminJami crashes on startup: Unable to initialize the Clutter backend: no available drivers found.This was working last week. This is on Kubuntu 21.10.
--
** Message: 08:04:30.181: Jami GNOME client version: 7695511b3526e91cf98ef0ff5f8fc39a42442982
** Message: 08:04:30.181: git ref: unknown
(jami-gnome:167893): Clutter-CRITICAL **...This was working last week. This is on Kubuntu 21.10.
--
** Message: 08:04:30.181: Jami GNOME client version: 7695511b3526e91cf98ef0ff5f8fc39a42442982
** Message: 08:04:30.181: git ref: unknown
(jami-gnome:167893): Clutter-CRITICAL **: 08:04:30.497: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found.
** (jami-gnome:167893): ERROR **: 08:04:30.497: Could not init clutter : -3
fish: “jami-gnome” terminated by signal SIGTRAP (Trace or breakpoint trap)