savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-03-16T20:27:41Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/334Disable the "+ Link another device" button when `Enable account` is set to `off`2021-03-16T20:27:41ZovariDisable the "+ Link another device" button when `Enable account` is set to `off`1. Open Settings
2. Account Settings
3. Set `Enable account` to `Off`
The `+ Link another device` should be disabled; however it isn't
4. Click `+ Link another device`
5. Insert password if required
6. Error message `Error connecting t...1. Open Settings
2. Account Settings
3. Set `Enable account` to `Off`
The `+ Link another device` should be disabled; however it isn't
4. Click `+ Link another device`
5. Insert password if required
6. Error message `Error connecting to the network. Please try again later.`
![image](/uploads/e37788c2bf20562cde2a3d9b51f36579/image.png)
https://git.jami.net/savoirfairelinux/ring-client-gnome/-/issues/893
Thank you
Linux Mint 20.1 Cinnamon<br>
Jami --edge snapdSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/333Tool-tips/popup do not show for buttons along the top row of the chatview2021-04-22T10:37:45ZovariTool-tips/popup do not show for buttons along the top row of the chatviewTool-tips/popup do **not** show for buttons in the top right of the chatview for:
1. `Start audio call`
2. `Start video call`
![image](/uploads/7039252ee72aeb8bfce408712ac854ac/image.png)
Tool-tips/popup do **not** show for button in t...Tool-tips/popup do **not** show for buttons in the top right of the chatview for:
1. `Start audio call`
2. `Start video call`
![image](/uploads/7039252ee72aeb8bfce408712ac854ac/image.png)
Tool-tips/popup do **not** show for button in the top left of the chatview for:
1. `back arrow`
The tool-tips/popups **do** show for `Send file`, `Leave audio message`, `Leave video message` and `Send` on the bottom row.
Thank you
Linux Mint 20.1 Cinnamon<br>
Jami --edge snapd
https://git.jami.net/savoirfairelinux/ring-lrc/-/issues/468#note_27805<br>
https://git.jami.net/savoirfairelinux/ring-lrc/-/commit/a17ee41e2a557217ef7a3fe61307f1a237bbf5f6https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/475swarm: conversation not loaded for disabled account2021-03-10T17:55:47ZKateryna Kostiukswarm: conversation not loaded for disabled accounthttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/474Crash during account creation2021-07-16T18:09:59ZPierre LespagnolCrash during account creationHappen sometimes during jams account creation, after this the client-qt fail to run with `what(): Contact out of range` exception
backtrace:
```
libcrypto.so.1.1![Unknown/Just-In-Time compiled code] (Unknown Source:0)
libcrypto.so.1.1!...Happen sometimes during jams account creation, after this the client-qt fail to run with `what(): Contact out of range` exception
backtrace:
```
libcrypto.so.1.1![Unknown/Just-In-Time compiled code] (Unknown Source:0)
libcrypto.so.1.1!BIO_write (Unknown Source:0)
asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::execution::any_executor<asio::execution::context_as_t<asio::execution_context&>, asio::execution::detail::blocking::never_t<0>, asio::execution::prefer_only<asio::execution::detail::blocking::possibly_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::tracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::untracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::fork_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::continuation_t<0> > > >, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>::operator()(std::error_code, unsigned long, int) (Unknown Source:0)
void asio::detail::executor_function::complete<asio::detail::binder2<asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::execution::any_executor<asio::execution::context_as_t<asio::execution_context&>, asio::execution::detail::blocking::never_t<0>, asio::execution::prefer_only<asio::execution::detail::blocking::possibly_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::tracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::untracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::fork_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::continuation_t<0> > > >, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>, std::error_code, unsigned long>, std::allocator<void> >(asio::detail::executor_function::impl_base*, bool) (Unknown Source:0)
void asio::io_context::basic_executor_type<std::allocator<void>, 4u>::execute<asio::detail::executor_function>(asio::detail::executor_function&&) const (Unknown Source:0)
asio::detail::reactive_socket_recv_op<asio::mutable_buffers_1, asio::ssl::detail::io_op<asio::basic_stream_socket<asio::ip::tcp, asio::execution::any_executor<asio::execution::context_as_t<asio::execution_context&>, asio::execution::detail::blocking::never_t<0>, asio::execution::prefer_only<asio::execution::detail::blocking::possibly_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::tracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::untracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::fork_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::continuation_t<0> > > >, asio::ssl::detail::handshake_op, dht::http::Connection::async_handshake(std::function<void (std::error_code const&)>)::{lambda(std::error_code const&)#1}>, asio::execution::any_executor<asio::execution::context_as_t<asio::execution_context&>, asio::execution::detail::blocking::never_t<0>, asio::execution::prefer_only<asio::execution::detail::blocking::possibly_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::tracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::outstanding_work::untracked_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::fork_t<0> >, asio::execution::prefer_only<asio::execution::detail::relationship::continuation_t<0> > > >::do_complete(void*, asio::detail::scheduler_operation*, std::error_code const&, unsigned long) (Unknown Source:0)
asio::detail::scheduler_operation::complete(asio::detail::scheduler_operation * const this, void * owner, const asio::error_code & ec, std::size_t bytes_transferred) (/home/plespagnol/Documents/ring-project/daemon/contrib/x86_64-linux-gnu/include/asio/detail/scheduler_operation.hpp:39)
asio::detail::scheduler::do_run_one(asio::detail::scheduler * const this, asio::detail::conditionally_enabled_mutex::scoped_lock & lock, asio::detail::scheduler::thread_info & this_thread, const asio::error_code & ec) (/home/plespagnol/Documents/ring-project/daemon/contrib/x86_64-linux-gnu/include/asio/detail/impl/scheduler.ipp:480)
asio::detail::scheduler::run(asio::detail::scheduler * const this, asio::error_code & ec) (/home/plespagnol/Documents/ring-project/daemon/contrib/x86_64-linux-gnu/include/asio/detail/impl/scheduler.ipp:203)
asio::io_context::run(asio::io_context * const this) (/home/plespagnol/Documents/ring-project/daemon/contrib/x86_64-linux-gnu/include/asio/impl/io_context.ipp:62)
operator()(const struct {...} * const __closure) (/home/plespagnol/Documents/ring-project/daemon/src/manager.cpp:456)
std::__invoke_impl<void, jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> >(std::__invoke_other, struct {...} &&)(struct {...} && __f) (/usr/include/c++/10/bits/invoke.h:60)
std::__invoke<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> >(struct {...} &&)(struct {...} && __fn) (/usr/include/c++/10/bits/invoke.h:95)
std::thread::_Invoker<std::tuple<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > >::_M_invoke<0>(std::_Index_tuple<0>)(std::thread::_Invoker<std::tuple<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > > * const this) (/usr/include/c++/10/thread:264)
std::thread::_Invoker<std::tuple<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > >::operator()(void)(std::thread::_Invoker<std::tuple<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > > * const this) (/usr/include/c++/10/thread:271)
std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > > >::_M_run(void)(std::thread::_State_impl<std::thread::_Invoker<std::tuple<jami::Manager::ManagerPimpl::ManagerPimpl(jami::Manager&)::<lambda()> > > > * const this) (/usr/include/c++/10/thread:215)
libstdc++.so.6![Unknown/Just-In-Time compiled code] (Unknown Source:0)
libpthread.so.0!start_thread(void * arg) (pthread_create.c:463)
libc.so.6!clone() (clone.S:95)
```https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/903Conversation background - AndroidTV2021-05-11T15:45:15ZAmirhossein NaghshzanConversation background - AndroidTVOn loading a conversation by contact shortcuts from home, the blue background is not visible and is totally grey.On loading a conversation by contact shortcuts from home, the blue background is not visible and is totally grey.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/901Delete contact dialog - AndroidTV2021-04-12T07:52:37ZAmirhossein NaghshzanDelete contact dialog - AndroidTVCurrently, contacts would be deleted as soon as the user press the button. It is better to confirm with the user by showing a dialog.Currently, contacts would be deleted as soon as the user press the button. It is better to confirm with the user by showing a dialog.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/900Picture-in-Picture title - AndroidTV2021-05-10T00:50:52ZAmirhossein NaghshzanPicture-in-Picture title - AndroidTVDuring a video call if press the home button and the video call changes to picture-in-Picture the title is "(No title program)"During a video call if press the home button and the video call changes to picture-in-Picture the title is "(No title program)"https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/473pulseaudio server should be allowed to autospawn when the daemon attempts to ...2021-04-08T20:42:07ZMaxim Cournoyerpulseaudio server should be allowed to autospawn when the daemon attempts to use pulseaudioThe preferred mode of operation of pulseaudio (and the one configured by default) is to autospawn the pulseaudio server on demand [0].
For some reason, the daemon disables AUTOSPAWN when attempting to connect to the pulseaudio server:
...The preferred mode of operation of pulseaudio (and the one configured by default) is to autospawn the pulseaudio server on demand [0].
For some reason, the daemon disables AUTOSPAWN when attempting to connect to the pulseaudio server:
```
if (pa_context_connect(context_, nullptr, PA_CONTEXT_NOAUTOSPAWN, nullptr) < 0)
throw std::runtime_error("Could not connect pulseaudio context to the server");
```
This causes Jami to fallback to ALSA even when the daemon was built with pulseaudio unless a pulseaudio server is already running, which degrades the audio experience (lacking echo cancellation, among other features provided by pulseaudio).
[0] https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Running/Maxim CournoyerMaxim Cournoyerhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/899No video on Rendezvous Mode - AndroidTV2021-03-15T20:10:59ZAmirhossein NaghshzanNo video on Rendezvous Mode - AndroidTVIf Rendezvous Mode is enabled in settings, during incoming video calls the screen is totally black. Neither receive video nor send it.If Rendezvous Mode is enabled in settings, during incoming video calls the screen is totally black. Neither receive video nor send it.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/332Use "Yes" and "No" buttons on Upgrade prompt [enhancement]2021-07-19T20:03:11ZNick-OpusVLUse "Yes" and "No" buttons on Upgrade prompt [enhancement]Hi, I noticed a mismatch in dialogue box contents and button labels on the Upgrade prompt.
The prompt is phrased as a question, but has "OK" and "Cancel".
My suggestion is to change the buttons to "Yes" and "No" respectively.
![Annota...Hi, I noticed a mismatch in dialogue box contents and button labels on the Upgrade prompt.
The prompt is phrased as a question, but has "OK" and "Cancel".
My suggestion is to change the buttons to "Yes" and "No" respectively.
![Annotation_2021-03-05_094351](/uploads/b96f824433aa7532d0690722539d8c04/Annotation_2021-03-05_094351.png)https://git.jami.net/savoirfairelinux/jami-project/-/issues/1205Use "Yes" and "No" buttons on Upgrade prompt [enhancement]2021-03-09T16:24:54ZNick-OpusVLUse "Yes" and "No" buttons on Upgrade prompt [enhancement]Hi, I noticed a mismatch in dialogue box contents and button labels on the Upgrade prompt.
The prompt is phrased as a question, but has "OK" and "Cancel".
My suggestion is to change the buttons to "Yes" and "No" respectively.
![Annota...Hi, I noticed a mismatch in dialogue box contents and button labels on the Upgrade prompt.
The prompt is phrased as a question, but has "OK" and "Cancel".
My suggestion is to change the buttons to "Yes" and "No" respectively.
![Annotation_2021-03-05_094351](/uploads/66412c8e080c7984d96dbbf30ffdfc01/Annotation_2021-03-05_094351.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/897Feature request floating bubble shortcut2021-11-25T16:53:02ZFeature request floating bubble shortcutA floating circle little shortcut widget that displays number of unread messages.
Optionally it can when clicked open a window that doesn't interrupt main screen app behavior as it still "floats" where human can see chat history and se...A floating circle little shortcut widget that displays number of unread messages.
Optionally it can when clicked open a window that doesn't interrupt main screen app behavior as it still "floats" where human can see chat history and send messages.
This can be a way to stay active without a notification, maybe even alternative switch to staying active.
The idea came from these unbelieveably popular proprietary projects "Messenger" for facebook, "Mobogram" for telegramhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1203Feature request: Allow custom contact names2021-03-10T12:59:17ZJivan PalFeature request: Allow custom contact namesAllow the user to optionally set their own preferred display name for a contact. This has a few nice user benefits, including mitigating the ability for contacts to change their display name and potentially fool the user (e.g. I talk to ...Allow the user to optionally set their own preferred display name for a contact. This has a few nice user benefits, including mitigating the ability for contacts to change their display name and potentially fool the user (e.g. I talk to Alice and Bob, Bob changes his display name to "Alice", and I mistakenly send a message for him that was intended for Alice). Optionally (but by default?) also still display the contact's actual display name alongside/below the user's preferred name for that contact, but in a smaller font.
For comparison, WhatsApp does this by default; if in a group chat and someone whose phone number I do not have in my device's contacts sends a message, that person's WhatsApp display name is shown preceded by `~`, e.g. `~John Smith`, else the name I have set in my device's contacts appears, e.g. `Johnny (work)`.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/896Client ringer does not respect volume settings and Do Not Disturb mode2021-08-30T14:38:24ZJivan PalClient ringer does not respect volume settings and Do Not Disturb modeUsing Jami for Android, version 20210205-01, on Android 9.0 (Samsung One UI 1.0) on a Samsung SM-A530F (Samsung Galaxy A8 (2018)).
This issue relates to the ringtone played when the client receives an incoming call. Potentially related:...Using Jami for Android, version 20210205-01, on Android 9.0 (Samsung One UI 1.0) on a Samsung SM-A530F (Samsung Galaxy A8 (2018)).
This issue relates to the ringtone played when the client receives an incoming call. Potentially related: #224.
It seems that Jami's ringer has a simple condition of "if the device's ringtone volume is 0, then don't play the ringtone; else play the ringtone at some hard-coded fixed volume X." If the device's ringtone volume is adjusted, Jami still rings at the same volume.
Also, if the device is put into Do Not Disturb mode (i.e. via [Settings] > [Notifications] > [Do Not Disturb], or equivalently through the quick settings toggle — note that this mode prevents notifications from appearing on screen and also silences all sounds except Media (i.e. Ringtone, Notification, and System volumes are all set to 0, and vibration is disabled; Media volume is left as is), the ringtone still plays. This is the case even if the Media volume is also set to 0 (so that *all* volumes are set to 0).https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/895Code coverage?2021-11-25T16:50:20ZArtemy GavrelyukCode coverage?I could not find any test coverage scripts and metrics. It could be great, if jami-client-android's code coverage was observableI could not find any test coverage scripts and metrics. It could be great, if jami-client-android's code coverage was observablehttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/331Permission denied for USB source2021-03-09T04:56:18ZovariPermission denied for USB sourcePermission denied accessing files from USB sources.
Will this be solved when installed from `deb` instead of `snapd`?
![image](/uploads/c28dfbe040b6479dae022aa466a58a14/image.png)
Workaround: save the file on the Desktop and restore f...Permission denied accessing files from USB sources.
Will this be solved when installed from `deb` instead of `snapd`?
![image](/uploads/c28dfbe040b6479dae022aa466a58a14/image.png)
Workaround: save the file on the Desktop and restore from backup using the copied file from the Desktop.
Thank you
Linux Mint 20.1 Cinnamon<br>
Jami --edge on Snaphttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/330jami-qt for Linux deb (non-Snap) support2021-03-09T04:46:56Zovarijami-qt for Linux deb (non-Snap) supportPlease enable Jami-qt for Linux to be installed with a deb file.
This would enable Jami-qt to be installed on Linux systems that do not have `snapd`
Thank you
Linux Mint 20.1 Cinnamon<br>
Jami --edge on SnapPlease enable Jami-qt for Linux to be installed with a deb file.
This would enable Jami-qt to be installed on Linux systems that do not have `snapd`
Thank you
Linux Mint 20.1 Cinnamon<br>
Jami --edge on Snaphttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/329update copyright from 2020 to 20212021-03-09T04:46:55Zovariupdate copyright from 2020 to 2021Please update copyright from `2020` to `2021`. Thank you
![image](/uploads/81b9ae203bb6ef33395f0ab1937efae6/image.png)
Linux Mint 20.1 Cinnamon<br>
Jami --edge on SnapPlease update copyright from `2020` to `2021`. Thank you
![image](/uploads/81b9ae203bb6ef33395f0ab1937efae6/image.png)
Linux Mint 20.1 Cinnamon<br>
Jami --edge on Snaphttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/328Dpi auto scaling will not happen when starting the application with 100% scal...2023-12-27T16:38:20ZMing Rui ZhangDpi auto scaling will not happen when starting the application with 100% scaling factorMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/472UPnP - Memory leak in libupnp and libixml2021-03-19T17:44:39ZMohamed ChibaniUPnP - Memory leak in libupnp and libixmlInvestigate memory leaks reported by ASAN (address sanitizer). See the comment below for the report.
Many libupnp and libixml methods allocate memory and expect the caller to release it, which does not seem to be always done. See UpnpDo...Investigate memory leaks reported by ASAN (address sanitizer). See the comment below for the report.
Many libupnp and libixml methods allocate memory and expect the caller to release it, which does not seem to be always done. See UpnpDownloadXmlDoc for example.Mohamed ChibaniMohamed Chibani