savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-11-15T15:18:36Zhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/594Record status is wrong2021-11-15T15:18:36ZSébastien BlinRecord status is wrong# Scenario
+ start call
+ Launch a record
+ Stop a call
+ Start a call
# Expected
Record should be off
# Current
Record is on, even if it's not recording# Scenario
+ start call
+ Launch a record
+ Stop a call
+ Start a call
# Expected
Record should be off
# Current
Record is on, even if it's not recordingSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/568Crash in conversationRepository2021-11-12T18:33:16ZSébastien BlinCrash in conversationRepository```
[1624127455.501|10853|jamiaccount.cpp :3833 ] Something went wrong when cloning conversation: Couldn't clone repository
[1624127455.506|15742|sip_utils.cpp :278 ] Registered thread 0x7ffe2f7fe428 (0x2A33)
[1624127455.510|10978...```
[1624127455.501|10853|jamiaccount.cpp :3833 ] Something went wrong when cloning conversation: Couldn't clone repository
[1624127455.506|15742|sip_utils.cpp :278 ] Registered thread 0x7ffe2f7fe428 (0x2A33)
[1624127455.510|10978|conversationrepository.cpp:1890 ] Start clone in /home/cyrille/.local/share/jami/fb33489037813e47/conversations/1bbe92a272e1207d6f1f37069bf3486110e7c166
--Type <RET> for more, q to quit, c to continue without paging--
Thread 1 "dring" received signal SIGSEGV, Segmentation fault.
0x0000555555feb844 in git_repository_workdir ()
(gdb) bt
#0 0x0000555555feb844 in git_repository_workdir ()
#1 0x0000555555ca350d in jami::ConversationRepository::infosabi:cxx11 const (this=0x7ffef801ae80) at conversationrepository.cpp:2972
#2 0x0000555555c7a0fb in jami::Conversation::infosabi:cxx11 const (
this=0x7fff640285d0) at conversation.cpp:943
#3 0x00005555557ef2f4 in jami::JamiAccount::conversationInfos (
this=0x7fffd0000b70,
conversationId="1bbe92a272e1207d6f1f37069bf3486110e7c166")
at jamiaccount.cpp:3987
#4 0x0000555555767dfa in DRing::conversationInfos (
accountId="fb33489037813e47",
conversationId="1bbe92a272e1207d6f1f37069bf3486110e7c166")
at conversation_interface.cpp:96
#5 0x000055555571ea62 in DBusConfigurationManager::conversationInfos(std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()
#6 0x0000555555731898 in cx::ring::Ring::ConfigurationManager_adaptor::_conversationInfos_stub(DBus::CallMessage const&) ()
#7 0x0000555555738172 in DBus::Callback<cx::ring::Ring::ConfigurationManager_adaptor, DBus::Message, DBus::CallMessage const&>::call(DBus::CallMessage const&) const ()
--Type <RET> for more, q to quit, c to continue without paging--
age const&) ()
#9 0x000055555574699a in DBus::ObjectAdaptor::handle_message(DBus::Message const&) ()
#10 0x0000555555743f06 in DBus::ObjectAdaptor::Private::message_function_stub(DBusConnection, DBusMessage, void*) ()
#11 0x00007ffff7f78270 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#12 0x00007ffff7f67f54 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#13 0x00005555557394b0 in DBus::Connection::Private::do_dispatch() ()
#14 0x000055555573b6d2 in DBus::Dispatcher::dispatch_pending(std::__cxx11::list<DBus::Connection::Private, std::allocator<DBus::Connection::Private> >&) ()
#15 0x000055555573b7cf in DBus::Dispatcher::dispatch_pending() ()
#16 0x000055555573cd2f in DBus::BusDispatcher::enter() ()
#17 0x00005555556ad40e in DBusClient::event_loop() ()
#18 0x00005555556a59b8 in main ()
(gdb)
```Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1277Call UI not shown when being answered2021-11-12T02:56:37ZPier-Luc ThériaultCall UI not shown when being answeredBug report form
---------------
## OS
Debian
## Jami daemon version:
10.1.0-e8dbf2af93
## Jami GNOME client version:
6dcd20b4489d303e8fcae996a4d83ab7c2e5d875
## Where did you get Jami?
<!-- (add an x in between the square bracket...Bug report form
---------------
## OS
Debian
## Jami daemon version:
10.1.0-e8dbf2af93
## Jami GNOME client version:
6dcd20b4489d303e8fcae996a4d83ab7c2e5d875
## Where did you get Jami?
<!-- (add an x in between the square brackets to select an option) -->
- [ ] My OS package manager (e.g. apt, yum, pacman)
- [ ] I downloaded it from jami.net
- [x] I built it from source using the build.py script
- [ ] I built it from source manually or other (please explain):
## Steps to reproduce bug
Steps:
1.Open Jami
2.Make a call
3.Wait for connection
## What you expect to happen:
When the other side picks up the call UI is shown.
## What happens instead:
The connecting interface is kept with the Talking label.
I need to click the contact to see the call ui.
## Additional information
At that moment I am already listening to my asterisk music
![connecting](/uploads/7cf2b7e00ecfe8d27fe69f3ec6079b66/connecting.png)
It should look like this:
![call-ui](/uploads/8fd36bf6cb3d81068d5af0ded0d435cb/call-ui.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1005(Feature request) display progress of media sending/downloading2021-11-11T14:57:59ZhardBSDk(Feature request) display progress of media sending/downloadinghttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1318https://git.jami.net/savoirfairelinux/jami-project/-/issues/1318https://git.jami.net/savoirfairelinux/jami-project/-/issues/1344Send files2021-11-11T14:30:20Zsmit smitSend filesWhen trying to send a file to the interlocutor, jamie tries to open a NEW connection, which is impossible on the open Internet. And file transfer is not working.
It is necessary to change the algorithm, use RELATED connections or post o...When trying to send a file to the interlocutor, jamie tries to open a NEW connection, which is impossible on the open Internet. And file transfer is not working.
It is necessary to change the algorithm, use RELATED connections or post on a third-party resource and throw a link. P2P will not work.https://git.jami.net/savoirfairelinux/jami-project/-/issues/1340Can't delete messages option on Linux2021-11-11T14:12:23ZNikolaY DimitrovCan't delete messages option on LinuxThere is no way to delete messages on Linux's Jami after last update Version: 202111051449. And messages gets gray to black immediately, but are not send.
Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
Deskto...There is no way to delete messages on Linux's Jami after last update Version: 202111051449. And messages gets gray to black immediately, but are not send.
Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 7.5.0
Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionichttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1343chats2021-11-11T14:12:22Zsmit smitchatsafter the updates received in September-November, the ability to delete messages from the chat disappeared.after the updates received in September-November, the ability to delete messages from the chat disappeared.https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1241account settings, connectivity, "Auto registration after expired" is only for...2021-11-10T20:20:32ZSébastien Blinaccount settings, connectivity, "Auto registration after expired" is only for SIPAmin BandaliAmin Bandalihttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/589Typing indicator: can contains duplicates2021-11-10T16:07:47ZSébastien BlinTyping indicator: can contains duplicatesSébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1017CALL: UI v.22021-11-10T15:37:59ZMaxime CalletCALL: UI v.2Preview:
![299c9d6f-5125-4988-b738-f7097a0ab964](/uploads/cd543b9c2cb4ee6266f060dc915bba44/299c9d6f-5125-4988-b738-f7097a0ab964.png)
**FEATURES:**
Must have:
- [x] bottomSheet: Implement a bottomsheet with 3 states (collapsed/half/ex...Preview:
![299c9d6f-5125-4988-b738-f7097a0ab964](/uploads/cd543b9c2cb4ee6266f060dc915bba44/299c9d6f-5125-4988-b738-f7097a0ab964.png)
**FEATURES:**
Must have:
- [x] bottomSheet: Implement a bottomsheet with 3 states (collapsed/half/extended)
- [x] bottomSheet: size scaling based on display size/density
- [x] bottomSheet: Implement the new ui logic for conference participants
- [x] UI: Handle Insets for system elements (navigation bar / status bar)
- [x] UI: Reduce size of preview
- [x] UI: Implement new android API for fullscreen
Good to have:
_if not ready will be part of an update later_
- [ ] bottomSheet: Implement the new ui logic for plugins
- [ ] Fix screen sharing issuesMaxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/499Audio only: Show Screen share2021-11-10T15:11:32ZSébastien BlinAudio only: Show Screen share![image](/uploads/c89bcc33a6013b080f0db52331d92882/image.png)
Screen share is possible.![image](/uploads/c89bcc33a6013b080f0db52331d92882/image.png)
Screen share is possible.Jami for educationAline Gondim SantosAline Gondim Santos2021-11-09https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/580Crash on frame updated (race condtion)2021-11-10T15:11:20ZSébastien BlinCrash on frame updated (race condtion)```
:191 ] [ShmHolder:Jami Daemon_shm_54741_3] New size: f=3686400, a=7372903
[1635450021.300|54865|sinkclient.cpp :191 ] [ShmHolder:Jami Daemon_shm_54741_1] New size: f=898560, a=1797223
[1635450021.312|54865|sinkclient.cpp :191...```
:191 ] [ShmHolder:Jami Daemon_shm_54741_3] New size: f=3686400, a=7372903
[1635450021.300|54865|sinkclient.cpp :191 ] [ShmHolder:Jami Daemon_shm_54741_1] New size: f=898560, a=1797223
[1635450021.312|54865|sinkclient.cpp :191 ] [ShmHolder:Jami Daemon_shm_54741_2] New size: f=921600, a=1843303
--Type <RET> for more, q to quit, c to continue without paging--
Thread 1 "jami-qt" received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:383
383 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: Aucun fichier ou dossier de ce type.
(gdb) bt
#0 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:383
#1 0x00005555555ce889 in ?? ()
#2 0x00007ffff59beb4e in ?? () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#3 0x00007ffff7d92e69 in lrc::api::AVModel::frameUpdated(QString const&) () from /usr/lib/libringclient.so.1.0.0
#4 0x00007ffff59b56c9 in QObject::event(QEvent*) () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#5 0x00007ffff70b6dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libqt-jami/lib/libQt5Widgets.so.5
#6 0x00007ffff70bfbb8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-jami/lib/libQt5Widgets.so.5
#7 0x00007ffff5987b2a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#8 0x00007ffff598a431 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#9 0x00007ffff59e2dd7 in ?? () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#10 0x00007ffff767f17d in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff767f400 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff767f4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff59e2432 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#14 0x00007ffff598663b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#15 0x00007ffff598e7e4 in QCoreApplication::exec() () from /usr/lib/libqt-jami/lib/libQt5Core.so.5
#16 0x0000555555596110 in main ()
```
Origin in `FrameWrapper::slotFrameUpdated(const QString& id)` there is a reserve instead a resize, which can cause the issue, however, there is no reason to not use storage.Sébastien BlinSébastien Blinhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/588Duplicate items in the conversation list2021-11-10T10:42:07ZovariDuplicate items in the conversation listThe conversation list has duplicates of some, but not all, of the conversations.
Seems to be a regression since the update to Version: 202111041938.
Are you able to reproduce? And fix?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt...The conversation list has duplicates of some, but not all, of the conversations.
Seems to be a regression since the update to Version: 202111041938.
Are you able to reproduce? And fix?
Thank you
Linux Mint 20.2 Cinnamon<br>
client-qt Version: 202111041938 deb editionhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/979Android: New features (possible)?2021-11-09T21:21:09ZElysAndroid: New features (possible)?I am not sure if it is possible to implement these new features -but I want to suggest the following:
1) Camera zoom: using twinme (during a video call, Link: https://twin.me/en/ ) it is possible to zoom in and out. Regarding Jami: Is i...I am not sure if it is possible to implement these new features -but I want to suggest the following:
1) Camera zoom: using twinme (during a video call, Link: https://twin.me/en/ ) it is possible to zoom in and out. Regarding Jami: Is it possible to allow to change the zoom during the video call?
For example: https://www.youtube.com/watch?v=5OSilg9pCTc
2) Telegram (Android) now enables you to share your screen AND camera AT THE SAME TIME!
Desktop (Windows): I once got the answer: https://git.jami.net/savoirfairelinux/ring-project/-/issues/1210
> [a virtual cam] will always be more powerful than any API.
What about android? Would it be possible to share my screen and the front or rear camera of my phone at the same time?
(Because it should be possible using Telegram: https://telegram.org/blog/group-video-calls?ln=r )https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/591Screen sharing is black/empty on GNU/Linux2021-11-09T21:03:55ZAltonsScreen sharing is black/empty on GNU/Linux## Describe your environment
Please specify the following:
- OS: Fedora 35, Gnome with Wayland
- Jami version: 202111042021
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. ...## Describe your environment
Please specify the following:
- OS: Fedora 35, Gnome with Wayland
- Jami version: 202111042021
- What build you are using: jami.net
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
2. Start a video call
3. Try to share the screen
4. Select one screen to share (all appear black on the preview)
- Actual result: The screen sharing is just black with the mouse appearing
- Expected result: The screen should properly be shared! (not just black) Moreover on Gnome desktop the native screen sharing should be used for a better user experience and intergration in Gnome desktop.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1026Can trigger calls with return from PiP2021-11-09T20:44:10ZSébastien BlinCan trigger calls with return from PiP# Scenario
+ Open Jami
+ Launch a call
+ Go in PiP mode (via Home)
+ Return from the PiP to the call
+ Press on return (not home)
=> This open the launcher without PiP
+ Click on Overview and select the latest Jami
=> A new call is l...# Scenario
+ Open Jami
+ Launch a call
+ Go in PiP mode (via Home)
+ Return from the PiP to the call
+ Press on return (not home)
=> This open the launcher without PiP
+ Click on Overview and select the latest Jami
=> A new call is launched, there is two instances of Jami with 2 active calls.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/127Support Qt 5.142021-11-05T20:42:21ZAndreas TraczykSupport Qt 5.14At least Fedora 32 Qt distro packages are 5.14, so this would help with eventually distributing jami-qt and allow for containerized tests and builds.
* [x] verify qt 5.14 support for linux distributions and docker images
* [x] verify ...At least Fedora 32 Qt distro packages are 5.14, so this would help with eventually distributing jami-qt and allow for containerized tests and builds.
* [x] verify qt 5.14 support for linux distributions and docker images
* [x] verify breakage in the interop layer
* [x] verify breakage the qml ui
* [x] verify the windows build and toolset requirementsAlbert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1338the jami interface in android 5.1 is distorted2021-11-05T18:42:12Zhigol higolthe jami interface in android 5.1 is distorted![Screenshot_2021-09-22-15-05-13](/uploads/049ed03880e3369461886fd51326f0c5/Screenshot_2021-09-22-15-05-13.jpg)![Screenshot_2021-11-05-18-07-48](/uploads/8187f58fd724d857706c3d7304c4300c/Screenshot_2021-11-05-18-07-48.png)![Screenshot_2021-09-22-15-05-13](/uploads/049ed03880e3369461886fd51326f0c5/Screenshot_2021-09-22-15-05-13.jpg)![Screenshot_2021-11-05-18-07-48](/uploads/8187f58fd724d857706c3d7304c4300c/Screenshot_2021-11-05-18-07-48.png)Maxime CalletMaxime Callethttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1337The incoming call is displayed for 30 seconds, no more2021-11-05T12:50:12ZIvan DanyliukThe incoming call is displayed for 30 seconds, no moreI use my own sip account
the incoming call is displayed for 30 seconds and is interrupted
on the sip server there are no restrictions, tested on other softphones, everything works
can i adjust this somehow in the settings jami?
Jami Dae...I use my own sip account
the incoming call is displayed for 30 seconds and is interrupted
on the sip server there are no restrictions, tested on other softphones, everything works
can i adjust this somehow in the settings jami?
Jami Daemon 10.1.0 (linux)
Linux-Mint 19-20https://git.jami.net/savoirfairelinux/jami-client-ios/-/issues/149segfault crash directly at startup2021-11-05T00:00:50ZStéphane Guillousegfault crash directly at startupHi there
I am using the following versions:
* iOS 14.8 on an iPhone 6s
* Jami 3.22 (but was already crashing with previous version)
I see the logo when opening it but it then straight away disappears.Hi there
I am using the following versions:
* iOS 14.8 on an iPhone 6s
* Jami 3.22 (but was already crashing with previous version)
I see the logo when opening it but it then straight away disappears.