savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2021-12-23T02:54:15Zhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1052download jami android from official site2021-12-23T02:54:15Zhigol higoldownload jami android from official siteThere is a request, please make a direct link to download jami for android from the official site, so that users do not depend on google play, which many do not have and from f-droid, which has not been updated for a long time. Telegram,...There is a request, please make a direct link to download jami for android from the official site, so that users do not depend on google play, which many do not have and from f-droid, which has not been updated for a long time. Telegram, WhatsApp and many other applications can be downloaded from their official sites, why can't you do the same?https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/34Text of hoverable button for opening file dialog in settings does not update ...2021-12-22T21:21:18ZAndreas TraczykText of hoverable button for opening file dialog in settings does not update when selected file changesItération 21https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/33Crash when caller hangs up before peer answered2021-12-22T21:21:17ZGuillaume HellerCrash when caller hangs up before peer answeredItération 21Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/32Incoming call UI needs attention2021-12-22T21:21:17ZAndreas TraczykIncoming call UI needs attentionI have noticed a couple bugs in the incoming call UI/UX mechanisms:
1. Incoming call notify dialog is sometimes not shown at all
2. The smart-list item corresponding to an incoming call is not correctly decorated
It's very likely that t...I have noticed a couple bugs in the incoming call UI/UX mechanisms:
1. Incoming call notify dialog is sometimes not shown at all
2. The smart-list item corresponding to an incoming call is not correctly decorated
It's very likely that the custom UI for the incoming call notifications will be replaced with a native solution, AND that in the event of the user being focused on the main window, that a primary
incoming call view is displayed.Itération 21Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/30Crash when declining incoming call (regression from the search api changes)2021-12-22T21:21:17ZSébastien BlinCrash when declining incoming call (regression from the search api changes)When declining an incoming call, the client is crashing.When declining an incoming call, the client is crashing.Itération 21Albert Babí OllerAlbert Babí Ollerhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/29Update doc + README2021-12-22T21:21:17ZSébastien BlinUpdate doc + READMEhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/28Verify migration from old client2021-12-22T21:21:17ZSébastien BlinVerify migration from old clientItération 21Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/27Update credit + version name2021-12-22T21:21:17ZSébastien BlinUpdate credit + version nameItération 21https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/26Send audio message, send video message at a wrong position2021-12-22T21:21:17ZSébastien BlinSend audio message, send video message at a wrong positionItération 21Andreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/25Media resize crash on linux2021-12-22T21:21:17ZSébastien BlinMedia resize crash on linuxhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/24Chatview lagguy when sending multiple messages2021-12-22T21:21:17ZSébastien BlinChatview lagguy when sending multiple messagesItération 21https://git.jami.net/savoirfairelinux/jami-client-gnome/-/issues/1283jami-qt seg-faults on exit2021-12-22T21:21:15Zw5pnyjami-qt seg-faults on exitOn a Dell Precision T5820 workstation running Ubuntu 20.04, jami-qt version 202112221430
from https://dl.jami.net/stable/ubuntu_20.04/ seg-faults on exit.
To reproduce:
1) Close jami
2) right click jami icon in system tray
3) choose ...On a Dell Precision T5820 workstation running Ubuntu 20.04, jami-qt version 202112221430
from https://dl.jami.net/stable/ubuntu_20.04/ seg-faults on exit.
To reproduce:
1) Close jami
2) right click jami icon in system tray
3) choose quit
Seg-fault results from the "quit"
running gdb on jami-qt and going through the above steps yields:
.
.
.
[1640205228.075|58994|sipvoiplink.cpp :750 ] Shutdown SIPVoIPLink@0x5555575a5620...
[1640205228.075|58994|siptransport.cpp :193 ] destroying SipTransportBroker@0x5555567850b0
[Thread 0x7fff5f7fe700 (LWP 2483891) exited]
[1640205228.810|58994|sipvoiplink.cpp :768 ] SIPVoIPLink@0x5555575a5620 is shutdown
[Thread 0x7fff5ffff700 (LWP 2483890) exited]
[Thread 0x7fff0affd700 (LWP 2483924) exited]
--Type <RET> for more, q to quit, c to continue without paging--
Thread 1 "jami-qt" received signal SIGSEGV, Segmentation fault.
0x00007ffff7acf4d2 in std::_Rb_tree<QString, std::pair<QString const, std::pair<lrc::api::account::Info, std::shared_ptr<lrc::Database> > >, std::_Select1st<std::pair<QString const, std::pair<lrc::api::account::Info, std::shared_ptr<lrc::Database> > > >, std::less<QString>, std::allocator<std::pair<QString const, std::pair<lrc::api::account::Info, std::shared_ptr<lrc::Database> > > > >::find(QString const&) () from /usr/lib/libringclient.so.1.0.0
(gdb) bt
#0 0x00007ffff7acf4d2 in std::_Rb_tree<QString, std::pair<QString const, std::pair<lrc::api::account::Info, std::shared_ptr<lrc::Database> > >, std::_Select1st<std::pair<QString const, std::pair<lrc::api::account::Info, std::shared_ptr<lrc::Database> > > >, std::less<QString>, std::allocator<std::pair<QString const, std::pair<lrc::api::account::Info, std::shared_ptr<lrc::Database> > > > >::find(QString const&) () at /usr/lib/libringclient.so.1.0.0
#1 0x00007ffff7ac48b1 in lrc::api::NewAccountModel::getAccountInfo(QString const&) const ()
at /usr/lib/libringclient.so.1.0.0
#2 0x0000555555633f68 in ()
#3 0x00005555555a222d in ()
#4 0x00005555555a9c93 in ()
#5 0x00007ffff6bfcbe5 in () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#6 0x00007ffff6ac5675 in () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#7 0x00007ffff6ac7777 in () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#8 0x00007ffff6ac866a in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#9 0x00007ffff6ae80f1 in () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#10 0x00007ffff6aea02f in () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#11 0x00007ffff6a7724d in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#12 0x00007ffff6c1cfa7 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#13 0x00007ffff6bc08ae in QQmlBoundSignalExpression::evaluate(void**) ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
--Type <RET> for more, q to quit, c to continue without paging--
#14 0x00007ffff6bc1948 in () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#15 0x00007ffff6bfc64d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#16 0x00007ffff6b9efbf in QQmlData::signalEmitted(QAbstractDeclarativeData*, QObject*, int, void**) () at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#17 0x00007ffff56f96d5 in () at /usr/lib/libqt-jami/lib/libQt5Core.so.5
#18 0x00007ffff6bbcfe9 in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#19 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#20 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#21 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#22 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#23 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#24 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#25 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#26 0x00007ffff6bbd00f in QQmlContextData::emitDestruction() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#27 0x00007ffff6bbd0fd in QQmlContextData::invalidate() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#28 0x00007ffff6b9dac4 in QQmlPrivate::qdeclarativeelement_destructor(QObject*) ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#29 0x00007fff7460bf99 in ()
at /usr/lib/libqt-jami/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so
#30 0x00007ffff6c284ae in QQmlApplicationEnginePrivate::cleanUp() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#31 0x00007ffff6c284fd in QQmlApplicationEngine::~QQmlApplicationEngine() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#32 0x00007ffff6c2851d in QQmlApplicationEngine::~QQmlApplicationEngine() ()
at /usr/lib/libqt-jami/lib/libQt5Qml.so.5
#33 0x00005555555d5063 in ()
#34 0x000055555559936f in main ()
(gdb)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/452settings ui: toggle switch states in dark mode appear inverted(colors)2021-12-22T20:40:41ZAndreas Traczyksettings ui: toggle switch states in dark mode appear inverted(colors)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/484Superposition of 2 contacts2021-12-22T20:38:31ZovariSuperposition of 2 contacts1. Call yourself, then end the conversation.
2. `Find a user or search for a conversation` and type a contact in your list, say `amarok` (but not yourself)<br>
![image](/uploads/3491ac8542ef2c695c658a23cad7ac61/image.png)
3. Click on the...1. Call yourself, then end the conversation.
2. `Find a user or search for a conversation` and type a contact in your list, say `amarok` (but not yourself)<br>
![image](/uploads/3491ac8542ef2c695c658a23cad7ac61/image.png)
3. Click on the contact<br>
![image](/uploads/d0574ea281da42fb8303ecbd905d4d6a/image.png)
4. Press the `×` which has the tooltip `Clear Text`<br>
![image](/uploads/dc6d045b25d8ac344076e9c1081b5186/image.png)
5. Bug: the first item in the list is an overlap of 2 contacts, i.e. yourself and amarok.<br>
a) Light theme<br>
![Light theme](/uploads/8e5a17b3ac3cd778b6d8fbb0dee0fd0f/image.png)<br>
b) Dark theme<br>
![Dark theme](/uploads/c86eb11dd94fd00a4d5b636d38c048ca/image.png)
Are you able to reproduce and fix?
Thank you
Jami-client-qt Version: 202106061341 deb edition<br>
Linux Mint 20.2 Cinnamonhttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/561(Feature request) Cache2021-12-22T20:37:33ZhardBSDk(Feature request) Cachehttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1323https://git.jami.net/savoirfairelinux/jami-project/-/issues/1323https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/560(Feature request) Typing indicators on chat's top bar2021-12-22T20:37:30ZhardBSDk(Feature request) Typing indicators on chat's top barhttps://git.jami.net/savoirfairelinux/jami-project/-/issues/1322https://git.jami.net/savoirfairelinux/jami-project/-/issues/1322https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/569Can't start two instances of Jami on one system2021-12-22T20:37:28ZvstoykovbgCan't start two instances of Jami on one systemI am trying to open two instances of Jami under different users on my Ubuntu 18 system.
I am using Jami installed via snap.
If I try to run a second instance of Jami at the same time I get these error message:
$ jami
Testing...I am trying to open two instances of Jami under different users on my Ubuntu 18 system.
I am using Jami installed via snap.
If I try to run a second instance of Jami at the same time I get these error message:
$ jami
Testing for explicit PulseAudio choice...
Testing for ALSA permissions...
...defaulting to using PulseAudio.
Qt: Session management error: Could not open network socket
"notify server name: gnome-shell, vendor: GNOME, version: 3.28.4, spec: 1.2"
Destroying connectivity monitor
Version: 202109292221
On a multi-user operating system there should not be such a problem. I do not encounter similar problem when I run browsers for example.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/399High cpu consumption while video call despite hardware acceleration turned on2021-12-22T20:37:04ZDoS007High cpu consumption while video call despite hardware acceleration turned onvideo call from windows to ipad results in very high cpu consumption, although i activated hardware acceleration on my windows surface. This made my surface pro 7 i5 turn off because of overheating several times. Don't understand why thi...video call from windows to ipad results in very high cpu consumption, although i activated hardware acceleration on my windows surface. This made my surface pro 7 i5 turn off because of overheating several times. Don't understand why this is happening, the hardware acceleration for h.264 should do everything. I don't understand why cpu consumption is so high (camera is 720p an 2 Mbit/s configured on jami windows with hardware acceleration turned on; hardware acceleration is also turned on on ipad pro 12.9).
It seems like hardware acceleration on windows is not working.
![image](/uploads/3c8e6c174a6f83ec548fdea2de94fd4c/image.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/549202109292122 segfaults at 720p webcam resolution2021-12-22T20:33:49Zxorbug202109292122 segfaults at 720p webcam resolutionHi,
today, after upgrading to _202109292122_, Jami crashed everytime it tried to acquire the camera. I could not even look into the audio/video settings anymore since opening that section of the settings would trigger the camera on, and ...Hi,
today, after upgrading to _202109292122_, Jami crashed everytime it tried to acquire the camera. I could not even look into the audio/video settings anymore since opening that section of the settings would trigger the camera on, and the client crashed.
In order to reset it to default settings but with the goal of setting it back to a higher resolution later, I removed _.config/jami/dring.yml*_ and restarted. At this point the camera was set to a lower (default) res, and the client not crashing. But as soon as I set it to 720p resolution, the client segfaulted again.
This is what is printed in the console starting from the moment I click and select the 720p resolution:
```
[1632994994.012| 7757|manager.cpp :1918 ] Saving Configuration to XDG directory /home/user/.config/jami/dring.yml
[1632994994.074| 7847|sinkclient.cpp :481 ] [Sink:0x560ef3607a30] Stopped - size=0x0, mixer=No
[1632994994.074| 7847|sinkclient.cpp :494 ] [Sink:0x560ef3607a30] Change frame position from [0, 0] to [0, 0]
[1632994994.075| 7847|video_input.cpp :209 ] VideoInput closed
[1632994994.076| 7757|sinkclient.cpp :333 ] [Sink:0x560ef35590d0] Sink [local] created
[1632994994.076| 7757|video_input.cpp :521 ] MRL: 'camera://Microsoft_Microsoft®_LifeCam_HD-3000'
[1632994994.076| 7757|audio_input.cpp :266 ] Switching audio source to match 'camera://Microsoft_Microsoft®_LifeCam_HD-3000'
[1632994994.076| 7757|threadloop.cpp :74 ] already started
[1632994994.076| 7852|sinkclient.cpp :191 ] [ShmHolder:Jami Daemon_shm_7757_0] New size: f=0, a=103
[1632994994.076| 7852|sinkclient.cpp :158 ] [ShmHolder:Jami Daemon_shm_7757_0] New holder created
[1632994994.076| 7852|sinkclient.cpp :282 ] [Sink:0x560ef35590d0] Shared memory [Jami Daemon_shm_7757_0] created
[1632994994.076| 7852|video_input.cpp :170 ] VideoInput ready to capture
[1632994994.076| 7852|media_decoder.cpp :127 ] Trying to open device /dev/video0 with format video4linux2, pixel format mjpeg, size 1280x720, rate 30,000000
[1632994994.303| 7852|media_decoder.cpp :145 ] Using format video4linux2
[1632994994.406| 7852|accel.cpp :204 ] -- Starting decoding init for cuda with default device.
[1632994994.406| 7852|media_decoder.cpp :495 ] Decoding video using MJPEG (Motion JPEG) (mjpeg)
[1632994994.406| 7852|media_decoder.cpp :505 ] Not using hardware decoding for mjpeg
[mjpeg @ 0x7fa090026640] overread 8
[1632994994.422| 7852|sinkclient.cpp :473 ] [Sink:0x560ef35590d0] Started - size=1280x720, mixer=No
[1632994994.422| 7852|sinkclient.cpp :191 ] [ShmHolder:Jami Daemon_shm_7757_0] New size: f=3686400, a=7372903
[1632994994.431| 7852|video_input.cpp :333 ] created decoder with video params : size=1280X720, fps=30,000000 pix=yuvj422p
[1632994994.431| 7852|sinkclient.cpp :473 ] [Sink:0x560ef35590d0] Started - size=1280x720, mixer=No
<here it segfaults>
```
Maybe it's something with the camera (which btw was working fine until now with the previous Jami version)? I also upgraded another machine (different hardware), and there is no problem with the old settings (camera at 720p as well, working as before).
Thanks.https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/131Contact request from removed contact cannnot be refused2021-12-22T20:32:35ZMing Rui ZhangContact request from removed contact cannnot be refused