savoirfairelinux issueshttps://git.jami.net/groups/savoirfairelinux/-/issues2023-12-27T18:02:17Zhttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/661unknown PortAudio functions2023-12-27T18:02:17ZNick Econopoulyunknown PortAudio functionsWhere are the functions `Pa_GetDefaultCommInputDevice()` and `Pa_GetDefaultCommOutputDevice();`? I can't find them in the PortAudio API.
(In `src/media/audio/portaudio/portaudiolayer.cpp` line 482)
If I replace them with their analogs...Where are the functions `Pa_GetDefaultCommInputDevice()` and `Pa_GetDefaultCommOutputDevice();`? I can't find them in the PortAudio API.
(In `src/media/audio/portaudio/portaudiolayer.cpp` line 482)
If I replace them with their analogs `Pa_GetDefaultInputDevice()` and `Pa_GetDefaultOutputDevice`, I get a linking error:
```
FAILED: bin/dbus/jamid
c++ -o bin/dbus/jamid bin/dbus/jamid.p/dbuscallmanager.cpp.o bin/dbus/jamid.p/dbusclient.cpp.o bin/dbus/jamid.p/dbusconfigurationmanager.cpp.o bin/dbus/jamid.p/dbusinstance.cpp.o bin/dbus/jamid.p/dbuspresencemanager.cpp.o bin/dbus/jamid.p/main.cpp.o bin/dbus/jamid.p/dbusvideomanager.cpp.o bin/dbus/jamid.p/dbuspluginmanagerinterface.cpp.o -Wl,--as-needed -Wl,--no-undefined -Wl,--start-group src/libjami.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libdbus-c++-1.a /usr/lib/libdbus-1.so -pthread /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libopendht.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libhttp_parser.a /usr/lib/libgnutls.so /usr/lib/libnettle.so /usr/lib/libargon2.so -lrt -ldl /usr/lib/libjsoncpp.so /usr/lib/libssl.so /usr/lib/libcrypto.so /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjsua2-x86_64-pc-linux-gnu.a /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../lib/libstdc++.so /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjsua-x86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjsip-ua-x
86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-g
nu/lib/libpjsip-simple-x86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/c
ontrib/x86_64-pc-linux-gnu/lib/libpjsip-x86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/
src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjmedia-codec-x86_64-pc-linux-gnu.a /home/wryco
de/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjmedia-videodev-x86_6
4-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/l
ib/libpjmedia-audiodev-x86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/c
ontrib/x86_64-pc-linux-gnu/lib/libpjmedia-x86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-gi
t/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjnath-x86_64-pc-linux-gnu.a /home/wrycode/bu
ild/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpjlib-util-x86_64-pc-linux-
gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libpj-x8
6_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gn
u/lib/libsrtp-x86_64-pc-linux-gnu.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x8
6_64-pc-linux-gnu/lib/libyuv-x86_64-pc-linux-gnu.a /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../.
./../lib/libopus.so /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../lib/libvpx.so /usr/lib/gcc
/x86_64-pc-linux-gnu/11.1.0/../../../../lib/libuuid.so -lm -lpthread /usr/lib/gcc/x86_64-pc-linux-
gnu/11.1.0/../../../../lib/libgnutls.so /usr/lib/libgit2.so /usr/lib/libsecp256k1.so /usr/lib/liba
vcodec.so /usr/lib/libavfilter.so /usr/lib/libavdevice.so /usr/lib/libavformat.so /usr/lib/libswsc
ale.so /usr/lib/libswresample.so /usr/lib/libavutil.so /usr/lib/libspeexdsp.so /home/wrycode/build
/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libfmt.a /usr/lib/libyaml-cpp.so
/usr/lib/libz.so /usr/lib/libasound.so /usr/lib/libpulse.so /usr/lib/libjack.so /usr/lib/libportau
dio.so /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libupnp
.a /home/wrycode/build/jami-daemon-git/src/ring-daemon/contrib/x86_64-pc-linux-gnu/lib/libixml.a -
lnatpmp /usr/lib/libwebrtc_audio_processing.so /usr/lib/libudev.so /usr/lib/libarchive.so -Wl,--en
d-group
/usr/bin/ld: src/libjami.a(jamidht_jamiaccount.cpp.o): in function `std::_MakeUniq<jami::TransferC
hannelHandler>::__single_object std::make_unique<jami::TransferChannelHandler, std::shared_ptr<jam
i::JamiAccount>, jami::ConnectionManager&>(std::shared_ptr<jami::JamiAccount>&&, jami::ConnectionM
anager&)':
/usr/include/c++/11.1.0/bits/unique_ptr.h:962: undefined reference to `jami::TransferChannelHandle
r::TransferChannelHandler(std::shared_ptr<jami::JamiAccount> const&, jami::ConnectionManager&)'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
```https://git.jami.net/savoirfairelinux/jami-daemon/-/issues/779conference: detached host appearing2023-12-27T18:01:47ZAline Gondim Santosconference: detached host appearingJoin a rdv from two different devices;
Crash one of them (force jami quit without correctly ending the call)
On the other one you will see the host in the place of this crashed participant. If the crashed participant is still there (a ...Join a rdv from two different devices;
Crash one of them (force jami quit without correctly ending the call)
On the other one you will see the host in the place of this crashed participant. If the crashed participant is still there (a frozen component), you can change the layout one or two times and the host will take its place.
Expected: the crashed participant should disappear and the host should not take its place.Aline Gondim SantosAline Gondim Santoshttps://git.jami.net/savoirfairelinux/jami-daemon/-/issues/887no video and audio in android - iOS call2023-12-27T17:50:47ZKateryna Kostiukno video and audio in android - iOS callWhen android and iOS are on LTE, there is no media in the call when the client that receives the call has TURN disabled.When android and iOS are on LTE, there is no media in the call when the client that receives the call has TURN disabled.Kateryna KostiukKateryna Kostiukhttps://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-client-qt/-/issues/226Video conferences: cannot merge between active calls on 2 different accounts2023-12-27T16:38:01ZSébastien BlinVideo conferences: cannot merge between active calls on 2 different accounts# Scenario
+ Add a conference call
+ start another call on snoyhrt svvouny
# Expected
+ Via the add participant, we should be able to merge the call and the conference call
# Current
Can only add other contacts
# User story
+ This...# Scenario
+ Add a conference call
+ start another call on snoyhrt svvouny
# Expected
+ Via the add participant, we should be able to merge the call and the conference call
# Current
Can only add other contacts
# User story
+ This allow merging between public/private accounts or Jami/SIP bridginghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/182Distorted sound when output device is changed from default2023-12-27T16:37:45ZnorstboxDistorted sound when output device is changed from default## Steps to reproduce
1. Open "Setting -> Audio/Video"
2. Set Audio "Output Device" to any specific device, instead of default "Primary Sound Driver"
3. Make voice call
## Current behavior
Sound is drastically distorted
## Expected out...## Steps to reproduce
1. Open "Setting -> Audio/Video"
2. Set Audio "Output Device" to any specific device, instead of default "Primary Sound Driver"
3. Make voice call
## Current behavior
Sound is drastically distorted
## Expected outcome
Sound without distortions
## Version information
202005081537https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1325Network doesn't support video calls2023-12-27T16:32:21ZElysNetwork doesn't support video callsI am using the newest beta version of Jami and Mate 20 Pro (EMUI 12)
Steps to reproduce:
Make a video call (Android -> Desktop)
You'll get this notification:
![Videocall](/uploads/c3a3d011bbad97909e011f570e49d51a/Videocall.png)
I thi...I am using the newest beta version of Jami and Mate 20 Pro (EMUI 12)
Steps to reproduce:
Make a video call (Android -> Desktop)
You'll get this notification:
![Videocall](/uploads/c3a3d011bbad97909e011f570e49d51a/Videocall.png)
I think it's wrong because I've tried like 5 other messengers with video calls without any issues (same network)
Also I think sometimes video calls still work although this notification is shown
AND you can make an audio call and add video.https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1192Buggy UI on latest beta2023-12-27T15:54:30ZMaxim CournoyerBuggy UI on latest beta- Jami version: Android 20230310-01 (Beta channel)
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
...- Jami version: Android 20230310-01 (Beta channel)
- Device model: Galaxy Tab S2
- Android version: 7
- What build you are using: Play Store
## Steps to reproduce
- Can you reproduce the bug: at will
- Steps:
1. Open Jami
- Actual result: UI is mostly blank
- Expected result: UI displays normally
## Additional information
It look like this:
![Screenshot_20230320-134033](/uploads/378c40c559cb2b2b89ee099b096a53c0/Screenshot_20230320-134033.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1247Implement new invitation design2023-12-27T15:40:15ZPierre NicolasImplement new invitation design![image](/uploads/886a98049b3bab229e688a330b9b1dbe/image.png)![image](/uploads/886a98049b3bab229e688a330b9b1dbe/image.png)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1263Invitations2023-12-27T15:40:04ZCharlotte HoffmannInvitationsRevoir le principe d'invitationsRevoir le principe d'invitationsCharlotte HoffmannCharlotte Hoffmannhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1274Send multiple pictures doesn't work properly2023-12-27T15:35:00ZPierre NicolasSend multiple pictures doesn't work properly## Describe your environment
Please specify the following:
- Device model: virtual pixel 6 pro
- Android version: api 33
- What build you are using: your own (commit id = f4d500bb254a313a01d0c9b71f34a4d414ed32e2, daemon commit i...## Describe your environment
Please specify the following:
- Device model: virtual pixel 6 pro
- Android version: api 33
- What build you are using: your own (commit id = f4d500bb254a313a01d0c9b71f34a4d414ed32e2, daemon commit id = e3f0ae1c1b201470e44d880f82c0747ede72b4a1)
## Steps to reproduce
- Can you reproduce the bug: occasionally
- Steps:
1. Go in 1:1 swarm
2. Select multiple pictures
3. Send selection
- Actual result: Sometimes it works (you can see your pictures have been sent), sometimes pictures are not displayed in the conversation making you think it didn't work. In fact, the complete conversation is broken and you can't send anything anymore. You need to restart the app and you will see that everything have been correctly sent.
## Additional information
![impossible_to_send_different_pictures](/uploads/eca14af914f04cbc7697f557cadcbd7e/impossible_to_send_different_pictures.mp4)https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1283Synchronisation between Android and iOS does not work as expected2023-12-27T15:33:46ZannaSynchronisation between Android and iOS does not work as expectedMe on Android and my contact on iOS first have to ring each other or send new messages before sometimes hours-old messages or documents are delivered.
I would expect that when both contacts are shown as online, a synchronisation between...Me on Android and my contact on iOS first have to ring each other or send new messages before sometimes hours-old messages or documents are delivered.
I would expect that when both contacts are shown as online, a synchronisation between both devices takes place. Both in this case between me and my contact, and between me and my computer if the latter is also online with me at the same time.
Világfa - 20230502-01 (F-Droid), latest iOS, latest Linux qthttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1307Reaction emoji picker, find emoji by its name2023-12-27T15:30:12ZWear GuxjReaction emoji picker, find emoji by its nameThe new emoji picker used for reactions is nice, it looks almost the same as the one used by Android's virtual keyboard, but there is one feature missing, that you could enter text to find a certain emoji. Can this be added to Jami as well?The new emoji picker used for reactions is nice, it looks almost the same as the one used by Android's virtual keyboard, but there is one feature missing, that you could enter text to find a certain emoji. Can this be added to Jami as well?https://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1348Implement swarm-history2023-12-27T15:19:17ZPierre NicolasImplement swarm-historyThere is a new API in daemon that give linearized message list (instead of just giving git tree).
It will make the android client code simpler (not having to deal with complete tree but just with linear message list).
Daemon API : http...There is a new API in daemon that give linearized message list (instead of just giving git tree).
It will make the android client code simpler (not having to deal with complete tree but just with linear message list).
Daemon API : https://review.jami.net/c/jami-daemon/+/25055
Qt client implementation: https://review.jami.net/c/jami-client-qt/+/25090Pierre NicolasPierre Nicolashttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/177Implement direct rendering pipeline for cuda hardware decoded frames using d3...2023-12-23T14:08:12ZAndreas TraczykImplement direct rendering pipeline for cuda hardware decoded frames using d3d11/qtDraw AVFrames with the AV_PIX_FMT_CUDA pixel format directly using d3d11 textures.Draw AVFrames with the AV_PIX_FMT_CUDA pixel format directly using d3d11 textures.Yang WangYang Wanghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/130Please use Hei typeface for Chinese2023-12-23T14:07:14ZlinsuiPlease use Hei typeface for ChineseIn version 202010021804 the Chinese font is changed to Song typeface which is a serif typeface. However it's not suitable for UI. Please use Hei typeface instead. Thanks!
Hei
![sshot-002](/uploads/ceab024c516b696ba5f334f3feffdff5/sshot-...In version 202010021804 the Chinese font is changed to Song typeface which is a serif typeface. However it's not suitable for UI. Please use Hei typeface instead. Thanks!
Hei
![sshot-002](/uploads/ceab024c516b696ba5f334f3feffdff5/sshot-002.png)
Song
![sshot-003](/uploads/4239f4c58251d1f53647ec98a343851f/sshot-003.png)https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1105addSwarmConversation incorrect mode2023-12-23T14:06:27ZSébastien BlinaddSwarmConversation incorrect mode`conversation::to_mode(details["mode"].toInt());` does an assumption from the daemon which is not true.
A mode is unknown when syncing, it will be ok after conversationReady`conversation::to_mode(details["mode"].toInt());` does an assumption from the daemon which is not true.
A mode is unknown when syncing, it will be ok after conversationReadyBackloghttps://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/883Functional tests (qml_tests) failures2023-12-23T14:05:02ZMaxim CournoyerFunctional tests (qml_tests) failuresHi,
After applying patches to fix #882 against 20221031.1308.130cc26, I was able to run the tests with a manual procedure borrowed from the `build.py` script (which is currently tailored for Windows):
```scheme
(replace 'check
...Hi,
After applying patches to fix #882 against 20221031.1308.130cc26, I was able to run the tests with a manual procedure borrowed from the `build.py` script (which is currently tailored for Windows):
```scheme
(replace 'check
(lambda* (#:key tests? #:allow-other-keys)
(when tests?
(setenv "QT_QPA_PLATFORM" "offscreen")
(setenv "QT_QUICK_BACKEND" "software")
;; The tests require a writable HOME.
(setenv "HOME" "/tmp")
(display "Running unittests...\n")
(invoke "tests/unittests" "-mutejamid")
(display "Running functional tests...\n")
;; This is to allow building from the source tarball or
;; directly from the git repository.
(let ((tests-qml (if (file-exists? "../client-qt/tests")
"../client-qt/tests/qml"
"../tests/qml")))
(invoke "tests/qml_tests" "-mutejamid"
"-input" tests-qml)))))
```
The unittests all pass, but the qml_tests return some failures:
```
starting phase `check'
Running unittests...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/runtime-nixbld'
(process:2064): libnotify-WARNING **: 20:06:20.854: Failed to connect to proxy
No accounts to migrate
20:06:20.857 os_core_unix.c !pjlib 2.12.1 for POSIX initialized
Daemon is running
[==========] Running 3 tests from 2 test suites.
[----------] Global test environment set-up.
[----------] 2 tests from AccountFixture
[ RUN ] AccountFixture.InitialAccountListCheck
[ OK ] AccountFixture.InitialAccountListCheck (0 ms)
[ RUN ] AccountFixture.CreateSIPAccountTest
error initializing NetworkManager client: Could not connect: No such file or directory
AccountModelPimpl::slotVolatileAccountDetailsChanged, can't find "1d75d198d2a21f3d"
AccountModelPimpl::slotVolatileAccountDetailsChanged, can't find "1d75d198d2a21f3d"
Syncing lrc accounts list with the daemon
"detected new account 1d75d198d2a21f3d"
database "/tmp/.local/share/unittests/jami/1d75d198d2a21f3d/history.db" version set to: "1"
Syncing lrc accounts list with the daemon
Syncing lrc accounts list with the daemon
"detected account removal 1d75d198d2a21f3d"
[ OK ] AccountFixture.CreateSIPAccountTest (4950 ms)
[----------] 2 tests from AccountFixture (4950 ms total)
[----------] 1 test from ContactFixture
[ RUN ] ContactFixture.AddSIPContactTest
AccountModelPimpl::slotVolatileAccountDetailsChanged, can't find "f96505d5790f5317"
AccountModelPimpl::slotVolatileAccountDetailsChanged, can't find "f96505d5790f5317"
Syncing lrc accounts list with the daemon
"detected new account f96505d5790f5317"
database "/tmp/.local/share/jami/f96505d5790f5317/history.db" version set to: "1"
Syncing lrc accounts list with the daemon
Syncing lrc accounts list with the daemon
"detected account removal f96505d5790f5317"
[ OK ] ContactFixture.AddSIPContactTest (14999 ms)
[----------] 1 test from ContactFixture (14999 ms total)
[----------] Global test environment tear-down
[==========] 3 tests from 2 test suites ran. (19950 ms total)
[ PASSED ] 3 tests.
Destroying connectivity monitor
Running functional tests...
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/runtime-nixbld'
(process:2082): libnotify-WARNING **: 20:06:41.435: Failed to connect to proxy
No accounts to migrate
dbus not connected
qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
Can't update current account info data for ""
20:06:41.437 os_core_unix.c !pjlib 2.12.1 for POSIX initialized
Daemon is running
********* Start testing of qml_test *********
Config: Using QtTest library 6.3.1, Qt 6.3.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.3.0), unknown unknown
QWARN : qml_test::tst_ChatViewFooter::compile()
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_ChatViewFooter.qml produced 1 error(s):
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_ChatViewFooter.qml:28,1: "qrc:/src/app/mainview/components": no such directory
Working directory: /tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build
Import paths:
'/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build/tests'
'qrc:/qt-project.org/imports'
'/gnu/store/g0cpw37529bbz2f0zbbwmivpd4igp4w6-qt5compat-6.3.1/lib/qt6/qml'
'/gnu/store/8nlck8a9s88krl7m8a0d36yf3j2b7mv4-qtdeclarative-6.3.1/lib/qt6/qml'
'/gnu/store/k0v5qlk1gkl62d0wspsy9y6khrn5cq0c-qtmultimedia-6.3.1/lib/qt6/qml'
'/gnu/store/1228mp35skd88ijx799v5851paadv9wg-qtwebchannel-6.3.1/lib/qt6/qml'
'/gnu/store/iygnhxwydlwbs1hc9knjvam6im489zyl-qtwebengine-6.3.1/lib/qt6/qml'
Plugin paths:
'.'
FAIL! : qml_test::tst_ChatViewFooter::compile() "qrc:/src/app/mainview/components": no such directory
Loc: [/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_ChatViewFooter.qml(28)]
QWARN : qml_test::UnknownTestFunc() dbus not connected
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() Can't update current account info data for ""
QWARN : qml_test::tst_FilesToSendContainer::compile()
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_FilesToSendContainer.qml produced 1 error(s):
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_FilesToSendContainer.qml:28,1: "qrc:/src/app/mainview/components": no such directory
Working directory: /tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build
Import paths:
'/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build/tests'
'qrc:/qt-project.org/imports'
'/gnu/store/g0cpw37529bbz2f0zbbwmivpd4igp4w6-qt5compat-6.3.1/lib/qt6/qml'
'/gnu/store/8nlck8a9s88krl7m8a0d36yf3j2b7mv4-qtdeclarative-6.3.1/lib/qt6/qml'
'/gnu/store/k0v5qlk1gkl62d0wspsy9y6khrn5cq0c-qtmultimedia-6.3.1/lib/qt6/qml'
'/gnu/store/1228mp35skd88ijx799v5851paadv9wg-qtwebchannel-6.3.1/lib/qt6/qml'
'/gnu/store/iygnhxwydlwbs1hc9knjvam6im489zyl-qtwebengine-6.3.1/lib/qt6/qml'
Plugin paths:
'.'
FAIL! : qml_test::tst_FilesToSendContainer::compile() "qrc:/src/app/mainview/components": no such directory
Loc: [/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_FilesToSendContainer.qml(28)]
QWARN : qml_test::UnknownTestFunc() dbus not connected
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() Can't update current account info data for ""
QWARN : qml_test::UnknownTestFunc() error initializing NetworkManager client: Could not connect: No such file or directory
PASS : qml_test::Local Account Test::initTestCase()
PASS : qml_test::Local Account Test::test_initially_no_account()
PASS : qml_test::Local Account Test::cleanupTestCase()
QWARN : qml_test::UnknownTestFunc() dbus not connected
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() Can't update current account info data for ""
QWARN : qml_test::tst_PresenceIndicator::compile()
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_PresenceIndicator.qml produced 1 error(s):
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_PresenceIndicator.qml:25,1: "qrc:/src/app/commoncomponents": no such directory
Working directory: /tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build
Import paths:
'/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build/tests'
'qrc:/qt-project.org/imports'
'/gnu/store/g0cpw37529bbz2f0zbbwmivpd4igp4w6-qt5compat-6.3.1/lib/qt6/qml'
'/gnu/store/8nlck8a9s88krl7m8a0d36yf3j2b7mv4-qtdeclarative-6.3.1/lib/qt6/qml'
'/gnu/store/k0v5qlk1gkl62d0wspsy9y6khrn5cq0c-qtmultimedia-6.3.1/lib/qt6/qml'
'/gnu/store/1228mp35skd88ijx799v5851paadv9wg-qtwebchannel-6.3.1/lib/qt6/qml'
'/gnu/store/iygnhxwydlwbs1hc9knjvam6im489zyl-qtwebengine-6.3.1/lib/qt6/qml'
Plugin paths:
'.'
FAIL! : qml_test::tst_PresenceIndicator::compile() "qrc:/src/app/commoncomponents": no such directory
Loc: [/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_PresenceIndicator.qml(25)]
QWARN : qml_test::UnknownTestFunc() dbus not connected
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() qt.core.qobject.connect: QObject::connect(PreviewEngine, MessagesAdapter): invalid nullptr parameter
QWARN : qml_test::UnknownTestFunc() Can't update current account info data for ""
QWARN : qml_test::tst_WizardView::compile()
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_WizardView.qml produced 1 error(s):
/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_WizardView.qml:27,1: "qrc:/src/app/wizardview": no such directory
Working directory: /tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build
Import paths:
'/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/build/tests'
'qrc:/qt-project.org/imports'
'/gnu/store/g0cpw37529bbz2f0zbbwmivpd4igp4w6-qt5compat-6.3.1/lib/qt6/qml'
'/gnu/store/8nlck8a9s88krl7m8a0d36yf3j2b7mv4-qtdeclarative-6.3.1/lib/qt6/qml'
'/gnu/store/k0v5qlk1gkl62d0wspsy9y6khrn5cq0c-qtmultimedia-6.3.1/lib/qt6/qml'
'/gnu/store/1228mp35skd88ijx799v5851paadv9wg-qtwebchannel-6.3.1/lib/qt6/qml'
'/gnu/store/iygnhxwydlwbs1hc9knjvam6im489zyl-qtwebengine-6.3.1/lib/qt6/qml'
Plugin paths:
'.'
FAIL! : qml_test::tst_WizardView::compile() "qrc:/src/app/wizardview": no such directory
Loc: [/tmp/guix-build-jami-20221031.1308.130cc26.drv-0/jami-project/client-qt/tests/qml/src/tst_WizardView.qml(27)]
Totals: 3 passed, 4 failed, 0 skipped, 0 blacklisted, 16ms
********* Finished testing of qml_test *********
Destroying connectivity monitor
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "tests/qml_tests" arguments: ("-mutejamid" "-input" "../client-qt/tests/qml") exit-status: 4 term-signal: #f stop-signal: #f>
phase `check' failed after 22.1 seconds
command "tests/qml_tests" "-mutejamid" "-input" "../client-qt/tests/qml" failed with status 4
```
Ideas?
Thanks!https://git.jami.net/savoirfairelinux/jami-client-qt/-/issues/1117D-Bus connection not reestablished by client when restarting jami-daemon2023-12-23T14:03:09ZAndreas TraczykD-Bus connection not reestablished by client when restarting jami-daemonWe should be able to restart the jami-daemon process while the client is running, and the client should:
1. suspend functionality during the daemon's absence
2. resume functionality once the daemon becomes available againWe should be able to restart the jami-daemon process while the client is running, and the client should:
1. suspend functionality during the daemon's absence
2. resume functionality once the daemon becomes available againAndreas TraczykAndreas Traczykhttps://git.jami.net/savoirfairelinux/jami-client-android/-/issues/1497Too much space between buttons in group call message2023-12-22T20:32:14ZEmma FalkiewitzToo much space between buttons in group call message**This bug happens on new chatview development branch.**
While we wait for the new group call message to be implemented.
![image](/uploads/c4a8bfbedfde134136a88ddd8094df63/image.png)
![image](/uploads/fc3f3b1c00047a583396e93e2f8cbc71/...**This bug happens on new chatview development branch.**
While we wait for the new group call message to be implemented.
![image](/uploads/c4a8bfbedfde134136a88ddd8094df63/image.png)
![image](/uploads/fc3f3b1c00047a583396e93e2f8cbc71/image.png)