savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-04-08T20:42:07Zhttps://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/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-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/902Send image/videos form gallery - AndroidTV2021-03-08T18:59:39ZAmirhossein NaghshzanSend image/videos form gallery - AndroidTVCurrently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.Currently, it is not possible to send a saved picture or video. We can only use the camera to take pictures/videos.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-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-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-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-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-android/-/issues/904Chat stops working after trying to send any kind of file2021-05-01T14:22:05ZChat stops working after trying to send any kind of file Android 10 MIUI 12.0.1 Xiaomi Redmi 8
Sending media stopped working a long time ago (15th october 2020 GooglePlay worked fine), but now even files (now upgraded from MIUI 11 to 12). it lets me take_a_photo/record_audio/choose_file and ... Android 10 MIUI 12.0.1 Xiaomi Redmi 8
Sending media stopped working a long time ago (15th october 2020 GooglePlay worked fine), but now even files (now upgraded from MIUI 11 to 12). it lets me take_a_photo/record_audio/choose_file and when jami is back on main screen i can't send even text messages (bubble doesn't appear), and in "Account >> Settings >> Media" it shows only one switch "enable video" that is returning its value to zero, instead of many buttons of codecs options. Full close of jami fixes texts and settings. This time i have contacts and devices so i have tried it only with same send recieve account.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1206Feature request: deletion of added contact date2021-08-17T20:15:31ZNetscapingFeature request: deletion of added contact dateWhen you add a contact, the time when you added the contact keeps showing and can't be deleted. It would be nice if you could delete the time of contact addition.When you add a contact, the time when you added the contact keeps showing and can't be deleted. It would be nice if you could delete the time of contact addition.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/335code smell: remove currentConvUid_ from MessageAdapter2021-07-16T19:58:21ZSébastien Blincode smell: remove currentConvUid_ from MessageAdapteras we have LRCInstance::getCurrentConvUid()as we have LRCInstance::getCurrentConvUid()https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/336Settings: Add support for isAllModerators (added into lrc)2021-03-12T21:00:13ZSébastien BlinSettings: Add support for isAllModerators (added into lrc)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/337Removal of Lrc singleton2021-04-02T19:37:50ZMing Rui ZhangRemoval of Lrc singletonMing Rui ZhangMing Rui Zhanghttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/905Feature request screen overlay detector2021-03-18T01:49:46ZFeature request screen overlay detectorScreenshots can be taken with apps that can draw over the screen without root. This looks more important than current forbidding.
Clearer description
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/905#note_27199
"Br...Screenshots can be taken with apps that can draw over the screen without root. This looks more important than current forbidding.
Clearer description
https://git.jami.net/savoirfairelinux/ring-client-android/-/issues/905#note_27199
"Briar" has developed this feature, and it doesn't let you enter passwords or chat until you figure out how to stop some of listed apps that have permission.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/476No SIP registration due to bad network detection2021-03-15T14:53:10ZEnrico ScholzNo SIP registration due to bad network detectionjami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
*...jami 20210308.1.7cc33bd does not do any SIP registration here. E.g. with tcpdump I see DNS queries (and responses) for the SIP server but no further communication to the SIP server itself.
Running the daemon with `--debug` shows
```
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
```
<details>
<summary>Full Log</summary>
<pre>
$ ring.cx --debug
(jami-gnome:822803): GLib-DEBUG: 14:24:25.931: setenv()/putenv() are not thread-safe and should not be used after threads are created
** (jami-gnome:822803): DEBUG: 14:24:25.931: debug enabled
** Message: 14:24:25.933: Jami GNOME client version: development
** Message: 14:24:25.933: git ref: unknown
** (jami-gnome:822803): DEBUG: 14:24:25.933: enabling autostart
** (jami-gnome:822803): DEBUG: 14:24:25.933: checking /usr/share/jami-gnome/jami-gnome.desktop
(jami-gnome:822803): dconf-DEBUG: 14:24:25.933: watch_established: "/net/jami/JamiGnome/" (establishing: 1)
** (jami-gnome:822803): DEBUG: 14:24:25.934: '/home/ensc/.config/autostart/jami-gnome.desktop' is already a symlink to '/usr/share/jami-gnome/jami-gnome.desktop'
(jami-gnome:822803): dbind-WARNING **: 14:24:25.945: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de
** (jami-gnome:822803): DEBUG: 14:24:26.098: installed translations for de_DE
(jami-gnome:822803): GLib-GIO-DEBUG: 14:24:26.106: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): GLib-DEBUG: 14:24:26.178: unsetenv() is not thread-safe and should not be used after threads are created
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Connecting to session manager
(jami-gnome:822803): Gtk-DEBUG: 14:24:26.178: Failed to get the GNOME session proxy: The name org.gnome.SessionManager is not owned
Can't open file: "/home/ensc/.local/share/jami/606bab6fe62f6e4c/profile.vcf"
** (jami-gnome:822803): DEBUG: 14:24:26.254: notify server name: naughty, vendor: awesome, version: 3.5, spec: 1.0
(jami-gnome:822803): Gtk-WARNING **: 14:24:26.255: Child name 'calls' not found in GtkStack
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.256: gtk_container_remove: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_container_add: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.257: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.257: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 1)
invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.vfs.GoaVolumeMonitor:: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer. (g-dbus-error-quark, 3)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.413: watch_fast: "/org/gtk/settings/file-chooser/" (establishing: 0, active: 0)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.414: watch_established: "/org/gtk/settings/file-chooser/" (establishing: 1)
(jami-gnome:822803): dconf-DEBUG: 14:24:26.565: watch_fast: "/net/jami/JamiGnome/" (establishing: 0, active: 2)
(jami-gnome:822803): Gtk-CRITICAL **: 14:24:26.585: gtk_scrolled_window_add: assertion 'child_widget == NULL' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.623: change_notify: /net/jami/JamiGnome/show-main-window
(process:822825): GLib-GIO-DEBUG: 14:24:26.661: Failed to initialize portal (GNetworkMonitorPortal) for gio-network-monitor: Not using portals
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: Failed to initialize networkmanager (GNetworkMonitorNM) for gio-network-monitor: NetworkManager not running
(process:822825): GLib-GIO-DEBUG: 14:24:26.663: _g_io_module_get_default: Found default implementation netlink (GNetworkMonitorNetlink) for ?gio-network-monitor?
(WebKitWebProcess:822824): dbind-WARNING **: 14:24:26.672: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer.
(jami-gnome:822803): dconf-DEBUG: 14:24:26.701: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.702: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.708: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.718: change_notify: /net/jami/JamiGnome/window-maximized
** (jami-gnome:822803): DEBUG: 14:24:26.718: NetworkManager client initialized, version: (null)
daemon running: no
nnetworking enabled: no
** (jami-gnome:822803): WARNING **: 14:24:26.718: no primary network connection detected, check network settings
(process:822825): GLib-GIO-DEBUG: 14:24:26.740: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ?gio-vfs?
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.756: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.776: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.792: change_notify: /net/jami/JamiGnome/window-height
(WebKitWebProcess:822824): GLib-GIO-DEBUG: 14:24:26.796: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.810: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.828: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.847: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.848: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.865: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): Gdk-CRITICAL **: 14:24:26.880: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.882: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.899: change_notify: /net/jami/JamiGnome/window-height
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-width
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_fast
(jami-gnome:822803): dconf-DEBUG: 14:24:26.917: change_notify: /net/jami/JamiGnome/window-height
</pre>
</details>
I am not using Gnome and network is managed manually (no NetworkManager)https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/477[To confirm] multidevice issue2021-03-15T16:32:53ZSébastien Blin[To confirm] multidevice issueAlice (2 devices A1, A0), Bob, Carla
+ A0 et Bob in call
+ Carla sends a message to Alice (or call), A1 will receives but not A0Alice (2 devices A1, A0), Bob, Carla
+ A0 et Bob in call
+ Carla sends a message to Alice (or call), A1 will receives but not A0Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/338Settings: plugins preferences not showing properly2021-03-22T16:20:58ZAline Gondim SantosSettings: plugins preferences not showing properlyWhen opening a plugins preferences list, they are not properly show.
Current behavior: preference reset or change force preferences to be properly shown.When opening a plugins preferences list, they are not properly show.
Current behavior: preference reset or change force preferences to be properly shown.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/906Android - Video out not showing2021-05-28T21:08:30ZXesús GonzálezAndroid - Video out not showing- Jami version: Together - 20210226-01
- Device model: Sony Xperia XZ1 (G8341)
- Android version: 9
- What build you are using: Play Store
- Can you reproduce the bug: at will
- Steps:
1. Starting video call between Android ...- Jami version: Together - 20210226-01
- Device model: Sony Xperia XZ1 (G8341)
- Android version: 9
- What build you are using: Play Store
- Can you reproduce the bug: at will
- Steps:
1. Starting video call between Android and Linux client.
2. Both devices successfully connected.
- Actual result: **Android video out NOT showing** (neither on Android screen nor on computer screen).
- Expected result: Android video out showing.https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/572Outgoing SIP calls drop after 32s2021-11-26T15:15:26ZDavid LecompteOutgoing SIP calls drop after 32sI am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:4...I am using an OVH SIP account. Outgoing calls to a landline or to another OVH SIP account drop after 32s, this is 100% reproducible.
I am using Trisquel 9 on a desktop PC and added Jami repository, the version of jami is 2021-03-08 21:43:25 UTC . The network connection is via ethernet, my ISP is SFR in Paris France, fiber connection.
The attached log was obtained with
/usr/lib/ring/dring -d -c 2>&1 | tee dring5.log
The image is a screen capture taken immediately after the call drop (less than 1s after) in order to show what was visible in the log. The big seqence of consecutive "underrun occured" was during the call but it paused more than 10s before the call drop.
[dring5.log](/uploads/648d1b648fb16fc641573235420d2b37/dring5.log)
![right_after_drop](/uploads/6f53ee76e0969c94a429aac2589da7e8/right_after_drop.png)Mohamed ChibaniMohamed Chibani