savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2018-05-21T22:32:01Zhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/409Instructions on Ring.cx ask the signing key to be downloaded over HTTP2018-05-21T22:32:01ZJami BotInstructions on Ring.cx ask the signing key to be downloaded over HTTPIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
This is vulnerable to MitM attack. From HackerNews:
RaleyField 2 hours ago
> wget -O - "http://gpl.savoirfairelinux.net/...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
This is vulnerable to MitM attack. From HackerNews:
RaleyField 2 hours ago
> wget -O - "http://gpl.savoirfairelinux.net/ring-download/ring.pub.key" | sudo apt-key add -
Ew.
To spell it out for you, sending keys unauthenticated is scary. Double scary because these folks are writing security software so it ought to be in their motor memory to avoid trivial mitm attacks.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/256android: opendht compilation error2018-05-21T23:20:17ZJami Botandroid: opendht compilation errorIssue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
<p>Some OpenDHT change did not compiled on GCC 4.9 (fixed in 4.9.2).</p>Issue generated from Tuleap's migration script.
**Originally submitted by: Adrien Béraud (adrienberaud)**
<p>Some OpenDHT change did not compiled on GCC 4.9 (fixed in 4.9.2).</p>https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/127Missing "Share desktop" functionality in Mac2018-05-22T00:32:42ZJami BotMissing "Share desktop" functionality in MacIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Mac version doesn't have "Share desktop" functionality.Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandr Sergheev (asergheev)**
Mac version doesn't have "Share desktop" functionality.https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/336daemon/lrc: bizzare call state transitions when call fails immediately2018-05-25T13:36:07ZJami Botdaemon/lrc: bizzare call state transitions when call fails immediatelyIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
It seems like when a call fails, lrc puts in Failed -> Over state, but then a new call object is created in the Failed state.
...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
It seems like when a call fails, lrc puts in Failed -> Over state, but then a new call object is created in the Failed state.
lrc log:
Creating the call to "ring" failed
Calling action ACCEPT (0) on Call(0x603000b18aa0) with state "Dialing" . Become "Failed"
Call State Changed for call "15222503668050492823" . New state : "FAILURE"
Call not found "15222503668050492823" new state "FAILURE"
New foreign call: "15222503668050492823"
Building call "15222503668050492823" failed, it may already have been destroyed by the daemon
Call State Changed for call "15222503668050492823" . New state : "OVER"
Call not found "15222503668050492823" new state "OVER"
New foreign call: "15222503668050492823"
Building call "15222503668050492823" failed, it may already have been destroyed by the daemon
State changing from "Failed" to "Over" on Call(0x603000b18aa0)
Cannot remove Call(0x603000b18aa0) : call not found in tree
Calling action REFUSE (1) on Call(0x603000b18aa0) with state "Failed" . Become "Over"https://git.jami.net/savoirfairelinux/jami-packaging/-/issues/46Add PureOS to the Jami download page2020-05-11T15:51:50ZovariAdd PureOS to the Jami download pageCould you please add [PureOS](https://pureos.net/) to the [Download Jami for GNU/Linux](https://jami.net/download-jami-linux/)?
> ### [FSF adds PureOS to list of endorsed GNU/Linux distributions](https://www.fsf.org/news/fsf-adds-pureos...Could you please add [PureOS](https://pureos.net/) to the [Download Jami for GNU/Linux](https://jami.net/download-jami-linux/)?
> ### [FSF adds PureOS to list of endorsed GNU/Linux distributions](https://www.fsf.org/news/fsf-adds-pureos-to-list-of-endorsed-gnu-linux-distributions-1)
> [PureOS](https://pureos.net/), a modern and user-friendly [Debian](https://www.debian.org/)-derived distribution.
The [Librem products from Purism](https://puri.sm/products/) have PureOS as the default operating system.
With PureOS, [Purism](https://puri.sm/) are shipping hardware with GNOME / GTK+ which converges the **desktop**, **laptop** and **[phone](https://puri.sm/products/librem-5/)**.<br>
https://puri.sm/posts/breaking-ground/
![image](/uploads/ad1e035298564299fa177cb6b11fe8f8/image.png)<br>
https://flatpak.org/setup/
What do you think?
Thank youhttps://git.jami.net/savoirfairelinux/jami-plugins/-/issues/15Blur plugin2021-03-31T15:05:08ZSébastien BlinBlur pluginAdd blur functionality to GreenScreen pluginAdd blur functionality to GreenScreen pluginAline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-project/-/issues/69lrc: fix warnings2018-05-25T13:36:33ZJami Botlrc: fix warningsIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
There are many warnings, some seemingly trivial to fix, which pop up when compiling lrc and when linking the clients against it....Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
There are many warnings, some seemingly trivial to fix, which pop up when compiling lrc and when linking the clients against it... This is distracting and makes it harder to see errors as well as notice when a new patch introduces new warnings thus potentially reducing code quality.
These warnings should be removed as much as possible, especially the ones easy to fix.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/410[GNOME] Adding contact to gnome contacts seems to break contact entry2018-05-21T22:36:16ZJami Bot[GNOME] Adding contact to gnome contacts seems to break contact entryIssue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
DESCRIPTION
Adding a contact (right click>add to contact) creates the contact in gnome contacts. When trying to edit the same cont...Issue generated from Tuleap's migration script.
**Originally submitted by: Simon Désaulniers (sim590)**
DESCRIPTION
Adding a contact (right click>add to contact) creates the contact in gnome contacts. When trying to edit the same contact in gnome-contacts application, unexpected behavior occurs. Adding a field (home phone for e.g.) replaces an already existing field in the contact info wether both field are of the same type or not. However, creating the contact at first from within gnome-contacts itself doesn't cause the problem. This lets me think the bug is due to the way Ring creates the contact (the API it's using).
NOTE
Attached to this bug report is a screenshot of an error message displayed by gnome-contacts after trying to add a field to a contact (created by Ring).
![sshot1](/uploads/8037d9959b04cabb038cfd6e814d4908/sshot1.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/257Android: bug creating SIP account2018-05-21T23:20:35ZJami BotAndroid: bug creating SIP accountIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>I wanted to make an IP call from android. I added a SIP account for that.</p>
<p>Funny thing is, I called it 'IP2IP' (alias ...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>I wanted to make an IP call from android. I added a SIP account for that.</p>
<p>Funny thing is, I called it 'IP2IP' (alias field)</p>
<p>Two things happened:</p>
<p>- In the account list I got a blanck entry instead of my new account</p>
<p>- In the account details of this bugged account I only saw the Media panel, and no possibility to delete this account. This is probably because there is some legacy code that disable some stuff for the case the account is the IP2IP one. It should be removed, this is a regular SIP account, with an empty hostname.</p>
<p> </p>
<p>After that I tried to create another SIP account.</p>
<p>The account list got strangely updated. I could now see the IP2IP account previously created but the new account was a white huge row. I provide a screenshot to explain this.</p>
<p>I can only see (cf. 2nd screenshot) that my SIP account replaced my Ring account (because it is first in the list) in the left navigation menu on the left of the share button</p>
![Screenshot_20160420-135135](/uploads/4536bfcad490adb3eb4630262f67a33a/Screenshot_20160420-135135.png)
![Screenshot_20160420-140313](/uploads/85320e80191295971c48961b429895a4/Screenshot_20160420-140313.png)https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/128OSX: improve in call UI2018-05-22T00:32:56ZJami BotOSX: improve in call UIIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
OSx client does not have specific UI for incoming calls, nore outgoing calls in process (not current).
There is also no contact ph...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
OSx client does not have specific UI for incoming calls, nore outgoing calls in process (not current).
There is also no contact photo displayed.
UI should stick to wireframes and what the Windows client has.https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/337lrc: wrong or missing audio device selection in certain cases2018-05-25T13:36:13ZJami Botlrc: wrong or missing audio device selection in certain casesIssue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The audio device selection can be lost or incorrectly set when chaning the audio driver selection.
The primary reason seems...Issue generated from Tuleap's migration script.
**Originally submitted by: Stepan Salenikovich (ssalenik)**
The audio device selection can be lost or incorrectly set when chaning the audio driver selection.
The primary reason seems to be because the device selection for each driver is not individually stored nor checked against what is selected in the daemon.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/41Memory creep in video calls2022-11-14T21:52:32ZPhilippe GorleyMemory creep in video callsDuring a video call, RAM usage by the daemon increases by ~1MB per second. Memory does not go back to "pre-call" levels once the call is terminated.During a video call, RAM usage by the daemon increases by ~1MB per second. Memory does not go back to "pre-call" levels once the call is terminated.Philippe GorleyPhilippe Gorleyhttps://git.jami.net/savoirfairelinux/jami-packaging/-/issues/48Add Debian 11 (bullseye) “testing” to the Jami download page2020-03-28T17:44:04ZovariAdd Debian 11 (bullseye) “testing” to the Jami download pageCould you please add [Debian 11 (bullseye) “testing”](https://www.debian.org/releases/bullseye/) to the [Download Jami for GNU/Linux](https://jami.net/download-jami-linux/)?
This would enable:
* Add PureOS to the Jami download page http...Could you please add [Debian 11 (bullseye) “testing”](https://www.debian.org/releases/bullseye/) to the [Download Jami for GNU/Linux](https://jami.net/download-jami-linux/)?
This would enable:
* Add PureOS to the Jami download page https://git.jami.net/savoirfairelinux/jami-packaging/issues/46
* [GNOME] Librem 5 phone client https://git.jami.net/savoirfairelinux/ring-client-gnome/issues/950<br>
https://azdle.net/2019/11/comparing-apples-and-gnomes/
Thank youhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/70LRC: AccountModel "cancel" action is broken2018-05-25T13:36:29ZJami BotLRC: AccountModel "cancel" action is brokenIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
It wont correctly restore the model stateIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
It wont correctly restore the model statehttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/411Unable to setup call2018-05-21T22:37:42ZJami BotUnable to setup callIssue generated from Tuleap's migration script.
**Originally submitted by: JB (bluetac)**
<p>I have the ring client installed on Xubuntu 14.04 and on my Nexus phone (Android 6.0 &quot;Marshmallow&quot;) with the ring beta client install...Issue generated from Tuleap's migration script.
**Originally submitted by: JB (bluetac)**
<p>I have the ring client installed on Xubuntu 14.04 and on my Nexus phone (Android 6.0 "Marshmallow") with the ring beta client installed and I'm unable to get a call setup between the two.</p>
<p>Messaging seems to be okay, so I assume there is no problem with the RingID's.</p>
<p>When calling from PC to Mobile - The call sometimes doesn't make it to the mobile, but when it does it takes a long time to initiate ringing (however the messages appear almost instantly). Once ringing you can answer the call but you get no audio and the PC continues to think the call is still setting up. The mobile client eventually gives up and closes the call, then after a few more seconds the PC recieves the OK and thinks the call has begun. The PC then shortly gets the disconnect or the BYE and then hangs up.</p>
<p>I have a network capture of the issue described, please let me know if you would like a copy. I am unaware of how to decrypt TLS messages so I can view to original SIP but I assume this is being caused by a timeout period being reached on either of the clients.</p>https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/258log\_file2018-05-21T23:21:35ZJami Botlog\_fileIssue generated from Tuleap's migration script.
**Originally submitted by: Ben Featherstone (featherstone)**
<p>Here is a copy of the log file for adb.</p>
<p>Let me know if there is anything else you need.</p>
[logring.txt](/...Issue generated from Tuleap's migration script.
**Originally submitted by: Ben Featherstone (featherstone)**
<p>Here is a copy of the log file for adb.</p>
<p>Let me know if there is anything else you need.</p>
[logring.txt](/uploads/4ebc032bbf7d5f88b2b85cfb9a569d59/logring.txt)https://git.jami.net/savoirfairelinux/jami-client-macos/-/issues/129Welcome wizard modification2018-05-22T00:33:46ZJami BotWelcome wizard modificationIssue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>- Change 'OK' button to 'Next'</p>
<p>- Allow account creation without entering name</p>
<p>- Animation during account ...Issue generated from Tuleap's migration script.
**Originally submitted by: Alexandre Lision (alision)**
<p>- Change 'OK' button to 'Next'</p>
<p>- Allow account creation without entering name</p>
<p>- Animation during account creation if possible (call to daemon is blocking on OSX/Windows, this may be more complicated)</p>https://git.jami.net/savoirfairelinux/jami-libclient/-/issues/338New year crash in LRC2018-05-25T13:36:24ZJami BotNew year crash in LRCIssue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to ...Issue generated from Tuleap's migration script.
**Originally submitted by: Emmanuel Lepage Vallee (elv13)**
The new time calculation code is broken as each values can be negative and this isn't taken into account.
I will revert to a version based on my old code but including the changes introduced by the rewrite.
It is faster anyway. In my opinion, it is also clear and simple and don't depend on 3rd party APIs at all, just plain C and decimal logichttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/42Add ringing timeout2022-11-14T21:52:32ZHugo LefeuvreAdd ringing timeoutCurrently there is no timeout for emitted calls. If a peer is connected but doesn't answer a call, then this call will ring 'forever', at least until the user manually aborts it or peer becomes unreachable.
We should implement such a ti...Currently there is no timeout for emitted calls. If a peer is connected but doesn't answer a call, then this call will ring 'forever', at least until the user manually aborts it or peer becomes unreachable.
We should implement such a timeout.Next major releaseHugo LefeuvreHugo Lefeuvrehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/71Gnome client segfaults (in libringclient) at launch2018-05-21T22:16:59ZJami BotGnome client segfaults (in libringclient) at launchIssue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
When launching gnome-ring on Linux, it segfaults immediately. This didn't happen a few days ago and seems related to a date, is th...Issue generated from Tuleap's migration script.
**Originally submitted by: Baptiste Jonglez (baptiste)**
When launching gnome-ring on Linux, it segfaults immediately. This didn't happen a few days ago and seems related to a date, is this the new y2k bug? :)
I am using libringclient version c6fc97a4b6e3baea116ec6ce122a73c3ac5af337 and gnome-ring version bd4b37702bb34dee98faa41489dcf98d403d2197. Below is the backtrace provided by gdb:
\~$ gdb gnome-ring
GNU gdb (GDB) 7.10.1
Reading symbols from gnome-ring...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/gnome-ring
[Thread debugging using libthread\_db enabled]
Using host libthread\_db library "/usr/lib/libthread\_db.so.1".
[New Thread 0x7fffe3c99700 (LWP 6694)]
[New Thread 0x7fffe3309700 (LWP 6695)]
[New Thread 0x7fffe2b08700 (LWP 6696)]
\*\* Message: Ring GNOME client version: 0.4.0
\*\* Message: git ref: bd4b37702bb34dee98faa41489dcf98d403d2197
Updating all accounts
Loading "32a968c6894c1912"
[New Thread 0x7fffd3fff700 (LWP 6697)]
[Thread 0x7fffd3fff700 (LWP 6697) exited]
QObject::connect: No such signal ConfigurationManagerInterface::incomingAccountMessage(QString,QString,QMap<QString, QString>)
Account parameter " "Account.presenceSubscribeSupported" " not found
Loading "IP2IP"
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7a99193 in HistoryTimeCategoryModel::indexToName(int) () from /usr/lib/libringclient.so.0.4.0
(gdb) bt
\#0 0x00007ffff7a99193 in HistoryTimeCategoryModel::indexToName(int) () from /usr/lib/libringclient.so.0.4.0
\#1 0x00007ffff7a70d4a in CategorizedHistoryModelPrivate::getCategory(Call const\*) () from /usr/lib/libringclient.so.0.4.0
\#2 0x00007ffff7a723a6 in CategorizedHistoryModelPrivate::add(Call\*) () from /usr/lib/libringclient.so.0.4.0
\#3 0x00007ffff7a7270d in CategorizedHistoryModel::addItemCallback(Call const\*) () from /usr/lib/libringclient.so.0.4.0
\#4 0x00007ffff7b04279 in LocalHistoryEditor::addExisting(Call const\*) () from /usr/lib/libringclient.so.0.4.0
\#5 0x00007ffff7b07643 in LocalHistoryCollection::load() () from /usr/lib/libringclient.so.0.4.0
\#6 0x0000000000427ba9 in LocalHistoryCollection\* CollectionManagerInterface<Call>::addCollection<LocalHistoryCollection>(, LoadOptions) ()
\#7 0x0000000000425b46 in ?? ()
\#8 0x00007ffff5fcc244 in ?? () from /usr/lib/libgobject-2.0.so.0
\#9 0x00007ffff5fe6a46 in g\_signal\_emit\_valist () from /usr/lib/libgobject-2.0.so.0
\#10 0x00007ffff5fe712f in g\_signal\_emit () from /usr/lib/libgobject-2.0.so.0
\#11 0x00007ffff62b6d92 in g\_application\_register () from /usr/lib/libgio-2.0.so.0
\#12 0x00007ffff62b7517 in ?? () from /usr/lib/libgio-2.0.so.0
\#13 0x00007ffff62b785a in g\_application\_run () from /usr/lib/libgio-2.0.so.0
\#14 0x00007ffff3d1e610 in \_\_libc\_start\_main () from /usr/lib/libc.so.6
\#15 0x00000000004249f9 in \_start ()
[0001-history-Fix-segfault-when-fuzzy-dates-span-two-disti.patch](/uploads/61e7415665a0f2d76fe6bc66c80fbe0d/0001-history-Fix-segfault-when-fuzzy-dates-span-two-disti.patch)