jami-project issueshttps://git.jami.net/savoirfairelinux/jami-project/-/issues2022-12-21T17:42:04Zhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1425Multi-Swarm (Jami-Beta; Windows 10 ) -> Swarm (Android) does not work2022-12-21T17:42:04ZElysMulti-Swarm (Jami-Beta; Windows 10 ) -> Swarm (Android) does not workNot sure if this is an issue or not:
using Jami beta version (Windows 10)
Jami beta version (Android)
But sending text messages Multi-Swarm -> Swarm does not work
I created a group (user 1(me),user 2 (second Jami account).
If I use t...Not sure if this is an issue or not:
using Jami beta version (Windows 10)
Jami beta version (Android)
But sending text messages Multi-Swarm -> Swarm does not work
I created a group (user 1(me),user 2 (second Jami account).
If I use the group to send text messages the android user never receives the text message.
However no issues if I don't use the "group chat" function and just send a message to the same user in the contact listhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1389(Swarm <-> Non-Swarm?) Sending text messages and/or attachments never works2022-08-09T15:01:21ZElys(Swarm <-> Non-Swarm?) Sending text messages and/or attachments never worksIt does not only involve attachments but also simple text messages (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1053 )
> does **NEVER** work (even if you add the Non-Swarm Contact (Version 20210521-01; your s...It does not only involve attachments but also simple text messages (See: https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1053 )
> does **NEVER** work (even if you add the Non-Swarm Contact (Version 20210521-01; your same user account) again):
> Jami Android Version 20220121-01 <-> Jami Android Version 20210521-01
> Jami Windows 10 Version 202112221635 <-> Jami Android Version 20210521-01
(Android:) Sometimes you receive an invite to add the same contact (that should receive the text message) again.
But you never get any text message.
EDIT: However, you can make voice and/ or video calls without any problems.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1283Do not add [nightly] repos to sources.list.d2021-08-03T15:22:22ZIaroslav GridinDo not add [nightly] repos to sources.list.dCurrently, jami-all package from https://dl.jami.net/ adds jami's key and repo to sources.list.d. Moreover, if package is installed from "internal" repo, it adds "nightly" still and overwrites the internal sources list. This seems likely...Currently, jami-all package from https://dl.jami.net/ adds jami's key and repo to sources.list.d. Moreover, if package is installed from "internal" repo, it adds "nightly" still and overwrites the internal sources list. This seems likely to cause issues to me and adding repo and key is not necessarily wanted by repository uses.https://git.jami.net/savoirfairelinux/jami-project/-/issues/10013 persons conference call screen disapearing after one participant disconnected2020-06-23T20:50:09ZLarbi Gharib3 persons conference call screen disapearing after one participant disconnected**Environment:**
* **Host participant:** Ubuntu 18.04
* **Invited participant 1:** iOS
* **Invited participant 2:** Android
**Issue steps to reproduce:**
1. Call participant 1 with video
2. Participant 1 accepts call
3. Add participan...**Environment:**
* **Host participant:** Ubuntu 18.04
* **Invited participant 1:** iOS
* **Invited participant 2:** Android
**Issue steps to reproduce:**
1. Call participant 1 with video
2. Participant 1 accepts call
3. Add participant 2 with video
4. Participant 2 accepts call
5. Call begins (15 minutes)
6. Participant 1 leave call
**Expected behavior:**
Conference call falls back to 1 to 1 video call and we can still see each other
**Actual behavior:**
Host participant cannot see the participant 2 and only sees the chat (Tried to click on the conference call [participant 1 contact name] and the participant 2 contact name in the left column call history, same result).
However participant 2 can see host participant as if the call fell back to a 1 to 1 video call.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/919i can't register on a sip server with TCP2022-11-11T16:54:22ZTolminoi can't register on a sip server with TCPi'm on OSX and on IOS and there isn't any way to define to use TCP Sip transporti'm on OSX and on IOS and there isn't any way to define to use TCP Sip transporthttps://git.jami.net/savoirfairelinux/jami-project/-/issues/836Debian to Android2020-03-23T20:46:39ZKitchMDebian to AndroidCall from Android on cellular network to Debian on fiber network allows a text message. However, there is no audio or video available.Call from Android on cellular network to Debian on fiber network allows a text message. However, there is no audio or video available.https://git.jami.net/savoirfairelinux/jami-project/-/issues/474gitlab setup (missing email notifications)2019-03-02T19:32:00ZRing Thinggitlab setup (missing email notifications)I don't get email notifications about the responses to the issue I had created, so maybe something needs to be fixed in the configuration.
Also, apologies for not having filled the bug template, but it is easy to overlook, it's not sele...I don't get email notifications about the responses to the issue I had created, so maybe something needs to be fixed in the configuration.
Also, apologies for not having filled the bug template, but it is easy to overlook, it's not selected by default for ring-client-android. It has to be chosen manually.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/424ring-daemon breaks: no member named 'raw\_chain' in 'pj\_ssl\_cert\_info'2018-05-22T00:46:43ZJami Botring-daemon breaks: no member named 'raw\_chain' in 'pj\_ssl\_cert\_info'Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Getting this in the FreeBSD port.
It also expects a missing symbol PJSIP\_TRANSPORT\_DTLS6.
You provide patches for pjsip. However, it isn'...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Getting this in the FreeBSD port.
It also expects a missing symbol PJSIP\_TRANSPORT\_DTLS6.
You provide patches for pjsip. However, it isn't easy to build pjsip. This is done by its own port. Ring port can't just easily repeat what the other port is doing.
Please merge your patches into the pjsip upstream, so that there will be no need to keep any patches.https://git.jami.net/savoirfairelinux/jami-project/-/issues/387Easier bug reports2018-05-22T00:39:04ZJami BotEasier bug reportsIssue generated from Tuleap's migration script.
**Originally submitted by: Olafur Egilsson (olafure)**
Please consider moving bug reports to github, where all the cool kids are.Issue generated from Tuleap's migration script.
**Originally submitted by: Olafur Egilsson (olafure)**
Please consider moving bug reports to github, where all the cool kids are.https://git.jami.net/savoirfairelinux/jami-project/-/issues/377ring-daemon build fails: can't find PIX\_FMT\_PLANAR and PIX\_FMT\_RGB2018-05-22T00:38:40ZJami Botring-daemon build fails: can't find PIX\_FMT\_PLANAR and PIX\_FMT\_RGBIssue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Build of ring-daemon-2.2.0 on FreeBSD 11 fails:
video\_scaler.cpp:95:28: error: use of undeclared identifier 'PIX\_FMT\_PLANAR'
if (...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
Build of ring-daemon-2.2.0 on FreeBSD 11 fails:
video\_scaler.cpp:95:28: error: use of undeclared identifier 'PIX\_FMT\_PLANAR'
if (not (desc->flags & PIX\_FMT\_PLANAR)
\^
video\_scaler.cpp:96:26: error: use of undeclared identifier 'PIX\_FMT\_RGB'
or desc->flags & PIX\_FMT\_RGB)
\^
These values originate from libav. libav-11.8\_2 has them, but some other version is bundled with the latest ffmpeg-3.3.2 that doesn't have them.
You need to make sure libav version is picked up first.
On my system libav instals this header as
/usr/local/include/libav/libavutil/pixdesc.h
and ffmpeg installs it as /usr/local/include/libav/libavutil/pixdesc.hPhilippe GorleyPhilippe Gorleyhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/371Latest version of ring-daemon (2.2.0) doesn't build with the latest version o...2018-05-22T00:38:10ZJami BotLatest version of ring-daemon (2.2.0) doesn't build with the latest version of opendht (1.3.2)Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
In file included from configurationmanager.cpp:49:
/usr/ports/net-im/ring-daemon/work/ring-daemon-2.2.0/src/ringdht/ringaccount.h:348:42: err...Issue generated from Tuleap's migration script.
**Originally submitted by: Yuri (yurivict)**
In file included from configurationmanager.cpp:49:
/usr/ports/net-im/ring-daemon/work/ring-daemon-2.2.0/src/ringdht/ringaccount.h:348:42: error: no member named 'Dht' in namespace 'dht'; did you mean 'dht'?
void saveNodes(const std::vector<dht::Dht::NodeExport>&) const;
\^\~\~\~\~\~\~\~
dht
/usr/local/include/opendht/default\_types.h:33:11: note: 'dht' declared here
namespace dht {
\^
In file included from configurationmanager.cpp:49:
/usr/ports/net-im/ring-daemon/work/ring-daemon-2.2.0/src/ringdht/ringaccount.h:349:43: error: no member named 'Dht' in namespace 'dht'; did you mean 'dht'?
void saveValues(const std::vector<dht::Dht::ValuesExport>&) const;
\^\~\~\~\~\~\~\~
dht
---------------------
It is impossible to make a package for Ring when your library releases don't match.
FreeBSD 11https://git.jami.net/savoirfairelinux/jami-project/-/issues/310Ring does not have a 'update' button2018-05-22T00:35:43ZJami BotRing does not have a 'update' buttonIssue generated from Tuleap's migration script.
**Originally submitted by: Svetlana Tkachenko (gryllida)**
We could have a 'nightly' and 'beta' and 'stable' (one day) release channels, and Ring could have an update button so that I don'...Issue generated from Tuleap's migration script.
**Originally submitted by: Svetlana Tkachenko (gryllida)**
We could have a 'nightly' and 'beta' and 'stable' (one day) release channels, and Ring could have an update button so that I don't have to manually download a new version.
Some details about how Firefox does updates:
https://wiki.mozilla.org/Releases/Update\_Channels
http://www.askvg.com/mozilla-updates-firefox-update-channels-nightly-aurora-beta-and-release/https://git.jami.net/savoirfairelinux/jami-project/-/issues/306LRC: call changes state in an unexpected way2018-05-25T12:51:44ZJami BotLRC: call changes state in an unexpected wayIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>I made a call to a machine with auto answer on, the call started (camera and audio), but dissapeared from the client complete...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>I made a call to a machine with auto answer on, the call started (camera and audio), but dissapeared from the client completely.</p>
<p>The client log only had this:<br />
Warning : call Call(0x9e2290) had an unexpected transition of state.( "Talking" )</p>
<p>Possibly changes in the daemon now allow state transitions which are not expected by lrc.</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/260daemon: putting in a "random" string for the nameserver makes the account inv...2018-05-22T00:34:11ZJami Botdaemon: putting in a "random" string for the nameserver makes the account invalidIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>using eg: &quot;asdfadfafd&quot; as the name server url invalidates the ring account... the ring account should work whether ...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>using eg: "asdfadfafd" as the name server url invalidates the ring account... the ring account should work whether the name server is valid or not</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/241[GNOME] Impossible to import beta1 account2018-05-22T00:33:45ZJami Bot[GNOME] Impossible to import beta1 accountIssue generated from Tuleap's migration script.
**Originally submitted by: Olivier SOLDANO (osoldano)**
<ul>
<li><strong>Overview</strong>
<ul>
<li>when trying to import a beta 1 old account, the procedure fails and outputs an...Issue generated from Tuleap's migration script.
**Originally submitted by: Olivier SOLDANO (osoldano)**
<ul>
<li><strong>Overview</strong>
<ul>
<li>when trying to import a beta 1 old account, the procedure fails and outputs an error</li>
</ul>
</li>
<li><strong>Steps</strong>
<ul>
<li>install beta1 version of ring, and create an account</li>
<li>export the account</li>
<li>install beta2 version and try to import the old account</li>
</ul>
</li>
<li><strong>Result</strong> (vs. expected result)
<ul>
<li>the application outputs "Error importing account(s)" (import the account and launch the migration procedure)</li>
</ul>
</li>
<li><strong>Frequency</strong>
<ul>
<li>always</li>
</ul>
</li>
</ul>
<ul>
<li><strong>Platform </strong>
<ul>
<li>Ubuntu 16.04</li>
</ul>
</li>
<li><strong>Logs</strong>
<ul>
<li>daemon </li>
</ul>
</li>
</ul>
<p>[1476881791.802|10003|manager.cpp:2347 ] Set accounts order : 23e111f45a1ef52a/</p>
<p>[1476881791.802|10003|manager.cpp:1482 ] Saving Configuration to XDG directory /home/osoldano/.config/ring/dring.yml</p>
<p>[1476881952.350|10003|archiver.cpp:171 ] Decryption failed: Can't decrypt data</p>
<ul>
<li>
<ul>
<li>client</li>
</ul>
</li>
</ul>
<p>Adding the new account to the account list ( "23e111f45a1ef52a" )</p>
<p>Adding the new account to the account list ( "23e111f45a1ef52a" )</p>
<p>\*\* (gnome-ring:10027): WARNING \*\*: failed to import account(s), err: 1</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/235It is allowed to import the same account multiple times2018-05-22T00:33:35ZJami BotIt is allowed to import the same account multiple timesIssue generated from Tuleap's migration script.
**Originally submitted by: Thibault Wittemberg (twittemberg)**
It is possible to add the same "multidevice" account multiple times on the same deviceIssue generated from Tuleap's migration script.
**Originally submitted by: Thibault Wittemberg (twittemberg)**
It is possible to add the same "multidevice" account multiple times on the same devicehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/462Outgoing call - not displaying recipient video2018-05-23T01:30:47ZJami BotOutgoing call - not displaying recipient videoIssue generated from Tuleap's migration script.
**Originally submitted by: Loïc Siret (lsiret)**
On multidevice branch.
I have 2 clients GNOME and OSX.
When I start a call from OSX to GNOME, I expect to see the GNOME client video...Issue generated from Tuleap's migration script.
**Originally submitted by: Loïc Siret (lsiret)**
On multidevice branch.
I have 2 clients GNOME and OSX.
When I start a call from OSX to GNOME, I expect to see the GNOME client video on the OSX. But I see a black screen.
When I start a call from GNOME to OSX, I expect to see the OSX client video on GNOME. But I see a black screen.
Running a wireshark on Caller machine show udp packet from other client.
Daemon log of Caller machine attached.
Working nice on master
[error.log](/uploads/a9e99578a97dc623e7c96ebbde00f14c/error.log)https://git.jami.net/savoirfairelinux/jami-project/-/issues/378daemon: integrate multidevice2018-05-22T00:38:40ZJami Botdaemon: integrate multideviceIssue generated from Tuleap's migration script.
**Originally submitted by: Andreas Traczyk (andreas.traczyk)**
<p>- &nbsp;Integrate multidevice and patch for UWP</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Andreas Traczyk (andreas.traczyk)**
<p>- Integrate multidevice and patch for UWP</p>Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/197daemon: message fails to send but status is IDLE2018-05-22T00:32:38ZJami Botdaemon: message fails to send but status is IDLEIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>If you create a new Ring account with a bad (or non working) bootstrap, the account never connects to the dht. If you then tr...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>If you create a new Ring account with a bad (or non working) bootstrap, the account never connects to the dht. If you then try to send a text message, it will of course fail, however, the status of the messges seems to stay on IDLE, see log:</p>
<p>[1473257868.497|13729|message\_engine.cpp:239 ] Could not save messages to /home/ssalenikovich/.cache/ring/92994cf5413c8fb7/messages: basic\_ios::clear: iostream error<br />
[1473257868.516|13729|sipaccount.cpp:2067 ] Unable to create request: Invalid Request URI (PJSIP\_EINVALIDREQURI)<br />
[1473257868.516|13729|message\_engine.cpp:137 ] Message 16160251769922510613: failure<br />
[1473257868.516|13729|message\_engine.cpp:158 ] Status IDLE for message 16160251769922510613<br />
[1473257882.640|13729|message\_engine.cpp:239 ] Could not save messages to /home/ssalenikovich/.cache/ring/92994cf5413c8fb7/messages: basic\_ios::clear: iostream error<br />
[1473257882.651|13729|sipaccount.cpp:2067 ] Unable to create request: Invalid Request URI (PJSIP\_EINVALIDREQURI)<br />
[1473257882.651|13729|message\_engine.cpp:137 ] Message 17238945268893409279: failure<br />
[1473257882.651|13729|message\_engine.cpp:158 ] Status IDLE for message 17238945268893409279</p>
<p> </p>
<p>The status should be FAILURE</p>https://git.jami.net/savoirfairelinux/jami-project/-/issues/181LRC - UserActionModel state is not properly updated for new outgoing call2018-05-25T12:53:26ZJami BotLRC - UserActionModel state is not properly updated for new outgoing callIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update ...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
<p>When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update the states of the actions. It seems this is because doing CallModel::getIndex() immediately after creating a new call results in an invalid index, thus the selectionModel can't be updated and the UAM relies on the selectionModel.<br />
</p>