savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2022-12-08T01:18:00Zhttps://git.jami.net/savoirfairelinux/jami-libclient/-/issues/426Location sharing support2022-12-08T01:18:00ZSébastien BlinLocation sharing supportDaemon 7.9.0 supports location sharing with direct p2p connections (cf android), so now, clients can show "... is sharing location" and this should be implementedDaemon 7.9.0 supports location sharing with direct p2p connections (cf android), so now, clients can show "... is sharing location" and this should be implementedhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1157Location Sharing tab: Location sharing cannot be switched off2023-05-29T15:56:07ZannaLocation Sharing tab: Location sharing cannot be switched offThe minimum possible value is currently 1.
Would be wonderful if there was an off switch. Or are there reasons why there currently isn't one?
Version: 202305271125The minimum possible value is currently 1.
Would be wonderful if there was an off switch. Or are there reasons why there currently isn't one?
Version: 202305271125https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/252location sharing: when sharing location an empty message is added to conversa...2023-02-23T16:22:53ZKateryna Kostiuklocation sharing: when sharing location an empty message is added to conversationAlireza ToghianiAlireza Toghianihttps://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/253location sharing: wrong remaining time for incoming location sharing2023-02-23T16:22:27ZKateryna Kostiuklocation sharing: wrong remaining time for incoming location sharingsteps to reproduce:
- Start location sharing with Jami on iOS device.
- iOS device received location.
- Map is appear. The remaining time is "0 minutes"steps to reproduce:
- Start location sharing with Jami on iOS device.
- iOS device received location.
- Map is appear. The remaining time is "0 minutes"Alireza ToghianiAlireza Toghianihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/931locationsharing: wrong title on unpined window2023-01-18T16:58:44ZNicolas Vengeonlocationsharing: wrong title on unpined windowOnly the registered name was displayed on the window's title.
Now, the title takes into account the alias, the registered name, or the uri
to be able to show a title whether there is a registered name or not.Only the registered name was displayed on the window's title.
Now, the title takes into account the alias, the registered name, or the uri
to be able to show a title whether there is a registered name or not.Nicolas VengeonNicolas Vengeonhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/871Lock on long merge commits2023-10-26T17:52:03ZSébastien BlinLock on long merge commitsOn Jami:Core, sometimes, we can't send messages. A thread seems to be blocked on git_merge_commits (with a lot of merge_annotated_commit)
The reason is still unclear.On Jami:Core, sometimes, we can't send messages. A thread seems to be blocked on git_merge_commits (with a lot of merge_annotated_commit)
The reason is still unclear.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1227Log: add shared preference to preserve log state accross reboots/restarts2024-01-30T14:53:40ZPierre NicolasLog: add shared preference to preserve log state accross reboots/restarts## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce ...## Describe your environment
- Device model: Samsung Galaxy Tab S5e SM-T720
- Android version: 11
- What build you are using: your own, commit 5be1de17c790bddfb30dde74c8a1364e213f9847
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Start logging
2. Restart the application
- Actual result: Jami is not logging anymore
## Additional information
![log_automatically_stop](/uploads/4f07d5cb38bbe2b7d22fe7faa62212a9/log_automatically_stop.mp4)Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/419Log "Did not find conference XXX"2021-04-19T14:28:29ZPierre LespagnolLog "Did not find conference XXX"Warning log is shown during conference for participant.
Potentially the client calls the wrong functionsWarning log is shown during conference for participant.
Potentially the client calls the wrong functionshttps://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-qt/-/issues/1074Logging: log-to-file option doesn't work when a filename isn't supplied2023-12-01T21:10:49ZAndreas TraczykLogging: log-to-file option doesn't work when a filename isn't suppliedThe option is designed to provide a default, user-writeable location in the case where no file is specified, but currently, `--disable-web-security` is supplied as a filename, which won't be user-writable for user installs.
The web opti...The option is designed to provide a default, user-writeable location in the case where no file is specified, but currently, `--disable-web-security` is supplied as a filename, which won't be user-writable for user installs.
The web options need better management + non-user writable files should fallback to a default user-writable file.Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/652Logging - Set default log info2024-01-19T13:15:35ZMohamed ChibaniLogging - Set default log infoThe current logs in client-qt/LRC lack a lot of information (timestamps, file, thread-id, ...). We need to have logs at least equivalent to daemon's logs:
```
[16:07:10| 1862|jamiaccount.cpp :2012 ] Whatever ...
```The current logs in client-qt/LRC lack a lot of information (timestamps, file, thread-id, ...). We need to have logs at least equivalent to daemon's logs:
```
[16:07:10| 1862|jamiaccount.cpp :2012 ] Whatever ...
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/245Logic error: A device that answer 2 minutes after a call trigger the bad timeout2020-06-25T20:33:15ZSébastien BlinLogic error: A device that answer 2 minutes after a call trigger the bad timeoutSince we removed the eventloop, this code doesn't make any sense:
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
```
bool
JamiAccount::handlePendingCall(PendingCall& pc, bool incoming)
{
auto call = pc.cal...Since we removed the eventloop, this code doesn't make any sense:
Related to https://git.jami.net/savoirfairelinux/ring-daemon/issues/227
```
bool
JamiAccount::handlePendingCall(PendingCall& pc, bool incoming)
{
auto call = pc.call.lock();
// Cleanup pending call if call is over (cancelled by user or any other reason)
if (not call || call->getState() == Call::CallState::OVER)
return true;
if ((std::chrono::steady_clock::now() - pc.start) >= ICE_NEGOTIATION_TIMEOUT) {
JAMI_WARN("[call:%s] Timeout on ICE negotiation", call->getCallId().c_str());
call->onFailure();
return true;
}
```
Because handlePendingCall() is only done on negotiation success.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-jams/-/issues/7Login page not displayed: error 401 returned with message "You are not authen...2020-07-07T20:15:15ZGuillaume HellerLogin page not displayed: error 401 returned with message "You are not authenticated"Go to https://192.168.49.120
Login panel is not displayed and Error 401 "You are not authenticated" is returned:
![image](/uploads/77c540481b2ed0e0ba852d4d7176f87c/image.png)Go to https://192.168.49.120
Login panel is not displayed and Error 401 "You are not authenticated" is returned:
![image](/uploads/77c540481b2ed0e0ba852d4d7176f87c/image.png)Ndèye Anna NdiayeWilliam EnrightNdèye Anna Ndiayehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1548login problem2023-09-07T19:04:22Zalik huesoslogin problemwhen I try to register or log into an account on a PC, the Jami application crashes after I enter my data and click "login" or "register"when I try to register or log into an account on a PC, the Jami application crashes after I enter my data and click "login" or "register"https://git.jami.net/savoirfairelinux/jami-project/-/issues/225Login with a single account on multiple devices and get notified on both2018-05-22T00:33:16ZJami BotLogin with a single account on multiple devices and get notified on bothIssue generated from Tuleap's migration script.
**Originally submitted by: Ciro Santilli (cirosantilli)**
I would like to:
- get text messages on all devices when they are turned on
- get voice call alerts on all devices, and whe...Issue generated from Tuleap's migration script.
**Originally submitted by: Ciro Santilli (cirosantilli)**
I would like to:
- get text messages on all devices when they are turned on
- get voice call alerts on all devices, and when one answers, stop the alert on other devices
To test this, I tried to copy paste my \~/.config/ring across two Linux computers, but the second computer got a new ring ID when I turned on ring, so I could not test it. Am I copying the wrong folder? Same question goes for other platforms.
If this simple copy-paste of folders would work, then this issue is closely related to: https://tuleap.ring.cx/plugins/tracker/?aid=314
Even better would be to sync history and contacts across devices, but maybe we should leave this for another issue.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1269Logitech c920pro webcam microphone on Xiaomi Mibox S Android TV2023-05-05T19:29:38ZbademuxLogitech c920pro webcam microphone on Xiaomi Mibox S Android TVLogitech c920pro webcam microphone doesn't work on Xiaomi Mibox S Android TV (latest Android 9)
Trueconf app handle Logitech c920pro microphone correctly so I assume we can make it work on mibox s.
Let me know how can I help.Logitech c920pro webcam microphone doesn't work on Xiaomi Mibox S Android TV (latest Android 9)
Trueconf app handle Logitech c920pro microphone correctly so I assume we can make it work on mibox s.
Let me know how can I help.https://git.jami.net/savoirfairelinux/jami-project/-/issues/890Logitech c920pro webcam microphone on Xiaomi Mibox S Android TV2023-05-05T19:29:39ZbademuxLogitech c920pro webcam microphone on Xiaomi Mibox S Android TVLogitech c920pro webcam microphone doesn't work on Xiaomi Mibox S Android TV (latest Android 9)
Trueconf app handle Logitech c920pro microphone correctly so I assume we can make it work on mibox s.
Let me know how can I help.Logitech c920pro webcam microphone doesn't work on Xiaomi Mibox S Android TV (latest Android 9)
Trueconf app handle Logitech c920pro microphone correctly so I assume we can make it work on mibox s.
Let me know how can I help.https://git.jami.net/savoirfairelinux/jami-jams/-/issues/45logout and redirect user to login page when token expires2021-08-19T20:30:20ZGuillaume Hellerlogout and redirect user to login page when token expiresNdèye Anna NdiayeNdèye Anna Ndiayehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/778Long delay before message appear as delivered2021-08-16T21:03:43ZRobert AndrewLong delay before message appear as deliveredI am experiencing very long delivery delay (messages stay grayed) from a broadband static IP to an Android device on 4G.
Could it be that Android devices do not automatically share their new dynamic IP? Or am I misinterpreting the graye...I am experiencing very long delivery delay (messages stay grayed) from a broadband static IP to an Android device on 4G.
Could it be that Android devices do not automatically share their new dynamic IP? Or am I misinterpreting the grayed messages (not delivered vs. not read) ?https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/916Long display names make the UI unusable2023-05-26T13:59:31ZPhilippe GorleyLong display names make the UI unusableMaking an account with a very long display name makes the UI unusable until that account is deleted or the name is shortened (via manually editing the configuration files). It also makes the client lag a bit.
![Screenshot_from_2018-09-1...Making an account with a very long display name makes the UI unusable until that account is deleted or the name is shortened (via manually editing the configuration files). It also makes the client lag a bit.
![Screenshot_from_2018-09-13_09-37-06](/uploads/93f93f3d1dfbe0324466c8fa7f1309ff/Screenshot_from_2018-09-13_09-37-06.png)